Partition table corrupted after battery died

FredBoucher · 2023-01-24 06:12:57

Hi,

My laptop had no power left so it shut down (I normally power it off before this happens, but I wasn't careful enough this time).

After charging it and attempting to reboot into Arch, I was immediately thrown into the emergency bash with the following error :

"
waiting 10 seconds for device /dev/disk/by-uuid/<uuid>
ERROR : device 'UUID=<uuid>' not found. Skipping fsck.
"

Note that I am triple-booting with Windows, Ubuntu, and Arch using Refind as a boot manager, and of course, none of the OSes boot considering the nature of the issue.

It's pretty obvious that it's a partition table issue and that was confirmed by the Dell diagnostic tool when it ran automatically on reboot.

I've attempted to use boot-repair on a live usb to no avail (it wouldn't even run).

I've attempted to run blkid in emergency mode but it returns absolutely nothing.

I am lost as to what to do next ; any advice ?

Thank you very much.

Last edited by FredBoucher (2023-01-24 06:18:06)

seth · 2023-01-24 08:36:01

Boot a live system (install iso or try grml) and post the output of "lsblk -f"
You can also assert the sanity of the possibly available FS (mount them and look around) and in doubt fix the UUID

nb.

I am triple-booting with Windows, Ubuntu, and Arch

3rd link below - it's not strictly a windows thing: you cannot reasonably run one system while another one is in hibernation (the windows specific thing is that hibernation is default and disguised as "look how fast windows boots now")

FredBoucher · 2023-01-24 15:10:09

Thank you for your reply.

I have run said command on my live system and it returns nothing interesting ; just the snap mount points and the usb itself : https://pastebin.com/SGN8vsRF

Do you have any other ideas ?

seth · 2023-01-24 15:21:11

That's not a partition table-problem.
Check the journal of the live system for sda1/ata related errors.

Does the drive still show up in the BIOS/UEFI?
Remove the battery from the notebook, wait, wait longer and put it back: does the drive show up again?

Diassemble the notebook and make sure the disk is properly seated and attached.

FredBoucher · 2023-01-25 03:46:04

Yeah, after further review, it's not a partition table issue.

I believe the ssd is fried even though it does show up in UEFI.

I've attempted to disconnect and reconnect it, and I've attempted to remove the battery and plug it back a few hours later, to no avail.

No sda/ata related errors in the journal.

topcat01 · 2023-01-25 04:02:02

What brand is the disk? Also, could you try it in an external enclosure on another (preferably Linux) machine?

Edit: Could be the same machine running off the iso, with the SSD in an external enclosure.

Edit 2: Also, can you carefully check the firmware setup to see if any settings changed due to the outage?

Last edited by topcat01 (2023-01-25 04:08:54)

seth · 2023-01-25 08:31:38

No sda/ata related errors in the journal.

Please post the journal

sudo journalctl -b | curl -F 'file=@-' 0x0.st

FredBoucher · 2023-01-25 22:03:23

I bought a new SSD and nothing changed ; the new disk is not detected either. Here is the output of lsblk -f with the new disk : https://pastebin.com/3ig6n439

Obviously, this leads me to think that the issue is not the disk itself.

Result of the journalctl -b command : http://0x0.st/oFNR.txt

The disk is an nvme m.2 Samsung 970.

Last edited by FredBoucher (2023-01-25 22:03:50)

topcat01 · 2023-01-25 22:45:40

Jan 25 20:37:41 ubuntu kernel: ahci 0000:00:17.0: Found 1 remapped NVMe devices.
Jan 25 20:37:41 ubuntu kernel: ahci 0000:00:17.0: Switch your BIOS from RAID to AHCI mode to use them.

Your firmware has reset to RST/RAID mode after the outage. This is why I was suggesting re-checking the settings above. This is good news, since probably the drives are fine.

Last edited by topcat01 (2023-01-25 22:46:42)

FredBoucher · 2023-01-26 02:05:10

... that did fix it.

I feel incredibly stupid now, but thank you very much for the help.

Arch Linux

#1 2023-01-24 06:12:57

Partition table corrupted after battery died

#2 2023-01-24 08:36:01

Re: Partition table corrupted after battery died

#3 2023-01-24 15:10:09

Re: Partition table corrupted after battery died

#4 2023-01-24 15:21:11

Re: Partition table corrupted after battery died

#5 2023-01-25 03:46:04

Re: Partition table corrupted after battery died

#6 2023-01-25 04:02:02

Re: Partition table corrupted after battery died

#7 2023-01-25 08:31:38

Re: Partition table corrupted after battery died

#8 2023-01-25 22:03:23

Re: Partition table corrupted after battery died

#9 2023-01-25 22:45:40

Re: Partition table corrupted after battery died

#10 2023-01-26 02:05:10

Re: Partition table corrupted after battery died

Board footer