Hi,
I’ve installed fedora 39 on my HP Spectre x360 notebook next to Windows 11 a few days ago with the fedora media writer.
It was running ok (no camera or fingerprint, but that’s fine…), but one big problem that I encountered, was that every time I put it to sleep (e.g. closed the lid), it would completely crash with error messages and symptoms similar to the one in this thread: https://gitlab.freedesktop.org/drm/i…0#note_1813550
i915 [drm] ERROR Failed to write source OUI
AUX B/DDI B/PHY B: timeout
As the comments in that discussion seemed to suggest a BIOS update might fix this, I went back on Windows and installed the newest BIOS I could find for my laptop (BIOS Version/Date Insyde F.23, 07/07/2023). After the installation I got greeted with a nice blue screen saying the volume is corrupt(failed to load image: Volume Corrupt\ start_image rturned Volume Corrupt.
I already tried booting from a live USB Stick with boot-repair (sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt update && sudo apt install -y boot-repair && boot-repair), but it didn’t seem to find anything: Ubuntu Pastebin
I did manage to mount the fedora partition and look at all the files in my home partition, so the data is still there. Tried to chroot into that partition and reinstall grub2 too. I’d be okay with losing my data on the linux partition, I just played around a little, but I want to learn. What other measures could I try to repair my volume (if it is even corrupt)? I did fsck and btrfs-check, btrfs-check output is here:
sudo btrfs check /dev/nvme0n1p6
Opening filesystem to check...
Checking filesystem on /dev/nvme0n1p6
UUID: 94a030ad-4509-4d11-b0e9-4892f1e71447
[1/7] checking root items
[2/7] checking extents
[3/7] checking free space tree
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
found 24377835520 bytes used, no error found
total csum bytes: 22218280
total tree bytes: 618086400
total fs tree bytes: 555286528
total extent tree bytes: 35012608
btree space waste bytes: 104322230
file data blocks allocated: 37300998144
referenced 38863679488
and lsblk:
ubuntu@ubuntu:~$ lsblk -o NAME,FSTYPE,LABEL,SIZE,MOUNTPOINT
NAME FSTYPE LABEL SIZE MOUNTPOINT
loop0 squashfs 3G /rofs
loop1 squashfs 4K /snap/bare/5
loop2 squashfs 63.4M /snap/core20/1974
loop3 squashfs 73.9M /snap/core22/858
loop4 squashfs 237.2M /snap/firefox/2987
loop5 squashfs 349.7M /snap/gnome-3-38-2004/143
loop6 squashfs 485.5M /snap/gnome-42-2204/120
loop7 squashfs 91.7M /snap/gtk-common-themes/1535
loop8 squashfs 452K /snap/snapd-desktop-integration/83
loop9 squashfs 12.3M /snap/snap-store/959
loop10 squashfs 53.3M /snap/snapd/19457
sda 29.3G
└─sda1 vfat UBUNTU 22_0 29.2G /cdrom
nvme0n1 953.9G
├─nvme0n1p1 vfat SYSTEM 260M
├─nvme0n1p2 16M
├─nvme0n1p3 ntfs Windows 779.9G
├─nvme0n1p4 ntfs 810M
├─nvme0n1p5 ext4 1G
└─nvme0n1p6 btrfs fedora 171.9G /home/ubuntu/fed
After messing around a little bit with grub, chroot, and so on, the error message on booting into fedora changed from Volume corrupt to Invalid image Failed to read header: Unsupported Failed to load image: Unsupported start_image() returned Unsupported
not sure if that is any better…
As I said, I don’t care too much about saving the data and I could just wipe the partition, but i want to understand for the next time i run into a similar problem
Thanks very much!
Drukob