Unbootable system after fsck failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
This may still be the same as bug 553374, though I thought that had been fixed and apparently it hasn't. The circumstances are not the same as in bug 563618; my hwclock seems to be fine.
On the laptop I upgraded from karmic to lucid, a failure during boot-time fsck again gave me a perpetual boot screen without any feedback and without any way out. (I know about the fsck error because pressing <esc> brought me to a text console that showed the output). I had to boot from a live CD again and run fsck manually.
So far I suspect the proprietary nVidia driver of causing the filesystem corruption; I don't recall the corruption happening while I was running without it. Another user with the same corruption problems in Karmic also had an nVidia card. If that is indeed the cause, a large class of users may find that Lucid spontaneously stops working after a while and from then on fails to boot without help from an expert and a live CD, no error message given. :(
summary: |
- Unbootable system after sck failure + Unbootable system after fsck failure |
tags: | added: karmic2lucid |
Hello
Is this problem present with the latest updated Lucid's or Maverick's packages?
Thanks in advance
Fabio