Ubuntu

Latest Feisty Upgrade wrote wrong head cylinders to 16

Bug #92318 reported by AkumA
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Brian Murray

Bug Description

I've updated about 1 hour ago Feisty. When i came back to Gnome the pc freezed at any open window.
The same with some windows in KDE session (Using UBUNTU i've also decided to install ONLY kde-base).

After rebooting few times i've watched boot with ALT+F1 and i've seen "File system not clean".

cfdisk.ext3 has given me strange advise, but i've rebooted and dediced to run testdisk.

It suggested me to change head cylinders to 255 because it's 16.
My partition was not ok.
I've changed that parameter, i've rebooted and now looks fine and all seem to work.

ProblemType: Bug
Architecture: i386
Date: Wed Mar 14 20:18:51 2007
DistroRelease: Ubuntu 7.04
Uname: Linux magrebianware 2.6.20-10-generic #2 SMP Mon Mar 12 00:02:49 UTC 2007 i686 GNU/Linux

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. How did you go about updating to Feisty? Was this a fresh install or did you use update-manager or . . . ? Thanks in advance.

Revision history for this message
AkumA (zio-protestante) wrote :

It's an edgy updated.
I have updated to Feisty with Feisty Herd 4.
I've done update-manager -d because the first time i've tried with a CD i've got back an error and i couldn't try with cd-rom anymore (I've tried with apt-cdrom and others but nothing).

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.