You are not logged in.
Hello,
I'm trying to install archlinux-2010.05-core-i686.iso on my old Toshiba Portege 3490CT from a CDrom drive.
Installation seems to start well, then stops with ERROR: boot device didn't show up after 30 seconds...
cat /proc/scsi/scsi
Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: Toshiba MK2016GA Rev: U0.3 Type: Direct-Access ANSI SCSI revision: 05
ls /dev
... sda sda1 sda2 sg0
I guessed sg0 was my CDrom drive so following past threads on the subject I tried the following
- exit (to retry) -> fail
- ln -s /dev/sg0 /dev/archiso then exit -> fail
- ln -sf /dev/sg0 /dev/archiso then exit -> fail
- reset bios to default values and retry -> fail
- there is no USB boot option in the bios, so I cannot try to boot with a USB stick
Can someone tell me what I am doing wrong, and if there are other solutions to try to achieve the installation ?
Offline
I had the same problem with my cd and the same problem when I install it from a usb drive. The problem was because the label wasn't the same that was on the configurations: ARCH_201005. So the lable of cd should be ARCH_201005.
Then that error disappear to me. But I'm not sure is that. You should wait for more replies for anyone confirm.
Last edited by ilusi0n (2010-08-17 15:03:07)
Offline
The label is correctly set to ARCH_201005 on my CD.
Any other hint ?
Offline
Try burning the ISO at the lowest speed.
Offline
If your cd is correctly identified, it should be /dev/sr0.
If its _not_ correctly identified but the system thinks there is _something_ there, you may end up with only /dev/sg0 which is really just a 'raw' device.
Actually - if it is properly recognized, it will be both /dev/sr0 and /dev/sg0 - but the one you have to use is /dev/sr0
Offline
I cheched the .iso and the burned CD MD5sum and they are correct.
The cd does not seem to be correctly identified : ls /dev shows sg0 along with sda, sda1, sda2, but no trace of sr0
How do I help the system identify the cd correctly ?
Note : The Toshiba Portege 3490CT CDrom drive is external, included in a port replicator, linked to the laptop through a (proprietary ?) port.
Offline
If its what I think it is try running "udevadm trigger" when it drops you to a shell. Thats what I had to do with my sata drive.
Offline
udevadm trigger
Does not solve the problem : boot device still "didn't show up", and ls /dev shows sg0, no sr0...
I tried changing the Bios setup :
- Parallel Port Mode from 'ECP' to 'Std. Bi-Direct.' -> no better
Any other hint ?
Offline
I had the same problem. Doing the below makes it work:
$ udevadm trigger
$ exit
I think it's something to do with newer computers that have SATA in preference to ATAPI.
Offline
What OS is installed on the laptop at the moment? You could load kernel & initrd from the archboot iso with grub/grub4dos installed on the hdd and do a net install if anything else fails.
Offline
The OS currently installed is 'Toutou linux', the french version of 'Puppy linux'
So let me check if I understand the different steps of your solution
- Apply the kexec patch to the current linux kernel
- Install Grub4dos (whereto : MBR ? partition boot sector ?)
- Launch 'Toutou Linux'
- Launch Grub4dos, calling the kernel located on the CDrom drive
- Continue with instructions given for a netinstall
Is this correct ?
Offline
Kexec patch? Not sure what that is. I guess you have grub installed already? grub4dos was in case you have windows.
The idea is to simply take vmlinuz and initrd.img from the archboot iso, copy them into your current /boot/, and create an entry in grub's menu.lst. On the archboot image there should be a syslinux.cfg or similar file where you can look for arguments to pass. Then you reboot, select the new grub entry, and start the net install. At that point, the installer is completely in your ram, so you can even partition the hole disk. Mind you though, if you delete your current /boot/ in the process and something goes wrong before you have completed installing arch, your hdd won't boot anymore.
Another option:
http://wiki.archlinux.org/index.php/Ins … ting_Linux
Last edited by hokasch (2010-08-18 14:32:06)
Offline
This might not be of much help to alxsal
If you are installing from USB it might ( as pointed out by illusi0n ) be that your label is not set correctly.
There is no tune2fs command in that shell so you would either have to rename your USB stick or burn a new CD with correct label.
Doing the following MIGHT do the trick. Since it just listens for a device at that position.
Remember to substitute with your device and ARCH build
mdkir /dev/disk/by-label
ln -s /dev/DEVICE /dev/disk/by-label/ARCH_201005
exit
Good luck
Offline