I am telling ya all thing.
1.I installed Manjaro
2.I have 2 disk. A ssd a hdd. SSD and HDD is ext4.
3.I installed erase and install option with. Just SSD mounted as root.
4.HDD is mounted as just drive.
5.But I can not access. For example: I can not creating new file on it.
I tried this command:
sudo chown myusername /dev/sda1
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 465,8G 0 disk
└─sda1 8:1 0 465,8G 0 part /run/media/caner/db5e4d93-0478-4aab-b34e-cea7b62ff3e7
sdb 8:16 0 223,6G 0 disk
├─sdb1 8:17 0 300M 0 part /boot/efi
├─sdb2 8:18 0 214,5G 0 part /
└─sdb3 8:19 0 8,8G 0 part [SWAP]
Is a device file, so you don’t chown/chmod it. You chown/chmod the mountpoint.
sudo chown $USER:$USER /run/media/caner/db5e4d93-0478-4aab-b34e-cea7b62ff3e7
/run is a temporary filesystem, it’s a place where software can put stuff without affecting the rest of the system. You should mount it elsewhere using
fstab or systemd unit files.
Note: This post is meant as a tutorial. Please do not post on this thread regarding any problems you’re having with permissions, but start a new thread instead. Thank you.
PREAMBLE: THE HISTORICAL BACKGROUND
If you are new to the world of GNU/Linux ─ and especially if you come from the Microsoft Windows ecosystem ─ then you will undoubtedly already have noticed that GNU/Linux handles permissions and storage volumes quite differently from what you might be used to…
Microsoft Windows started its life as a graphical user interface on top of MS-DOS, a 16-bit single-user, single-tasking operating system that in turn originated as 86DOS, an unauthorized 16-bit rewrite (by Tim Paterson of Seattle Computer) of Digital Research’s originally 8-bit CP/M operating system. Both CP/M and MS-DOS were at the time developed for computers that did not support any other storage media than floppy disks.
Considering this legacy, Microso…
Disk device recognition
Manjaro uses udev (see Arch Wiki) to load devices at boot time. The loading of devices is arbitrary and therefore you cannot predict which device will be available at a given path.
But static device names do exist and you can assign specific locations to your device and thus ensure e.g. scripts will work as expected.
What to learn
Overview of system mount units
Structure and Content of a mount unit
Mount at boot (immediate mount)
Mount on demand (m…
I had a similar issue the other day, I have the KDE partition manager I created the partition using this. Don’t know if this will help you out, but worth a shot.