can't put files onto ssd. Looking at gparted, I'm not seeing what is wrong. It's formatted, has a name and a label and I'm stumped

[fritz1]

 

[Trenix25]

Do you get an error when you try to mount this file system? What error do you get when you try to write to it? What does journalctl -xe say when you try to do either of these two things?

Signed,

Matthew Campbell

 

[fritz1]

It says "Could not make folder /media/Big-Place...
I do not know what journalctl -xe is

 

[Condobloke]

journalctl -xe

Copy and paste it into terminal and hit enter.

Copy and paste the result back here in your next post

 

[fritz1]

[jan@ketchup ~]$ journalctl -xe
bash: journalctl: command not found
[jan@ketchup ~]$

My OS doesn't use systemd

 

[Fanboi]

My OS doesn't use systemd

What is your OS? It would help others if you posted OS info at the very least as different distros ship with different utilities and a different way of doing things. I mean Slackware seems very different to the Arch/Debian/Fedora distros I'm more familiar with. Puppy does entirely its own thing (though depending on the base distro, there is some familiarity). So it's handy to know your OS.

Regarding systemd, no problem, you can check kernel message using dmesg. Try to mount the volume, when it fails, run dmesg | tail -n 10 (it should be in the 10 most recent lines, but you can change this number as needed). Also checking dmesg | grep "sdb" may give additional insights.

That said,

Could not make folder /media/Big-Place...

could indicate a permissions thing. It would help to know how you are trying to mount it. I presume in a file manager of sorts.
For a test, as root, try mounting it to /mnt/, a'la mount /dev/sdb1 /mnt/ from the CLI. If that works, you may want to try just creating a mountpoint in /media/ or, if preferred, /media/<your user name> and adding an entry to /etc/fstab/ to mount it. Make sure you add "user" and "rw" to mount options and if you don't want it mounted at startup, "noauto".
You could also check the permissions on /media/ and, if it exists, /media/<your user name>, but I don't see why this would be an issue, since most systems create folders dynamically under the current user for mounting volumes -- again why OS info and mount agent are useful. For example, Thunar will need gvfs to dynamically mount filesystems as a normal user to be enabled (IIRC even with fuse installed).

 

[fritz1]

Thank you, I don't know why I didn't mention it before, I'm using PCLinuxOS.
[jan@ketchup ~]$ dmesg | tail -n 10
[ 46.989580] Bluetooth: RFCOMM ver 1.11
[ 72.947649] Disabled but requested by user space. You should enable Landlock at boot time: https://docs.ker
nel.org/userspace-api/landlock.html#boot-time-configuration
[ 175.869965] EXT4-fs (sdb1): mounted filesystem 36b47d89-3d6b-4e95-890c-fb9e1612cf6e r/w with ordered data m
ode. Quota mode: none.
[ 222.774867] JFS: nTxBlock = 8192, nTxLock = 65536
[ 222.812060] SGI XFS with ACLs, security attributes, realtime, quota, no debug enabled
[ 660.533065] EXT4-fs (sdb1): unmounting filesystem 36b47d89-3d6b-4e95-890c-fb9e1612cf6e.
[ 1132.521631] input: WH2037A (AVRCP) as /devices/virtual/input/input17
[ 4005.818932] input: WH2037A (AVRCP) as /devices/virtual/input/input18
[ 9342.381958] EXT4-fs (sdb1): mounted filesystem 36b47d89-3d6b-4e95-890c-fb9e1612cf6e r/w with ordered data m
ode. Quota mode: none.
[25421.561554] EXT4-fs (sdb1): unmounting filesystem 36b47d89-3d6b-4e95-890c-fb9e1612cf6e.
[jan@ketchup ~]$

I'm puzzled, I can create folders and move files now. Thanks for the help
There is a folder named /Disk that has a padlock on it. I can't seem to do anything with that folder

 

[dos2unix]

Do you know the root password?

Is this a docker container?

 

[Fanboi]

There is a folder named /Disk that has a padlock on it. I can't seem to do anything with that folder

If it's in the root directory and you mean /disk (lowercase) then it's probably the PCLinuxOS version of /media, i.e. a parent directory for dynamic mount points for removable media. The padlock icon appears in most file managers for stuff the current user does not have write permissions for.

 

[Jarret B]

Since you used GParted, the partition is owned by Root. You need to take ownership of the partition to make this work better. See 'https://www.linux.org/threads/lfcs-–-file-permissions.21498/#post-63113' for ownership and file permissions.

 

[fritz1]

This sdd was an internal drive before I change the computer to a nuc form-factor, so now it sits in a box attached by a cable. I don't know what docker is, too many confusing explanations to follow.
Anyway, /Disk with the padlock has disappeared and a new folder which I created when I moved multiple GB in folder to the SDD to clear up space on my internal drive. There's also a new folder called /.trash-500, not really sure what created that one.
Oops, sorry got sidetracked with someones book, thanks

 

[Fanboi]

This sdd was an internal drive before I change the computer to a nuc form-factor, so now it sits in a box attached by a cable. I don't know what docker is, too many confusing explanations to follow.
Anyway, /Disk with the padlock has disappeared and a new folder which I created when I moved multiple GB in folder to the SDD to clear up space on my internal drive. There's also a new folder called /.trash-500, not really sure what created that one.
Oops, sorry got sidetracked with someones book, thanks

Re: "too many confusing explanations to follow."

* Most of us have our own methods of investigating issues. I usually check the kernel messages on a fresh boot, reproduce the issue, then look at them again. Some prefer systemd's journalctl as is presents info on additional system components beyond basic kernel stuff.

* Docker is (in this context), it's a containerization software (and full-on platform to split hairs): https://www.docker.com/
(don't worry about it). @dos2unix likely was trying to eliminate the possibility of your running PCLinuxOS in a container, as that would've given some useful insight if you had been.

* The link to permissions posted by @Jarret B was a useful tutorial for not just managing, but understanding permissions as this appeared to be permission-related (well, is still technically, except now your system is managing it properly).
Off-topic: That article is very comprehensive and definitely worth bookmarking. It explains things better than I, or anyone I know, ever could.

Re: Your new questions

* The .trash-<number> is part of the "trashcan" feature. It may safely be deleted if you don't use the trashcan feature.

* Whatever that /Disk directory was, it was obviously a temporary mountpoint. I have no idea how/why the PCLinuxOS folk did it this way, but hey, it's an open source world.

Closing commentary: So far as how things are seeming to "fix" themselves, I'm guessing it's because you're using a "managed system" (if I can apply that term in this context) and not handling things manually. So something went wrong somewhere and "fixed itself" kinda like "did you turn it off and on again". That's the only up side of managed systems, though for me there's nothing more tedious than tracking down what's to blame for a problem in a managed system, so I try to strike a balance, sort of I manage what causes most issues and leave be the rest...

But I digress, so long as everything's working for you, that's great as it gives you time to gradually build up the knowledge to troubleshoot, and although learning is really a lifelong process, it's a good one since you have a real feeling of accomplishment each step of the way.

 

[fritz1]

I'm in the life-forgetting mode, CRS, means I'm getting old. Been using PCLOS for decades and so used to the GUI it's difficult to recall what stuff means anymore. All these new terms are just confusing.
Yes, I did reboot cause we lost power. Didn't equate the two events till now. Anyhow, I was wanting to use the drive for a VM but I'm having issues with remembering what to do next and where I'm at in the process. Keep running into walls with unexpected events.
Thanks for the assist!

 

[Fanboi]

Anyhow, I was wanting to use the drive for a VM but I'm having issues with remembering what to do next and where I'm at in the process. Keep running into walls with unexpected events.
Thanks for the assist!

Simply:
Okay, if you mean you want to use a partition, i.e. /dev/sdXY where X is the disk and Y the partition, eg /dev/sdb2, that's pretty simple. Just add -drive file=/dev/sdXY to your startup parameters (you don't specify format in this case as you would with an img file).

Caveats:
1. You will need to chown the partition in question (or set up permissions). Straightforward (ch)owning: sudo chown <username>:<usergroup> /dev/sdXY . Warning: guides out there will say "you need root, so run your VM using sudo" -- do not. Never run a VM as root as a rule -- cases where you have to are beyond this scope.

2. In your VM the partition will not be enumerated as expected. It will not have a partition number. So for example, my shared partition used to appear as /dev/sdd7 on my host. In my VM it was just /dev/sdc -- no number.

3. It's easiest and safest to format it on your host first. That way any issues will be picked up by the host system which can see the entire disk, whereas the VM will only see that partition, which it is technically treating as a disk.

Notes:
If you want to use the entire physical disk, not a partition, then let me know because that process is a little different. It's a little safer confining the VM to a parition over the full disk, though. Also, if you need a step by step setting up a VM using qemu, let us know, though I'm sure there are a few simple tutorials on this forum.

Edit: If you meant to use the drive to store the VM disk image, appologies, for the needless tutorial, lol.