[SOLVED] fstab, chown or chmod - A partition

[Sector11]

As seen here. Busy day yesterday ... 2nd of 2 posts looking for help.

In preparation of moving ahead deleted three partitions /media/5, 6 & 7 and created
/media/5 - my docs, downloads, images, conkys, videos etc etc
/media/6 - darkside root
/media/7 - darkside home
/media/8 - bbq test root
/media/9 - bbq test home
/media/10 - bbq NO-GUI (a future event) Thanks to ppl here

Tried everything with fstab to get 5 thru 10 "owned" by sector11 & read/writable {is that chuckling I hear in the back row?}

chmod and chown are ?? to this noob... it looked like:

sudo chown -hR sector11 ... might be a way to start but:

sudo chown -hR sector11 /dev/sda5
or
sudo chown -hR sector11 /media/sda5

Can I chown a "partition"?

so I cheated: use THOR (Thunar root) and changed permission Group to sector11 R/W

Ummmmmmmmmmm never mind:

Code: Select all

 26 Aug 13 | 12:54:19 ~
    $ sudo chown -hR sector11 /media/sda6
[sudo] password for sector11: 
chown: cannot access ‘/media/sda6’: No such file or directory
 
 26 Aug 13 | 12:54:31 ~
    $ sudo chown -hR sector11 /media/6
 
 26 Aug 13 | 12:55:12 ~
    $ 

- see that's what I get for (continued) searching while asking for help!

[machinebacon]

Too complicated, dear S11.

For this we have udisks, and if it doesn't rock, there's still disk-manager (as root).

Post your fstab please ;)

Edit:

Code: Select all

sudo blkid -o list
sudo fdisk -l
cat /etc/fstab

[Sector11]

@ machinebacon

complicated ... from you ... ?????

udisk I don't know - will research

disk-manager I have: but it doesn't give me ownership ... just mount/unmount and mountpoint - I tried changing Options to sector11 - no go. :(

here you go:

Code: Select all

 
 26 Aug 13 | 14:02:38 ~
    $ sudo blkid -o list
[sudo] password for sector11: 
device                     fs_type    label       mount point                    UUID
---------------------------------------------------------------------------------------------------------------------
/dev/sda5                  ext4                   /media/5                       4e253402-7c18-4346-85ce-4eaa74877cfb
/dev/sda6                  ext4                   /media/6                       e0ab7e4b-aa10-401e-8b41-97de506b48d0
/dev/sda1                  ext4                   /                              4fb35957-ffa5-4011-8cae-a3ed9e293c3b
/dev/sda2                  ext4                   /home                          fabad1fb-6591-4c27-9b50-2720d9589d64
/dev/sda3                  swap                   (not mounted)                  863eb84a-d7bd-46b5-9b60-6717f4baf77d
/dev/sda7                  ext4                   /media/7                       87a28229-79e5-445e-a0f0-64ccbb0ef175
/dev/sda8                  ext4                   /media/8                       367c6683-97cc-452e-8cfb-beb948dd7e3f
/dev/sda9                  ext4                   /media/9                       348d6607-e7cd-4e29-b55d-5298f8b5d870
/dev/sda10                 ext4                   /media/10                      684440b6-4b6c-4082-863b-5bab46e6f21c
/dev/sdb1                  ext4       disk        /media/sector11/disk           abb17351-0de9-45a1-a910-78398f2730c6
 
 26 Aug 13 | 14:02:57 ~
    $ 

Code: Select all

 26 Aug 13 | 14:03:01 ~
    $ sudo fdisk -l
[sudo] password for sector11: 

Disk /dev/sda: 250 GB, 250056737280 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System 
/dev/sda1   *           1        1959    15735636   83  Linux
Warning: Partition 1 does not end on cylinder boundary.
/dev/sda2            1959        3916    15719602   83  Linux
Warning: Partition 2 does not end on cylinder boundary.
/dev/sda3            3916        4439     4200997   82  Linux swap
Warning: Partition 3 does not end on cylinder boundary.
/dev/sda4            4439       30402   208547797    5  Extended
Warning: Partition 4 does not end on cylinder boundary.
/dev/sda5            4439       19843   123732630   83  Linux
Warning: Partition 5 does not end on cylinder boundary.
/dev/sda6           19843       21945    16884315   83  Linux
Warning: Partition 6 does not end on cylinder boundary.
/dev/sda7           21945       24046    16876282   83  Linux
Warning: Partition 7 does not end on cylinder boundary.
/dev/sda8           24047       26148    16876282   83  Linux
Warning: Partition 8 does not end on cylinder boundary.
/dev/sda9           26148       28250    16884315   83  Linux
Warning: Partition 9 does not end on cylinder boundary.
/dev/sda10          28250       30402    17285940   83  Linux
Warning: Partition 10 does not end on cylinder boundary.

Disk /dev/sdb: 250 GB, 250056737280 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System 
/dev/sdb1               1       30402   244204033   83  Linux
Warning: Partition 1 does not end on cylinder boundary.
 
 26 Aug 13 | 14:03:17 ~
    $ 

Code: Select all

 26 Aug 13 | 14:03:39 ~
    $ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>

proc	/proc	proc	defaults	0	0
#Entry for /dev/sda1 :
UUID=4fb35957-ffa5-4011-8cae-a3ed9e293c3b	/	ext4	relatime,errors=remount-ro	0	1
#Entry for /dev/sda5 :
UUID=4e253402-7c18-4346-85ce-4eaa74877cfb	/media/5	ext4	defaults	0	0
#Entry for /dev/sda6 :
UUID=e0ab7e4b-aa10-401e-8b41-97de506b48d0	/media/6	ext4	defaults	0	0
#Entry for /dev/sda7 :
UUID=87a28229-79e5-445e-a0f0-64ccbb0ef175	/media/7	ext4	defaults	0	0
#Entry for /dev/sda8 :
UUID=367c6683-97cc-452e-8cfb-beb948dd7e3f	/media/8	ext4	defaults	0	0
#Entry for /dev/sda9 :
UUID=348d6607-e7cd-4e29-b55d-5298f8b5d870	/media/9	ext4	defaults	0	0
#Entry for /dev/sda10 :
UUID=684440b6-4b6c-4082-863b-5bab46e6f21c	/media/10	ext4	defaults	0	0
#Entry for /dev/sda2 :
UUID=fabad1fb-6591-4c27-9b50-2720d9589d64	/home	ext4	relatime	0	0
UUID=12fdb838-a76f-4f29-a0cf-b5cdc6d379ed	none	swap	sw	0	0
/dev/cdrom	/media/cdrom	udf,iso9660	user,noauto,exec,utf8	0	0

 26 Aug 13 | 14:03:42 ~
    $ 

[pidsley]

Hey again S11.

Can I ask why you think you need or want user access to all those partitions, and why you want to mount them all at once? I understand accessing shared data (your sda5) as user, but the others you don't need to even mount. I'm assuming you're doing all this from sda1 and sda2 -- your root and home in your "normal" install.

For example, I have two installs on this machine. I use a shared data partition at sda6 and a single combined root/home for the first install at sda1. "lsblk" on this machine looks like this:

Code: Select all

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 111.8G  0 disk 
├─sda1   8:1    0    10G  0 part /
├─sda2   8:2    0   1.5G  0 part [SWAP]
├─sda3   8:3    0     1K  0 part 
├─sda5   8:5    0   9.8G  0 part 
└─sda6   8:6    0  90.6G  0 part /media/shared

My fstab in the first install looks like this:

Code: Select all

/dev/sda1   /               ext4    errors=remount-ro 0 1
/dev/sda2   none            swap    sw              0 0
/dev/sda6   /media/shared	ext4	 defaults	0 2

In the other install (on sda5) I also mount sda6 at /media/shared. I don't mount sda5 at all in the first install, or sda1 in the second, unless I need or want to access something there, and then I mount it manually as root.

Can you access your shared data at /media/5 as normal user, once sda5 is mounted there? That's all you really need. The other partitions will take care of themselves when you install on them. You don't need to mount them in your first install, and you certainly don't want to give your normal user access to the root partitions in the other installs.

Does this make sense?

[machinebacon]

^Thanks again pidsley, that's what I thought too :)

@Sector: yes, complicated, because I can not follow why ownership should be changed :) If it is just about accessing data, and you are using udisks alreasy (or udisks2 when you run a newer systemd), things are solved automagically, and via the group identifier GUID.

[Sector11]

Hey guys ... Certainly you can ask, pidsley, and what you say does make sense.

Bit of History:
When I came from W2K to Linux (Ubuntu) I had problems even getting a data partition I could use. So I went about doing what I could - searching and asking. I was angry that "I" couldn't mount (at first) partitions I created, and when I finally could I couldn't read/write to them. At that time I had 3 IDE HDD's here and could not use anything but my / & /home combined 30GB partition on hda1, that really pissed me off. Over 50% of hda1 I could not access let alone the other two HDD's that I couldn't even see.

to continue
My /media/5 will be accessible, as user, by all distros - except the No-GUI whenever it goes in.

At one time I had 12 partitions here, and no external HDD so my backups went to their own partition. At least I have an Ext USB HDD to take care of that problem, it only gets plugged in when it's needed. It use to get mounted as soon as it was plugged in, now for some reason I have to physically mount it, I'll get that changed again -when I get time to research how. No, I'm not asking. :)

I hit that problem again with this change, and it has been so long ago that I forgot how to get them to be mine. Now they are empty, they are mine, if I need them they are set up.

When I use the first two partitions for "darkside", media/6 & 7, I will set them up properly in disk-manager and unmount them. But I'll know I can mount them if I want.

Then when a 'test' distro goes in the same process will take place, set them up with disk-man and then unmount them.

The final 16GB partition will be a NO-GUI install when the time comes, and get the same treatment, but it will have everything on the one partition.

None of the above will have access to this system (1 & 2). As long as this works, my wife is happy.

This way - if I want to store something on them until the time comes to put a disto there I can - it's my option.

machinebacon

Code: Select all

 26 Aug 13 | 23:34:09 ~
    $ ser udisks
p   gir1.2-udisks-2.0                                  - GObject based library to access udisks2 - introspection data 
i A libudisks2-0                                       - GObject based library to access udisks2                      
p   libudisks2-dev                                     - GObject based library to access udisks2 - development files  
p   udisks                                             - storage media interface                                      
p   udisks-doc                                         - storage media interface - documentation                      
p   udisks-glue                                        - simple automount daemon with support for user-defined actions
i A udisks2                                            - D-BUS service to access and manipulate storage devices       
p   udisks2-doc                                        - udisks2 documentation                                        
 
 26 Aug 13 | 23:34:29 ~
    $ udisks2
bash: udisks2: command not found
 
 26 Aug 13 | 23:34:44 ~
    $ sudo udisks2
sudo: udisks2: command not found
 
 26 Aug 13 | 23:34:50 ~
    $ 

Never realized I had that installed ... and it's not working ... I'm guessing on this system I need udisks not udisks2 that BBQ uses. (that's going in tomorrow, hopefully, with darkside)

Update
udisks - installed and works ... tomorrow I read the man page. Looks like it's more powerful than disk-manager, that would be nice - set up some aliases & dump disk-manager.

[machinebacon]

udisks is a kind of state-of-the-art disk manager (if you check #! you see it comes with udisk and upower -- in combination with policykit you can have stuff mounted without password, or reboot/shutdown/suspend, where we needed dbus --send stuff in the past)

As for your automounting of USB devices - install the package "usbmount".

Good night ;)

[hinto]

FWIW,
/media is generally where say, cd/dvd, usb drives are mounted.
/mnt, /net are generally automounter. (for nfs/afs locations)
More "permanent" partitions are mounted somewhere meaningful. /data?

Nothing is really set in stone, tho,
-Hinto

[wuxmedia]

I'm lazy - I normally mount stuff in $HOME/data.
With whatever permissions horror that entails 8)

[hinto]

^yep.. That's a good choice,too.
Someplace other than /media keeps me sane for non-removable disks.
-Hinto

[pidsley]

Nothing is really set in stone, tho,
-Hinto

Exactly. I mount things manually, so I put them where I want. I hate these stupid "rules" about where things are supposed to be mounted.

[hinto]

..and don't forget gvfs-mount puts things in ~/.gvfs
Go figure.

At one time everything not local went to a subdirectory in /mnt.

-Hinto

[gurtid]

I manually mount at /tmp so that no tidy up is required.

[Sector11]

FWIW,
/media is generally where say, cd/dvd, usb drives are mounted.
/mnt, /net are generally automounter. (for nfs/afs locations)
More "permanent" partitions are mounted somewhere meaningful. /data?

Nothing is really set in stone, tho,
-Hinto

Yea I know about /mnt too. It's a super bad habit from my Ubuntu days that I never remember to shake ...
disk-manager would make /media/ to /mnt/ changes a snap, that's not the problem ...

I have so many instances of

Code: Select all

cd /media/5/<directory>

in various files various locations
it's going to be a chore changing them all ...

Other than one 16GB USB stick (ntfs - for use in the TV) everything I have is ext4

[pidsley]

^ There is no reason to change them. It's your system, you can mount things wherever you want.

[hinto]

^don't forget symlinks, too. If you do change the mount points, symlinking to them can ease the transition.
-Hinto

[Sector11]

Nothing is really set in stone, tho,
-Hinto

Exactly. I mount things manually, so I put them where I want. I hate these stupid "rules" about where things are supposed to be mounted.

^ There is no reason to change them. It's your system, you can mount things wherever you want.

Hmmm pidsley, I get the feeling you are playing the devil's advocate in some respects. That's good makes a person think.

It's your second statement that led me down this path in the first place. I got angry that Linux would not let 'me' use my drives and partitions the way I wanted when I didn't have that problem with Win. Of course in time I found out who this "root" was and understood that having 'admin' privileges as a user is not necessarily a good thing.

Still there are people that add their 'user' to the sudoers list anyway. Not this kid, I even like turning off the "xx min" grace period for 'sudo' ... I use a command that requires sudo - I use a password, period.

^don't forget symlinks, too. If you do change the mount points, symlinking to them can ease the transition.
-Hinto

I used symlinks once ... can't remember what for ... I tend to forget things (/media/5/tips-n-tricks - text files help me remember things) ... but it broke somehow ... never used them since ... maybe when changing distros.

I'd rather have direct links ... 'I feel better that way'. I will however change how I do things if I find that I'm doing something wrong that can hurt the system.

[hinto]

Nothing special about symlinks...

Check it out...
Say you take this:

Code: Select all

#Entry for /dev/sda5 :
UUID=4e253402-7c18-4346-85ce-4eaa74877cfb   /media/5   ext4   defaults   0   0

And change it to this:

Code: Select all

#Entry for /dev/sda5 :
UUID=4e253402-7c18-4346-85ce-4eaa74877cfb   /data/5   ext4   defaults   0   0

I didn't mention a /data mount point but it's as good as any. You just create the directory /data/5 and change fstab.
The symlink (since your fingers are used to /media/5) would be:

Code: Select all

ln -s /data/5 /media/5

Then when you have re-taught your fingers to cd /data/5, then you can remove the symlink.

[johnraff]

I used symlinks once ... can't remember what for ... I tend to forget things (/media/5/tips-n-tricks - text files help me remember things) ... but it broke somehow ... never used them since ... maybe when changing distros.

I'd rather have direct links ... 'I feel better that way'. I will however change how I do things if I find that I'm doing something wrong that can hurt the system.

By "direct links" do you mean hard links? If so, remember if you delete a hard link you delete the linked file too. A hard link is like an alternative name for the same place, while a symlink is more like a forwarding address, if that makes any sense.

[bizcuit]

Hiya's Sector ! Welcome to the grill.

Know this is marked as solved but going to add some babble anyway.

I've taken to using a shared data partition for convenience sake. You can definitely chown a mount point. Not seeing any reason why it'd be a problem with uid/gid ( or file permissions), all Debian + grill should be the same as long as you're using the same username across installs.

Debian should have the 1st user and their gid as 1000 default in all of em. It's a partition like any other partition ... So this is a quick babble how to on what I'm getting at.

You'd have to create a mount point for all those partitions in each OS/install you want to set this up with. ie: As root or using sudo ... if you're root, you obviously wouldn't need to add sudo to the following terminal commands. But am going to proceed as if you are using sudo.

Let's say I have an ext4 partition I want to automount in XYZ-linux install and it's on sda5. I decide to call this mount point Data and creating it in /media. You can name yours whatever ya like etc.

Pop open a terminal ...

"sudo mkdir /media/Data"
then next "sudo mount -t ext4 /dev/sda5 /media/Data"
Then "sudo umount /dev/sda5"

That creates the mount point, mounts it and then umounts it. Next in that OS's /etc/fstab file add an entry for it. If doing so as root you of course don't need to add the gksudo ( anal edit: If done as root you'd use gksu, rather than gksudo) and texteditor is the text editor you prefer .. leafpad, gedit, geany etc etc.

ie: "gksudo texteditor /etc/fstab"

Add the entry for that partition, like others have mentioned UUID is the more "correct" way of identifying partitions in fstab. So why not go ahead and do it.

Find the UUID's of your partitions. "sudo blkid" It'll show you the UUID's of the partitions. In this case I'd obviously want the UUID for sda5. Once I've got that info in hand I add an fstab entry like ..

# Shared data on sda5
UUID=6ed81c34-d8e8-1be3-849a-dd4ee44e62e4 /media/Data ext4 defaults 0 2

Now to chown ( change ownership of those mount points, again the one I'm using as an example is /media/Data).

"sudo chown -R yourusername:yourusername /media/Data"

In your case ... seems you'd need to do this (create, mount and unmount mount points and add an fstab entry.) for partitions 5, 7 and 9 in each of the nix OS's/installs you have installed on your pc.

To end it all off ... Just drag and drop those the mount pts you created into the sidepane of thunar or pcmanfm. Not sure if it works the same in other file-managers. An example of doing this with thunar.

Open thunar ... click File System in the lefthand side pane. It opens .. then click on the media directory/folder ( if you created your mount points there). In this example you'd see a directory called Data there. Left click on that directory and drag n drop it into Thunars lefthand side-pane. It'll create a shortcut in the side-pane for accessing Data.

Pcmanfm ... pretty much same thing ... Open the sucker ... there's a search bar up at the top under the menu. In that search bar I typed "/" < For root and hit enter, takes you to the root file system. Then clicked on the media directory ( where I'd created my mount points.) and drag and dropped it into the pcmanfm sidepane.

There ya have it hope it helps you in your quest to tame gnu/nix Sector. Need any clarification about this babble PM me ( or comment )here or in #!ville fellow nixer.