Closing per the previous comment. Thanks.
** Changed in: linux (Ubuntu)
Status: Incomplete = Invalid
--
HDD rename after 09/12 update (incl. GCC and glibc) caused boot failure
https://bugs.launchpad.net/bugs/270118
You received this bug notification because you are a member of Ubuntu
It happened one dark and stormy night so far nothing has broken
after that day.
Please close this.
Regards
--
HDD rename after 09/12 update (incl. GCC and glibc) caused boot failure
https://bugs.launchpad.net/bugs/270118
You received this bug notification because you are a member of
Hi gobble,
This bug was reported a while ago and there hasn't been any activity in
it recently. We were wondering if this is still an issue? Can you try
with the latest development release of Ubuntu? ISO CD images are
available from http://cdimage.ubuntu.com/releases/ .
If it remains an issue,
** Changed in: linux (Ubuntu)
Sourcepackagename: None = linux
--
HDD rename after 09/12 update (incl. GCC and glibc) caused boot failure
https://bugs.launchpad.net/bugs/270118
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
PS: The /dev/sda3 you see here is from the Ubuntu 8.0.4 boot/install CD not the
installed one that got blown up yesterday.
Just so there is no confusion.
Cheers
--
HDD rename after 09/12 update (incl. GCC and glibc) caused boot failure
https://bugs.launchpad.net/bugs/270118
You received this
OK I rdumped the lost+found, and it seems all the files are in there -
some 36GB. Will work on recovery for each block/inode, lets not make
this the subject of the CR. The main focus of this CR should be
1. did an Ubuntu update result in reordering of disks?
2. Was the fsck a result of a
