Find the answer to your Linux question:
Page 2 of 3 FirstFirst 1 2 3 LastLast
Results 11 to 20 of 22
Originally Posted by CodeRoot What do these commands yield? (as root): grep subfs /proc/modules /proc/mounts /var/log/boot.msg No output, just next line grep subfs /var/log/messages | tail No output, just next ...
  1. #11
    Just Joined!
    Join Date
    Aug 2006
    Posts
    8

    Unhappy



    Quote Originally Posted by CodeRoot
    What do these commands yield? (as root):

    grep subfs /proc/modules /proc/mounts /var/log/boot.msg
    No output, just next line

    grep subfs /var/log/messages | tail
    No output, just next line

    grep subfs /var/log/warn | tail
    No output, just next line

    udevinfo -d | grep -A 6 block
    # udevinfo -d | grep -A 6 block
    /block/hda=/dev/hda
    /block/hda/hda1=/dev/hda1
    /block/hda/hda2=/dev/hda2
    /block/hda/hda5=/dev/hda5
    /block/hda/hda6=/dev/hda6
    /block/hda/hda7=/dev/hda7
    /block/hdc=/dev/hdc
    /block/hdd=/dev/hdd
    /class/input/input0/event0=/dev/input/event0
    /class/input/input1/event1=/dev/input/event1
    /class/input/input3/event2=/dev/input/event2
    /class/input/input3/mouse0=/dev/input/mouse0
    /class/input/mice=/dev/input/mice
    /class/misc/device-mapper=/dev/device-mapper

    And finally, last ( but not least ? )...
    ls -al /sys/block/hd*[/code]
    # ls -al /sys/block/hd*
    /sys/block/hda:
    total 0
    drwxr-xr-x 8 root root 0 2006-08-29 21:22 .
    drwxr-xr-x 29 root root 0 2006-08-29 21:22 ..
    -r--r--r-- 1 root root 4096 2006-08-29 21:22 dev
    lrwxrwxrwx 1 root root 0 2006-08-29 21:22 device -> ../../devices/pci0000:00/0000:00:06.0/ide0/0.0
    drwxr-xr-x 2 root root 0 2006-08-30 01:22 hda1
    drwxr-xr-x 2 root root 0 2006-08-30 01:22 hda2
    drwxr-xr-x 2 root root 0 2006-08-30 01:22 hda5
    drwxr-xr-x 2 root root 0 2006-08-30 01:22 hda6
    drwxr-xr-x 2 root root 0 2006-08-30 01:22 hda7
    drwxr-xr-x 3 root root 0 2006-08-29 21:22 queue
    -r--r--r-- 1 root root 4096 2006-08-29 21:22 range
    -r--r--r-- 1 root root 4096 2006-08-29 21:22 removable
    -r--r--r-- 1 root root 4096 2006-08-29 21:22 size
    -r--r--r-- 1 root root 4096 2006-08-29 21:22 stat
    --w------- 1 root root 4096 2006-08-29 21:22 uevent

    /sys/block/hdc:
    total 0
    drwxr-xr-x 3 root root 0 2006-08-30 01:22 .
    drwxr-xr-x 29 root root 0 2006-08-29 21:22 ..
    -r--r--r-- 1 root root 4096 2006-08-29 21:22 dev
    lrwxrwxrwx 1 root root 0 2006-08-29 21:22 device -> ../../devices/pci0000:00/0000:00:06.0/ide1/1.0
    drwxr-xr-x 3 root root 0 2006-08-29 21:22 queue
    -r--r--r-- 1 root root 4096 2006-08-30 01:29 range
    -r--r--r-- 1 root root 4096 2006-08-29 21:22 removable
    -r--r--r-- 1 root root 4096 2006-08-30 01:22 size
    -r--r--r-- 1 root root 4096 2006-08-30 01:29 stat
    --w------- 1 root root 4096 2006-08-30 01:29 uevent

    /sys/block/hdd:
    total 0
    drwxr-xr-x 3 root root 0 2006-08-30 01:22 .
    drwxr-xr-x 29 root root 0 2006-08-29 21:22 ..
    -r--r--r-- 1 root root 4096 2006-08-29 21:22 dev
    lrwxrwxrwx 1 root root 0 2006-08-29 21:22 device -> ../../devices/pci0000:00/0000:00:06.0/ide1/1.1
    drwxr-xr-x 3 root root 0 2006-08-29 21:22 queue
    -r--r--r-- 1 root root 4096 2006-08-30 01:29 range
    -r--r--r-- 1 root root 4096 2006-08-29 21:22 removable
    -r--r--r-- 1 root root 4096 2006-08-30 01:22 size
    -r--r--r-- 1 root root 4096 2006-08-30 01:29 stat
    --w------- 1 root root 4096 2006-08-30 01:29 uevent

  2. #12
    Banned CodeRoot's Avatar
    Join Date
    Sep 2005
    Posts
    567
    O.K. - one more time...

    Code:
    find /lib -name "subfs*"
    /sbin/modprobe -l | grep subfs
    The reason for all of the various commands is basically just to get an idea of the "state of things" on your system (with regard to 'udev' and 'subfs'). Some of the commands are a bit redundant, but it's better than doing a "back and forth" - one command at a time - "O.K., now try this" - fourteen times (or whatever)... If you would like more [specific] information about what all this data tells me - let me know...

    I am thinking you may be missing a kernel module ('subfs', namely).

    Please see:

    Code:
    man submount
    If the 'find' command (above) yields [something like '/lib/modules/*/*/subfs.ko'], you have it. Otherwise, you probably don't...

    If you don't have it -- try changing these lines in your 'fstab' file:

    Code:
    /dev/hdc /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
    /dev/hdd /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
    to:

    Code:
    /dev/hdc /media/dvdrecorder udf ro,user,noauto,unhide 0 0
    /dev/hdd /media/cdrecorder iso9660 ro,user,noauto,unhide,utf8 0 0
    With this, you will have to mount and unmount them manually:

    Code:
    mount /media/dvdrecorder
    mount /media/cdrecorder
    Code:
    umount /media/dvdrecorder
    umount /media/cdrecorder

  3. #13
    Just Joined!
    Join Date
    Aug 2006
    Posts
    8
    Quote Originally Posted by CodeRoot
    O.K. - one more time...

    Code:
    find /lib -name "subfs*"
    /sbin/modprobe -l | grep subfs
    The reason for all of the various commands is basically just to get an idea of the "state of things" on your system (with regard to 'udev' and 'subfs'). Some of the commands are a bit redundant, but it's better than doing a "back and forth" - one command at a time - "O.K., now try this" - fourteen times (or whatever)... If you would like more [specific] information about what all this data tells me - let me know...

    I am thinking you may be missing a kernel module ('subfs', namely).
    How could it just disapear? I thought only windoze played such games.

    Code:
    mount /media/dvdrecorder
    mount /media/cdrecorder
    Code:
    umount /media/dvdrecorder
    umount /media/cdrecorder
    PC is not accepting that.
    # mount /media/cdrecorder
    mount: unknown filesystem type 'subfs

  4. #14
    Banned CodeRoot's Avatar
    Join Date
    Sep 2005
    Posts
    567
    Quote Originally Posted by new2nix
    How could it just disapear?
    We don't know this, yet. But, I believe the commands at the top of my last post would give us a bit of worthwhile information...

    Quote Originally Posted by new2nix
    PC is not accepting that.
    You have to change your 'fstab' file before you try the commands at the bottom of my last post...

    Or, you can try "explicit" commands:

    Code:
    mount -t udf -o ro,user,noauto,unhide /dev/hdc /media/dvdrecorder
    mount -t iso9660 -o ro,user,noauto,unhide,utf8 /dev/hdd /media/cdrecorder
    Please see:

    Code:
    man mount

  5. #15
    Just Joined!
    Join Date
    Sep 2006
    Posts
    4

    Red face Thanks!

    Quote Originally Posted by CodeRoot
    O.K. - one more time...

    Code:
    find /lib -name "subfs*"
    /sbin/modprobe -l | grep subfs
    The reason for all of the various commands is basically just to get an idea of the "state of things" on your system (with regard to 'udev' and 'subfs'). Some of the commands are a bit redundant, but it's better than doing a "back and forth" - one command at a time - "O.K., now try this" - fourteen times (or whatever)... If you would like more [specific] information about what all this data tells me - let me know...

    I am thinking you may be missing a kernel module ('subfs', namely).

    Please see:

    Code:
    man submount
    If the 'find' command (above) yields [something like '/lib/modules/*/*/subfs.ko'], you have it. Otherwise, you probably don't...

    If you don't have it -- try changing these lines in your 'fstab' file:

    Code:
    /dev/hdc /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
    /dev/hdd /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
    to:

    Code:
    /dev/hdc /media/dvdrecorder udf ro,user,noauto,unhide 0 0
    /dev/hdd /media/cdrecorder iso9660 ro,user,noauto,unhide,utf8 0 0
    With this, you will have to mount and unmount them manually:

    Code:
    mount /media/dvdrecorder
    mount /media/cdrecorder
    Code:
    umount /media/dvdrecorder
    umount /media/cdrecorder
    I came around here, in search of a solution to exactly the same problem. Everytime I update Suse, and I did that a lot from release 8.0 onwards, it appears that they have changed something in the removable disk mounting stuff. Without doing it properly, that is. The lines you gave here just did the trick!
    I saw no hurah message from new2nix, so here it is from me.

    Thanks a lot!

  6. #16
    Banned CodeRoot's Avatar
    Join Date
    Sep 2005
    Posts
    567

    Smile

    Quote Originally Posted by mumsoft
    I came around here, in search of a solution to exactly the same problem. Everytime I update Suse, and I did that a lot from release 8.0 onwards, it appears that they have changed something in the removable disk mounting stuff. Without doing it properly, that is. The lines you gave here just did the trick!
    I saw no hurah message from new2nix, so here it is from me.

    Thanks a lot!
    I am happy that you found it useful. You are very welcome!

  7. #17
    Just Joined!
    Join Date
    Jan 2007
    Posts
    1
    I came here for the same problem on SuSe as well, and it works perfectly now --Thanks CodeRoot!!

  8. #18
    Just Joined!
    Join Date
    Aug 2006
    Posts
    8
    Quote Originally Posted by mumsoft
    I saw no hurah message from new2nix, so here it is from me.

    Thanks a lot!
    Because it didn't work for me.

    I followed the instructions I was given, so that /etc/fstab now reads ;
    /dev/hdc /media/dvdrecorder udf ro,user,noauto,unhide 0 0
    /dev/hdd /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocha rset=utf8 0 0


    Rebooted (months of reboots), and when running the mount command I was given I still get errors.

    >mount /media/dvdrecorder
    mount: wrong fs type, bad option, bad superblock on /dev/hdc,
    missing codepage or other error
    In some cases useful info is found in syslog - try
    dmesg | tail or so

    (Root or user. Same result.)

    Also, nobody seems to understand that DVD's do play. I watch movies all the time. How is that working if the disk (dvd) isn't mounted? Or maybe I'm just not explaining it enough.

  9. #19
    Just Joined! hailgautam's Avatar
    Join Date
    Feb 2007
    Posts
    1
    I was not able to view my cddirve, so after some research i appended the following lines to fstab.



    Code:
    /dev/hdc /media/dvdrecorder udf ro,user,noauto,unhide 0 0 
    /dev/hdd /media/cdrecorder iso9660 ro,user,noauto,unhide,utf8 0 0
    but then onwards i am not able to login to GNOME at all, even after I deleted those lines, I am still not able to login and getting return to the login Screen.

    I am able to login throug "Root" and also able to login to my id from FVWM.

    When I am trying to login from KDE, it is giving the following error message:

    There was an error setting up inter-process communication for KDE. The message returned by the system was:

    Could not read network connection list:
    home/gomzy/.DCOPserver_linux-xqmk_20
    Please check that "dcopserver" program is running.....

  10. #20
    Banned CodeRoot's Avatar
    Join Date
    Sep 2005
    Posts
    567
    Quote Originally Posted by bryvo
    I came here for the same problem on SuSe as well, and it works perfectly now --Thanks CodeRoot!!
    ... very welcome...

Page 2 of 3 FirstFirst 1 2 3 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •