Need help with fstab entry PCLOS2009.2

[teddyred]

I've had to reinstall 2009 from a remaster.  Now the cdrom isn't recognized and automounted as before.  Have tried remedying this in PCC with no luck.  Apparently the /etc/fstab entry needs to be edited.  Here is a copy of my fstab folder:

_________________________________________________________________________ 
# Entry for /dev/hda1 :
UUID=71354dda-c243-4c67-ae73-485ab8873a7e / ext3 defaults 1 1
none /dev/pts devpts mode=0620 0 0
# Entry for /dev/hda3 :
UUID=d33ff4f9-b71b-46e8-8e0f-b734aa36fe02 /home ext3 defaults 1 2
/dev/hdd /media/cdrom auto umask=0,user,iocharset=utf8,sync,ro 0 0
# Entry for /dev/hdb1 :
UUID=474AD2192ED32F2F /media/hdb1 ntfs-3g user 0 0
none /proc proc defaults 0 0
# Entry for /dev/hda2 :
UUID=31351f88-5b8c-4c8e-b6d7-2652945ccdb3 swap swap defaults 0 0

____________________________________________________________________________

Sure would appreciate help with this.

teddyred

[tschommer]

# Entry for /dev/hda1 :
UUID=71354dda-c243-4c67-ae73-485ab8873a7e / ext3 defaults 1 1
none /dev/pts devpts mode=0620 0 0
# Entry for /dev/hda3 :
UUID=d33ff4f9-b71b-46e8-8e0f-b734aa36fe02 /home ext3 defaults 1 2
/dev/hdd /media/cdrom auto umask=0,user,iocharset=utf8,sync,ro 0 0
# Entry for /dev/hdb1 :
UUID=474AD2192ED32F2F /media/hdb1 ntfs-3g user 0 0
none /proc proc defaults 0 0
# Entry for /dev/hda2 :
UUID=31351f88-5b8c-4c8e-b6d7-2652945ccdb3 swap swap defaults 0 0

teddyred, I see you have an entry for the cdrom. Try commenting it out:

# /dev/hdd /media/cdrom auto umask=0,user,iocharset=utf8,sync,ro 0 0

Save, reboot and see if it's okay. I have no entries for CD/DVD devices in my fstab, so it should work fine.

Fingers crossed

Torsten

[Old-Polack]

I've had to reinstall 2009 from a remaster.  Now the cdrom isn't recognized and automounted as before.  Have tried remedying this in PCC with no luck.  Apparently the /etc/fstab entry needs to be edited.  Here is a copy of my fstab folder:

_________________________________________________________________________ 
# Entry for /dev/hda1 :
UUID=71354dda-c243-4c67-ae73-485ab8873a7e / ext3 defaults 1 1
none /dev/pts devpts mode=0620 0 0
# Entry for /dev/hda3 :
UUID=d33ff4f9-b71b-46e8-8e0f-b734aa36fe02 /home ext3 defaults 1 2
/dev/hdd /media/cdrom auto umask=0,user,iocharset=utf8,sync,ro 0 0
# Entry for /dev/hdb1 :
UUID=474AD2192ED32F2F /media/hdb1 ntfs-3g user 0 0
none /proc proc defaults 0 0
# Entry for /dev/hda2 :
UUID=31351f88-5b8c-4c8e-b6d7-2652945ccdb3 swap swap defaults 0 0

____________________________________________________________________________

Sure would appreciate help with this.

teddyred

Put a # in front of the /dev/hdd line, then save the file.

[teddyred]

Thanks for the replies torsten & OP..........
Have tried both suggestions and I get an 'access denied' error message each time attempting to save the changes.
And doing this as 'root'.  Just won't let me edit fstab.

teddyred

[tschommer]

teddyred,

I'm not sure I get what you did exactly.

Open a console (or press <alt><f2>), and enter kdesu kwrite /etc/fstab, enter your root password and make the changes as described by O-P and myself (same thing actually). Save the file, reboot and check it out.

You say you get an "access denied" message, but you're doing this as "root"? Root should be able to do it all, so I'm sure I'm misunderstanding something...

[teddyred]

teddyred,

You say you get an "access denied" message, but you're doing this as "root"? Root should be able to do it all, so I'm sure I'm misunderstanding something...

tschommer, yes I tried to undertake these actions signed in as ´root´.  I didn´t understand the access denied either.
Now my problems have multiplied.  When rebooting I get an ´out of range´ notice on the monitor.  So I guess I´ll
have to try a reinstall.

[Old-Polack]

teddyred,

You say you get an "access denied" message, but you're doing this as "root"? Root should be able to do it all, so I'm sure I'm misunderstanding something...

tschommer, yes I tried to undertake these actions signed in as ´root´.  I didn´t understand the access denied either.
Now my problems have multiplied.  When rebooting I get an ´out of range´ notice on the monitor.  So I guess I´ll
have to try a reinstall.

Highly doubtful you need to reinstall. The out of range signal means you are getting no signal from the graphics card. You may have a bad physical connection somewhere. Could be the cable or the pin connections with the video slot, if it's a separate card. While you're at checking things, check the connections to the hard drive too.

Try booting the live CD to see if you get a video signal from that.

[teddyred]

Thanks, OP..........
I have reinstalled 2009.2 and everything is stable with no 'video out of range' alert.  In the process now of getting everything set back up.  In doing the reinstall, I formatted /home so I'll start with a clean slate.  My previous /home is saved on another partition so I'm debating whether to try to move it wholly or piecemeal to the new /home just created.  Don't want to use any files from the previous setup that might be tainted.  So as I progress with it, I'll shout if I encounter any problems.  Thanks for your expertise and helpfulness.

teddyred

[melodie]

Hi,

My guess would be that you may have damaged some file and directory permissions. If you check that the permissions in the source directory (old home of your's) are 755 ( drwxr-xr-x) for the directories and 644 (-rw-r--r--)for the files, it might come out ok.

There are some command lines to make all directories and subdirectories get the same perms, and another for the files to get all the 644 perms. Are there some executable files in the home user directory in KDE version ? I am not fully sure of this, but it may not be too difficult to fix incase there is one.

Do you want to invoke "ls -l" in the console from within the related directories ?

[teddyred]

Hi,

My guess would be that you may have damaged some file and directory permissions. If you check that the permissions in the source directory (old home of your's) are 755 ( drwxr-xr-x) for the directories and 644 (-rw-r--r--)for the files, it might come out ok.

There are some command lines to make all directories and subdirectories get the same perms, and another for the files to get all the 644 perms. Are there some executable files in the home user directory in KDE version ? I am not fully sure of this, but it may not be too difficult to fix incase there is one.

Do you want to invoke "ls -l" in the console from within the related directories ?

Thanks, melodie, but I have reinstalled from a remaster I created a couple months ago.  And all seems to be OK at this time.  I treasure my 2009 setup and am so relieved to be able to reinstall.  I have KDE4 installed on a separate drive and have used it some, but dread the thought of having to use it primarily.  I will stick with my KDE 3 installation as long as possible.  And I have added ´youcantoo´s frozen repo to synaptic in case I need to reinstall anything.
Again thanks to you and all the others who tirelessly respond to our requests.  You are a wonderful group.

teddyred

[tschommer]

teddyred, just out of curiosity - could you please post the contents of your current /etc/fstab file?

[melodie]

Just incase, would you also give us the content of the file /etc/PolicyKit/PolicyKit.conf ?

[teddyred]

teddyred, just out of curiosity - could you please post the contents of your current /etc/fstab file?

Torsten, here is the contents of /etc/fstab after reinstalling the remaster.  As I say, the system is
working well now.  No hiccups yet.  Thanks.

________________________________________________________________________________________________________

# Entry for /dev/hda1 :
UUID=71354dda-c243-4c67-ae73-485ab8873a7e / ext3 defaults 1 1
none /dev/pts devpts mode=0620 0 0
# Entry for /dev/hda3 :
UUID=d33ff4f9-b71b-46e8-8e0f-b734aa36fe02 /home ext3 defaults 1 2
# Entry for /dev/hdb1 :
UUID=474AD2192ED32F2F /media/hdb1 ntfs-3g user 0 0
none /proc proc defaults 0 0
# Entry for /dev/hda2 :
UUID=31351f88-5b8c-4c8e-b6d7-2652945ccdb3 swap swap defaults 0 0

[teddyred]

Just incase, would you also give us the content of the file /etc/PolicyKit/PolicyKit.conf ?

Melodie, here is the contents of etc/PolicyKit/PolicyKit.conf after reinstalling the remaster.   Thanks again for your interest.

_______________________________________________________________________________________________



<?xml version="1.0" encoding="UTF-8"?> <!-- -*- XML -*- -->

<!DOCTYPE pkconfig PUBLIC "-//freedesktop//DTD PolicyKit Configuration 1.0//EN"
"http://hal.freedesktop.org/releases/PolicyKit/1.0/config.dtd">

<!-- See the manual page PolicyKit.conf(5) for file format -->

<config version="0.1">
<match action="org.freedesktop.hal.storage.*">
<return result="yes"/>
</match>
<match action="hal-storage-mount-fixed-extra-options">
<return result="yes" />
</match>
<match action="hal-storage-mount-removable-extra-options">
<return result="yes" />
</match>
<match action="org.freedesktop.hal.power-management.lcd-panel">
<return result="yes"/>
</match>
<match action="org.freedesktop.hal.power-management.cpufreq">
<return result="yes"/>
</match>
<match action="org.freedesktop.hal.power-management.shutdown">
<return result="yes"/>
</match>
<match action="org.freedesktop.hal.power-management.shutdown-multiple-sessions">
<return result="yes"/>
</match>
<match action="org.freedesktop.hal.power-management.reboot">
<return result="yes"/>
</match>
<match action="org.freedesktop.hal.power-management.reboot-multiple-sessions">
<return result="yes"/>
</match>
<match action="org.freedesktop.hal.power-management.set-powersave">
<return result="yes"/>
</match>
<match action="org.freedesktop.hal.power-management.suspend">
<return result="yes"/>
</match>
<match action="org.freedesktop.hal.power-management.hibernate">
<return result="yes"/>
</match>
<match action="org.freedesktop.hal.power-management.light-sensor">
<return result="yes"/>
</match>
<match action="org.freedesktop.hal.power-management.keyboard-backlight">
<return result="yes"/>
</match>
</config>

[melodie]

Code: [Select]

<?xml version="1.0" encoding="UTF-8"?> <!-- -*- XML -*- -->

<!DOCTYPE pkconfig PUBLIC "-//freedesktop//DTD PolicyKit Configuration 1.0//EN"
"http://hal.freedesktop.org/releases/PolicyKit/1.0/config.dtd">

<!-- See the manual page PolicyKit.conf(5) for file format -->

<config version="0.1">
<match action="org.freedesktop.hal.storage.*">
<return result="yes"/>
</match>
Just after this part add this:

Code: [Select]

<match action="org.freedesktop.hal.storage.mount-removable">
<return result="yes"/>
</match>
It will help for several things. USB devices and cameras connected a USB Mass Storage as well.

For the fstab, here is a model you can use:
http://melodie.tyruiop.org/PCLinuxOS/ElementsAjoutes/HomeRoot/ModelesConf/fstab.modele

Instead of naming the device /dev/hdc or /dev/hdd or else, which may change if you add other devices (hdd or usb... ) you would use the fix naming from /dev : cdrom and so on.

Code: [Select]

/dev/cdrom             /media/cd   auto    ro,user,noauto,unhide   0      0
/dev/dvd               /media/dvd  auto    ro,user,noauto,unhide   0      0
/dev/fd0               /media/fl   auto    user,noauto             0      0
auto option : will detect the fs type. ro : you can't write on CD's that are allready burned... the rest of the options are fully tested and should not bring you problems. You just need to check what directory exists under /media, that will be used as a mount point. You might prefer  "ro,user,auto,unhide" instead of " ro,user,noauto,unhide".

It's possible that just the PolicyKit.conf modification will be enough... until Xorg 1.8 at least.