The first time linux really let me down. A couple of months ago I installed Linux on a new Toshiba laptop, erasing all windows partitions. I was not an easy installation, I had to find out about EFI and change BIOS settings which took some time.
Now after months of working without any problem the system will not boot anymore. The normal boot screen comes up, but after some time it hangs after displaying these messages:
udevadm: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
Trying manual resume from /dev/disk/by-id/ata/-TOSHIBA_MQ01ABD100_93FWTDIRT-part2
udevadm: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
resume device /dev/disk/by-id/ata/-TOSHIBA_MQ01ABD100_93FWTDIRT-part2 not found (ignoring)
Trying manual resume from /dev/disk/by-id/ata/-TOSHIBA_MQ01ABD100_93FWTDIRT-part2
udevadm: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
resume device /dev/disk/by-id/ata/-TOSHIBA_MQ01ABD100_93FWTDIRT-part2 not found (ignoring)
Waiting for device /dev/root to appear: ….............. Could not find /dev/root
Want me to fall back to /dev/disk/by-id/ata/-TOSHIBA_MQ01ABD100_93FWTDIRT-part3? (Y/n)
I tried the rescue disk with some success - could start up and save vital data. However, during start op, amongst many other messages this one appeared:
partition 1 on /dev/sr does not appear … fatal!
I tried to re-install grub2-efi with Yast but that did not work, giving the message:
Path 'boot/grub2' is not readable by GRUB on boot. Installation is impossible
I conclude from this there's something wrong with the EFI boot partition (/dev/sda1). However mounting it, showed everything in place.
Unmounting and trying fsck does not indicate any errors. However when I mount it again and try fsck, it indicates that the 'Dirty bit' is set because the filesystem was not properly unmounted.
My questions:
- Has anyone seen this boot failure before and found a solution?
- Can I simply let fsck remove this dirty bit and hope it solves the problem (I'm a bit wary here - afraid to do further damage)
- I saw in in other thread a similar problem (e.g. mentioning failure to load libz.so.1 during boot) and it was mentioned that 'remake initrd' had solved the problem. But could not find any useful further reference to that. Does anyone know if this could be useful?
- or is this a really fatal problem?
Thanks for any helpful tips!
Now after months of working without any problem the system will not boot anymore. The normal boot screen comes up, but after some time it hangs after displaying these messages:
udevadm: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
Trying manual resume from /dev/disk/by-id/ata/-TOSHIBA_MQ01ABD100_93FWTDIRT-part2
udevadm: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
resume device /dev/disk/by-id/ata/-TOSHIBA_MQ01ABD100_93FWTDIRT-part2 not found (ignoring)
Trying manual resume from /dev/disk/by-id/ata/-TOSHIBA_MQ01ABD100_93FWTDIRT-part2
udevadm: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
resume device /dev/disk/by-id/ata/-TOSHIBA_MQ01ABD100_93FWTDIRT-part2 not found (ignoring)
Waiting for device /dev/root to appear: ….............. Could not find /dev/root
Want me to fall back to /dev/disk/by-id/ata/-TOSHIBA_MQ01ABD100_93FWTDIRT-part3? (Y/n)
I tried the rescue disk with some success - could start up and save vital data. However, during start op, amongst many other messages this one appeared:
partition 1 on /dev/sr does not appear … fatal!
I tried to re-install grub2-efi with Yast but that did not work, giving the message:
Path 'boot/grub2' is not readable by GRUB on boot. Installation is impossible
I conclude from this there's something wrong with the EFI boot partition (/dev/sda1). However mounting it, showed everything in place.
Unmounting and trying fsck does not indicate any errors. However when I mount it again and try fsck, it indicates that the 'Dirty bit' is set because the filesystem was not properly unmounted.
My questions:
- Has anyone seen this boot failure before and found a solution?
- Can I simply let fsck remove this dirty bit and hope it solves the problem (I'm a bit wary here - afraid to do further damage)
- I saw in in other thread a similar problem (e.g. mentioning failure to load libz.so.1 during boot) and it was mentioned that 'remake initrd' had solved the problem. But could not find any useful further reference to that. Does anyone know if this could be useful?
- or is this a really fatal problem?
Thanks for any helpful tips!