After successful installation and several successful boots, the home partition (/home) is getting corrupted beyond repair

Bug #120918 reported by Dan Gilliam on 2007-06-18
2
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Undecided
Unassigned

Bug Description

Laptop is a Toshiba M55; I've now twice had this same exact thing occur. I install successfully, it boots properly several times, and then after 4 or 5 successful boots, it all of a sudden comes up with a corrupted /home partition. fsck won't touch it, due to inability to access the partition, even when I use a rescue cd. It claims that the partition size is incorrectly reported from the mbr. I'm unable to provide more info from the system, as I wasn't able to ever get the thing all the way back up. On attempting to reinstall ubuntu, the entire mbr appears to have been corrupted, and I have to basically start from a fixmbr on the XP side (dual boot), THEN I can continue re-partitioning my disk. I've now tried this with bsd and several linux versions, and feisty is the only one doing it.

Paul Dufresne (paulduf) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better.
Frankly, I don't know much to which package associate this bug, so I choose the kernel of Feisty.

Are you still using it with Ubuntu, is so which version?
The kernel, to begin investigating would need the following:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies.

Paul Dufresne (paulduf) 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!

Changed in linux-source-2.6.20:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers