Unable to boot, unable to access internal harddrive when booting from SD card, unable to edit drive partitions

Dearest Lubuntu friends,

I experienced a boot issue today. I am using 22.04.3 LTS (Jammy Jellyfish) on a ~2017 Dell XPS intel Core i7 vPro 7th Gen laptop. The notice was fast but it appeared to mention kernel panic not syncing.

The Dell Bios tool took over and identified errors and wanted me to enter a recovery mode. As I did not want to revert to Windows, I got a hold of a 22.04.3 LTS (Jammy Jellyfish) SD card instance and was able to boot the computer selecting “Try Lubuntu.” My plan was to get into the hard drive that way to try and fix the problem.

However, when I try to access the drive “LITEONIT LGT-256M6G,” I receive error messages “Can’t mount file” “The path is not mounted.”

Listing partitions shows sda without a mountpoint:

lubuntu@lubuntu:~$ lsblk -o NAME,FSTYPE,LABEL,SIZE,MOUNTPOINT
NAME FSTYPE LABEL SIZE MOUNTPOINT
loop0 squashfs 2.4G /rofs
loop1 squashfs 163.3M /snap/firefox/1635
loop2 squashfs 91.7M /snap/gtk-common-themes/1535
loop3 squashfs 62M /snap/core20/1587
loop4 squashfs 400.8M /snap/gnome-3-38-2004/112
loop5 squashfs 47M /snap/snapd/16292
loop6 squashfs 4K /snap/bare/5
sda 238.5G
sdb iso9660 Lubuntu 22.04.1 LTS amd64 29G
├─sdb1 iso9660 Lubuntu 22.04.1 LTS amd64 2.5G /cdrom
├─sdb2 vfat ESP 4.1M
├─sdb3 300K
└─sdb4 ext4 writable 26.5G /var/crash
sdc 0B
zram0 7.7G [SWAP]

Following instructions to try and mount the drive manually produces the following:

lubuntu@lubuntu:~$ sudo mkdir /mnt/drive256
lubuntu@lubuntu:~$ sudo mount -t auto -v /dev/sda /mnt/drive256
NTFS signature is missing.
Failed to mount ‘/dev/sda’: Invalid argument
The device ‘/dev/sda’ doesn’t seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
NTFS signature is missing.
Failed to mount ‘/dev/sda’: Invalid argument
The device ‘/dev/sda’ doesn’t seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

Specifying a partition number produces these results:

lubuntu@lubuntu:~$ sudo mount -t auto -v /dev/sda1 /mnt/drive256
mount: /mnt/drive256: special device /dev/sda1 does not exist.
lubuntu@lubuntu:~$ sudo mount -t auto -v /dev/sda2 /mnt/drive256
mount: /mnt/drive256: special device /dev/sda2 does not exist.
lubuntu@lubuntu:~$ sudo mount -t auto -v /dev/sda3 /mnt/drive256
mount: /mnt/drive256: special device /dev/sda3 does not exist.
lubuntu@lubuntu:~$ sudo mount -t auto -v /dev/sda4 /mnt/drive256
mount: /mnt/drive256: special device /dev/sda4 does not exist.

Here is a screenshot of KDE Partition manager for sda:

So, I suppose my question is either how can I actually access this drive? And barring that, how can I get the data off it?

I would of course be bummed if the drive cannot be restored, but it would be less than ideal to not be able to get the data on it. Some things are backed up, but of course not everything!

Thank y’all so much in advance for your help!

All the best,
thankyouguitar

I ran boot-repair at some point and it was suggested that I post this output to the forum to ask for help:

boot-repair-4ppa2056 [20231018_2011]

============================== Boot Info Summary ===============================

=> Windows Vista is installed in the MBR of /dev/sda.

sda1: __________________________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 

sda2: __________________________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 

sda3: __________________________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 

sda4: __________________________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 

sdb: ___________________________________________________________________________

File system:       iso9660
Boot sector type:  Grub2 (v1.99-2.00)
Boot sector info:  Grub2 (v1.99-2.00) is installed in the boot sector of 
                   sdb and looks at sector 0 of the same hard drive for 
                   core.img, but core.img can not be found at this 
                   location.
Mounting failed:   mount: /mnt/BootInfo/FD/sdb: /dev/sdb already mounted or mount point busy.

================================ 0 OS detected =================================

================================ Host/Hardware =================================

CPU architecture: 64-bit
Video: HD Graphics 615 from Intel Corporation
Live-session OS is Ubuntu 64-bit (Ubuntu 22.04.1 LTS, jammy, x86_64)

===================================== UEFI =====================================

BIOS/UEFI firmware: 2.6.2(2.6) from Dell Inc.
The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
SecureBoot disabled (confirmed by mokutil).
BootCurrent: 0002
Timeout: 2 seconds
BootOrder: 0000,0001,0005,0004,0006,0003,0002
Boot0000* LITEONIT LGT-256M6G BBS(HD,LITEONIT LGT-256M6G,0x0)…
Boot0001* Realtek PXE B39 D00 BBS(128,Realtek PXE B39 D00,0x0)…
Boot0002* UEFI USB Device PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/USB(2,0)/USB(1,0)/Unit(0)/HD(2,GPT,d2cc4593-30fe-4f63-99cd-a043799af9b2,0x4ff8cc,0x2130)N…YM…R,Y.
Boot0003* Windows Boot Manager HD(1,GPT,6a5cbc52-9e9f-4c18-84b0-f4f3ee547152,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS…x…B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}…5……
Boot0004* UEFI USB NIC (IPV4) PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/USB(2,0)/USB(2,0)/MAC(a0cec89d56e9,0)/IPv4(0.0.0.00.0.0.0,0,0)N…YM…R,Y.
Boot0005* ubuntu HD(1,GPT,6a5cbc52-9e9f-4c18-84b0-f4f3ee547152,0x800,0x32000)/File(\EFI\ubuntu\shimx64.efi)
Boot0006* UEFI USB NIC (IPV6) PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)/USB(2,0)/USB(2,0)/MAC(a0cec89d56e9,0)/IPv6([::]:<->[::]:,0,0)N…YM…R,Y.

============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________

Partitions info (1/3): _________________________________________________________

Partitions info (2/3): _________________________________________________________

Partitions info (3/3): _________________________________________________________

fdisk -l (filtered): ___________________________________________________________

Disk sda: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk identifier: 0xd3788d00
Boot Start End Sectors Size Id Type
sda1 2625390770 3807080241 1181689472 563.5G 32 unknown
sda2 4136475296 6497827710 2361352415 1.1T ec unknown
sda3 561899388 4320574757 3758675370 1.8T 30 unknown
sda4 4117237596 5849152122 1731914527 825.8G 19 unknown
Partition table entries are not in disk order.
Disk sdb: 28.97 GiB, 31104958464 bytes, 60751872 sectors
Disk identifier: D2CC4593-30FE-4F63-99CF-A043799AF9B2
Start End Sectors Size Type
sdb1 64 5241035 5240972 2.5G Microsoft basic data
sdb2 5241036 5249531 8496 4.1M EFI System
sdb3 5249532 5250131 600 300K Microsoft basic data
sdb4 5251072 60751808 55500737 26.5G Linux filesystem
Disk zram0: 7.75 GiB, 8318705664 bytes, 2030934 sectors

parted -lm (filtered): _________________________________________________________

sda:256GB:scsi:512:512:unknown:ATA LITEONIT LGT-256:;
sdb:31.1GB:scsi:512:512:gpt:Generic MassStorageClass:;
1:32.8kB:2683MB:2683MB::ISO9660:hidden, msftdata;
2:2683MB:2688MB:4350kB::Appended2:boot, esp;
3:2688MB:2688MB:307kB::Gap1:hidden, msftdata;
4:2689MB:31.1GB:28.4GB:ext4::;

blkid (filtered): ______________________________________________________________

NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda
sdb iso9660 2022-08-09-12-03-48-00 Lubuntu 22.04.1 LTS amd64
├─sdb1 iso9660 2022-08-09-12-03-48-00 d2cc4593-30fe-4f63-99ce-a043799af9b2 Lubuntu 22.04.1 LTS amd64 ISO9660
├─sdb2 vfat 8D6C-A9F8 d2cc4593-30fe-4f63-99cd-a043799af9b2 ESP Appended2
├─sdb3 d2cc4593-30fe-4f63-99cc-a043799af9b2 Gap1
└─sdb4 ext4 424260e0-fa85-4319-8849-712ff3f794dd 9533f9e3-d418-0d47-b86b-b86e50f2c9fa writable
sdc

Mount points (filtered): _______________________________________________________

                                                          Avail Use% Mounted on

/dev/disk/by-label/writable[/install-logs-2023-10-18.0/crash] 24.5G 0% /var/crash
/dev/disk/by-label/writable[/install-logs-2023-10-18.0/log] 24.5G 0% /var/log
/dev/sdb1 0 100% /cdrom

Mount options (filtered): ______________________________________________________

======================== Unknown MBRs/Boot Sectors/etc =========================

Unknown BootLoader on sda1

Unknown BootLoader on sda2

Unknown BootLoader on sda3

Unknown BootLoader on sda4

Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would not act on the boot.

From those unrealistic sizes and positions reported from sda,
it looks like your sda MBR is corrupt - in particular, the partition table.

Dare I ask did you backup your MBR at any time in the past ?
(that’s one of the must do’s when using MBR. Utilities like e.g Clonezilla will do this automatically for you when backing up a disk). I’m not sure about Windows recovery mode though, but hey,… what have you got to lose?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.