|
Home > Archive > Linux Debian support > November 2007 > / partition vanishes?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
/ partition vanishes?
|
|
| Noozer 2007-10-22, 1:14 am |
| I've installed Debian lenny on my machine. The install is less than 12 hours
old. I'm not using etch as it does not handle the IDE/Sata controllers on my
Asus P4C800E Dlx mainboard properly.
For some reason, the system has suddenly started complaining that /dev/sdc2
is missing when the kernel starts.
/hdc is the boot drive. /hdc1 holds /boot and /hdc2 holds / .
The install was basic, I did not select any of the software groups presented
to me during the installation. There is a small install glitch where the
ICH5 and Promise SATA controllers end up reversed between the installation
process and the resulting system. Easy enough to fix in grubs menu.lst file
(change hd3,0 ot hd0,0).
I've been able to install the packages I need using aptitude: screen, less,
samba, openssh, vsftpd, webmin, etc... I've successfully shut the PC down
and restarted, and rebooted a number of times without an issue.
At this point the system complains that /dev/sdc2 (my / partition) is not
available. I can boot from the install CD and mount all my partitions
successfully, including /dev/sdc2, so the partitions are there.
- The PC starts, BIOS detects all the drives as expected.
- The grub menu appears and after a few seconds begins the process of
loading the kernel, etc.
- The screen clears and the message "Loading, please wait..." appears.
- The machine just sits there for approximately 5 minutes
- Finally I get the following on my screen:
ALERT! /dev/sdc2 does not exist. Dropping to a shell.
Check your root = boot argument (cat /proc/cmdline)
Check for missing modules (cat /proc/modules), or device files (ls /dev)
- Then Busybox starts and I get the following message: /bin/sh: can't
access a tty; job control turned off
- Finally, I'm left sitting at a "(initramfs) " prompt
The /dev directory does not have a sdc2 file. The cmdline and modules files
seem fine.
I'm stumped at this point. I was modifying SSH and Samba config files before
rebooting the machine. I can't think of anything that I would have done to
break the system.
Debian installed so smoothly on my laptop, I can't believe the issues I'm
having getting it onto my desktop PC.
How do I get my / partition back?
| |
| sk8r-365 2007-10-22, 1:14 am |
| Horton heard a Who named Noozer saying:
> I've installed Debian lenny on my machine. The install is less than 12 hours
> old. I'm not using etch as it does not handle the IDE/Sata controllers on my
> Asus P4C800E Dlx mainboard properly.
>
> For some reason, the system has suddenly started complaining that /dev/sdc2
> is missing when the kernel starts.
>
> /hdc is the boot drive. /hdc1 holds /boot and /hdc2 holds / .
>
> The install was basic, I did not select any of the software groups presented
> to me during the installation. There is a small install glitch where the
> ICH5 and Promise SATA controllers end up reversed between the installation
> process and the resulting system. Easy enough to fix in grubs menu.lst file
> (change hd3,0 ot hd0,0).
<snip>
>
> How do I get my / partition back?
Post your fstab or check that eash mount point and option is correct.
--
sk8r-365
The U.S. Congress enjoys damaging "big business"
but are themselves building big government!
| |
| thunder 2007-10-22, 1:14 am |
| On Mon, 22 Oct 2007 03:39:03 +0000, Noozer wrote:
> I've installed Debian lenny on my machine. The install is less than 12
> hours old. I'm not using etch as it does not handle the IDE/Sata
> controllers on my Asus P4C800E Dlx mainboard properly.
>
> For some reason, the system has suddenly started complaining that
> /dev/sdc2 is missing when the kernel starts.
>
> /hdc is the boot drive. /hdc1 holds /boot and /hdc2 holds / .
I'm a little confused. If it's a SATA drive shouldn't the above be sdc, not hdc?
> The install was basic, I did not select any of the software groups
> presented to me during the installation. There is a small install glitch
> where the ICH5 and Promise SATA controllers end up reversed between the
> installation process and the resulting system. Easy enough to fix in
> grubs menu.lst file (change hd3,0 ot hd0,0).
In your menu.lst file, what does the kernel line say? Something isn't adding up. (hd0,0) would
be sda, not sdc, no?
title Debian
root (hd0,0)
kernel /boot/vmlinuz* root=/dev/sda2 ro single
> I've been able to install the packages I need using aptitude: screen,
> less, samba, openssh, vsftpd, webmin, etc... I've successfully shut the
> PC down and restarted, and rebooted a number of times without an issue.
>
> At this point the system complains that /dev/sdc2 (my / partition) is
> not available. I can boot from the install CD and mount all my
> partitions successfully, including /dev/sdc2, so the partitions are
> there.
>
> - The PC starts, BIOS detects all the drives as expected. - The grub
> menu appears and after a few seconds begins the process of loading the
> kernel, etc.
> - The screen clears and the message "Loading, please wait..." appears. -
> The machine just sits there for approximately 5 minutes - Finally I get
> the following on my screen:
>
> ALERT! /dev/sdc2 does not exist. Dropping to a shell.
> Check your root = boot argument (cat /proc/cmdline)
> Check for missing modules (cat /proc/modules), or device files (ls
> /dev)
>
> - Then Busybox starts and I get the following message: /bin/sh: can't
> access a tty; job control turned off
> - Finally, I'm left sitting at a "(initramfs) " prompt
>
> The /dev directory does not have a sdc2 file. The cmdline and modules
> files seem fine.
>
> I'm stumped at this point. I was modifying SSH and Samba config files
> before rebooting the machine. I can't think of anything that I would
> have done to break the system.
>
> Debian installed so smoothly on my laptop, I can't believe the issues
> I'm having getting it onto my desktop PC.
>
> How do I get my / partition back?
| |
| Noozer 2007-10-22, 1:14 am |
|
"thunder" <thunder@TAKEOUTgti.net> wrote in message
news:pan.2007.10.22.04.13.19@TAKEOUTgti.net...
> On Mon, 22 Oct 2007 03:39:03 +0000, Noozer wrote:
>
>
> I'm a little confused. If it's a SATA drive shouldn't the above be sdc,
> not hdc?
Yes... is /sdc and not /hdc.
>
> In your menu.lst file, what does the kernel line say? Something isn't
> adding up. (hd0,0) would
> be sda, not sdc, no?
>
> title Debian
> root (hd0,0)
> kernel /boot/vmlinuz* root=/dev/sda2 ro single
Similar to this:
title Debian
root (hd0,0)
kernel /boot/vmlinuz* root=/dev/sdc2 ro single
When I boot from the installation CD, the PC sees /dev/sdc as the third
drive in the system. When I boot from the hard drive, /dev/sdc ends up being
the first drive in the system.
*sigh*
I found out what causes the problem... The only PATA hard disk in the
system. I finally gave up on the PC. I pulled the PATA drive out of the
system to put into another machine and now the Debian machine starts up fine
again! Reinstall the PATA drive and it doesn't boot normally.
This PATA drive has been in this Linux box since the install. No idea why it
suddenly is causing issues. I guess it could be just too many drives in the
system messing up the PSU.
| |
| thunder 2007-10-22, 1:14 am |
| On Mon, 22 Oct 2007 05:13:08 +0000, Noozer wrote:
>
> Similar to this:
> title Debian
> root (hd0,0)
> kernel /boot/vmlinuz* root=/dev/sdc2 ro single
Look at the above line. (hd0,0) is the first drive, but you are telling grub that the root partition
is on the third drive. Since the grub menu is coming up, (hd0,0) is correct. Try changing
root=/dev/sdc2 to root=/dev/sda2.
> When I boot from the installation CD, the PC sees /dev/sdc as the third
> drive in the system. When I boot from the hard drive, /dev/sdc ends up
> being the first drive in the system.
| |
| Noozer 2007-10-22, 7:14 am |
|
"thunder" <thunder@TAKEOUTgti.net> wrote in message
news:pan.2007.10.22.05.36.07@TAKEOUTgti.net...
> On Mon, 22 Oct 2007 05:13:08 +0000, Noozer wrote:
>
>
>
> Look at the above line. (hd0,0) is the first drive, but you are telling
> grub that the root partition
> is on the third drive. Since the grub menu is coming up, (hd0,0) is
> correct. Try changing
> root=/dev/sdc2 to root=/dev/sda2.
I agree with you 100%, but it doesn't boot if I specify (hd3,0) and sdc2. It
also doesn't boot if I specify (hd0,0) and sda2.
It works fine with (hd0,0) and root on /dev/sdc2.
I think it's all related to the bug being tracked here (and I'm sure
elsewhere as well):
https://bugs.launchpad.net/ubuntu/+.../grub/+bug/8497
| |
| thunder 2007-10-22, 7:14 am |
| On Mon, 22 Oct 2007 06:18:27 +0000, Noozer wrote:
> I think it's all related to the bug being tracked here (and I'm sure
> elsewhere as well):
>
> https://bugs.launchpad.net/ubuntu/+.../grub/+bug/8497
Ouch! I'm sure that sucker has led to many hours of frustration. :-(
| |
| Hadron 2007-10-22, 7:14 am |
| sk8r-365 <sk8r-365@sk8r.debian.etch.invalid.org> writes:
> Horton heard a Who named Noozer saying:
> <snip>
>
>
> Post your fstab or check that eash mount point and option is correct.
I had the same.
You need to edit the boot line in the grub config file.
--
You can get *anywhere* in ten minutes if you drive fast enough.
| |
| Jim Beard 2007-10-24, 7:14 pm |
| Noozer wrote:
> For some reason, the system has suddenly started complaining that /dev/sdc2
> is missing when the kernel starts.
>
> /hdc is the boot drive. /hdc1 holds /boot and /hdc2 holds / .
So which is your _real_ boot drive? /dev/sdc or /dev/hdc?
If /dev/hdc, reset your boot settings to boot from that. Then
the OS will not care if /dev/sdc exists or not.
Cheers!
jim b.
--
UNIX is not user-unfriendly; it merely
expects users to be computer-friendly.
| |
| Noozer 2007-10-26, 7:16 am |
|
"Noozer" <dont.spam@me.here> wrote in message
news:rXUSi.108016$1y4.46865@pd7urf2no...
> I've installed Debian lenny on my machine. The install is less than 12
> hours old. I'm not using etch as it does not handle the IDE/Sata
> controllers on my Asus P4C800E Dlx mainboard properly.
....
> At this point the system complains that /dev/sdc2 (my / partition) is not
> available. I can boot from the install CD and mount all my partitions
> successfully, including /dev/sdc2, so the partitions are there.
>
> - The PC starts, BIOS detects all the drives as expected.
> - The grub menu appears and after a few seconds begins the process of
> loading the kernel, etc.
> - The screen clears and the message "Loading, please wait..." appears.
> - The machine just sits there for approximately 5 minutes
> - Finally I get the following on my screen:
>
> ALERT! /dev/sdc2 does not exist. Dropping to a shell.
> Check your root = boot argument (cat /proc/cmdline)
> Check for missing modules (cat /proc/modules), or device files (ls /dev)
>
> - Then Busybox starts and I get the following message: /bin/sh: can't
> access a tty; job control turned off
> - Finally, I'm left sitting at a "(initramfs) " prompt
Hmph... Wasn't a power issue after all. Just finished replacing the 3 year
old 400watt PSU with a new Corsair 620watt unit.
Same issue.
It *seems* that if I unplug my usb cable from my motorola 5100 cable modem
that it increases the chances of a good boot. Could be a coincidence, but
it's worked the last couple of times.
Since I'm dropped to a very basic prompt when this fails, I'm not sure what
I should be looking at.
| |
| thunder 2007-10-26, 7:16 am |
| On Fri, 26 Oct 2007 10:31:39 +0000, Noozer wrote:
> It *seems* that if I unplug my usb cable from my motorola 5100 cable
> modem that it increases the chances of a good boot. Could be a
> coincidence, but it's worked the last couple of times.
>
> Since I'm dropped to a very basic prompt when this fails, I'm not sure
> what I should be looking at.
Have you looked at your /boot/grub/device.map ?
| |
| sk8r-365 2007-10-26, 1:14 pm |
| Horton heard a Who named Noozer saying:
<snip>
>
> It *seems* that if I unplug my usb cable from my motorola 5100 cable modem
> that it increases the chances of a good boot. Could be a coincidence, but
> it's worked the last couple of times.
Yeah, my machine does that whenever I leave an USB memory stick plugged
in at boot time.
--
sk8r-365
The U.S. Congress enjoys damaging "big business"
but are themselves building big government!
| |
| Darren Salt 2007-10-26, 1:14 pm |
| I demand that sk8r-365 may or may not have written...
> Horton heard a Who named Noozer saying:
> <snip>
[vbcol=seagreen]
[vbcol=seagreen]
> Yeah, my machine does that whenever I leave an USB memory stick plugged
> in at boot time.
Which suggests that you're using an initrd/initramfs and have either a SATA
HD or an IDE HD for which one of the libata drivers is being used. Evidently,
USB is being probed first (or the probing is completed first), and the USB
memory stick is being assigned "sda" (or whatever your HD normally gets).
This is where sticking USB mass storage, SATA disks, SCSI disks, IDE disks
(unless you're using the "old" IDE drivers) etc. in the same namespace looks
silly. You could modify your /etc/fstab to do mounting by partition label
(e2label will help) or by UUID; your initrd will need to be regenerated.
I build the drivers for the boot device into the kernel and to let the
drivers for other mass-storage devices be loaded as needed. The main intended
consequence of this is that I have no need of an initrd - and I don't use
one. :-)
--
| Darren Salt | linux or ds at | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Buy local produce. Try to walk or cycle. TRANSPORT CAUSES GLOBAL WARMING.
Remember, UNIX spelled backwards is XINU.
| |
| sk8r-365 2007-10-26, 7:11 pm |
| Horton heard a Who named Darren Salt saying:
> I demand that sk8r-365 may or may not have written...
>
>
>
>
> Which suggests that you're using an initrd/initramfs and have either a SATA
> HD or an IDE HD for which one of the libata drivers is being used. Evidently,
> USB is being probed first (or the probing is completed first), and the USB
> memory stick is being assigned "sda" (or whatever your HD normally gets).
<snip>
That's correct; there's one SATA and two IDE (DVD/CDROM) connected. Plus, two
USB printers and the net is served by an NIC to a cable modem. Everything is
fine if the memory stick (which is not bootable and is vfat formatted) is not
connected. Further more, I am using an initrd, but I rarely reboot and even less
use the memory stick, so I'll leave things as is. If that situation occurs with
a boot, and the stick is connected, I merely remove the stick and soft restart.
However, OP has to figure out a method to deal with his USB cable modem and the
boot process. Your lack of using an initrd may his best option if, indeed, the
USB cable modem is the cause.
--
sk8r-365
The U.S. Congress enjoys damaging "big business"
but are themselves building big government!
| |
| AJackson 2007-11-03, 1:13 am |
| On Oct 26, 7:47 pm, sk8r-365 <sk8r-...@sk8r.debian.etch.invalid.org>
wrote:
> Horton heard a Who named Darren Salt saying:
>
>
>
>
>
>
> <snip>
>
> That's correct; there's one SATA and two IDE (DVD/CDROM) connected. Plus, two
> USB printers and the net is served by an NIC to a cable modem. Everything is
> fine if the memory stick (which is not bootable and is vfat formatted) is not
> connected. Further more, I am using an initrd, but I rarely reboot and even less
> use the memory stick, so I'll leave things as is. If that situation occurs with
> a boot, and the stick is connected, I merely remove the stick and soft restart.
> However, OP has to figure out a method to deal with his USB cable modem and the
> boot process. Your lack of using an initrd may his best option if, indeed, the
> USB cable modem is the cause.
He would only need to compile the kernel with boot disks devices
driver in kernel.
Rest could be handled by initrd.
But best solution is by using a UUID and using that in fstab and in
grub instead of device names.
Good luck
|
|
|
|
|