*** This bug is a duplicate of bug 436076 ***
https://bugs.launchpad.net/bugs/436076
I had this issue while upgrading to ext4.... so I added the FS features
and touched the /forcefsck.
I was able to get out of the trap... but it drove me insane...
1. enter GRUB and modify the root= parameter to something like /dev/hdx99 - it
has just to be invalid -> this brings you into busybox upon startup
2. in busybox, mount your partition where fsck lies in to somewhere, I used /tmp
3. just type the full path to fsck.ext4 - it will bail out, missing
libraries....
4. prefix the fsck with
LD_PRELOAD=<fullpathtomissinglibraryhere>:<anothermissinglibrary>:<andanother>
5. you will repear step 4 until all libraries are preloaded
6. if you have issues with your root partition, you will have to copy all the
stuff to the busybox, unmount, and execute from there
To the DEVs: PLEASE give a possibility to "init=/bin/sh"! It would have
saved me hours....
--
mountall loops indefinitely on fsck failure
https://bugs.launchpad.net/bugs/430713
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
