Partitioning Malfunction- Cant't boot into ubuntu partition
Hi,
I am running Ubuntu Dapper on a Toshiba Tecra A8. I had 4 partitions, in this order: Xp, swap, ubuntu, and a hidden partition that contained the initial xp install. I recently decided that it would be a good a idea to free up some space and to use as a universal data partition. I took off some space from my xp partition, and I deleted my swap partition. Now that I had only 3 partitions I would be able to create a 4th one. So with this newly unallocated space, I created an extended partition, and within this partition I recreated my swap partition. I also used the extended partition to create the data partition that I wanted. So now my new partition set up was: windows(sda1),extended(sda4), swap(sda5),data(sda6),ubuntu(sda3), and the hidden one.(sda2) I did all this partitioning with gparted , and after initially creating the unallocated space from the xp partition everything still booted up fine. I finished the job at another time, and I went back in with gparted, deleted swap, and then did everything as said. After doing this with gparted, I rebooted, and the ubuntu loading up sequence got stuck at mounting root fs. I wanted to see what was wrong so I booted up with the recovery mode, and this is what I got: Code:
[17179572.632000] ide0:I/O resource 0x1f0-0x1f7 not free |
Because it used to be sda4, now it's sda3.
Reboot, and when the grub menu comes up, highlight your selection, hit <e> to edit the selection, the <e> on the kernel line. Change sda4 to sda3, and hit <Enter> to save the change. Then <b> to boot it. This is a "one-time only" change - if it works, update menu.lst to match. Your fstab will be wrong as well - unless you used UUID. |
Hey it's me again,
My Ubuntu partition was never labeled as sda4. I am pretty sure it has always been sda3. Here's my menu.lst file (It is unchanged since before I wasn't able to boot into ubuntu): Code:
title Ubuntu, kernel 2.6.15-28-386 |
Post your fstab just for giggles.
|
Here's my fstab:
Code:
# /etc/fstab: static file system information. |
I hate to do this but...Bump...Please Help. If I didn't give adequate information, please tell me.
|
I think we will also need to see the output of fdisk -l
How are you getting things like fstab--eg are you using a live CD? |
Okay Now I am confused. Here's the output from fdisk -l:
Code:
[/home/dsl]# fdisk -l |
My impression is that you are booting into Ubuntu OK, but the error comes when it attempts to mount sda4.
But WAIT!!! Your fstab entries show sdXX, and fdisk shows hdXX What is the drive? IDE/PATA? SATA? |
Right, that is why I was so confused from the fdisk output, but I don't think that is the problem. I believe that damn small linux has a driver problem or something similar, and that's why the drives were named as PATA drives. My drive is a fujitsu MHV2080BH PL, and it is definitely SATA. In gparted the drives are labeled as SDX and just to make sure, I booted up with my Dapper live-cd and here's the fdisk -l output:
Code:
ubuntu@ubuntu:~$ sudo fdisk -l |
You did not change the fstab entry for your new swap partition i.e. from sda4 to sda5. The OS is dying because it can not read data saved to the old swap partition. Did you also format your new swap partition using mkswap?
You might need to add resume=/dev/hda5 as a kernel option in grub. |
Code:
sda1 < sda5 sda6 > sda3 sda2 EDIT: someone beat me to it! (1 min) |
Well the fstab that I posted earlier is a dated one, and I already updated it to mirror my new drive structure. However, Michaelk is right, and the problem is with the new swap drive. I added resume=/dev/sda5 to the boot config, on the fly, and it finally got past mounting root fs. Then a new problem came up, and I realized that I had earlier renamed everything in the fstab to HDX, thinking that was problem. Since I now know that dsl was misreading the drive, I immediately changed my fstab back to SDX, and ubuntu booted up properly. The resume=/dev/sda5 addition seems temporary and sort of like a fix. How do I make everything right so it is as if nothing went wrong.
Daws, I understand that my drive configuration is not pretty, but what are the alternatives. Is it bad because it is not in order, or because I had to use an extended partition. Thanks again guys, Hal |
Good catch about the resume michaelk. In a normal (non sw-suspend) system swap is irrelevant to startup - it'll just fail to "mount", and moan about it.
You should only need the resume keyword once I'd imagine - once swap comes up, it should be found o.k. after that. As for your partition layout, don't worry about it, it'll be fine. |
I guess that clears everything up for me. My new data partition is working perfectly. Just wanted to tell everybody thanks for the feedback.
|
All times are GMT -5. The time now is 10:19 AM. |