You are not logged in.
This is my problem after/during the boot of the Arch for the first time:
Root device `/dev/hda3`doesn`t exist, attempting to create it
ERROR: Failed to parse block device ids for `/dev/hda3`
ERROR: Unable to detect or create root device `/dev/hda3`
You are being dropped to a recovery shell
Type `reboot` to reboot
Type `exit` to try and continue booting
NOTE: klibc contains no 'ls' binary, use `echo *` instead
If the device `/dev/hda3` gets created while you are here,
try adding `rootdelay=10` or higher to the kernel command-line
ramfs$
I have 10 partitions. (Mint mounting points)
Sda1 system reserved (NTFS)
Sda2 W7
Sda3 NTFS
Sda4 extended
Sda5 ext4 (Mint 8)
Sda6 swap
Sda7 Arch /
Sda8 Arch /var
Sda9 Arch swap
Sda10 Arch /home
Any ideas ?
Last edited by webmasteryoda (2010-03-20 11:17:09)
Offline
Many ideas. What is the archlinux entry in your /boot/grub/menu.lst or if you are using grub2, /boot/grub/grub.cfg?
aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies
Offline
Whose grub is it, mint's? Your arch appears to be in sda7 which would be hd0,6 in grub... Start at the wall and make sure grub finds the kernel Check the grub wiki if unsure and mind whether you've got grub1 or 2 installed.
HTH
never trust a toad...
::Grateful ArchDonor::
::Grateful Wikipedia Donor::
Offline
I installed Arch without Grub or any other boot loader.
Then I logged to my Mint 8 and used update-grub script.... so its Mints Grub2.....
I am rlly a novice.... is there a workaround to solve this problem ?
Thx inadvance
Offline
post your /boot/grub/menu.lst from mint.
Offline
Its Grub2. So there is no menu.lst. But I found this in the grub.cfg:
menuentry "arch (on /dev/sda7)" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set faa7744d-d27e-4350-8a1d-b18b5413fc5a
linux /boot/vmlinuz26 root=/dev/hda3 ro
initrd /boot/kernel26.img
}
menuentry "arch-fallback (on /dev/sda7)" {
insmod ext2
set root=(hd0,7)
search --no-floppy --fs-uuid --set faa7744d-d27e-4350-8a1d-b18b5413fc5a
linux /boot/vmlinuz26 root=/dev/hda3 ro
initrd /boot/kernel26-fallback.img
Is it causing the problems ?
Offline
How important is mint to you? I ask because grub2 has completely failed to autodetect your Arch install, and my recommendation would be that you install grub from the Arch install cd, configure it the sane way i.e. by hand, and get Arch going - that is the purpose of all this, right?
Once that's done, you can (optionally) add your Mint and W7 entries to grub's menu.lst - again, by hand.
Offline
Shouldn't the Arch / partition be (hd0,6)? At the moment it would be looking in your /var partition...
set root=(hd0,6)
http://wiki.archlinux.org/index.php/GRU … NU.2FLinux
#edit - toad has already made the same point...
Last edited by jasonwryan (2010-03-20 02:19:59)
Offline
You'll also need to change the lines linux /boot/vmlinuz26 root=/dev/hda3 ro to linux /boot/vmlinuz26 root=/dev/sda7 ro but changing grub.cfg would only be a temporary solution as any future upgrade-grub will over write it.
aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies
Offline
Well I did it....
All I have to do is to change Mints grub.cfg
I replaced hda3 with sda7, so its working now...
I also realize that its temporary solution until the grub update or upgrade..... but I am satisfied atm
So thx to all the beautiful people of Arch community
All I have to do now is to set my internet connection and use my new shiny OS
And btw, I am Ubuntu user, but want to learn more of native Linux through command line of Arch.....
thx
Offline
This also happened to me. The problem is that the OS prober is finding lilo.conf in Arch's /etc, which points to /dev/hda3 by default. If you change this to your /dev/sda7, next time you do update-grub it'll be fine. So, boot into Arch and replace every /dev/hda3 in lilo.conf by /dev/sda7.
Cheers.
Offline