Drive problem

Draiocht · 09-29-2005, 07:29 AM

Thanks again,

ls -l /dev/sr* (with the space I missed earlier) gave no response at all and just returned me to the prompt. I will try moving the append line a bit later, (I've just been recruited to help a friend fix his car) and will post the results. I had been wondering about the re running lilo after alterations thing but to make sure, I've been rebooting after each modification just to make certain that any changes I have made take effect.

Back later,

Draiocht

dracolich · 09-29-2005, 07:38 AM

Don't be too hard on yourself, MMYoung. Until recently I always forgot it. I must've done a hunderd kernel recompiles and installs. And always I would reboot and it works fine the first time, but the second time it would give an error. Or I add lines to lilo.conf to boot my brand new kernel and then it's not in the list after rebooting. That's when I smacked my forehead and said "Duh, I forgot to rerun lilo." After enough smacks I finally rememberd to do it every time.

Yeah, the append line can be anywhere under the associated image, I just thought it might not be working from the global section. I keep mine under the images like I posted because I run a 2.6 with a 2.4 as backup and don't want the same append for both.

Draiocht · 09-29-2005, 11:35 AM

Hi all,

I just moved the append line in lilo.conf and ran lilo. Whilst the device still won't mount and the error message stating that it does not exist still shows up when I try to use it, I am now getting an output from the ls -l /dev/sr* command. Here it is:

Code:

root@Avalon:~# ls -l /dev/sr0
brw-rw----  1 root cdrom 11, 0 1999-04-13 04:24 /dev/sr0
root@Avalon:~# ls -l /dev/sr*
brw-rw----  1 root cdrom 11,  0 1999-04-13 04:24 /dev/sr0
brw-rw----  1 root cdrom 11,  1 1999-04-13 04:24 /dev/sr1
brw-rw----  1 root cdrom 11, 10 1999-04-13 04:24 /dev/sr10
brw-rw----  1 root cdrom 11, 11 1999-04-13 04:24 /dev/sr11
brw-rw----  1 root cdrom 11, 12 1999-04-13 04:24 /dev/sr12
brw-rw----  1 root cdrom 11, 13 1999-04-13 04:24 /dev/sr13
brw-rw----  1 root cdrom 11, 14 1999-04-13 04:24 /dev/sr14
brw-rw----  1 root cdrom 11, 15 1999-04-13 04:24 /dev/sr15
brw-rw----  1 root cdrom 11,  2 1999-04-13 04:24 /dev/sr2
brw-rw----  1 root cdrom 11,  3 1999-04-13 04:24 /dev/sr3
brw-rw----  1 root cdrom 11,  4 1999-04-13 04:24 /dev/sr4
brw-rw----  1 root cdrom 11,  5 1999-04-13 04:24 /dev/sr5
brw-rw----  1 root cdrom 11,  6 1999-04-13 04:24 /dev/sr6
brw-rw----  1 root cdrom 11,  7 1999-04-13 04:24 /dev/sr7
brw-rw----  1 root cdrom 11,  8 1999-04-13 04:24 /dev/sr8
brw-rw----  1 root cdrom 11,  9 1999-04-13 04:24 /dev/sr9

Draiocht

gbonvehi · 09-29-2005, 11:41 AM

Try using scd0 instead of sr0 and see what happens.

Also instead of modifing /etc/fstab to try the CD, just try to mount something from console, put a Data CD on the drive and type:

Code:

mount -t iso9660 /dev/scd0 /mnt/cdrom

or

Code:

mount -t iso9660 /dev/sr0 /mnt/cdrom

MMYoung · 09-29-2005, 03:00 PM

Quote:

Originally posted by Draiocht

Code:

root@Avalon:~# ls -l /dev/sr0 brw-rw---- 1 root cdrom 11, 0 1999-04-13 04:24 /dev/sr0

GREAT!!! That's EXACTLY what it should be. Now for the easy stuff.

Open a terminal and log in as root. Now, all you have to do is create the symlink in /dev that is stated in your /etc/fstab. For example my fstab states the following for my CDROM:

/dev/cdrom /mnt/cdrom auto noauto,user,owner,ro 0 0

So I have to make sure there actually IS a /dev/cdrom that is "linked" to the actaul device node for my CDROM. In my case the actual device, when booting to a 2.4.xx kernel, is /dev/sr0 (just like yours) so all you have to do is finish the link. You do that by entering the following from the terminal, logged in as root:

ln -s /dev/sr0 /dev/cdrom

When you press enter, the link is created and now you mount the the drive (or actually the filesystem on a CD in the drive) by just using the mount command or clicking on it in Computer or Home (whatever your DE/WM uses). You will need to edit the symlink (the /dev/cdrom part) to match whatever is in your fstab. Also make sure that you (your user name) is a member of the cdrom group for non-root CD burning purposes.

HTH,
MMYoung

Draiocht · 09-29-2005, 06:17 PM

Thanks very much indeed everyone. My cdrw mounts from KDE and I can view files just fine. I haven't tried writing to it yet as I don't yet have burning software. Since the drive was completely dead after the installation of Slack it seemed to make sense to get it running and then get it burning. All I have to do now is explore and install said software and take it from there. Thanks to everyone here I've learned more about LINUX in the last few days, and in particular using the power of the command line, than I have since I first installed it just a few weeks ago.

This is great, when I ran windows I got frustrated when things didn't work and I couldn't find a way in to do anything about it. Now with LINUX, and the help of people on these forums I get a great sense of achievement when I can get into the system and get them working,

and best of all, I learn.

Regards,

Draiocht

MMYoung · 09-29-2005, 07:12 PM

I'm glad you got it working! Just wish we could've got it working sooner.

Later,
MMYoung