Hi there, after sudo zypper dup my system doesn’t boot anymore. It can’t find a fstab line about my usb drive.
Even blkid can’t find the drive. But a version earlier, 6.17.8-1 can! No problem. So I boot with that kernel now but how can I solve this problem for the 6.17.9-1 version?
Thx Nico
Can you provide more details of the error causing failure to boot i.e. press esc key to see boot messages? A picture of the error? Does boot process completely halt when using kernel 6.17.9-1?
I think you have the fstab line, but the kernel does not detect the drive, hence cannot mount it.
Comment out the line, unplug the drive, reboot into 6.17.9-1 kernel.
In a terminal window run `sudo dmesg -w (keeps it running in follow mode)
Next plug in the USB drive, and tell us what happened.
Look in the terminal to see if there are any new messages from dmesg
Knurpht, after comment out the line in fstab and reboot into 6.17.9-1 i got a black screen. After a while (I guess 1 min 30) i was able to use alt ctrl f1 and see that the blkid still didn’t find the drive. X not starting (maybe already running). And no new entry’s in dmesg. So, I think the kernel is lacking the usb driver?
Nico
Could be, no idea what is going on. I’d wait until a new kernel appears.
It seems you commented out the wrong entry in fstab then. Can you show your fstab?
If only the /home/nico/mnt/downloads directory is on the external USB, and this line is commented out, the system should start.
Except if the system needs the directory!
UUID=365b4bd6-d5be-44f6-bd9a-9e1f1f1a3690 / btrfs defaults 0 0
UUID=365b4bd6-d5be-44f6-bd9a-9e1f1f1a3690 /var btrfs subvol=/@/var 0 0
UUID=365b4bd6-d5be-44f6-bd9a-9e1f1f1a3690 /usr/local btrfs subvol=/@/usr/local 0 0
UUID=365b4bd6-d5be-44f6-bd9a-9e1f1f1a3690 /srv btrfs subvol=/@/srv 0 0
UUID=365b4bd6-d5be-44f6-bd9a-9e1f1f1a3690 /root btrfs subvol=/@/root 0 0
UUID=365b4bd6-d5be-44f6-bd9a-9e1f1f1a3690 /opt btrfs subvol=/@/opt 0 0
UUID=365b4bd6-d5be-44f6-bd9a-9e1f1f1a3690 /boot/grub2/x86_64-efi btrfs subvol=/@/boot/grub2/x86_64-efi 0 0
UUID=365b4bd6-d5be-44f6-bd9a-9e1f1f1a3690 /boot/grub2/i386-pc btrfs subvol=/@/boot/grub2/i386-pc 0 0
UUID=bbfbb972-7235-4752-b0a6-88d491802862 swap swap defaults 0 0
UUID=b466887c-d404-4f3b-bdaa-1f5076015517 /home btrfs defaults 0 0
UUID=2C0C-FE8E /boot/efi vfat utf8 0 2
UUID=24254a71-1454-485a-a84c-d0f84a560cbd /home/nico/mnt/Downloads ext4 defaults 0 0
UUID=f618a3c9-3b5e-4efb-913c-4d13b8d22fb9 /home/nico/mnt/Vbox ext4 defaults 0 0
UUID=7C9CA7349CA6E7BA /home/nico/mnt/Windows ntfs defaults 0 0
192.168.0.5:/var/www/html/sb /home/nico/nfs/sb nfs defaults 0 0
192.168.0.5:/var/gopher /home/nico/nfs/gopher nfs defaults 0 0
192.168.0.5:/share /home/nico/nfs/share nfs defaults 0 0
Make this one:
# UUID=24254a71-1454-485a-a84c-d0f84a560cbd /home/nico/mnt/Downloads ext4 defaults 0 0
Had ik gedaan.
Resultaat hetzelfde. Ik wacht wel een update ronde.
Nico
I get it. The rest can feed it to some translation program 
Sorry 
Nico
for translation: it is Dutch to English
I find out by compare the both lsmod list that uas.ko is missing in version 6.17.9-1 and the drive is an usb-2 drive… uas.ko.zst is missing in /usr/lib/modules/etc/etc/etc
Can I install from cli this module? How. Can i use the 6.17.8-1 module? How?
Nico
@Pitmaster It’s not /usr/lib/modules/6.17.9-1-default/kernel/drivers/usb/storage/uas.ko.zst
Should be using usb-storage…
It’s not there Malcolm
6.17.8-1 use usb-storage on uas and 6.17.9-1 use only usb-storage.
@Pitmaster then you have something wrong with your install…
ls -la /usr/lib/modules/6.17.9-1-default/kernel/drivers/usb/storage/uas.ko.zst
-rw-r--r-- 1 root root 24753 Nov 24 03:58 /usr/lib/modules/6.17.9-1-default/kernel/drivers/usb/storage/uas.ko.zst
lsmod | grep uas
uas 36864 0
usb_storage 90112 1 uas
scsi_mod 348160 9 scsi_dh_emc,sd_mod,scsi_dh_alua,usb_storage,uas,libata,sg,scsi_dh_rdac,sr_mod
usbcore 454656 15 pl2303,usbserial,rtl2832_sdr,xhci_hcd,ehci_pci,dvb_usb_v2,usbhid,btmtk,dvb_usb_rtl28xxu,usb_storage,ehci_hcd,btusb,xhci_pci,uas
scsi_common 16384 7 scsi_mod,sd_mod,usb_storage,uas,libata,sg,sr_mod
Clear! Thank you.
Next question: how to repair?
@Pitmaster Not really sure. Open a couple of terminals and in one run journalctl -f to follow the log. In the other run udevadm monitor and check the outputs when you plug/unplug the device for possible errors/warnings.
@Pitmaster run zypper dup to get to the 6.18.0 kernel and see if that helps.