Re: Can't see my drives

Re: Can't see my drives

[grottoBoy rant]

Don't know if you've fixed this already, I don't know about configuring for 
CDRW as scsi emulation or whatever, but were you specifying iso9660 
filesystem type when attempting to mount, ie.
mount -t iso9660 /dev/(?) /mnt/cdrom
man mount for syntax

later

----Original Message Follows----


On Saturday 24 August 2002 03:58, Ray Olszewski wrote:
 > Selected responses only (though the additional detail in your reply
 > helped).
 >
 > You say your /dev/cdrom symlink is to /dec/scd0 . That's a scsi device, 
and
 > you have an IDE drive (apparently as the secondary slave, since that is
 > what /dev/hdd is).

Correct.

 > Unless you are running scsi-ide emulation (see below),
 > your immediate problem is simply that the synmlink is wrong. Try removing
 > it by hand and repointing it to the right place, that is (as root)
 >
 >          rm /dev/cdrom
 >          ln -s /dev/hdd /dev/cdrom
 >
 > Then see if you can mount an iso9660 CD successfully.

Tried that, got (as 'me')
"mount:  only root can mount /dev/cdrom on /mnt/cdrom"

and, as  su root, I got:
"mount:  wrong fs type, bad option, bad superblock on /dev/cdrom,
or too many mounted filesystems
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)"

 > On another matter, someone else asked you to check permissions. That was
 > good advice in concept, but wrong in a detail -- you need to check the
 > permissions on the underlying device, not on the symlink. Symlinks always
 > are mode 777, as you reported.
 >
 > Finally, I note that your CD device is a CD writer. To use it as a
 > *writer*, you do need to implement ide-scsi emulation.  So I'd guess that
 > that was how you had it set up when it worked before (in which case,
 > /dev/scd0 would be the right device to use when accessing it) ... but 
that
 > in doing the upgrade, you lostr that emulation.

I remember now, and I'd say you're exactly right!

Is this going to happen *every* time I upgrade?   8(

 > Since I use neither Red Hat
 > nor kudzu, I can't tell you in detail how to restore ide-scsi emulation,
 > but the outline is --
 >
 >          1. Pass a boottime argument to the kernel (in lilo.conf) of this
 > form: append="hdd=ide-scsi"
 >
 >          2. Enable ide-scsi emulation in the kernel. One way is by
 > compiling and loading this set of modules:
 >                  # the stuff to enable ide-scsi emulation for the CD-ROM
 >                  scsi_mod
 >                  sr_mod scd0
 >                  sg
 >                  ide-scsi
 >
 >          3. For reading, the CD drive should then look like it is a scsi
 > device, at /dev/scd0
 >
 >          4. For writing, it is *probably* at lun 0,0,0 -- you can check
 > this with "cdrecord --scanbus".

Yes, it is 0,0,0

I'm going to search back through my files and try and find the instructions 
I
used when first installing the CD-writer.   Unfortunately the original is on
a cd-rom which I can't read at the moment....     :)

As a related question, is there anywhere on the Internet a page that 
explains
(in simple language) what the boot-up sequence of Linux is (and XFree86 for
that matter) and what files get read in what order?   Man pages are always
much too detailed and limited in scope to be easy to follow.

cr
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs









_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Can't see my drives

[cr]

On Friday 30 August 2002 05:07, grottoBoy rant wrote:
> Don't know if you've fixed this already, I don't know about configuring for
> CDRW as scsi emulation or whatever, but were you specifying iso9660
> filesystem type when attempting to mount, ie.
> mount -t iso9660 /dev/(?) /mnt/cdrom
> man mount for syntax
>
> later
>

Yes, I was, exactly that.

I've shelved the problem for now as other things took up my time, however 
I've managed to find the original instructions I used to configure the thing, 
so I'll work through them (as soon as I have enough time) and see if that 
fixes it.

Thanks

cr
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Can't see my drives

[Chuck Gelm]

Howdy, Y'all:

 I noticed that the poster never mentioned, explicitly,
that they were mounting the filesystem as type iso9660.
i.e.
mount -t iso9660 /dev/sd0? /cdrom-rw
      ^^^^^^^^^^
Since I am a newbie, I didn't post, until now.

I recall, time after time, the helpful guru's
(What is plural of 'guru'?)
ask for the explicit 'command' and the
explicit 'error message'.
;-)
Chuck

cr wrote:
> 
> On Friday 30 August 2002 05:07, grottoBoy rant wrote:
> > Don't know if you've fixed this already, I don't know about configuring for
> > CDRW as scsi emulation or whatever, but were you specifying iso9660
> > filesystem type when attempting to mount, ie.
> > mount -t iso9660 /dev/(?) /mnt/cdrom
> > man mount for syntax
> >
> > later
> >
> 
> Yes, I was, exactly that.
> 
> I've shelved the problem for now as other things took up my time, however
> I've managed to find the original instructions I used to configure the thing,
> so I'll work through them (as soon as I have enough time) and see if that
> fixes it.
> 
> Thanks
> 
> cr
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: Can't see my drives

[James Miller]

On 30 Aug 2002, Chuck Gelm wrote:

> (What is plural of 'guru'?)

It's "gurutavatimundiharistrasnivishumaximotiousnesses". Note the "es" on 
the end. Only in the case of this word does Sanskrit form the plural like 
English (and German, when they're not being silly and trying to indicate 
plural by using "en"), using "es". In all other cases, an additional 16 
syllables are needed to form the plural of common nouns.

Finally, a question that even *I* can answer!

James :>]

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Can't see my drives

[B.J. Wilson]

> > (What is plural of 'guru'?)
>
> It's "gurutavatimundiharistrasnivishumaximotiousnesses".

Yeah - don't you remember singing that song from "Shiva Poppins" when you
were a kid? ;-)




-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Can't see my drives

[cr]

On Saturday 31 August 2002 05:08, Chuck Gelm wrote:
> Howdy, Y'all:
>
>  I noticed that the poster never mentioned, explicitly,
> that they were mounting the filesystem as type iso9660.
> i.e.
> mount -t iso9660 /dev/sd0? /cdrom-rw
>       ^^^^^^^^^^
> Since I am a newbie, I didn't post, until now.
>
> I recall, time after time, the helpful guru's
> (What is plural of 'guru'?)
> ask for the explicit 'command' and the
> explicit 'error message'.
> ;-)
> Chuck

I'll keep this short, don't wanna waste bandwidth - yes I know the importance 
of the *exact* commands / error messages (and fstab entries), I did quote 'em 
(or what I thought were the relevant ones) earlier in the thread, but until I 
have time to try some more experimenting I won't have any to report at this 
point.

cr
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Can't see my drives

[grottoBoy rant]

Hi,

My fstab file is set the same, I'm on RH7.2...

During boot, do you see the device recognized.

Anything showing related to /mnt/(dev) that seems funny if you enter the 
command dmesg, or tail /var/log/messages?

Maybe you could doublecheck permissions on the device
ls -l cdrom would show permissions, and should show /dev/cdrom linked to 
/dev/hd*, you can then check permissions on /dev/hd*

On my box brw-rw---- for /dev/hdc
lrwxrwxrwx for /dev/cdrom

later...




----Original Message Follows----


I'm having trouble 'seeing' the floppy drive or the CD-ROM.

I'm running RedHat 7.2, in all previous versions I had no trouble reading 
the
floppy or CD-ROM, for example just by going    cd /mnt/cdrom       ls

But now this doesn't work any more.   Doesn't matter whether I'm 'me' or
su root,
cd /mnt/cdrom  and   cd /mnt/floppy   apparently work, but
a following   ls    won't show the files.

mdir   usually seems to work, though.

Nautilus  and Konqueror  show /mnt/cdrom and /mnt/floppy  but not the
contents.     Konq in superuser mode shows a 'CDRom device' but then
gives a message
"Could not mount device
The reported error was
mount:  /dev/cdrom:  unknown device"

On the other hand,  /mnt/dosC  works fine.

/etc/fstab says:
/dev/fd0          /mnt/floppy      auto         noauto,owner,kudzu    0 0
/dev/cdrom      /mnt/cdrom      iso9660    noauto,owner,kudzu,ro   0 0

Any suggestions of what might be wrong?

cr



_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Can't see my drives

[cr]

On Friday 23 August 2002 03:09, grottoBoy rant wrote:
> Hi,
>
> My fstab file is set the same, I'm on RH7.2...
>
> During boot, do you see the device recognized.
Yes, there's some message about it  (can't recall specifics without rebooting)

>
> Anything showing related to /mnt/(dev) that seems funny if you enter the
> command dmesg, or tail /var/log/messages?

dmesg shows it as hdd (which I think is correct, it's the slave on the 
secondary IDE controller).   Nothing that looks suspicious though.

> Maybe you could doublecheck permissions on the device
> ls -l cdrom would show permissions, and should show /dev/cdrom linked to
> /dev/hd*, you can then check permissions on /dev/hd*
>
> On my box brw-rw---- for /dev/hdc

Same for mine from /dev/hda to /dev/hdd

> lrwxrwxrwx for /dev/cdrom
Same for mine.

I rather suspect fstab may be wrong...   

cr
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Can't see my drives

[cr]

I'm having trouble 'seeing' the floppy drive or the CD-ROM.

I'm running RedHat 7.2, in all previous versions I had no trouble reading the 
floppy or CD-ROM, for example just by going    cd /mnt/cdrom       ls

But now this doesn't work any more.   Doesn't matter whether I'm 'me' or 
su root, 
cd /mnt/cdrom  and   cd /mnt/floppy   apparently work, but 
a following   ls    won't show the files.

mdir   usually seems to work, though.

Nautilus  and Konqueror  show /mnt/cdrom and /mnt/floppy  but not the 
contents.     Konq in superuser mode shows a 'CDRom device' but then
gives a message  
"Could not mount device
The reported error was
mount:  /dev/cdrom:  unknown device"

On the other hand,  /mnt/dosC  works fine.

/etc/fstab says:
/dev/fd0          /mnt/floppy      auto         noauto,owner,kudzu    0 0
/dev/cdrom      /mnt/cdrom      iso9660    noauto,owner,kudzu,ro   0 0

Any suggestions of what might be wrong?

cr
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Can't see my drives

[Ray Olszewski]

Your report is a bit hard to read, so please forgive me if I have 
misinterpreted what you sent.

1.  /dev/cdrom is usually a symlink, not a real device entry. Is it 
pointing to the right actual device (/dev/hd?, if your system is IDE, or 
/dev/sd? if it is SCSI, where ? gets replaced with the right letter for the 
physical drive)?

2. What is "/mnt/dosC"? I imagine it is a symlink to something (since it is 
not in the fstab listing you sent), but I can't *guess* what it is.

3. In the fstab intfo you sent, both filesystems are "noauto", meaning that 
you need (as root) to execute a mount command before the filesystem will be 
present at the mount point. You do not mention doing so before trying the 
floppy, and you only mention using some KDE app to mount the CD. 
Try  running the appropriate mount commands, as root, from the command line 
(e.g., put in a floppy, then enter "mount /mnt/floppy", and do similar 
things with an iso9660 CD) and seeing it that works. If not, please post 
again, this time including

         A. The COMPLETE cli command you enter and the COMPLETE error report.
         B. The output of "ls -l /dev/cdrom"
         C. Info on what kind of CD drive you have and what IDE or SCSI 
channel it is connected to.

At 11:05 PM 8/22/02 +1200, cr wrote:
>I'm having trouble 'seeing' the floppy drive or the CD-ROM.
>
>I'm running RedHat 7.2, in all previous versions I had no trouble reading the
>floppy or CD-ROM, for example just by going    cd /mnt/cdrom       ls
>
>But now this doesn't work any more.   Doesn't matter whether I'm 'me' or
>su root,
>cd /mnt/cdrom  and   cd /mnt/floppy   apparently work, but
>a following   ls    won't show the files.
>
>mdir   usually seems to work, though.
>
>Nautilus  and Konqueror  show /mnt/cdrom and /mnt/floppy  but not the
>contents.     Konq in superuser mode shows a 'CDRom device' but then
>gives a message
>"Could not mount device
>The reported error was
>mount:  /dev/cdrom:  unknown device"
>
>On the other hand,  /mnt/dosC  works fine.
>
>/etc/fstab says:
>/dev/fd0          /mnt/floppy      auto         noauto,owner,kudzu    0 0
>/dev/cdrom      /mnt/cdrom      iso9660    noauto,owner,kudzu,ro   0 0
>
>Any suggestions of what might be wrong?





--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Can't see my drives

[cr]

On Friday 23 August 2002 03:05, Ray Olszewski wrote:
> Your report is a bit hard to read, so please forgive me if I have
> misinterpreted what you sent.

Thanks for answering!    I'll try and clarify -

> 1.  /dev/cdrom is usually a symlink, not a real device entry. Is it
> pointing to the right actual device (/dev/hd?, if your system is IDE, or
> /dev/sd? if it is SCSI, where ? gets replaced with the right letter for the
> physical drive)?

Hmmm....   it's pointing to  /dev/scd0, from the look of it.    
>
> 2. What is "/mnt/dosC"? I imagine it is a symlink to something (since it is
> not in the fstab listing you sent), but I can't *guess* what it is.

It's a DOS drive, I only mentioned it to indicate that my permissions for the 
/mnt directory seem to be OK, otherwise it's irrelevant.   Sorry for 
confusing the issue.

> 3. In the fstab intfo you sent, both filesystems are "noauto", meaning that
> you need (as root) to execute a mount command before the filesystem will be
> present at the mount point. You do not mention doing so before trying the
> floppy, and you only mention using some KDE app to mount the CD.
> Try  running the appropriate mount commands, as root, from the command line
> (e.g., put in a floppy, then enter "mount /mnt/floppy", and do similar
> things with an iso9660 CD) and seeing it that works. If not, please post
> again, this time including
>
>          A. The COMPLETE cli command you enter and the COMPLETE error
> report. 

As 'me' *or* as su root :

mount /mnt/floppy
mount: block device /dev/fd0 is write-protected, mounting read-only   

[that's correct by the way, the floppy was write-protected]
and    ls     works fine.     Thanks.


> B. The output of "ls -l /dev/cdrom"

lrwxrwxrwx     1 root     root      9 Jul 17 02:11    /dev/cdrom -> /dev/scd0


The following don't work, for 'me' or as su root:

mount /dev/cdrom
mount: /dev/cdrom: unknown device

mount /mnt/cdrom
mount: /dev/cdrom: unknown device

mount /dev/scd0
mount: can't find /dev/scd0 in /etc/fstab or /etc/mtab


>          C. Info on what kind of CD drive you have and what IDE or SCSI
> channel it is connected to.

It's a LG 8080 cd-writer.    IDE.     Worked fine with my previous RH6.2, and 
seems to work OK with apps like X-CD-Roast.   I'm not sure what IDE channel 
it's on, I think it's the slave on the secondary IDE controller (cos I have 
three hard drives).   Would that make it hdd0?    In fact  dmesg   shows it 
as hdd - 
hdd: LG CD-RW CED8080B, ATAPI CD/DVD-ROM drive

I thought kudzu was supposed to find things like that?   But anyway, 'mount 
/dev/hdd0' just gets a 'can't find /dev/hdd0 in /etc/fstab or /etc/mtab'

The full contents of my /etc/fstab are:

LABEL=/                 /                       ext2    defaults        1 1
LABEL=/boot             /boot                   ext2    defaults        1 2
/dev/hdc5               /cr3                    ext3    defaults        1 2
/dev/hdb6               /cr4                    ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
LABEL=/home             /home                   ext3    defaults        1 2
/dev/hdb1               /mnt/dosC               vfat    defaults        0 0
/dev/hdc1               /mnt/dosD               vfat    defaults        0 0
none                    /proc                   proc    defaults        0 0
none                    /dev/shm                tmpfs   defaults        0 0
LABEL=/usr              /usr                    ext3    defaults        1 2
/dev/hda5               swap                    swap    defaults        0 0
/dev/fd0                /mnt/floppy             auto    noauto,owner,kudzu 0 0
/dev/cdrom              /mnt/cdrom              iso9660 noauto,owner,kudzu,ro 
0 0


I'm not sure where some of this came from, RH 7.2 seems to have invented some 
of it.

Should I try adding a line to fstab - 
/dev/hdd          /mnt/cdrom        iso9660 owner,kudzu,ro  0 0

cr


> At 11:05 PM 8/22/02 +1200, cr wrote:
> >I'm having trouble 'seeing' the floppy drive or the CD-ROM.
> >
> >I'm running RedHat 7.2, in all previous versions I had no trouble reading
> > the floppy or CD-ROM, for example just by going    cd /mnt/cdrom       ls
> >
> >But now this doesn't work any more.   Doesn't matter whether I'm 'me' or
> >su root,
> >cd /mnt/cdrom  and   cd /mnt/floppy   apparently work, but
> >a following   ls    won't show the files.
> >
> >mdir   usually seems to work, though.
> >
> >Nautilus  and Konqueror  show /mnt/cdrom and /mnt/floppy  but not the
> >contents.     Konq in superuser mode shows a 'CDRom device' but then
> >gives a message
> >"Could not mount device
> >The reported error was
> >mount:  /dev/cdrom:  unknown device"
> >
> >On the other hand,  /mnt/dosC  works fine.
> >
> >/etc/fstab says:
> >/dev/fd0          /mnt/floppy      auto         noauto,owner,kudzu    0 0
> >/dev/cdrom      /mnt/cdrom      iso9660    noauto,owner,kudzu,ro   0 0
> >
> >Any suggestions of what might be wrong?
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Can't see my drives

[Ray Olszewski]

Selected responses only (though the additional detail in your reply helped).

You say your /dev/cdrom symlink is to /dec/scd0 . That's a scsi device, and 
you have an IDE drive (apparently as the secondary slave, since that is 
what /dev/hdd is). Unless you are running scsi-ide emulation (see below), 
your immediate problem is simply that the synmlink is wrong. Try removing 
it by hand and repointing it to the right place, that is (as root)

         rm /dev/cdrom
         ln -s /dev/hdd /dev/cdrom

Then see if you can mount an iso9660 CD successfully.

On another matter, someone else asked you to check permissions. That was 
good advice in concept, but wrong in a detail -- you need to check the 
permissions on the underlying device, not on the symlink. Symlinks always 
are mode 777, as you reported.

Finally, I note that your CD device is a CD writer. To use it as a 
*writer*, you do need to implement ide-scsi emulation.  So I'd guess that 
that was how you had it set up when it worked before (in which case, 
/dev/scd0 would be the right device to use when accessing it) ... but that 
in doing the upgrade, you lostr that emulation. Since I use neither Red Hat 
nor kudzu, I can't tell you in detail how to restore ide-scsi emulation, 
but the outline is --

         1. Pass a boottime argument to the kernel (in lilo.conf) of this form:
                 append="hdd=ide-scsi"

         2. Enable ide-scsi emulation in the kernel. One way is by 
compiling and loading this set of modules:
                 # the stuff to enable ide-scsi emulation for the CD-ROM
                 scsi_mod
                 sr_mod scd0
                 sg
                 ide-scsi

         3. For reading, the CD drive should then look like it is a scsi 
device, at /dev/scd0

         4. For writing, it is *probably* at lun 0,0,0 -- you can check 
this with "cdrecord --scanbus".

At 09:18 PM 8/23/02 +1200, cr wrote:
>On Friday 23 August 2002 03:05, Ray Olszewski wrote:
> > Your report is a bit hard to read, so please forgive me if I have
> > misinterpreted what you sent.
>
>Thanks for answering!    I'll try and clarify -
>
> > 1.  /dev/cdrom is usually a symlink, not a real device entry. Is it
> > pointing to the right actual device (/dev/hd?, if your system is IDE, or
> > /dev/sd? if it is SCSI, where ? gets replaced with the right letter for the
> > physical drive)?
>
>Hmmm....   it's pointing to  /dev/scd0, from the look of it.
> >
> > 2. What is "/mnt/dosC"? I imagine it is a symlink to something (since it is
> > not in the fstab listing you sent), but I can't *guess* what it is.
>
>It's a DOS drive, I only mentioned it to indicate that my permissions for the
>/mnt directory seem to be OK, otherwise it's irrelevant.   Sorry for
>confusing the issue.
>
> > 3. In the fstab intfo you sent, both filesystems are "noauto", meaning that
> > you need (as root) to execute a mount command before the filesystem will be
> > present at the mount point. You do not mention doing so before trying the
> > floppy, and you only mention using some KDE app to mount the CD.
> > Try  running the appropriate mount commands, as root, from the command line
> > (e.g., put in a floppy, then enter "mount /mnt/floppy", and do similar
> > things with an iso9660 CD) and seeing it that works. If not, please post
> > again, this time including
> >
> >          A. The COMPLETE cli command you enter and the COMPLETE error
> > report.
>
>As 'me' *or* as su root :
>
>mount /mnt/floppy
>mount: block device /dev/fd0 is write-protected, mounting read-only
>
>[that's correct by the way, the floppy was write-protected]
>and    ls     works fine.     Thanks.
>
>
> > B. The output of "ls -l /dev/cdrom"
>
>lrwxrwxrwx     1 root     root      9 Jul 17 02:11    /dev/cdrom -> /dev/scd0
>
>
>The following don't work, for 'me' or as su root:
>
>mount /dev/cdrom
>mount: /dev/cdrom: unknown device
>
>mount /mnt/cdrom
>mount: /dev/cdrom: unknown device
>
>mount /dev/scd0
>mount: can't find /dev/scd0 in /etc/fstab or /etc/mtab
>
>
> >          C. Info on what kind of CD drive you have and what IDE or SCSI
> > channel it is connected to.
>
>It's a LG 8080 cd-writer.    IDE.     Worked fine with my previous RH6.2, and
>seems to work OK with apps like X-CD-Roast.   I'm not sure what IDE channel
>it's on, I think it's the slave on the secondary IDE controller (cos I have
>three hard drives).   Would that make it hdd0?    In fact  dmesg   shows it
>as hdd -
>hdd: LG CD-RW CED8080B, ATAPI CD/DVD-ROM drive
>
>I thought kudzu was supposed to find things like that?   But anyway, 'mount
>/dev/hdd0' just gets a 'can't find /dev/hdd0 in /etc/fstab or /etc/mtab'
>
>The full contents of my /etc/fstab are:
>
>LABEL=/                 /                       ext2    defaults        1 1
>LABEL=/boot             /boot                   ext2    defaults        1 2
>/dev/hdc5               /cr3                    ext3    defaults        1 2
>/dev/hdb6               /cr4                    ext3    defaults        1 2
>none                    /dev/pts                devpts  gid=5,mode=620  0 0
>LABEL=/home             /home                   ext3    defaults        1 2
>/dev/hdb1               /mnt/dosC               vfat    defaults        0 0
>/dev/hdc1               /mnt/dosD               vfat    defaults        0 0
>none                    /proc                   proc    defaults        0 0
>none                    /dev/shm                tmpfs   defaults        0 0
>LABEL=/usr              /usr                    ext3    defaults        1 2
>/dev/hda5               swap                    swap    defaults        0 0
>/dev/fd0                /mnt/floppy             auto    noauto,owner,kudzu 0 0
>/dev/cdrom              /mnt/cdrom              iso9660 noauto,owner,kudzu,ro
>0 0
>
>
>I'm not sure where some of this came from, RH 7.2 seems to have invented some
>of it.
>
>Should I try adding a line to fstab -
>/dev/hdd          /mnt/cdrom        iso9660 owner,kudzu,ro  0 0
>
>cr
>
>
> > At 11:05 PM 8/22/02 +1200, cr wrote:
> > >I'm having trouble 'seeing' the floppy drive or the CD-ROM.
> > >
> > >I'm running RedHat 7.2, in all previous versions I had no trouble reading
> > > the floppy or CD-ROM, for example just by going    cd /mnt/cdrom       ls
> > >
> > >But now this doesn't work any more.   Doesn't matter whether I'm 'me' or
> > >su root,
> > >cd /mnt/cdrom  and   cd /mnt/floppy   apparently work, but
> > >a following   ls    won't show the files.
> > >
> > >mdir   usually seems to work, though.
> > >
> > >Nautilus  and Konqueror  show /mnt/cdrom and /mnt/floppy  but not the
> > >contents.     Konq in superuser mode shows a 'CDRom device' but then
> > >gives a message
> > >"Could not mount device
> > >The reported error was
> > >mount:  /dev/cdrom:  unknown device"
> > >
> > >On the other hand,  /mnt/dosC  works fine.
> > >
> > >/etc/fstab says:
> > >/dev/fd0          /mnt/floppy      auto         noauto,owner,kudzu    0 0
> > >/dev/cdrom      /mnt/cdrom      iso9660    noauto,owner,kudzu,ro   0 0
> > >
> > >Any suggestions of what might be wrong?

--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Can't see my drives

[Riley Williams]

Hi Ray, CR.

> Selected responses only (though the additional detail in your reply
> helped).
>
> You say your /dev/cdrom symlink is to /dec/scd0 . That's a scsi
> device, and you have an IDE drive (apparently as the secondary
> slave, since that is what /dev/hdd is). Unless you are running
> scsi-ide emulation (see below), your immediate problem is simply
> that the synmlink is wrong. Try removing it by hand and repointing
> it to the right place, that is (as root)
>
>          rm /dev/cdrom
>          ln -s /dev/hdd /dev/cdrom
>
> Then see if you can mount an iso9660 CD successfully.
>
> On another matter, someone else asked you to check permissions. That
> was good advice in concept, but wrong in a detail -- you need to
> check the permissions on the underlying device, not on the symlink.
> Symlinks always are mode 777, as you reported.

All agreed so far, at least in the context it is given.

> Finally, I note that your CD device is a CD writer. To use it as a
> *writer*, you do need to implement ide-scsi emulation.  So I'd guess
> that that was how you had it set up when it worked before (in which
> case, /dev/scd0 would be the right device to use when accessing it)
> ... but that in doing the upgrade, you lost that emulation.

Possibly of relevance here, although I'm not certain of this: Somewhere
in the 2.4 kernel timeframe, a recommendation was made that the nodename
for SCSI CD's change from /dev/scdN to /dev/srN if my memory is correct,
and I think Red Hat made the change between 7.1 and 7.2 so it could
simply be that the nodename /dev/scd0 should now be /dev/sr0 instead.

> Since I use neither Red Hat nor kudzu, I can't tell you in detail
> how to restore ide-scsi emulation, but the outline is --
>
>  1. Pass a boottime argument to the kernel (in lilo.conf) of this
>     form: append="hdd=ide-scsi"
>
>  2. Enable ide-scsi emulation in the kernel. One way is by compiling
>     and loading this set of modules:
>
>	  # the stuff to enable ide-scsi emulation for the CD-ROM
>	  scsi_mod
>	  sr_mod scd0
>	  sg
>	  ide-scsi
>
>  3. For reading, the CD drive should then look like it is a scsi 
>     device, at /dev/scd0
>
>  4. For writing, it is *probably* at lun 0,0,0 -- you can check 
>     this with "cdrecord --scanbus".

That is a reasonable general outline for Red Hat as well. Yes, I use Red
Hat, but right at this moment, I don't have access to a 7.3 system to
check the details on.

Best wishes from Riley.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Can't see my drives

[cr]

On Saturday 24 August 2002 10:47, Riley Williams wrote:

>
> Possibly of relevance here, although I'm not certain of this: Somewhere
> in the 2.4 kernel timeframe, a recommendation was made that the nodename
> for SCSI CD's change from /dev/scdN to /dev/srN if my memory is correct,
> and I think Red Hat made the change between 7.1 and 7.2 so it could
> simply be that the nodename /dev/scd0 should now be /dev/sr0 instead.

My RH 7.2 still has, in /dev, files named scd0 to scd7, also srnd0 to srnd7, 
but no sr0 etc.     It may be that they changed between 7.2 and 7.3, which I 
don't have.

cr

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Can't see my drives

[cr]

On Saturday 24 August 2002 03:58, Ray Olszewski wrote:
> Selected responses only (though the additional detail in your reply
> helped).
>
> You say your /dev/cdrom symlink is to /dec/scd0 . That's a scsi device, and
> you have an IDE drive (apparently as the secondary slave, since that is
> what /dev/hdd is). 

Correct.

> Unless you are running scsi-ide emulation (see below),
> your immediate problem is simply that the synmlink is wrong. Try removing
> it by hand and repointing it to the right place, that is (as root)
>
>          rm /dev/cdrom
>          ln -s /dev/hdd /dev/cdrom
>
> Then see if you can mount an iso9660 CD successfully.

Tried that, got (as 'me') 
"mount:  only root can mount /dev/cdrom on /mnt/cdrom"

and, as  su root, I got:
"mount:  wrong fs type, bad option, bad superblock on /dev/cdrom,
or too many mounted filesystems
(could this be the IDE device where you in fact use 
ide-scsi so that sr0 or sda or so is needed?)"

> On another matter, someone else asked you to check permissions. That was
> good advice in concept, but wrong in a detail -- you need to check the
> permissions on the underlying device, not on the symlink. Symlinks always
> are mode 777, as you reported.
>
> Finally, I note that your CD device is a CD writer. To use it as a
> *writer*, you do need to implement ide-scsi emulation.  So I'd guess that
> that was how you had it set up when it worked before (in which case,
> /dev/scd0 would be the right device to use when accessing it) ... but that
> in doing the upgrade, you lostr that emulation. 

I remember now, and I'd say you're exactly right!   

Is this going to happen *every* time I upgrade?   8(

> Since I use neither Red Hat
> nor kudzu, I can't tell you in detail how to restore ide-scsi emulation,
> but the outline is --
>
>          1. Pass a boottime argument to the kernel (in lilo.conf) of this
> form: append="hdd=ide-scsi"
>
>          2. Enable ide-scsi emulation in the kernel. One way is by
> compiling and loading this set of modules:
>                  # the stuff to enable ide-scsi emulation for the CD-ROM
>                  scsi_mod
>                  sr_mod scd0
>                  sg
>                  ide-scsi
>
>          3. For reading, the CD drive should then look like it is a scsi
> device, at /dev/scd0
>
>          4. For writing, it is *probably* at lun 0,0,0 -- you can check
> this with "cdrecord --scanbus".

Yes, it is 0,0,0

I'm going to search back through my files and try and find the instructions I 
used when first installing the CD-writer.   Unfortunately the original is on 
a cd-rom which I can't read at the moment....     :)

As a related question, is there anywhere on the Internet a page that explains 
(in simple language) what the boot-up sequence of Linux is (and XFree86 for 
that matter) and what files get read in what order?   Man pages are always 
much too detailed and limited in scope to be easy to follow.

cr
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Can't see my drives

[Ray Olszewski]

Selected responses only, below.

At 08:27 PM 8/24/02 +1200, cr wrote:
>[...]
> > Then see if you can mount an iso9660 CD successfully.
>[...]
>and, as  su root, I got:
>"mount:  wrong fs type, bad option, bad superblock on /dev/cdrom,
>or too many mounted filesystems
>(could this be the IDE device where you in fact use
>ide-scsi so that sr0 or sda or so is needed?)"

Hmmm ... well, as we previously discussed, you do need to use ide-scsi 
anyway (for burning). But I'm surprised that you can't use it as a reader 
dieectly in IDE mode. Unless perhaps you have the ide-scsi stuff partly 
installed, just not working right. Perhaps Riley's comment that you need to 
switch scsi device names is on target?

Before I set up ide-scsi here, my CD burner worked just fine as a reader in 
ide mode.

[...]
> > Finally, I note that your CD device is a CD writer. To use it as a
> > *writer*, you do need to implement ide-scsi emulation.  So I'd guess that
> > that was how you had it set up when it worked before (in which case,
> > /dev/scd0 would be the right device to use when accessing it) ... but that
> > in doing the upgrade, you lostr that emulation.
>
>I remember now, and I'd say you're exactly right!
>
>Is this going to happen *every* time I upgrade?   8(

Probably. You'll need to make notes about how you set this up and redo it 
with every full-level (not incremental) upgrade. (Or you could switch to a 
distro that does upgrades more gently, as Debian does ... but I digress.)

[...]
>As a related question, is there anywhere on the Internet a page that explains
>(in simple language) what the boot-up sequence of Linux is (and XFree86 for
>that matter) and what files get read in what order?   Man pages are always
>much too detailed and limited in scope to be easy to follow.

You probably want to know about the init sequence, not the boot-up 
sequence. Booting just involves getting the kernel running and starting the 
init process. The init process (normally, and we can easily neglect the 
exceptions for the moment) is governed by the directives in /etc/inittab. 
Typically, these directives involve a three-step init process:

         1. Init into single-user more and run a script. On my systems, and 
pretty much every Linux system I've ever sern, this is a script called rcS. 
Its location varies a bit; on my systems, the coverning line reads 
"si::sysinit:/etc/init.d/rcS". This script in turn runs other scripts; if 
you understand shell scripting, you can follow the sequence by reading the 
scripts.

         2. Init into normal multi-user mode (governed by a runlevel 
specification). This works the same way as step 1, except init runs a 
different script, again as specified in inittab for the default or chosen 
runlevel. On my systems, it is a line like "l2:2:wait:/etc/init.d/rc 2" -- 
which says run the script /etc/init.d/rc and pass to it the argument "2".

         3. Run other processes specified for the chosen or default 
runlevel. Typically these are just the tty processes that allow for console 
logins (look for lines like "1:2345:respawn:/sbin/getty 38400 tty1"), but 
some distros use this step to run an X-based login process like xdm or to 
run consoles on serial ports.

I'm not sure if there is a general turorial on the boot/init process, but 
were I looking for one, I'd look through the HowTos at (for example) 
www.linuxdoc.org .


--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski					-- Han Solo
Palo Alto, California, USA			  ray@comarre.com
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Can't see my drives

[cr]

On Sunday 25 August 2002 03:05, Ray Olszewski wrote:
> Selected responses only, below.



> Before I set up ide-scsi here, my CD burner worked just fine as a reader in
> ide mode.

That's exactly what I'd expect to be able to do.   

In fact,as I recall it, when I replaced my old 6x CD-ROM (IDE) drive with my 
LG cd-writer  (also IDE), I don't think the system even 'noticed' the 
change....   it all worked exactly as before.

I think I'll try to work back to the original IDE CD-ROM setup, and see how I 
go from there.

[.....]
> >
> >Is this going to happen *every* time I upgrade?   8(
>
> Probably. You'll need to make notes about how you set this up and redo it
> with every full-level (not incremental) upgrade. (Or you could switch to a
> distro that does upgrades more gently, as Debian does ... but I digress.)

Umm OK, this time I *will* take notes.   :)

> [...]
>
> >As a related question, is there anywhere on the Internet a page that
> > explains (in simple language) what the boot-up sequence of Linux is (and
> > XFree86 for that matter) and what files get read in what order?   Man
> > pages are always much too detailed and limited in scope to be easy to
> > follow.
>
> You probably want to know about the init sequence, not the boot-up
> sequence. Booting just involves getting the kernel running and starting the
> init process. The init process (normally, and we can easily neglect the
> exceptions for the moment) is governed by the directives in /etc/inittab.
> Typically, these directives involve a three-step init process:
>
>          1. Init into single-user more and run a script. On my systems, and
> pretty much every Linux system I've ever sern, this is a script called rcS.
> Its location varies a bit; on my systems, the coverning line reads
> "si::sysinit:/etc/init.d/rcS". This script in turn runs other scripts; if
> you understand shell scripting, you can follow the sequence by reading the
> scripts.
>
>          2. Init into normal multi-user mode (governed by a runlevel
> specification). This works the same way as step 1, except init runs a
> different script, again as specified in inittab for the default or chosen
> runlevel. On my systems, it is a line like "l2:2:wait:/etc/init.d/rc 2" --
> which says run the script /etc/init.d/rc and pass to it the argument "2".
>
>          3. Run other processes specified for the chosen or default
> runlevel. Typically these are just the tty processes that allow for console
> logins (look for lines like "1:2345:respawn:/sbin/getty 38400 tty1"), but
> some distros use this step to run an X-based login process like xdm or to
> run consoles on serial ports.

Thanks!   I'll file this and print out a copy for reference.

> I'm not sure if there is a general turorial on the boot/init process, but
> were I looking for one, I'd look through the HowTos at (for example)
> www.linuxdoc.org .

I don't recall seeing one, but I'll check again.

cr

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Can't see my drives

[Arthur Othieno]

----- Original Message -----
From: "Ray Olszewski" <ray@comarre.com>
To: <cr@orcon.net.nz>; <linux-newbie@vger.kernel.org>
Sent: Saturday, August 24, 2002 4:05 PM
Subject: Re: Can't see my drives


> Selected responses only, below.
>
> At 08:27 PM 8/24/02 +1200, cr wrote:
> >[...]
> > > Then see if you can mount an iso9660 CD successfully.
> >[...]
> >and, as  su root, I got:
> >"mount:  wrong fs type, bad option, bad superblock on /dev/cdrom,
> >or too many mounted filesystems
> >(could this be the IDE device where you in fact use
> >ide-scsi so that sr0 or sda or so is needed?)"
>
> Hmmm ... well, as we previously discussed, you do need to use ide-scsi
> anyway (for burning). But I'm surprised that you can't use it as a reader
> dieectly in IDE mode. Unless perhaps you have the ide-scsi stuff partly
> installed, just not working right. Perhaps Riley's comment that you need
to
> switch scsi device names is on target?
>
> Before I set up ide-scsi here, my CD burner worked just fine as a reader
in
> ide mode.
>
> [...]
> > > Finally, I note that your CD device is a CD writer. To use it as a
> > > *writer*, you do need to implement ide-scsi emulation.  So I'd guess
that
> > > that was how you had it set up when it worked before (in which case,
> > > /dev/scd0 would be the right device to use when accessing it) ... but
that
> > > in doing the upgrade, you lostr that emulation.
> >
> >I remember now, and I'd say you're exactly right!
> >
> >Is this going to happen *every* time I upgrade?   8(
>
> Probably. You'll need to make notes about how you set this up and redo it
> with every full-level (not incremental) upgrade. (Or you could switch to a
> distro that does upgrades more gently, as Debian does ... but I digress.)
>
> [...]
> >As a related question, is there anywhere on the Internet a page that
explains
> >(in simple language) what the boot-up sequence of Linux is (and XFree86
for
> >that matter) and what files get read in what order?   Man pages are
always
> >much too detailed and limited in scope to be easy to follow.

There is a HOWTO that describes the Linux 'boot-up sequence' dubbed
"From-Power-Up-To-Bash-Prompt HOWTO".
"The UNIX and Internet Fundamentals HOWTO" may also be useful. Get them all
at http://www.tldp.org/docs.html#howto

> You probably want to know about the init sequence, not the boot-up
> sequence. Booting just involves getting the kernel running and starting
the
> init process. The init process (normally, and we can easily neglect the
> exceptions for the moment) is governed by the directives in /etc/inittab.
> Typically, these directives involve a three-step init process:

Before initialising any scripts, init looks for a line in inittab that
defines it's default runlevel. This
should be something like: "id:5:initdefault:" in your case. It then runs an
initialisation script...

>          1. Init into single-user more and run a script. On my systems,
and
> pretty much every Linux system I've ever sern, this is a script called
rcS.
> Its location varies a bit; on my systems, the coverning line reads
> "si::sysinit:/etc/init.d/rcS". This script in turn runs other scripts; if
> you understand shell scripting, you can follow the sequence by reading the
> scripts.

On RedHat, the initialisation script is actually /etc/rc.d/rc.sysinit, so
you will have a line simillar to 'si::sysinit:/etc/rc.d/rc.sysinit' in your
inittab file...

>          2. Init into normal multi-user mode (governed by a runlevel
> specification). This works the same way as step 1, except init runs a
> different script, again as specified in inittab for the default or chosen
> runlevel. On my systems, it is a line like "l2:2:wait:/etc/init.d/rc 2" --
> which says run the script /etc/init.d/rc and pass to it the argument "2".
>
>          3. Run other processes specified for the chosen or default
> runlevel. Typically these are just the tty processes that allow for
console
> logins (look for lines like "1:2345:respawn:/sbin/getty 38400 tty1"), but
> some distros use this step to run an X-based login process like xdm or to
> run consoles on serial ports.

Redhat runs mingetty instead which is a minimal getty for consoles, so you
might see a few lines like:
"l:2345:respawn:/sbin/mingetty tty1"

The last line in inittab reads "x:5:respawn:/etc/X11/prefdm -nodaemon", this
is actually a shell script
that runs xdm on tty7 in most cases

> I'm not sure if there is a general turorial on the boot/init process, but
> were I looking for one, I'd look through the HowTos at (for example)
> www.linuxdoc.org .

The HOWTOs recommended above should do the trick ;-)

Sorry about the attention-to-detail (if I may say) on RedHat Ray, I'm just
trying to make
CR feel at home with his box ;-)

--Arthur--

> --
> -------------------------------------------"Never tell me the
odds!"--------
> Ray Olszewski -- Han Solo
> Palo Alto, California, USA   ray@comarre.com
> --------------------------------------------------------------------------
-----
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
>

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Can't see my drives

[cr]

On Monday 26 August 2002 07:53, Arthur Othieno wrote:
> Subject: Re: Can't see my drives
>
> > Selected responses only, below.
> >


> > >As a related question, is there anywhere on the Internet a page that
> > > explains
> > >(in simple language) what the boot-up sequence of Linux is (and XFree86
> > > for that matter) and what files get read in what order?   Man pages are
> > > always much too detailed and limited in scope to be easy to follow.
>
> There is a HOWTO that describes the Linux 'boot-up sequence' dubbed
> "From-Power-Up-To-Bash-Prompt HOWTO".
> "The UNIX and Internet Fundamentals HOWTO" may also be useful. Get them all
> at http://www.tldp.org/docs.html#howto

Thanks!   I looked in linuxdocs.org but either missed them or they're not 
there.    I'll get them.


>
> On RedHat, the initialisation script is actually /etc/rc.d/rc.sysinit, so
> you will have a line simillar to 'si::sysinit:/etc/rc.d/rc.sysinit' in your
> inittab file...

I did find sysinit, and it's biiig... still, it's comprehensible.  (Just  :)


>
> > I'm not sure if there is a general turorial on the boot/init process, but
> > were I looking for one, I'd look through the HowTos at (for example)
> > www.linuxdoc.org .
>
> The HOWTOs recommended above should do the trick ;-)
>
> Sorry about the attention-to-detail (if I may say) on RedHat Ray, I'm just
> trying to make
> CR feel at home with his box ;-)
>
> --Arthur--

Thanks guys for the help, I've been running Linux for a while now but never 
really learnt the basics of it -  I guess it's time I did so (rather than 
just frantically scrabbling around when something stops working  :)

cr

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs