Arch Linux

HyperBaton

Member

From: Belgium

Registered: 2008-01-18

Posts: 207

[SOLVED] Moved Arch Linux to a new system - can't boot

My Arch Linux server used to run on a 32-bit system. I have new hardware now, a 64-bit system, but for now I just want to use my 'old' Arch. So I have plugged in the hard drive, I can get to Grub, I can even start booting Arch, but it fails saying this:

Root device '/dev/sda1' doesn't exist, attempting to create it
ERROR: Failed to parse block device name for '/dev/sda1'
ERROR: Unable to create/detect root device '/dev/sda1'

It also suggests something about setting a rootdelay parameter, I've tried this, but it's a no go.
Also, sometimes this happens when it's supposed to be 'hd' instead of 'sd', but this is a system that has been in use for quite some time using the 'sd' naming convenstion.

So, basically, I'm out of ideas, any thoughts? Thanks

Last edited by HyperBaton (2008-12-26 13:59:48)

kludge

Member

Registered: 2008-08-03

Posts: 294

Re: [SOLVED] Moved Arch Linux to a new system - can't boot

well, the obvious question is, "does /dev/sda1 exist?"  does this new machine use differnt block-device/bus hardware?  does your initcpio have the right modules?

---

[23:00:16]    dr_kludge | i want to invent an olfactory human-computer interface, integrate it into the web standards, then produce my own forked browser.
[23:00:32]    dr_kludge | can you guess what i'd call it?
[23:01:16]    dr_kludge | nosilla.
[23:01:32]    dr_kludge | i really should be going to bed.  i'm giggling madly about that.

Xyne

Administrator/PM

Registered: 2008-08-03

Posts: 6,965

Website

Re: [SOLVED] Moved Arch Linux to a new system - can't boot

The names depend on the system setup. If you move a disk, the drive name get's re-assigned (I think this is the reason for using UUIDs, but I could be wrong). If you have the live installation cd, boot up with that and check the disk/partition names with "fdisk -l", then reboot without the CD and edit the grub entry to use the right disk.

---

My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone

HyperBaton

Member

From: Belgium

Registered: 2008-01-18

Posts: 207

Re: [SOLVED] Moved Arch Linux to a new system - can't boot

Yes, the device is /dev/sda according to the Arch LiveCD. This new mainboard does have SATA slots compared to the old one, but considering this is a PATA hard drive, it shouldn't matter right?

archlinuxsagi

Member

Registered: 2008-09-12

Posts: 259

Re: [SOLVED] Moved Arch Linux to a new system - can't boot

I guess your initcpio doesn't have the right module.
Use the livecd and see the detected module using mkinitcpio -M

See whether this modules exist in your hard disk /etc/mkinitcpio.conf and then recompile the cpio image.

HyperBaton

Member

From: Belgium

Registered: 2008-01-18

Posts: 207

Re: [SOLVED] Moved Arch Linux to a new system - can't boot

Yes, I just checked out the mkinitcpio.conf. The problem was the modules section, a specific VIA module was loaded. I removed all modules and just let autodetect do the job and I generated a new image. The system is booting now!

Thanks a lot for the help!

dav7

Member

From: Australia

Registered: 2008-02-08

Posts: 674

Re: [SOLVED] Moved Arch Linux to a new system - can't boot

Remember to mark this solved

---

Windows was made for looking at success from a distance through a wall of oversimplicity. Linux removes the wall, so you can just walk up to success and make it your own.
--
Reinventing the wheel is fun. You get to redefine pi.

HyperBaton

Member

From: Belgium

Registered: 2008-01-18

Posts: 207

Re: [SOLVED] Moved Arch Linux to a new system - can't boot

Done!