Arch Linux

xavi3r

Member

Registered: 2007-02-03

Posts: 2

[SOLVED] Boot problem

When I try to boot my Arch I get such error message:

Boot device /dev/hda3' doesn't exist, attempting to create it
ERROR: Failed to phrase block device name for '/dev/hda3'
ERROR: Unable to create/detect root device '/dev/hda3'
Dropping to a recovery shell... type 'exit' to reboot
NOTE: klibc contains no 'ls' binary, use 'echo*' instead

If the device '/dev/hda3' gets created while you are here,
try adding 'rootdelay=8' or higher to the kernel command-line
sh: no job control in this shell
ramfs$

This problem occurred after I made system upgrade, I upgraded to latest kernel (2.6.24.3-1) and to the latest grub. I've also tried to boot with Arch installation CD, but the problem remained.

What to do?

P.S.: I apologize if there is any existing topic about similar issue, but I haven't found anything.

Last edited by xavi3r (2009-07-02 10:41:18)

rossm

Member

From: Australia/Melbourne

Registered: 2006-09-25

Posts: 15

Re: [SOLVED] Boot problem

Try booting from a  setup disk or some such and edit /boot/grub/menu.lst so that it refers to "sda3" rather than "hda3". If your installation was fairly old you may also need to edit /etc/fstab  as well.

Last edited by rossm (2008-03-02 20:20:31)

xavi3r

Member

Registered: 2007-02-03

Posts: 2

Re: [SOLVED] Boot problem

I booted from a setup CD, and then I changed in /etc/fstab /dev/hda3 to /dev/sda3 and now works fine. I also had to changed /dev/hda3 to /dev/sda3 in /boot/grub/menu.lst.
Thank you very much for your help, now my system works perfectly.

Last edited by xavi3r (2008-11-26 07:40:00)

synthead

Member

Registered: 2006-05-09

Posts: 1,337

Re: [SOLVED] Boot problem

I booted from a setup CD, and then I changed in /etc/fstab /dev/hda3 to /dev/sda3 and now works fine. I also had to changed /dev/hda3 to /dev/sda3 in /boot/grub/menu.lst.
Thank you very much for your help.

My fstab and menu.lst file are both set to sda3, yet it still has this identical problem.

agentultra

Member

Registered: 2008-02-13

Posts: 13

Re: [SOLVED] Boot problem

I booted from a setup CD, and then I changed in /etc/fstab /dev/hda3 to /dev/sda3 and now works fine. I also had to changed /dev/hda3 to /dev/sda3 in /boot/grub/menu.lst.
Thank you very much for your help.

My fstab and menu.lst file are both set to sda3, yet it still has this identical problem.

I have the exact same problem.

I just tried using an install CD to upgrade pacman, resync the trees, and upgrade; but to no avail.

I'm guessing the new kernel doesn't like my hdd, so I'll try moving back to an older version.

Any thoughts what could be causing this?

Update: Rolling back to older kernels doesn't seem to be doing the trick. I can mount the disk fine from the install cd shell.

Last edited by agentultra (2008-03-10 14:53:02)

Romashka

Forum Fellow

Registered: 2005-12-07

Posts: 1,054

Re: [SOLVED] Boot problem

those who still have the issue - what's your HOOKS line in mkinitcpio.conf?

---

to live is to die

agentultra

Member

Registered: 2008-02-13

Posts: 13

Re: [SOLVED] Boot problem

those who still have the issue - what's your HOOKS line in mkinitcpio.conf?

HOOKS="base udev autodetect pata scsi sata usbinput keymap filesystems"

schmoemi

Member

From: Gersthofen, BY, Germany

Registered: 2004-10-17

Posts: 51

Website

Re: [SOLVED] Boot problem

those who still have the issue - what's your HOOKS line in mkinitcpio.conf?

HOOKS="base udev autodetect pata scsi sata usbinput keymap filesystems"

I had the same problem after my last update.

The new PATA drivers map SATA and PATA disks to "sdX", but as I have both of them, it goes completely weird then.
The installed SATA disk "sda" remains "sda", while the PATA IDE disk (with my root partition), formerly "hda", is called "sdb" now.
So I had to change all the menu.lst and fstab entries from "hda" to "sdb" to make the PC boot again.

---

The time when Microsoft starts making something that doesn't suck will be when they start making vacuum cleaners.

marxav

Member

From: Gatineau, PQ, Canada

Registered: 2006-09-24

Posts: 386

Re: [SOLVED] Boot problem

I have the exact problem  but renaming my entries from hda to sda does not work.  If I boot from the CD with arch boot=/dev/sda3 then I get FILESYSTEM CHECK FAILED.  So I mount -n -o remount,rw / as suggested.  Then if I do ls /boot, there is no menu subdir ??

I have seen other postings about this topic, but I always reach a dead end ...

Last edited by marxav (2008-05-25 17:10:53)

_Marco_

Member

Registered: 2008-04-21

Posts: 242

Re: [SOLVED] Boot problem

@xavi3r
I don't know how to fix this problem keeping the last kernel, but you can try reinstalling the old version as described here
http://wiki.archlinux.org/index.php/Kernel_Panics
@marxav
is the mouse a bluetooth mouse? (I read another topic on bluetooth issue lately)

marxav

Member

From: Gatineau, PQ, Canada

Registered: 2006-09-24

Posts: 386

Re: [SOLVED] Boot problem

@xavi3r
I don't know how to fix this problem keeping the last kernel, but you can try reinstalling the old version as described here
http://wiki.archlinux.org/index.php/Kernel_Panics
@marxav
is the mouse a bluetooth mouse? (I read another topic on bluetooth issue lately)

I just reinstalled kernel 2.6.23.12-3, no change, same problem.

marxav

Member

From: Gatineau, PQ, Canada

Registered: 2006-09-24

Posts: 386

Re: [SOLVED] Boot problem

This is how I solved it:

In /etc/mkinitcpio.conf, I changed :

HOOKS="base udev autodetect pata scsi sata filesystems"

To:
HOOKS="base udev autodetect ide scsi sata filesystems"

Then ran

mkinitcpio -p kernel26

cujo

Member

Registered: 2007-03-28

Posts: 45

Re: [SOLVED] Boot problem

I'm still getting the same error after trying the above.  Anyone have other ideas?

This bug report sounds eerily similar to the problem I experienced, except I use ext3...

http://bugs.archlinux.org/task/10534

Last edited by cujo (2008-05-30 14:14:47)

yvonney

Member

Registered: 2008-06-11

Posts: 671

Re: [SOLVED] Boot problem

My 8 hours over 2 days with the ramfs  etc. etc. issues was simply that grub and the bios see the drive at different places. So, changing  men.lst to hd(0,0) and having my external drive as the first drive/boot drive solved it. sorry if this isn't totally relevant, or, helpful.