USB is known for being flaky and randomly disconnecting. Normally it is not an issue since it just reconnects it almost instantly with normal USB devices. Bit different with things like hard drives and such.

 

My guess is that the USB is just disconnecting and that is causing your trouble.

 

To fix it, first thing I would do is a new cable and try a different USB port. This will sort it out most of the time if it is not a hardware issue.

I had a new 12TB disk (attached via USB) fail on preclear twice now.

I am on Unraid 6.9.0-beta25 with Unassigned Devices 2020.07.26b (Plus 2020.05.22). I also tried on Unraid 6.8.3 before upgrading to the new beta.

Here is the disk log which is showing errors that I do not understand. Furthermore the errors seems to happen earlier before the webui notified me that the preclear had failed.

I have precleared other USB disk drives multiple times before (> 6 months). However recently (< 1-2 months) I am having problems with other disks attached via USB (causing docker/system hangs and other nasty things)
 

Jul 29 19:43:31 MasterTower kernel: sd 1:0:0:0: [sdb] 1465081856 512-byte logical blocks: (750 GB/699 GiB)
Jul 29 19:43:31 MasterTower kernel: sd 1:0:0:0: [sdb] Write Protect is off
Jul 29 19:43:31 MasterTower kernel: sd 1:0:0:0: [sdb] Mode Sense: 47 00 10 08
Jul 29 19:43:31 MasterTower kernel: sd 1:0:0:0: [sdb] No Caching mode page found
Jul 29 19:43:31 MasterTower kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
Jul 29 19:43:31 MasterTower kernel: sdb: sdb1
Jul 29 19:43:31 MasterTower kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Jul 29 19:43:31 MasterTower kernel: BTRFS: device label cache1 devid 2 transid 9272 /dev/sdb1 scanned by udevd (1339)
Jul 29 19:44:13 MasterTower emhttpd: WD_Elements_25A3_574D41553430303136323237-0:0 (sdb) 512 1465081856
Jul 29 19:48:38 MasterTower kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
Jul 29 19:48:38 MasterTower kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 00 00 00 00 00 00 20 00
Jul 29 19:48:38 MasterTower kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
Jul 29 19:48:38 MasterTower kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jul 29 19:48:38 MasterTower kernel: Buffer I/O error on dev sdb, logical block 0, async page read
Jul 30 17:18:01 MasterTower kernel: sd 1:0:0:0: [sdb] Spinning up disk...
Jul 30 17:18:18 MasterTower kernel: sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Jul 30 17:18:18 MasterTower kernel: sd 1:0:0:0: [sdb] 23437705216 512-byte logical blocks: (12.0 TB/10.9 TiB)
Jul 30 17:18:18 MasterTower kernel: sd 1:0:0:0: [sdb] 4096-byte physical blocks
Jul 30 17:18:18 MasterTower kernel: sd 1:0:0:0: [sdb] Write Protect is off
Jul 30 17:18:18 MasterTower kernel: sd 1:0:0:0: [sdb] Mode Sense: 47 00 10 08
Jul 30 17:18:18 MasterTower kernel: sd 1:0:0:0: [sdb] No Caching mode page found
Jul 30 17:18:18 MasterTower kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
Jul 30 17:18:18 MasterTower kernel: sdb: sdb1
Jul 30 17:18:18 MasterTower kernel: sd 1:0:0:0: [sdb] Attached SCSI disk

 

Edited July 31, 20205 yr by ZipsServer
more info

First step is to try another USB port and cable if possible.

 

If that is not possible and you plan to shuck that drive anyways, might as well shuck it now and run the pre-clear on a sata port. You can shuck those drives pretty easy without damaging them, allowing you to put it back together if you need to return it.

 

The trick is to slide the outside case off the cage and not pry it off. Look up some videos on youtube if needed.

I should have mentioned that I already tried another USB port (one integrated on the MB and one plugged in to the MB via an adapter)

I also do not have any SATA ports free. I only have 14 slots and they are all filled. Really need to upgrade to a new case/SAS backplane. (That is also why I am running three other drives via USB ports)

ouch, you are in a touch spot.

 

I have had pretty good luck with USB to 3.5" docks but I only use them for backups, never had an issue with them but then I also generally only use them for short periods for backups.

 

One thing I know is that unless you have a fan blowing on the external drives, they can easily get very hot and that could lead to issues. I have  a 120mm fan connected to a USB port with an adapter off ebay that works great at keeping temps under control and it is quite due to only being run at 5v.

Edited July 31, 20205 yr by TexasUnraid

Hi all. I have a SD/MicroSD card reader, and the MicroSD port shows up as its own device under UD, but I never use it. I'd like to hide it in UD. Is this possible?

You can't hide a device from UD.  The best you can do is to mark it as passed through so UD will ignore it.

9 hours ago, dlandon said:

You can't hide a device from UD.  The best you can do is to mark it as passed through so UD will ignore it.

Good info, thank you! How do you go about marking an unassigned device as pass through? I poked around the UD settings but I'm not seeing anything.

3 hours ago, Phoenix Down said:

Good info, thank you! How do you go about marking an unassigned device as pass through? I poked around the UD settings but I'm not seeing anything.

'Pass Thru' switch in the UD page.

5 hours ago, dlandon said:

'Pass Thru' switch in the UD page.

Mount button is grayed out and "Pass Thru" column (and most every column) is just "-". I suppose I need to have a MicroSD card inserted to activate the Pass Thru option?

3 hours ago, Phoenix Down said:

Mount button is grayed out and "Pass Thru" column (and most every column) is just "-". I suppose I need to have a MicroSD card inserted to activate the Pass Thru option?

Setting pass through will not do anything more than what you already have.

Is the encryption done through Disk Utility on Mac OS in the format Mac OS Extended (Journaled, Encrypted) supported? When mounting the disk the encrypted partition won't mount, but I also can't use the Set Encrypted Disk Password to select the disk and enter the Disk Password. If not what is the recommended way to encrypt a drive for use in Unraid and Mac OS?

9 hours ago, Moniker01 said:

Is the encryption done through Disk Utility on Mac OS in the format Mac OS Extended (Journaled, Encrypted) supported?

I doubt it.  Unraid encryption uses Linux Luks encryption.  I doubt Mac OS will support that and vice versa.

Ok so I removed the encryption. Now I get an error when running an rsync:

rsync: write failed on "/mnt/disks/Drive": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(374) [receiver=3.1.3]

The drive is an empty 1TB 2.5 inch SATA HD connected via a USB to SATA adapter. No matter what file size I try and transfer I get the error.

Post diagnostics.

scarif-diagnostics-20200805-1138.zip

Mount the disk and show a screen shot of the disk on the UD page.

 

Edit: Click the '+' so all partitions show.

Edited August 5, 20205 yr by dlandon

I'm away from my network right now, and had someone send me the screenshot, so while in the image the drive isn't mounted, when I was running rsync, both partitions were mounted. EFI had something like 11MB used of 212MB and the other about 600MB out of 1TB.

Edited August 5, 20205 yr by Moniker01
Add info

Which partition are you trying to copy files to?

10 hours ago, Moniker01 said:

rsync: write failed on "/mnt/disks/Drive": No space left on device (28)

This is neither of those partitions.  One is 'EFI' the other is a disk serial number.

38 minutes ago, dlandon said:

Which partition are you trying to copy files to?

This is neither of those partitions.  One is 'EFI' the other is a disk serial number.

Apologies, it was the one with the serial number but in order to condense, I replaced the serial number with "drive"

Here is an image with the drive mounted.

28 minutes ago, Moniker01 said:

Apologies, it was the one with the serial number but in order to condense, I replaced the serial number with "drive"

Here is an image with the drive mounted.

So are you saying that you edited the error message from rsync that you posted earlier and condensed that error message by replacing the serial number with "Drive"?

 

Or are you saying that you think you have successfully changed the mount name to "Drive"?

 

What do you get from the command line with this?

ls -lah /mnt/disks

 

 

The second partition has more than enough room.  I would change the mount point of that partition to something easier to work with.  That complex serial number is a bit difficult to work with in a script.

Error is

rsync: write failed on "/mnt/disks/APPLE_HDD_HTS_541010A9E662_JD8002EZOXX3TD": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(374) [receiver=3.1.3]

8 minutes ago, Moniker01 said:

/mnt/disks/APPLE_HDD_HTS_541010A9E662_JD8002EZOXX3TD

The destination is /mnt/disks/APPLE_HDD_HTS_541010A9E662_JD8002EZOXX3TD-part2.

 

As I said earlier, change the mount point of the second partition to a meaningful name and use that as the destination.

Edited August 5, 20205 yr by dlandon

On 8/5/2020 at 10:12 AM, dlandon said:

The destination is /mnt/disks/APPLE_HDD_HTS_541010A9E662_JD8002EZOXX3TD-part2.

 

As I said earlier, change the mount point of the second partition to a meaningful name and use that as the destination.

Thanks for your help. I'm still having issues, but I'm pretty busy with other stuff right nw, so if I have any more issues, I'll ask them in a few days