You are not logged in.
Pages: 1
Hello
I installed Arch 0.7.2 from a CD, only the base packages. After the restart, grub loads normally, windows starts, but not Arch.. I get the msg:
Mounting /dev/root on /new_root failed: No such device or address
pivot_root:pivot_root: No such file or directory
umount: /initrd: No such file or directory
umount: /initrd: No such file or directory
/linuxrc: 490: /sbin/busybox: not found
Freeing unused kernel memory: 244k freed
BusyBox v1.0.1 (2006.05.09-19:19+0000) Build-in shell (ash)
Enter 'help' for a list of build-in commands.
/bin/sh:can't accesses tty; job control turned off
#
My grub.menu.lst looks normal, i don't need to change initrd26.img to kernel26.img since the kernel26.img does not exist, and when i do this i get File Not Found.
I've installed Arch from this cd a couple of times.. and i have no idea why now this problem.
Thanks in advance
Last edited by Flufinela (2007-06-12 08:24:08)
Offline
You downloaded an outdated ISO. Please get the latest one for the release Duke aka 2007.5.
I recognize that while theory and practice are, in theory, the same, they are, in practice, different. -Mark Mitchell
Offline
I did download the Duke 2007 5 version.
When i runned the installation process, and the 'partition your hard drive' mode i got Fatal error cannot open disk drive.. If you try to install you don't even get an error message which tells you - "hey are you stupid, i told you you have no hard drive"
So bullish that I am, I did continue installing. Everything went smooth.. after restart i got the same msg i posted. Editing the boot line does not change anything, because the system can not find the files...
I have another question.. If the installation is working.. WHY change it.. I mean.. even it it was an outdated one.. Better outdated one than NONE at ALL...
Last edited by Flufinela (2007-06-12 09:47:41)
Offline
I think you're missing the point of arch here.
The installer not finding you harddisk can have several reason, I am sure as an advanced user you know that it could be either:
* misconfigured hw and only certain configurations get around it
* missing module on the installer cd -> file a bug
* conflict between pata and legacy_ide -> force legacy_ide as described in the docs
* scsi? modprobe manually, we dont' do coldplugging
There's a ton of things you can actually do to help us make your experience better but first you should really have read the suggestions in the docs of the new installer like in [1].
Also, your original problem was a "disfuntional installer". That's why we updated ours to implement the move from initrd to initramfs. This happened ages ago and it was never recommended to use outdated installers anyway.
I recognize that while theory and practice are, in theory, the same, they are, in practice, different. -Mark Mitchell
Offline
Pages: 1