Solved Trouble formatting 128Gb USB Memory as multiple partitions.

smithi · Sep 22, 2023

gpw928 said:
I was perplexed by your issues. So I plugged in a 128GB thumb drive:
[...]

Then I followed your process:

Code:

[sherman.143] # gpart destroy -F /dev/da8
da8 destroyed
[sherman.144] # gpart create -s mbr /dev/da8
da8 created
[sherman.145] # gpart show /dev/da8
=>       63  242501825  da8  MBR  (116G)
         63  242501825       - free -  (116G)

[sherman.146] # gpart add -s 30G -t fat32 /dev/da8
da8s1 added
[sherman.147] # gpart add -s 30G -t fat32 /dev/da8
da8s2 added
[sherman.148] # gpart add -s 30G -t fat32 /dev/da8
da8s3 added
[sherman.149] # gpart add -s 30G -t fat32 /dev/da8
gpart: autofill: No space left on device

Here's a big difference. OP seemed to have had s4 truncated to fit - as if no size had been specified - but then
CuatroTorres had no such issue in post #4, even showing "da0s4 added" - so what might account for that?

gpw928 said:
[sherman.150] # gpart show /dev/da8
=> 63 242501825 da8 MBR (116G)
63 62914560 1 fat32 (30G)
62914623 62914560 2 fat32 (30G)
125829183 62914560 3 fat32 (30G)
188743743 53758145 - free - (26G)

Not sure, but I suspect starting at sector 63 might be due to the CHS alignment of fat32, rather than Logical Block Addressing of fat32lba, introduced with Windows95 IIRC, long time ago.

Which may explain why just the OP's last slice being created as fat32lba "didn't work"?

gpw928 said:
[sherman.151] # newfs_msdos -L FILES -F 32 /dev/da8s2

Might 4 partitions with the same label cause any issue?

gpw928 said:
Apart from insufficient space to allocate 30G to the last partition (you clearly had a similar problem), everything worked.

Even with the wrong target USB device, apparently?

gpw928 said:
As others have suggested, the logic of what you are doing needs to be reviewed, but technically, I think that your thumb drive is not working properly. Please show us the entries from /var/log/messages between when you plug it in and when you create the fat32 file system.

Yes.

Maybe good to know brand and model thumb drive too? My bad pair were 64G Lexar USB2; I wondered why they were so cheap.

VladiBG · Sep 22, 2023

There's some fake USB drives which have some cheap eMMC card with small size of 4-8GB with modified firmware which report the USB drive as 8TB - 16TB USB disk which you can get for $5. When you try to use or format such disk you get all kind of errors.

Using any kind of FLASH memory for storing a CCTV will wear it very fast and make it unusable. That's why in DVRs they use standard HDD instead of SSDs.

fixit9660 · Sep 22, 2023

6502 said:
If disk size limit is the reason for 4 volumes, try to format the whole USB disk with exFAT.

I've tried this already. The CCTV wouldn't recognise it.

fixit9660 · Sep 22, 2023

gpw928 said:

I was perplexed by your issues. So I plugged in a 128GB thumb drive:

Code:

Sep 22 07:42:09 sherman kernel: da8 at umass-sim0 bus 0 scbus13 target 0 lun 0
Sep 22 07:42:09 sherman kernel: da8: <PNY USB 3.1 FD PMAP> Removable Direct Access SPC-4 SCSI device
Sep 22 07:42:09 sherman kernel: da8: Serial Number 070009CD1DAE6B02
Sep 22 07:42:09 sherman kernel: da8: 400.000MB/s transfers
Sep 22 07:42:09 sherman kernel: da8: 118409MB (242501888 512 byte sectors)
Sep 22 07:42:09 sherman kernel: da8: quirks=0x2<NO_6_BYTE>

Then I followed your process:

Code:

[sherman.143] # gpart destroy -F /dev/da8
da8 destroyed
[sherman.144] # gpart create -s mbr /dev/da8
da8 created
[sherman.145] # gpart show /dev/da8
=>       63  242501825  da8  MBR  (116G)
         63  242501825       - free -  (116G)

[sherman.146] # gpart add -s 30G -t fat32 /dev/da8
da8s1 added
[sherman.147] # gpart add -s 30G -t fat32 /dev/da8
da8s2 added
[sherman.148] # gpart add -s 30G -t fat32 /dev/da8
da8s3 added
[sherman.149] # gpart add -s 30G -t fat32 /dev/da8
gpart: autofill: No space left on device
[sherman.150] # gpart show /dev/da8
=>       63  242501825  da8  MBR  (116G)
         63   62914560    1  fat32  (30G)
   62914623   62914560    2  fat32  (30G)
  125829183   62914560    3  fat32  (30G)
  188743743   53758145       - free -  (26G)

[sherman.151] # newfs_msdos -L FILES -F 32 /dev/da8s2
/dev/da8s2: 62899136 sectors in 982799 FAT32 clusters (32768 bytes/cluster)
BytesPerSec=512 SecPerClust=64 ResSectors=32 FATs=2 Media=0xf0 SecPerTrack=63 Heads=255 HiddenSecs=0 HugeSectors=62914560 FATsecs=7679 RootCluster=2 FSInfo=1 Backup=2

Note that I added all the partitions to the same device (da8).

Apart from insufficient space to allocate 30G to the last partition (you clearly had a similar problem), everything worked.

As others have suggested, the logic of what you are doing needs to be reviewed, but technically, I think that your thumb drive is not working properly. Please show us the entries from /var/log/messages between when you plug it in and when you create the fat32 file system.

This is what I did:


gpart destroy -F /dev/da0
dd if=/dev/zero of=/dev/da0 bs=512 count=34
dd if=/dev/zero of=/dev/da0 bs=512 seek=245759966
remove USB at 12:02:23
re-insert USB 12:03:18
gpart create -s mbr /dev/da0
gpart add -s 30G -t fat32 /dev/da0
gpart add -s 30G -t fat32 /dev/da0
gpart add -s 30G -t fat32 /dev/da0
gpart add -s 27G -t fat32 /dev/da0
newfs_msdos -L FILES -F 32 /dev/da0s1

Output of cat /var/log/messages | grep -A 900 "12:02:23":

Sep 22 12:02:23 freenas ugen1.2: <vendor 0x058f USB DISK 3.2> at usbus1 (disconnected)
Sep 22 12:02:23 freenas umass0: at uhub2, port 3, addr 2 (disconnected)
Sep 22 12:02:23 freenas da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
Sep 22 12:02:23 freenas da0: < USB DISK 3.2 8.01> s/n 041A0DCD detached
Sep 22 12:02:23 freenas (da0:umass-sim0:0:0:0): Periph destroyed
Sep 22 12:02:23 freenas umass0: detached
Sep 22 12:03:18 freenas ugen1.2: <vendor 0x058f USB DISK 3.2> at usbus1
Sep 22 12:03:18 freenas umass0 on uhub2
Sep 22 12:03:18 freenas umass0: <vendor 0x058f USB DISK 3.2, class 0/0, rev 2.10/0.02, addr 2> on usbus1
Sep 22 12:03:18 freenas umass0: SCSI over Bulk-Only; quirks = 0x4101
Sep 22 12:03:18 freenas umass0:7:0: Attached to scbus7
Sep 22 12:03:19 freenas (probe0:umass-sim0:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00
Sep 22 12:03:19 freenas (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Sep 22 12:03:19 freenas (probe0:umass-sim0:0:0:0): SCSI status: Check Condition
Sep 22 12:03:19 freenas (probe0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Sep 22 12:03:19 freenas (probe0:umass-sim0:0:0:0): Info: 0
Sep 22 12:03:19 freenas (probe0:umass-sim0:0:0:0): Error 22, Unretryable error
Sep 22 12:03:19 freenas da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
Sep 22 12:03:19 freenas da0: < USB DISK 3.2 8.01> Removable Direct Access SPC-4 SCSI device
Sep 22 12:03:19 freenas da0: Serial Number 041A0DCD
Sep 22 12:03:19 freenas da0: 40.000MB/s transfers
Sep 22 12:03:19 freenas da0: 120000MB (245760000 512 byte sectors)
Sep 22 12:03:19 freenas da0: quirks=0x3<NO_SYNC_CACHE,NO_6_BYTE>
Sep 22 12:10:51 freenas (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 11 00 00 00 01 00
Sep 22 12:10:51 freenas (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Sep 22 12:10:51 freenas (da0:umass-sim0:0:0:0): Retrying command
Sep 22 12:10:56 freenas (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 11 00 00 00 01 00
Sep 22 12:10:56 freenas (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Sep 22 12:10:56 freenas (da0:umass-sim0:0:0:0): Retrying command
Sep 22 12:11:01 freenas (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 11 00 00 00 01 00
Sep 22 12:11:01 freenas (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Sep 22 12:11:01 freenas (da0:umass-sim0:0:0:0): Retrying command
Sep 22 12:11:07 freenas (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 11 00 00 00 01 00
Sep 22 12:11:07 freenas (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Sep 22 12:11:07 freenas (da0:umass-sim0:0:0:0): Retrying command
Sep 22 12:11:12 freenas (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 11 00 00 00 01 00
Sep 22 12:11:12 freenas (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Sep 22 12:11:12 freenas (da0:umass-sim0:0:0:0): Error 5, Retries exhausted
Sep 22 12:12:06 freenas (da0:umass-sim0:0:0:0): got CAM status 0x44
Sep 22 12:12:06 freenas (da0:umass-sim0:0:0:0): fatal error, failed to attach to device
Sep 22 12:12:06 freenas da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
Sep 22 12:12:06 freenas da0: < USB DISK 3.2 8.01> s/n 041A0DCD detached
Sep 22 12:12:06 freenas g_access(952): provider da0 has error 6 set
Sep 22 12:12:06 freenas g_access(952): provider da0 has error 6 set
Sep 22 12:12:06 freenas g_access(952): provider da0 has error 6 set
Sep 22 12:12:06 freenas g_access(952): provider da0 has error 6 set
Sep 22 12:12:06 freenas g_access(952): provider da0 has error 6 set
Sep 22 12:12:12 freenas (da0:umass-sim0:0:0:0): Periph destroyed

The USB Memory was bought new in original packaging from a reputable online dealer a few days ago. It's a PNY Brand 128GB 3.1 Flash Drive, FD128ATT431KK-EF.
Just for info:


diskinfo -v da0
da0
        512             # sectorsize
        125829120000    # mediasize in bytes (117G)
        245760000       # mediasize in sectors
        0               # stripesize
        0               # stripeoffset
        15297           # Cylinders according to firmware.
        255             # Heads according to firmware.
        63              # Sectors according to firmware.
         USB DISK 3.2   # Disk descr.
        041A0DCD        # Disk ident.
        No              # TRIM/UNMAP support
        Unknown         # Rotation rate in RPM
        Not_Zoned       # Zone Mode

fixit9660 · Sep 22, 2023

VladiBG said:
There's some fake USB drives which have some cheap eMMC card with small size of 4-8GB with modified firmware which report the USB drive as 8TB - 16TB USB disk which you can get for $5. When you try to use or format such disk you get all kind of errors.

Using any kind of FLASH memory for storing a CCTV will wear it very fast and make it unusable. That's why in DVRs they use standard HDD instead of SSDs.

I'm only going to be using the USB Memory for transferring files, (snapshots, video cuttings), off the CCTV system. It'll get very little regular use otherwise. I understand the limitations of solid-state memory devices.

YYY__ · Sep 22, 2023

smithi,
Sorry, it was a simulation to show the /dev/daX drive issue. It was not a true partition of a 128GB flash memory.

In any case. Partitioning will depend on the limitations of the CCTV system. He should check the manual specifications.
The 32GB limitation seems like a Windows OS thing. The limit of 4 primary partitions is also not being exceeded.
As I said, I would try making the partitioning scheme with fdisk, it seems more robust to me. For example, it warned me that it had a GPT mark from a previous format in the past. I was hell-bent on making an MBR scheme, so the drive was not working properly.

fixit9660 · Sep 22, 2023

Following balangas suggestion, I tried to create a single NTFS partition, and got some interesting results:

gpart destroy -F /dev/da0
gpart create -s MBR da0
gpart add -t ntfs da0
mkntfs /dev/da0s1
The partition start sector was not specified for /dev/da0s1 and it could not be obtained automatically.  It has been set to 0.
The number of sectors per track was not specified for /dev/da0s1 and it could not be obtained automatically.  It has been set to 0.
The number of heads was not specified for /dev/da0s1 and it could not be obtained automatically.  It has been set to 0.
Cluster size has been automatically set to 4096 bytes.
To boot from a device, Windows needs the 'partition start sector', the 'sectors per track' and the 'number of heads' to be set.
Windows will not be able to boot from this device.
Initializing device with zeroes:   0%Error writing to /dev/da0s1: Input/output error

Found bad cluster (4864). Adding to list of bad blocks.
Initializing device with zeroes:   0%Error writing to /dev/da0s1: Input/output error

Found bad cluster (4865). Adding to list of bad blocks.
Initializing device with zeroes:   0%Error writing to /dev/da0s1: Input/output error

Found bad cluster (4866). Adding to list of bad blocks.
Initializing device with zeroes:   0%Error writing to /dev/da0s1: Input/output error

Found bad cluster (4867). Adding to list of bad blocks.
Initializing device with zeroes:   0%Error writing to /dev/da0s1: Input/output error

Found bad cluster (4868). Adding to list of bad blocks.
Initializing device with zeroes:   0%Error writing to /dev/da0s1: Input/output error

Found bad cluster (4869). Adding to list of bad blocks.
Initializing device with zeroes:   0%Error writing to /dev/da0s1: Input/output error

Found bad cluster (4870). Adding to list of bad blocks.
Initializing device with zeroes:   0%Error writing to /dev/da0s1: Input/output error

Found bad cluster (4871). Adding to list of bad blocks.
Initializing device with zeroes:   0%Error writing to /dev/da0s1: Input/output error

Found bad cluster (4872). Adding to list of bad blocks.
Initializing device with zeroes:   0%Error writing to /dev/da0s1: Input/output error

Found bad cluster (4873). Adding to list of bad blocks.
Initializing device with zeroes:   0%^C

I'll let this finish.

I eventually gave up at:


Found bad cluster (5344). Adding to list of bad blocks.
Initializing device with zeroes:   0%^C

I decided to try the quick version and, after setting the env variable got:


mkntfs -Q /dev/da0s1
The partition start sector was not specified for /dev/da0s1 and it could not be obtained automatically.  It has been set to 0.
The number of sectors per track was not specified for /dev/da0s1 and it could not be obtained automatically.  It has been set to 0.
The number of heads was not specified for /dev/da0s1 and it could not be obtained automatically.  It has been set to 0.
Cluster size has been automatically set to 4096 bytes.
To boot from a device, Windows needs the 'partition start sector', the 'sectors per track' and the 'number of heads' to be set.
Windows will not be able to boot from this device.
Creating NTFS volume structures.
Error writing to /dev/da0s1: Input/output error
Error writing non-resident attribute value.
add_attr_data_positioned failed: Input/output error
Couldn't create $LogFile: Input/output error

Does this indicate a faulty USB Memory? Will fsck work on it at this point?

smithi · Sep 22, 2023

fixit9660 said:
Does this indicate a faulty USB Memory? Will fsck work on it at this point?

Sure seems so, on top of all the errors in /var/log/messages.

[Edit: no, fsck won't help, it's for filesystem errors, usually UFS, not underlying media errors]

Try a full disk dd from /dev/zero with status=progress and conv=noerror,sync ?

At least you should be able to get your money back, if it behaves as badly tested on a real FreeBSD system.

But first, what version of freenas and more importantly, underpinned by which version of FreeBSD? Can you try another stick? 64G aren't so expensive.

gpw928 · Sep 22, 2023

The log messages clearly indicate a serious problem related to the hardware or the driver.

You could try it on a variety of USB port types and operating systems just to verify that your specific combination does not have a bug.

And, of course, FreeNAS bugs may be different to FreeBSD bugs...

USB ports will generally be colour coded black, blue, or red (from least to most capable). Try the thumb drive on a different type of USB port.

On any Unix-like system, I would destructively test media (here da0) with dd if=/dev/zero of=/dev/da0 bs=1024k oflag=sync status=progress.

You can judge the success with:

the appearance of any error message from dd;
the printed summary provided by dd before it exits;
the exit status, as indicated with Bourne shell's echo $0; and
any messages appearing in /var/log/messages.

This tests writes to the entire media, and might take quite a while with a large thumb drive.

I expect that suppliers are generally more likely to believe it's broken if you can assert it won't work with M$ Windows.

If it were mine, I would test it on another system, and if it still fails, ask the supplier to replace it.

fixit9660 · Sep 23, 2023

I'm running FreeBSD 11.3-RELEASE-p14 FreeNAS-11.3-U5

I tried to run the command:
dd if=/dev/zero of=/dev/da0 bs=1024k oflag=sync status=progress conv=noerror,sync
but it didn't like the oflag operand:
dd: unknown operand oflag
I checked the FreeBSD 11.3 man page and it does specify this operand so I don't understand why it doesn't like it. I then omitted it and it ran, but like an idiot I managed to Control-C it. This is what I got before:

dd if=/dev/zero of=/dev/da0 bs=1024k status=progress conv=noerror,sync           
  1048576 bytes (1049 kB, 1024 KiB) transferred 3.054s, 343 kB/s
  2097152 bytes (2097 kB, 2048 KiB) transferred 6.111s, 343 kB/s
  3145728 bytes (3146 kB, 3072 KiB) transferred 9.207s, 342 kB/s
^C^C


4+0 records in
3+0 records out
3145728 bytes transferred in 110.989108 secs (28343 bytes/sec)

I've re-inserted and "gpart create -s mbr /dev/da0" so that I can see it on the system again, and run the above command again.
It started to run and produced the same output as above before failing:


dd: /dev/da0: Input/output error

I got the following Exit Code:


echo $0
_su

I've had to remove/re-insert the USB Memory several times to be able to see it on the system, and I've made two attempts to run the dd command. I even tried putting the USB Memory into a different USB port. I got the following /log/messages entries:


Sep 23 08:02:18 freenas ugen1.2: <vendor 0x058f USB DISK 3.2> at usbus1
Sep 23 08:02:18 freenas umass0 on uhub2
Sep 23 08:02:18 freenas umass0: <vendor 0x058f USB DISK 3.2, class 0/0, rev 2.10/0.02, addr 2> on usbus1
Sep 23 08:02:18 freenas umass0:  SCSI over Bulk-Only; quirks = 0x4101
Sep 23 08:02:18 freenas umass0:7:0: Attached to scbus7
Sep 23 08:02:19 freenas (probe0:umass-sim0:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 
Sep 23 08:02:19 freenas (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Sep 23 08:02:19 freenas (probe0:umass-sim0:0:0:0): SCSI status: Check Condition
Sep 23 08:02:19 freenas (probe0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Sep 23 08:02:19 freenas (probe0:umass-sim0:0:0:0): Info: 0
Sep 23 08:02:19 freenas (probe0:umass-sim0:0:0:0): Error 22, Unretryable error
Sep 23 08:02:19 freenas da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
Sep 23 08:02:19 freenas da0: < USB DISK 3.2 8.01> Removable Direct Access SPC-4 SCSI device
Sep 23 08:02:19 freenas da0: Serial Number 041A0DCD
Sep 23 08:02:19 freenas da0: 40.000MB/s transfers
Sep 23 08:02:19 freenas da0: 120000MB (245760000 512 byte sectors)
Sep 23 08:02:19 freenas da0: quirks=0x3<NO_SYNC_CACHE,NO_6_BYTE>
Sep 23 08:17:12 freenas (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 19 00 00 00 80 00 
Sep 23 08:17:12 freenas (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Sep 23 08:17:12 freenas (da0:umass-sim0:0:0:0): Retrying command
Sep 23 08:17:18 freenas (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 19 00 00 00 80 00 
Sep 23 08:17:18 freenas (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Sep 23 08:17:18 freenas (da0:umass-sim0:0:0:0): Retrying command
Sep 23 08:17:23 freenas (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 19 00 00 00 80 00 
Sep 23 08:17:23 freenas (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Sep 23 08:17:23 freenas (da0:umass-sim0:0:0:0): Retrying command
Sep 23 08:17:34 freenas (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 19 00 00 00 80 00 
Sep 23 08:17:34 freenas (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Sep 23 08:17:34 freenas (da0:umass-sim0:0:0:0): Retrying command
Sep 23 08:17:45 freenas (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 19 00 00 00 80 00 
Sep 23 08:17:45 freenas (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Sep 23 08:17:45 freenas (da0:umass-sim0:0:0:0): Error 5, Retries exhausted
Sep 23 08:18:45 freenas (da0:umass-sim0:0:0:0): got CAM status 0x44
Sep 23 08:18:45 freenas (da0:umass-sim0:0:0:0): fatal error, failed to attach to device
Sep 23 08:18:45 freenas da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
Sep 23 08:18:45 freenas da0: < USB DISK 3.2 8.01> s/n 041A0DCD detached
Sep 23 08:18:45 freenas g_access(952): provider da0 has error 6 set
Sep 23 08:18:45 freenas g_access(952): provider da0 has error 6 set
Sep 23 08:18:45 freenas g_access(952): provider da0 has error 6 set
Sep 23 08:18:45 freenas g_access(952): provider da0 has error 6 set
Sep 23 08:18:45 freenas g_access(952): provider da0 has error 6 set
Sep 23 08:18:45 freenas g_access(952): provider da0 has error 6 set
Sep 23 08:18:50 freenas (da0:umass-sim0:0:0:0): Periph destroyed
Sep 23 08:22:09 freenas ugen1.2: <vendor 0x058f USB DISK 3.2> at usbus1 (disconnected)
Sep 23 08:22:09 freenas umass0: at uhub2, port 3, addr 2 (disconnected)
Sep 23 08:22:09 freenas umass0: detached
Sep 23 08:22:17 freenas ugen1.2: <vendor 0x058f USB DISK 3.2> at usbus1
Sep 23 08:22:17 freenas umass0 on uhub2
Sep 23 08:22:17 freenas umass0: <vendor 0x058f USB DISK 3.2, class 0/0, rev 2.10/0.02, addr 2> on usbus1
Sep 23 08:22:17 freenas umass0:  SCSI over Bulk-Only; quirks = 0x4101
Sep 23 08:22:17 freenas umass0:7:0: Attached to scbus7
Sep 23 08:22:18 freenas (probe0:umass-sim0:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 
Sep 23 08:22:18 freenas (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Sep 23 08:22:18 freenas (probe0:umass-sim0:0:0:0): SCSI status: Check Condition
Sep 23 08:22:18 freenas (probe0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Sep 23 08:22:18 freenas (probe0:umass-sim0:0:0:0): Info: 0
Sep 23 08:22:18 freenas (probe0:umass-sim0:0:0:0): Error 22, Unretryable error
Sep 23 08:22:18 freenas da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
Sep 23 08:22:18 freenas da0: < USB DISK 3.2 8.01> Removable Direct Access SPC-4 SCSI device
Sep 23 08:22:18 freenas da0: Serial Number 041A0DCD
Sep 23 08:22:18 freenas da0: 40.000MB/s transfers
Sep 23 08:22:18 freenas da0: 120000MB (245760000 512 byte sectors)
Sep 23 08:22:18 freenas da0: quirks=0x3<NO_SYNC_CACHE,NO_6_BYTE>
Sep 23 08:27:58 freenas ugen1.2: <vendor 0x058f USB DISK 3.2> at usbus1 (disconnected)
Sep 23 08:27:58 freenas umass0: at uhub2, port 4, addr 2 (disconnected)
Sep 23 08:27:58 freenas da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
Sep 23 08:27:58 freenas da0: < USB DISK 3.2 8.01> s/n 041A0DCD detached
Sep 23 08:27:58 freenas (da0:umass-sim0:0:0:0): Periph destroyed
Sep 23 08:27:58 freenas umass0: detached
Sep 23 08:28:01 freenas ugen1.2: <vendor 0x058f USB DISK 3.2> at usbus1
Sep 23 08:28:01 freenas umass0 on uhub2
Sep 23 08:28:01 freenas umass0: <vendor 0x058f USB DISK 3.2, class 0/0, rev 2.10/0.02, addr 2> on usbus1
Sep 23 08:28:01 freenas umass0:  SCSI over Bulk-Only; quirks = 0x4101
Sep 23 08:28:01 freenas umass0:7:0: Attached to scbus7
Sep 23 08:28:03 freenas (probe0:umass-sim0:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 
Sep 23 08:28:03 freenas (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error
Sep 23 08:28:03 freenas (probe0:umass-sim0:0:0:0): SCSI status: Check Condition
Sep 23 08:28:03 freenas (probe0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
Sep 23 08:28:03 freenas (probe0:umass-sim0:0:0:0): Info: 0
Sep 23 08:28:03 freenas (probe0:umass-sim0:0:0:0): Error 22, Unretryable error
Sep 23 08:28:03 freenas da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
Sep 23 08:28:03 freenas da0: < USB DISK 3.2 8.01> Removable Direct Access SPC-4 SCSI device
Sep 23 08:28:03 freenas da0: Serial Number 041A0DCD
Sep 23 08:28:03 freenas da0: 40.000MB/s transfers
Sep 23 08:28:03 freenas da0: 120000MB (245760000 512 byte sectors)
Sep 23 08:28:03 freenas da0: quirks=0x3<NO_SYNC_CACHE,NO_6_BYTE>
Sep 23 08:33:21 freenas (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 19 00 00 00 80 00 
Sep 23 08:33:21 freenas (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Sep 23 08:33:21 freenas (da0:umass-sim0:0:0:0): Retrying command
Sep 23 08:33:32 freenas (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 19 00 00 00 80 00 
Sep 23 08:33:32 freenas (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Sep 23 08:33:32 freenas (da0:umass-sim0:0:0:0): Retrying command
Sep 23 08:33:43 freenas (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 19 00 00 00 80 00 
Sep 23 08:33:43 freenas (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Sep 23 08:33:43 freenas (da0:umass-sim0:0:0:0): Retrying command
Sep 23 08:33:54 freenas (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 19 00 00 00 80 00 
Sep 23 08:33:54 freenas (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Sep 23 08:33:54 freenas (da0:umass-sim0:0:0:0): Retrying command
Sep 23 08:33:59 freenas (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 19 00 00 00 80 00 
Sep 23 08:33:59 freenas (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Sep 23 08:33:59 freenas (da0:umass-sim0:0:0:0): Error 5, Retries exhausted
Sep 23 08:34:54 freenas (da0:umass-sim0:0:0:0): got CAM status 0x44
Sep 23 08:34:54 freenas (da0:umass-sim0:0:0:0): fatal error, failed to attach to device
Sep 23 08:34:54 freenas da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
Sep 23 08:34:54 freenas da0: < USB DISK 3.2 8.01> s/n 041A0DCD detached
Sep 23 08:34:54 freenas g_access(952): provider da0 has error 6 set
Sep 23 08:34:54 freenas g_access(952): provider da0 has error 6 set
Sep 23 08:34:54 freenas g_access(952): provider da0 has error 6 set
Sep 23 08:34:54 freenas g_access(952): provider da0 has error 6 set
Sep 23 08:34:54 freenas g_access(952): provider da0 has error 6 set
Sep 23 08:34:54 freenas g_access(952): provider da0 has error 6 set
Sep 23 08:34:59 freenas (da0:umass-sim0:0:0:0): Periph destroyed

This is the only large USB Memory I have. I really should/will buy a selection of sizes to mitigate further experiences. (Once upon a time I would have bought these freely but Retirement has curtailed that sort of activity.)
Unless you have any more suggestions are you satisfied that this is faulty?

smithi · Sep 23, 2023

fixit9660 said:
I'm running FreeBSD 11.3-RELEASE-p14 FreeNAS-11.3-U5

Mmm.

fixit9660 said:
I tried to run the command:
dd if=/dev/zero of=/dev/da0 bs=1024k oflag=sync status=progress conv=noerror,sync
but it didn't like the oflag operand:
dd: unknown operand oflag

Not important here, methinks.

fixit9660 said:
I checked the FreeBSD 11.3 man page and it does specify this operand so I don't understand why it doesn't like it. I then omitted it and it ran, but like an idiot I managed to Control-C it. This is what I got before:
dd if=/dev/zero of=/dev/da0 bs=1024k status=progress conv=noerror,sync 1048576 bytes (1049 kB, 1024 KiB) transferred 3.054s, 343 kB/s 2097152 bytes (2097 kB, 2048 KiB) transferred 6.111s, 343 kB/s 3145728 bytes (3146 kB, 3072 KiB) transferred 9.207s, 342 kB/s ^C^C 4+0 records in 3+0 records out 3145728 bytes transferred in 110.989108 secs (28343 bytes/sec)

Yeah well, roughly 120 × 10^9 / (340 × 10^3) is in the order of 379,000 seconds, call it 105 hours or 4.4 days.

At USB2 speed of 40MB/s it should take less than an hour, but it was in strife immediately.

fixit9660 said:
This is the only large USB Memory I have. I really should/will buy a selection of sizes to mitigate further experiences. (Once upon a time I would have bought these freely but Retirement has curtailed that sort of activity.)

Even 32G is a lot of snapshots and video cuttings, and 32G sticks - especially USB2 if that's all your box does - are 'cheap as chips' these days, AU$5 free postage, $10 USB3 (£5?)

fixit9660 said:
Unless you have any more suggestions are you satisfied that this is faulty?

Quite satisfied, unless it's your FreeNAS box. gpw928's post says it better, I'm just adding fuel ... cheers

fixit9660 · Sep 23, 2023

That is brilliant!

I have re-tried it in my Windoze-based PC and it still fails the inbuilt OS, AOMEI Partition Assistant, and Admin-enabled CLI options for doing anything with the format. (Oddly something I have called called HDTune sees the USB and tests the media fine. It's on its own there!). I've asked the USB Memory supplier for a replacement.

Thank you all very much for your help and patience. It is very much appreciated!!