flash drive mounting read-only

I'm getting a strange issue.. my flash drive is mounting read-only. I can do the disk check in windows or repair disk in macos to fix it and then it works fine for the next boot, but if I reboot my unraid it goes back to readonly, I get this in the syslog:

Oct  1 20:53:05 knox kernel: FAT-fs (sdg1): error, fat_free_clusters: deleting FAT entry beyond EOF

Oct  1 20:53:05 knox kernel: FAT-fs (sdg1): Filesystem has been set read-only

These are all clean reboots (proper array stop and reboot through the GUI), and there is tonnes of space on my flash drive. Is my flash drive dying? Any ideas what might be causing this?

Cheers,

whiteatom

I don't know if this will help anyone.. because I have no idea how to read this.. but is this normal for a flash drive??

root@knox:/boot# fdisk -l /dev/sdg1

Disk /dev/sdg1: 1014 MB, 1014496256 bytes
32 heads, 61 sectors/track, 1015 cylinders
Units = cylinders of 1952 * 512 = 999424 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb0bcd68e

This doesn't look like a partition table
Probably you selected the wrong device.

     Device Boot      Start         End      Blocks   Id  System
/dev/sdg1p1   ?     1651315     1777688   123339962   78  Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
     phys=(518, 102, 15) logical=(1651314, 30, 24)
Partition 1 has different physical/logical endings:
     phys=(743, 0, 62) logical=(1777687, 27, 34)
Partition 1 does not end on cylinder boundary.
/dev/sdg1p2   ?      221758      619137   387841909+  10  OPUS
Partition 2 has different physical/logical beginnings (non-Linux?):
     phys=(205, 7, 0) logical=(221757, 23, 51)
Partition 2 has different physical/logical endings:
     phys=(920, 235, 50) logical=(619136, 23, 61)
Partition 2 does not end on cylinder boundary.
/dev/sdg1p3   ?      957768     1940980   959615034   8b  Unknown
Partition 3 has different physical/logical beginnings (non-Linux?):
     phys=(260, 125, 54) logical=(957767, 22, 38)
Partition 3 has different physical/logical endings:
     phys=(893, 46, 60) logical=(1940979, 26, 37)
Partition 3 does not end on cylinder boundary.
/dev/sdg1p4   ?     1168905     1173169     4161537    a  OS/2 Boot Manager
Partition 4 has different physical/logical beginnings (non-Linux?):
     phys=(269, 111, 50) logical=(1168904, 12, 37)
Partition 4 has different physical/logical endings:
     phys=(0, 0, 0) logical=(1173168, 8, 26)
Partition 4 does not end on cylinder boundary.

Partition table entries are not in disk order

And here's the output of my disk repair... (Mac OSX Disk Utility)

Verify and Repair volume “UNRAID”
Checking file system** /dev/disk1s1
** Phase 1 - Preparing FAT
** Phase 2 - Checking Directories
/CONFIG/plugins/couchpotato_v2/settings.conf starts with free cluster
Truncate? yes
** Phase 3 - Checking for Orphan Clusters
Found orphan cluster(s)
Fix? yes
Marked 2 clusters as free
Free space in FSInfo block (201765) not correct (201767)
Fix? yes
243 files, 807068 KiB free (201767 clusters)

I would expect to see 1 partition, not multiple.

You used fdisk incorrectly, and it is trying to interpret your first partition as the master-boot-record. 

You need to use fdisk on the full drive, not on a partition.

you should type

fdisk -lu /dev/sdg

Joe.. Agreed about the partitions numbers.. and windows/macos only see one.

Corrected fdisk output:

ot@knox:/mnt/apps/data/couchpotato_v2# fdisk -lu /dev/sdg

Disk /dev/sdg: 1014 MB, 1014497280 bytes
255 heads, 63 sectors/track, 123 cylinders, total 1981440 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 identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdg1   *           2     1981439      990719    b  W95 FAT32
Partition 1 has different physical/logical beginnings (non-Linux?):
     phys=(1023, 254, 63) logical=(0, 0, 3)
Partition 1 has different physical/logical endings:
     phys=(1023, 254, 63) logical=(123, 86, 27)

Ok today I rebooted to install the new SF and all is well

Then.... about 15 mins later, (while troubleshooting some couchpotato problems), I "cat" a file on the flash drive.. and got this in my syslog.

Oct  4 12:18:13 knox kernel: FAT-fs (sdg1): error, fat_free_clusters: deleting FAT entry beyond EOF
Oct  4 12:18:13 knox kernel: FAT-fs (sdg1): Filesystem has been set read-only

This is getting really annoying. Is this a bad flash drive?

whiteatom

Ok today I rebooted to install the new SF and all is well

 

Then.... about 15 mins later, (while troubleshooting some couchpotato problems), I "cat" a file on the flash drive.. and got this in my syslog.

Oct  4 12:18:13 knox kernel: FAT-fs (sdg1): error, fat_free_clusters: deleting FAT entry beyond EOF
Oct  4 12:18:13 knox kernel: FAT-fs (sdg1): Filesystem has been set read-only

 

This is getting really annoying. Is this a bad flash drive?

 

whiteatom

New flash drive and no problems so far.