Can't generate new folder

Can you create files/directories outside the lost+found folder with sudo?

Please explain more - using the terminal?

So how do I create a folder in the 872GB drive?

Is the partition already mounted somewhere?

Not that I am aware.

As I have said, "I can open lost+found as administrator and generate a folder inside lost+found but does not seem right!"

"Is the partition already mounted somewhere?"

How can I find if that is the case?

https://drive.google.com/file/d/1Ci29iWPR3ZHZgIzMlX2-78IWcQQxu_SR/view?usp=sharing
https://drive.google.com/file/d/1yjmXWdUbCL-8NAhbDYdPhehkdR60RzbK/view?usp=sharing
https://drive.google.com/file/d/1I9FmkWKsLAKqsHXiD2dtEAB6otlsGTj3/view?usp=sharing

When you have the status as shown in https://drive.google.com/file/d/1yjmXWdUbCL-8NAhbDYdPhehkdR60RzbK/view?usp=sharing

Open a terminal window and execute the command

mkdir -v /media/richard/my_test

What happens?

hear are the results:-

richard@richard-H81M-S2H:~$ mkdir -v /media/richard/my_test
mkdir: cannot create directory ‘/media/richard/my_test’: Permission denied
richard@richard-H81M-S2H:~$ mkdir -v /media/richard/my_test
mkdir: cannot create directory ‘/media/richard/my_test’: Permission denied

I repeated 2 times while having lost+found only was showing them with test folder showing.

I hope this is informative.

Rich.b

Try

sudo chown richard:richard /media/richard
mkdir -v /media/richard/my_test

and report the results

richard@richard-H81M-S2H:~$ sudo chown richard:richard /media/richard
[sudo] password for richard:
richard@richard-H81M-S2H:~$ mkdir -v /media/richard/my_test
mkdir: created directory '/media/richard/my_test'
richard@richard-H81M-S2H:~$

This has created a directory. Is that what you wanted?

Yes I believe so.

Thank you Manfred

I have discovered what the difference between the 3 partitions
1.1TB Owner: Me Parent Folder: media/richard Filesystem type: fuse
57GB Owner: Me Parent Folder: media/richard Filesystem type: fuse
872GB Owner: “root” Parent Folder: media/richard Filesystem type: ext3/ext4

Q 1/ So how do I change the “Permissions” on this 872GB partition from ROOT to Me?
Q 2/ Why was this permission different, I do not remember setting this partition to different permission.

"fuse" and "ext3/ext4" are not "permissions", but are related to different file system types.

If you create and format a new partition with Microsoft Windows, then it is formatted as "NTFS" file system. This file system does not have the same file access rights system as Unix systems, but generally allows read/write/delete to everybody.

If you create and format a new partition with a Unix-type system as Ubuntu, then it is formatted as "extended file system" ext3 or ext4. This file system allows setting access right for users and groups and applies "secure by default" which is "no access except for the administrator". You have to allow access (this was already done with the "chown" command given previously).

I greatly appreciate your detailed explanation. I am aware of some of the different file systems for Microsoft Windows (NTFS) and Unix-type systems (ext3/4).

Q 1/ Are you suggesting that this external drive was format by Windows or in the NTFS format?

I used to subscribe to Linux Format magazine for 2/3 years.
I have 2 books published by O'Reilly, Arnold Robbins pocket reference & Linux pocket guide, Daniel J Barrett.

Q 2/ Could you recommend a practical book or magazine so I could learn a lot more?

Thank you Manfred for help.

To check the format of the disk partitions issue the command

sudo fdisk -l

Let's see what this output tells about your disk with the three partitions (ignore all output for "loop" devices).

And for the books: sorry, no idea. I suggest that you do a web search for "Ubuntu recommended reading" or some similar search terms.

richard@richard-H81M-S2H:~$ sudo fdisk -l
[sudo] password for richard:
Disk /dev/loop0: 291 MiB, 305086464 bytes, 595872 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/sda: 447.1 GiB, 480103981056 bytes, 937703088 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 29FC9098-B3E1-41E1-BFC7-2FFFB921A5D6

Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 921133055 920082432 438.7G Linux filesystem
/dev/sda3 921133056 937701375 16568320 7.9G Linux swap

Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x5a05f99a

Device Boot Start End Sectors Size Id Type
/dev/sdb1 1985 1843206143 1843204159 878.9G f W95 Ext'd (LBA)
/dev/sdb2 1843206144 3907028991 2063822848 984.1G 83 Linux
/dev/sdb5 2048 1024002047 1024000000 488.3G 7 HPFS/NTFS/exFAT
/dev/sdb6 1024004096 1843206143 819202048 390.6G 83 Linux

Partition 1 does not start on physical sector boundary.
Partition table entries are not in disk order.

Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xbf03cfb1

Device Boot Start End Sectors Size Id Type
/dev/sdc1 2048 1062661583 1062659536 506.7G 83 Linux
/dev/sdc2 1062662142 3907028991 2844366850 1.3T 5 Extended
/dev/sdc5 2016665600 3907028991 1890363392 901.4G 83 Linux
/dev/sdc6 1062662144 2016665599 954003456 454.9G 83 Linux

Partition 2 does not start on a physical sector boundary.
Partition table entries are not in disk order.

Disk /dev/sdh: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xe5d5229b

Device Boot Start End Sectors Size Id Type
/dev/sdh1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sdh2 208896 111536127 111327232 53.1G 7 HPFS/NTFS/exFAT
/dev/sdh3 114608128 2203817983 2089209856 996.2G 7 HPFS/NTFS/exFAT
/dev/sdh4 2203817984 3907028991 1703211008 812.2G 83 Linux
richard@richard-H81M-S2H:~$

I assume that you are talking about

Device Boot Start End Sectors Size Id Type
/dev/sdh1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sdh2 208896 111536127 111327232 53.1G 7 HPFS/NTFS/exFAT
/dev/sdh3 114608128 2203817983 2089209856 996.2G 7 HPFS/NTFS/exFAT
/dev/sdh4 2203817984 3907028991 1703211008 812.2G 83 Linux

sdh2 and sdh3 are NTFS-formatted, sdh4 is Linux (which most probably is ext4)

(Note that the differences in size are caused by using 1000 vs. 1024 for the multiplication factor)
812.2G means 812.2 GiB (base 1024) = 812.2*1.024*1.024*1.024= 872.1 GB (base 1000)

Yes thank you Manfred I follow that.