I thought creating a gpt partition table would fix it but I was wrong. This time I clicked on the offending drive in the file manager and a 'permission denied' message appeared. So I suppose I will have to chmod it. The proper command would be 'chmod -r 777 {device}'? Wait a second.... I seem to remember that this is a sign of a disk going bad. Is this so? Two devices going bad at the same time? Talk about bad luck! On Tue, Jan 17, 2023 at 8:31 AM Michael wrote: > I was kinda oopy last night (I didn't google a solution to how to fix it ) > but I just did and found out how to set the partition table. But which > should I choose? I've heard gpt mentioned but am unsure. Could I hear some > opinions from the learnED here? > > On Mon, Jan 16, 2023 at 9:29 PM Michael wrote: > >> in my other thread I looked at a gparted report. Well it had something >> related to this thread. In the report it is mentioned that file system >> type is ext4 but that the partition table is msdos. Does that matter.How >> should it be fixed if it does? >> >> ======================================== >> Device: /dev/sdb >> Model: SanDisk Ultra >> Serial: >> Sector size: 512 >> Total sectors: 240353280 >> >> Heads: 255 >> Sectors/track: 2 >> Cylinders: 471280 >> >> Partition table: msdos >> >> PartitionTypeStartEndFlagsPartition NameFile SystemLabelMount Point >> /dev/sdb1 Primary 2048 240353279 ext4 >> /media/michael/5d19820a-dfe9-4a0f-8593-9339e9b4ecd2 >> >> ======================================== >> >> >> On Mon, Jan 16, 2023 at 8:41 PM Michael wrote: >> >>> Okay, I spent the last thirty minutes copying all the files from the >>> fat fomatted drive to a folder on the desktop. Then I formatted the drive >>> to ext4. Now I can't drag the files back on to the USB drive. I suppose I >>> could chmod -r 777 the drive but what is the right way to do it? >>> -- >>> :-)~MIKE~(-: >>> >> >> >> -- >> :-)~MIKE~(-: >> > > > -- > :-)~MIKE~(-: > -- :-)~MIKE~(-: