Install can't find source media - ide cdrom
While trying to install Slack 8.1 I can't get it to find the source media. I am using a cdrom I made from an image I got from one of their mirrors.
I have a plextor CDW, which I assumed to be IDE, but have to add the following kernel argument to lilo: append="hdc=ide-scsi"
I have installed redhat and lfs without this problem on this exact same system.
Is it that this drive needs scsi emmulation (whatever that is exactly...) and these modules aren't loaded? Could I then get a different iso somehow?
Here is a copy of my dmesg. I've tried added different versions of the append deal - append="ide-scsi=hdd" etc.
While googling the problem someone mentioned that they solved a similar situation my first mounting the drive and then running setup. However, I have yet to be able to mount the drive - can mount floppies, but not the cdrom, not on and /dev - scd, scd0, hdd, hdc etc.
I've also tried buring another copy of the iso - the first was 8.0, and then again with 8.1, same results.
If I can add anything else to the problem description just let me know :)
You shouldn't need any append statement for the CDRW during the install. The proper statement would be append="hdc=ide-scsi" in the lilo.conf after the install is complete. And that is only if you desire to burn CD's under Slack. For just mounting and reading CD's the kernel messages indicate the drive is at hdc. If I understand the report correctly, you should also just use the standard bare.i kernel default.
The CD is obviously being read because it appears to be booting the kernel and loading the ramdisk image. There are many problems of course that result in an unusable CD but it appears that at least this part should be OK. To mount the CD manually, after a simple default boot from the CD, and see what errors might be reported use:
mount -t iso9660 /dev/hdc /cdrom
Post back what error message you receive. If none, then attempt to run setup and see if it will install from the CD.
Hey! I'm facing exactly the same problem. My 1 is a plain ide asus 52X cdrom, which is also located in /dev/hdc. Yes it did boot from the cd but when it came to selecting source it turned out that it can't find the cdrom! Weird....
I also did mount it manually but then it said "Mount: Not a directory". I'm frustrated as well..... sigh
Hope someone can come in and give a hand! ;)
Can you be more specific as to what reported the error? Was it when you attempted to mount the cd manually or during the setup program?
The /cdrom is not a real directory, it should be a sym link to another. Unfortunately, I can't remember what the real path is. But it should be a part of the ram disk image that was loaded. Use the "dmesg" command to see any error messages reported after attempting to manually mount the CD. The normal reply to the console is a single line of text stating that the CD is mounted read-only.
If the CD mounts OK, then you can validate the slackware install packages with the following:
md5sum --check CHECKSUMS.md5
That is provided the md5sum command is available under the install root disk image. I do not know if it is or not. If the program isn't available, then it would have to be from another installation.
If you are able to validate the files then the setup install script shouldn't have any problems with the packages. If not, then CD is probably corrupted. Slack 8.1 iso requires a 700 MByte CD. It will not fit on a 650 MByte CD.
Perhaps the info has helped.
Thanks alot for the reply and the clarification on passing that parameter.
I boot using bare.i, and still not seeing the cdrom, I try to mount as suggested. Starts out:
"root@slackware:/# mount -t iso9660 /dev/hdc /cdrom"
and then replies
"mount: block device /dev/hdc is write-protected, mounting read-only"
"mount: not a directory"
So the cdrom under / is a symlink to /var/log/mount (I think it was), and obviously nothing was mounted there.
Here is the dmesg output. Note where is says file size not equal to 0, then defective cdrom.
Could this really just be a defective cdrom. If so, how could it be reading in the first place. Note that this is also I've tried 2 different disks now with the same results. I'll gladly burn another if that's all there is too it!
The output would tend to indicate a corrupt CD. When I mounted my Slack 8.1 install CD the only thing the kernel reports through dmesg is:
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
The reported console output message is:
mount: block device /dev/cdrom3 is write-protected, mounting read-only
In regard to your cd burn. How did you burn it and how was it downloaded?
There are many Windows programs that are known to corrupt iso images or they do not understand Rockridge extensions, etc. Also, many Windows browsers also tend to corrupt ftp transfers.
In addition the Slack 8.1 iso is well over 650 MByte. The CDR must be a 700 MByte CDR unless you recreate it to fit on a 650MByte.
If you have a linux system available with the ISO image, you could attempt to mount the image under loopback:
mount -t iso9660 -o loop /path/to/iso/image.iso /mount/point
Substitute actual names in the above as required. But that would allow you to mount the file system and test the integrity. In the slackware directory you can the check the md5sums for all the packages.
md5sum --check CHECKSUMS.md5
Any errors reported probably indicate a corrupted iso image. Perhaps try a different mirror. Validate your burned CD against the original ISO image after the burn if possible. I use the cmp command under Linux. Something like:
cmp -l /dev/hdc isoimage.iso
should report any differences in the files. Or you could use the dd command to rip the image first to hard disk and then compare the two files. Either command would force the CD to be read, and you can view the dmesg output to see if there are any error messages reported.
Hope it helps to identify the problem.
I burned this iso under linux with a 700mb disk.
I under my current linux box I mounted the disk, ran the checksums and got all kinds of errors. Should have done that first!
I'll try another mirror and post back if there's any change.
Hey wait! I found the solution! In my case, which is similar with tunedlow, is not caused by cd corruption... Yes i mounted the device during installation by giving command like "mount .... iso 9660...etc etc."
But it's not the case, then a person came up last night and told me an approach. ( thanks to that guy )
u just type ide=nodma as a parameter to the boot.
eg: Boot: bare.i ide=nodma
i tried it and it works perfectly.... hope this piece of information helps...
anyway, thanks also to those who have been trying to help in this forum..
Yes! That worked for me too. Made a new disk from a different mirror but still same problem. Adding that line let me find the disk right away. Now I'll have to read a bit and see why that worked! Thank you both very much.
Wow... I had the same problem with an old PC today. It works for me too!
|All times are GMT -5. The time now is 06:43 AM.|