On 02/05/2010 09:12 PM, Bob S wrote:
On Friday 05 February 2010 03:54:40 David C. Rankin wrote:
On 02/04/2010 11:11 PM, Bob S wrote:
Hello SuSE people.
Running 11.2 with KDE4.3.5. I have several different OS's on my machine and several different partitions which are common to them all. ie. /datastorage, /mediastorage, /backup etc which I can access from each OS. Each of those are listed in my 11.2 fstab. I had the same setup when I tried 11.1.
I am unable to mount them in 11.2 getting the message "Hal Device Volume Permission denied. /dev/hda? is listed in fstab but refuses to mount" David> > was able to get around that in 11.1 (something aboutPolicy Kit) but darned if I can remember what it was that I did.
Would some kind soul out there jog the gray matter and put me on the right track?
<snip>
David,
As per my original post in the second paragraph above, that is the message I get. However, nothing in my fstab is /dev/hd? They are all mounted by Label as per below except for two fat partitions and swap which are designated as /dev/sd??.
LABEL=11.2 / ext3 acl,user_xattr 1 1 LABEL=11.2home /home ext3 acl,user_xattr 1 2 LABEL=11.2tmp /tmp ext3 acl,user_xattr 1 2 LABEL=11.2usr /usr ext3 acl,user_xattr 1 2 LABEL=11.2var /var ext3 acl,user_xattr 1 2 LABEL=11.0 / ext3 acl,user_xattr 1 1 LABEL=11.0home /11.0home ext3 acl,user_xattr 1 2 LABEL=11.0var /11.0var ext3 acl,user_xattr 1 2 LABEL=11.0tmp /11.0tmp ext3 acl,user_xattr 1 2 /dev/disk/by-id/scsi-SATA_ST3250824AS_4ND4ZTYJ-part3 swap swap defaults 0 0 LABEL=10.2 /10.2 ext3 defaults 1 2 LABEL=10.2home /10.2home ext3 defaults 1 2 LABEL=10.2tmp /10.2tmp ext3 defaults 1 2 LABEL=10.2var /10.2var ext3 defaults 1 2 LABEL=backup /backup ext3 defaults 1 2 LABEL=datastorage /datastorage ext3 defaults 1 2 /dev/sdc7 /fat vfat users,gid=users,umask=0002,utf8=true 0 0 LABEL=mediadata /mediadata ext3 defaults 1 2 LABEL=storage /storage ext3 defaults 1 2 /dev/sda1 /windows fat users,gid=users,umask=0002,utf8=true 0 0 LABEL=workspace /workspace ext3 defaults 1 2 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0
For more info to think about. All of the partitions in the fstab show up in that left sidebar in Dolphin. That is where I click on them to open them and get the error message. They don't show up in the main root directory in Konqueror at all.
======== notes: /datastorage, /mediastorage, /backup etc which I can access from each OS. Each of those are listed in my 11.2 fstab. ======= Bob, I'm confused (not uncommon), when you boot 11.2, or any of the other OS's, I see that backup, datastorage, and mediadata should be mounted -- period on /backup, /datastorage, and /mediadata (presuming 'mediadata' is actually your 'mediastorage' in disguise ;-) <wild ass guess> When I think about things that could skuttle the mount and cause problems similar to what you are seeing, the number-one thought is that somehow during one of your boots into one of the OS's one, or all, of the drives failed to mount and data got written to the 'mount point' ending up on the / partition under the /backup, /datastorage, and /mediadata 'directories' instead of the actual 'partitions' that is now causing problems in mounting the drives because you have a non-empty mount-point and throws a /dev/sda... error because that is the drive where the partition should have been mounted, but now contains only spurious data. Now I do not know how this is handled with any of the newer suse releases, but in the past, long before the new mystery of hal/dbus/PolicyKit descended upon us -- if you had a partition fail to mount and wrote data to the mount point when no partition was mounted, then when the mount problem was fixed, the next time you actually had a successful mount, the mounted partition would simple "cover up" the underlying data in the mount point/directory and things would simply carry on as normal until you unmounted the partition and did an ls on the mount point only to discover there were still files on the 'unmounted' partition... Now, who knows with the new wizardry. I don't know if this is your problem or not, but a simple way to check is to boot into the OS of your choice and then 'umount' the /backup, /datastorage, and /mediadata partitions and then do a simple 'ls' on the mount point. Clear as mud -- Right??
A little more investigation shows I can open the two fat partitions (/dev/sda1 & /dev/sdc7) but have to give the root password to Dolphin.
I think Carlos nailed this one user/users fat/vfat.. Getting more
curious I open the partitioner and ????? my three drives are designated hda, and hdb (both ide) and sde !!! (sata) And, yes. the drives I can't mount have the little asterisk after them. The note in the "Help" menu mentions something about no-auto or automount, but that is not my case as seen in the fstab above. My 10.2 and 11.0 attributes are exactly like the 11.2 one. So why won't they mount and show up in the "/" directory like the other OS's?
When I started this reply, I was still shady on exactly what you are seeing when you boot and can't get the drives mounted. I'm not saying I can solve it with this additional information, but posting it might help me or someone else get to the bottom of it. I think the following information would help (1) boot, then before you do anything else, give the output of: df -h mount cat /proc/partitions cat /proc/diskstats ls -al /backup ls -al /datastorage ls -al /mediadata (2) Manually unmount 'umount' /backup, /datastorage, and /mediadata, then give the same information df -h mount cat /proc/partitions cat /proc/diskstats ls -al /backup ls -al /datastorage ls -al /mediadata (3) Manually mount /backup, /datastorage, and /mediadata, then give the following: df -h mount cat /proc/partitions cat /proc/diskstats ls -al /backup ls -al /datastorage ls -al /mediadata (4) dmesg output (bzipped if you post it somewhere, if you don't have a site you can post it on, send it to me by email and I'll post it on my site for the community to get to) (5) /var/log/messages (same deal) With all that additional information, hopefully we will be able to discover where the gremlins in your system are hiding. Also, if anybody else can think of additional output that would help diagnose the problem, please chime in. I'm no mount problem guru and Bob could really use the additional help ;-) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org