Can't store files in newly formatted hard disk. Mount point problem?

[CharlesV]

I got a suggestion to use Gnome-Disk-Utility. It worked great on MX and much easier for me as a basic user than other approaches. But I learned much from the various proposed solutions. Appreciate all your help.

Glad to hear you have it resolved, Please mark as solved using the check mark on the top right of the post that resolved it.

[m_pav]

in gparted after right clicking the filesystem and selecting the Label File System option, when the box opens I can just type for example "wd500s" for the western digital disk and it will automatically supply the "/media/shalom/". Is that right?

Correct, but you still need to click the ↵ "Apply changes" button in gparted to save the changes first, then you must close gparted before you try anything with the File Manager because Gparted is set to hide all non-essential storage devices from the OS. Closing Gparted makes them visible again.

After changing the label name, and mounting the file system, I only need to use the command "sudo chown shalom:shalom /media/shalom/wd500s/." With the dot at the end? And that should be it?

Correct for this one action with the proviso the "path" in the command needs to reflect the actual path in use for when you want to do the same with the next drive.

The system will pick up the partition label and use it as the mount point. As it is now, the only thing it has to grab onto is the 128-bit hexadecimal-type UUID, and that's why you're seeing those mind-numbing partition identifiers. Labels just make more sense to us humans

[atomick]

There are some articles out there, as to setting mount points in /media as to being the place to set such mount points. High level suggest this is incorrect. I had one time created a post with step by step after partitioning and format gpart procedure yet think sensored.
high suggest is to as root user and or sudo user

Code: Select all

 cd to  / 
sudo mkdir -p NamePoint       - one could call it anything example :   myDrvE or mybig500 wd500 seag1T
copy your /etc/fstab to  a .sav
use blkid  or sudo blkid -o list  - we want to know the full UUID,  and place this into /etc/fstab   open a line above the last comment swap swap 
write in the UUID  ex:
UUID=fa55c912-...-07b4cfc9a6f   /mybig500    ext4   defaults,data=ordered 0 2       - please note no double quotes around the UUID content for writing to  fstab  here I shortened the whole info solely example.

add more drive UUID's  if your rebuilding a new install and converting from that other OS.            - using ntfs-3g has slight different entry  

I spaced this to show usually 1 space between content with data=ordered for proper ext4 management 0 2 on the end means no fsck at boot and 2 means if errors detected perform at boot fsck after boot drives are checked.

if all good write out the file make sure the /etc/fstab is still owned by root
permissions on this file are commonly 644 or root read/write group read and others read.

/media is for all your portable flash drives usb adaptors and auto mount of new devices plugged into usb ports. cameras mp3 players phones. Not for permanent mounted drive points.

see /dev/disks for appropriate matching if you wish.

so unlike that other OS to check and make sure all is good sudo mount -a will now provide instant access oh one more command we must perform before or after the sudo mount -a
permissions and ownership if in a shell
cd /
sudo chown atomick:atomick /mybig500 - replace myName with your own login account name see its delimited via a one colon. name : name mountPT
sudo chmod 754 /mybig500 - play around with this if so wish 775 or 744 would allow others to read and you own it all
Testing it
cd /mybig500
touch test
ls -la
rm test
Results touch test will open touch a new file called test
ls -la will show it to us by listing
rm test
proves you can read and write to this new mounted drive /mybig500 and its now your own.
this will all be available any and all boot cycle.
man mount
man fstab
man chown
man chmod
all to learn syntax and gain knowledge.
Last note yes you can Short PartUUID or /dev/sdb1 in place of UUID but Linux Likes the whole UUID use in /etc/fstab

[m_pav]

There are some articles out there, as to setting mount points in /media as to being the place to set such mount points. High level suggest this is incorrect.

/media/<username>/<devlabel> is the Debian default for all dynamically mounted content that is not in fstab, so are these high level sources now against Debians default placements?

The OP has not specifically pointed out he's looking out for permanent placements, besides, the choice is totally up to him and no harm is done using the /media/ directory as a top level mount point for non-system storage.

[atomick]

again being a long ago "Sun God" Admin. I've stuck thru such methods has always worked 100% of all time such method root - fs - Mount Point Entries.
also worked with HP-uniix ago as well as many other Hardware OS platforms. So fossilized under the finger.. What works, is the end result. I have a debian image, focus has kept me addicted to MX.

one most very provocative feature of *NIX OS distro's

Always more than one method to perform a process-method and feature. Other Programming languages also provide Features. The addiction to *Nix is that so much can be learned, with the drive to do so provides building blox and wide spread knowledge = the win win
ending any day with a good feeling. Vi fingers shaken after long term doing other works on that other OS yet always been in some sort of Linux Distro dual booting kept the feature many Distro ago with Mint Capture at Beta thru to odd
release issue, And wanting choice to try then the long Term #1 MX. Nothing is perfect yet some contain diamonds once learned. (Snapshot and USB-writers = awesome).
Yet patience and research build ones attachments to their own very customizable Distro value. Since 23.1 MX devo team has pulled off some amazing Challenges
to play with VirtualBox keeps the pond full of fish. (good hardware sets the stage). SS - now works across my AMD7950x3D and amd7945HX device both have nvidia GPU's / no more SS-load to VBox and see the boot start flashing cursor sit there. As well SS deployment to other devices also works. As this Laptop 7945HX installed from
7950x3D Device. All Good! Cheers.

[atomick]

m_pav ! possibly you miss read my info on a scan. Same info mentioned. Yet ubuntu forum seems to have a document reference as some seem to mount drives to /media as a mount point -- less your supporting the comment, True. yes. or more correct to system wide setups.

https://askubuntu.com/questions/125257/ ... hard-drive
See item #57 item-3 in that post. Above info is more correct using the item 2-1 /dev/Device assignment either or is okay with UUID=uniq being same newer reference but you can only find to see this sudo blkid or sudo blkid -o list out put. take it tad further sudo /dev/sda or sudo /dev/sda1 etc.
I'll stick to my knowledge and set my storage drives to a rooted name mount point. as described with a meaning and or reference how in plan.

Life is Grand "Cheers" .