i've a computer with debian etch. i've recently added a new sata hard drive
and enter the harddrive in /etc/fstab. It was working fine. Suddenly
today Debian etch is not booting properly. I'm getting
the following errors:

Begin:Mounting root file system ...
Begin:Running /scripts/local-top ...
Done.
Begin:Running /scripts/local-premount ...
Done.
mount:Mounting /dev/sda1 on /root failed:No such Device

Begin:Running /scripts/local-bottom...
Done.
Begin:Running /scripts/init-bottom...
mount:Mounting /root/dev on /dev/.static/dev failed:No such file or
directory
Done.
mount:Mounting /sys on /root/sys failed:No such file or directory

mount:Mounting /proc on /root/proc failed:No such file or directory
Target file system doesn't have /sbin/init

BusyBox v1.1.3(Debian 1:1.1.3-3)Built in Shell(ash)
Enter '' for a list of built in commands
/bin/sh:can't access tty;job control turned off
(initramfs)

I've checked the cables it's fine. One more thing i like to mention. When i

disconnect the brand new hard drive no problem on booting. The problem
is only when i add the new hard drive. Can anyone kindly me find the
problem? Thanks.

On Mon, 6 Aug 2007, William Walter wrote:

> i've a computer with debian etch. i've recently added a new sata hard drive
> and enter the harddrive in /etc/fstab. It was working fine. Suddenly
> today Debian etch is not booting properly. I'm getting
> the following errors:
>
> Begin:Mounting root file system ...
> Begin:Running /scripts/local-top ...
> Done.
> Begin:Running /scripts/local-premount ...
> Done.
> mount:Mounting /dev/sda1 on /root failed:No such Device
>
> Begin:Running /scripts/local-bottom...
> Done.
> Begin:Running /scripts/init-bottom...
> mount:Mounting /root/dev on /dev/.static/dev failed:No such file or
> directory
> Done.
> mount:Mounting /sys on /root/sys failed:No such file or directory
>
> mount:Mounting /proc on /root/proc failed:No such file or directory
> Target file system doesn't have /sbin/init
>
> BusyBox v1.1.3(Debian 1:1.1.3-3)Built in Shell(ash)
> Enter '' for a list of built in commands
> /bin/sh:can't access tty;job control turned off
> (initramfs)
>
> I've checked the cables it's fine. One more thing i like to mention. When i
>
> disconnect the brand new hard drive no problem on booting. The problem
> is only when i add the new hard drive. Can anyone kindly me find the
> problem? Thanks.
>


Sounds like your new drive is being found first. One thing you could do
is, boot up with the new drive disconnected. run blkid, this will print
out the uuid of drive/partitions. in /etc/fstab , replace /dev/sda# with
the corresponding uuid. that way your system wont get confused when it
finds the new disk.

-+-
8 out of 10 Owners who Expressed a Preference said Their Cats Preferred Techno.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On 8/6/07, Jeff D <fixedored@gmail.com> wrote:
>
> On Mon, 6 Aug 2007, William Walter wrote:
>
> > i've a computer with debian etch. i've recently added a new sata hard
> drive
> > and enter the harddrive in /etc/fstab. It was working fine. Suddenly
> > today Debian etch is not booting properly. I'm getting
> > the following errors:
> >
> > Begin:Mounting root file system ...
> > Begin:Running /scripts/local-top ...
> > Done.
> > Begin:Running /scripts/local-premount ...
> > Done.
> > mount:Mounting /dev/sda1 on /root failed:No such Device
> >
> > Begin:Running /scripts/local-bottom...
> > Done.
> > Begin:Running /scripts/init-bottom...
> > mount:Mounting /root/dev on /dev/.static/dev failed:No such file or
> > directory
> > Done.
> > mount:Mounting /sys on /root/sys failed:No such file or directory
> >
> > mount:Mounting /proc on /root/proc failed:No such file or directory
> > Target file system doesn't have /sbin/init
> >
> > BusyBox v1.1.3(Debian 1:1.1.3-3)Built in Shell(ash)
> > Enter '' for a list of built in commands
> > /bin/sh:can't access tty;job control turned off
> > (initramfs)
> >
> > I've checked the cables it's fine. One more thing i like to mention.
> When i
> >
> > disconnect the brand new hard drive no problem on booting. The problem
> > is only when i add the new hard drive. Can anyone kindly me find
> the
> > problem? Thanks.
> >
> >Sounds like your new drive is being found first. One thing you could do
> >is, boot up with the new drive disconnected. run blkid, this will print
> >out the uuid of drive/partitions. in /etc/fstab , replace /dev/sda# with
> >the corresponding uuid. that way your system wont get confused when it
> >finds the new disk.



After modifying the fstab file with UUID debian boots up without any error.
I believe you are right. Thanks a lot for solving this problem.

The problem resurfaced again today. The same error message came up and
Debian Etch refuse to boot up.
I used UUID of all the hard drives. Still no luck in fixing this problem. Is
there anything else I should
do?

On Sun, Aug 12, 2007 at 13:56:21 -0400, William Walter wrote:
> The problem resurfaced again today. The same error message came up and
> Debian Etch refuse to boot up.
> I used UUID of all the hard drives. Still no luck in fixing this problem. Is
> there anything else I should
> do?

Where did you put the UUIDs? Both into /etc/fstab and into
/boot/grub/menu.lst? Did you update your initrd after making the
changes?

(You will get more/faster answers if you keep relevant parts of earlier
messages in your mail. Most of the time people don't feel like digging
through the archives just to find out what a particular question is
about.)

--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

>On Sun, Aug 12, 2007 at 13:56:21 -0400, William Walter wrote:
> The problem resurfaced again today. The same error message came up and
> Debian Etch refuse to boot up.
> I used UUID of all the hard drives. Still no luck in fixing this problem.
Is
> there anything else I should
> do?
>
>>Florian Kulzer wrote:
>> Where did you put the UUIDs? Both into /etc/fstab and into
>> /boot/grub/menu.lst?

Okay. Now i've changed the entry in menu.lst to use UUID.
There's no sign of booting problem for now. Thanks for
pointing that out.

>> Did you update your initrd after making the
>> changes?

How can I do that?

>> (You will get more/faster answers if you keep relevant parts
>> of earlier messages in your mail. Most of the time people
>> don't feel like digging through the archives just to find
>> out what a particular question is about.)

Sorry for that. My bad. i'll remember that from now on.

>On Sun, Aug 12, 2007 at 13:56:21 -0400, William Walter wrote:
> The problem resurfaced again today. The same error message came up and
> Debian Etch refuse to boot up.
> I used UUID of all the hard drives. Still no luck in fixing this problem.
Is
> there anything else I should
> do?
>
>>Florian Kulzer wrote:
>> Where did you put the UUIDs? Both into /etc/fstab and into
>> /boot/grub/menu.lst?

Okay. Now i've changed the entry in menu.lst to use UUID.
There's no sign of booting problem for now. Thanks for
pointing that out.

>> Did you update your initrd after making the
>> changes?

How can I do that?

>> (You will get more/faster answers if you keep relevant parts
>> of earlier messages in your mail. Most of the time people
>> don't feel like digging through the archives just to find
>> out what a particular question is about.)

Sorry for that. My bad. i'll remember that from now on.

On Wed, Aug 15, 2007 at 00:04:43 -0400, William Walter wrote:
> >On Sun, Aug 12, 2007 at 13:56:21 -0400, William Walter wrote:
> > The problem resurfaced again today. The same error message came up and
> > Debian Etch refuse to boot up.
> > I used UUID of all the hard drives. Still no luck in fixing this problem.
> Is
> > there anything else I should
> > do?
> >
> >>Florian Kulzer wrote:
> >> Where did you put the UUIDs? Both into /etc/fstab and into
> >> /boot/grub/menu.lst?
>
> Okay. Now i've changed the entry in menu.lst to use UUID.
> There's no sign of booting problem for now. Thanks for
> pointing that out.
>
> >> Did you update your initrd after making the
> >> changes?
>
> How can I do that?

If you are using a stock Debian kernel or a self-compiled kernel built
with make_kpkg then you can simply run "dpkg-reconfigure" on your kernel
image, i.e.

dpkg-reconfigure linux-image-$(uname -r)

This will take care of the initrd automatically. (The "$(uname -r)" part
expands into the version string of your currently running kernel.)

You can also call the initrd generator directly, "mkinitrd" or "yaird";
see the manpages for details. (The default for Debian is to use
mkinitrd, I think.)

Right now it looks like you don't have to do anything to the initrd. I
just mentioned it for the sake of completeness: If boot problems persist
even after fixing /etc/fstab and /boot/grub/menu.lst then the initrd is
the next thing to check since it also contains information about the
location of the root partition.

--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Wed, Aug 15, 2007 at 00:04:43 -0400, William Walter wrote:
> >On Sun, Aug 12, 2007 at 13:56:21 -0400, William Walter wrote:
> > The problem resurfaced again today. The same error message came up and
> > Debian Etch refuse to boot up.
> > I used UUID of all the hard drives. Still no luck in fixing this problem.
> Is
> > there anything else I should
> > do?
> >
> >>Florian Kulzer wrote:
> >> Where did you put the UUIDs? Both into /etc/fstab and into
> >> /boot/grub/menu.lst?
>
> Okay. Now i've changed the entry in menu.lst to use UUID.
> There's no sign of booting problem for now. Thanks for
> pointing that out.
>
> >> Did you update your initrd after making the
> >> changes?
>
> How can I do that?

If you are using a stock Debian kernel or a self-compiled kernel built
with make_kpkg then you can simply run "dpkg-reconfigure" on your kernel
image, i.e.

dpkg-reconfigure linux-image-$(uname -r)

This will take care of the initrd automatically. (The "$(uname -r)" part
expands into the version string of your currently running kernel.)

You can also call the initrd generator directly, "mkinitrd" or "yaird";
see the manpages for details. (The default for Debian is to use
mkinitrd, I think.)

Right now it looks like you don't have to do anything to the initrd. I
just mentioned it for the sake of completeness: If boot problems persist
even after fixing /etc/fstab and /boot/grub/menu.lst then the initrd is
the next thing to check since it also contains information about the
location of the root partition.

--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org