Hi all,
Sorry for the delay, my monitor went down and I've had to move around and dig out another one to replace it, glad to be a geek and have spares. Let me take it a bit at a time,
llivv,
llivv wrote:What file manager are you getting this info from?
I stated before that this is the window which appears when I right click on the drive icon on the desktop. This icon does not appear on the desktop if the drive is not mounted, it will then only appear in the "computer" folder.
llivv wrote:What desktop are you using? Gnome - Kde - XFCE - LXDE?
Very sorry, I forgot to mention that from the start, I simply did a basic default install (apart from manually partitioning the drive), plus Samba server, using the defult Gnome desktop.
llivv wrote:You are able to access the drives as root from the commandline, correct?
I am very new to the commandline in Linux, although I was very used to it in DOS years ago! I had not tried to be honest, but have now looked up the copy command and copied /etc/fstab to /mnt/VideoDrive which worked. ls -l showed it as belonging to root. It did not appear on the drive when the drive icon is clicked. I personally would not have expected it to as they are different folders but this mount directory is confusing me I have to confess. perhaps someone could explain it to me.
llivv wrote:After you get the Owner root and Group root from the (file manager your using)? can you double check to see that the owner and group are still mike:mike as listed when you are root in the terminal...
I have got the same result as before showing as mike:mike
bluesdog
bluesdog wrote:Designate ownership in /etc/fstab with a line like: Code: Select all/dev/hda1 /mnt/hda1 ext3 defaults 0 1
as you can see from my earlier post, the entry in fstab is the same as yours except for the 0/1 at the end of the line. I have changed mine from a 0 to a 1, made the similar change in mtab, shut right down and rebooted and it has made no difference.
bluesdog wrote:Normal user full access to a mount point can be achieved by (root) chown username:group /mountpoint, adding the -R switch if the location already contains files/folders.A typical example: Code: Select allchown -R mike:users /mnt/VideoDrive
again as earlier I have done this and as there are no files in /mnt/VideoDrive to show, I did it from /mnt and it showed /mnt/VideoDrive as being owned by user:group, mike:mike and yet in practice I still cannot use the drive.
bluesdog wrote:When /etc/fstab has been edited correctly, you may test by issuing the (root) command Code: Select allmount -afollowed by Code: Select allmount -l
yep have now done that, thanks. After -l in the list was /dev/hdb1 on VideoDrive type ext3 (rw), excellent, except that nothing has actually changed. Went to the desktop, double clicked drive icon, shows contents as lost + found only as before, right clicked on background, create directory option in dropdown list is still unavailable. Selected properties again and low and behold in permissions nothing has changed, still as detailed before. So I shutdown, rebooted, went back into root terminal and redid mount -l which showed exactly the same line complete with read/write flags and everthing else is still the same.
bluesdog wrote:The command is 'umask', not 'unmask''umask' is not required for ext3 formatted partitions.See man umask for proper useage.
yep, sorry, typo, I did umask not unmask and have since removed it simply leaving "defaults" but it's nice to know that it isn't required for ext3, I'll remember that one, thanks.
Now I'm by now means new to computers although I have only been using Linux for about a year, (mostly using, not exploring unfortunately), so I can fllow pretty well what we have been doing and whyand it seems to me that everything is showing that there should be no problems and that it should be working properly, so I'm stumped.
My next thought, unless anyone has seen something here, is that I have left another partition on hda so that I could install another distro or upgrade later if wanted, so if I re-install on that partition and can then compare the two in case the second install works and maybe find the solution. If it doesn't work properly there either, then at least it will show that nothings corrupted here.