dlandon

The nvme drive format problem has been fixed in the next releaase of UD.

Can't help unless you post diagnostics.

Update to the latest version. It has more explanation.

I've actually disabled USB3 in my BIOS and have zero issues with any of my USB devices. Speed is not a concern to me when doing backups and copies. I just plug them in and walk away until they are done. The USB keyboard I use won't work right unless I use it in a USB2 port.

Yes on the USB port. Try a USB2 port. Sometimes there are issues with USB3. Check your BIOS USB settings. You may want to turn off USB3, or maybe a legacy USB setting?

Is this disk in a docking station?

Looks like more disk issues: Mar 8 14:09:16 Tower kernel: ACPI Error: AE_AML_BUFFER_LIMIT, Evaluating _PMM (20180810/power_meter-338) Mar 9 00:45:16 Tower ntfs-3g[10025]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 9 00:45:16 Tower ntfs-3g[10025]: Failed to read vcn 0x0: Input/output error Mar 9 00:45:16 Tower ntfs-3g[10025]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 9 00:45:16 Tower ntfs-3g[10025]: Failed to read $MFT bitmap: Input/output error Mar 9 00:45:16 Tower kernel: Buffer I/O error on dev sdb1, logical block 1042943528, async page read Mar 9 00:45:16 Tower kernel: Buffer I/O error on dev sdb1, logical block 222969621, async page read Mar 9 00:45:18 Tower ntfs-3g[10025]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 9 00:45:18 Tower ntfs-3g[10025]: Failed to read vcn 0x0: Input/output error Mar 9 00:45:18 Tower ntfs-3g[10025]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 9 00:45:18 Tower ntfs-3g[10025]: Failed to read vcn 0x0: Input/output error Mar 9 00:45:18 Tower kernel: Buffer I/O error on dev sdb1, logical block 365629928, async page read Mar 9 00:45:18 Tower kernel: Buffer I/O error on dev sdb1, logical block 368747454, async page read Mar 9 00:45:18 Tower kernel: Buffer I/O error on dev sdb1, logical block 222969621, async page read Mar 9 00:45:18 Tower ntfs-3g[10025]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 9 00:45:18 Tower ntfs-3g[10025]: Failed to read $MFT bitmap: Input/output error Mar 9 00:45:18 Tower ntfs-3g[10025]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 9 00:45:18 Tower ntfs-3g[10025]: Failed to read $MFT bitmap: Input/output error Mar 9 00:45:18 Tower ntfs-3g[10025]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 9 00:45:18 Tower ntfs-3g[10025]: Failed to read vcn 0x0: Input/output error Mar 9 00:45:18 Tower ntfs-3g[10025]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 9 00:45:18 Tower ntfs-3g[10025]: Failed to read $MFT bitmap: Input/output error Mar 9 00:45:18 Tower kernel: Buffer I/O error on dev sdb1, logical block 222969621, async page read Mar 9 00:45:18 Tower kernel: Buffer I/O error on dev sdb1, logical block 1042943528, async page read Mar 9 00:45:18 Tower kernel: Buffer I/O error on dev sdb1, logical block 222969621, async page read Mar 9 00:45:18 Tower ntfs-3g[10025]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 9 00:45:18 Tower kernel: Buffer I/O error on dev sdb1, logical block 478551780, async page read Mar 9 00:45:18 Tower ntfs-3g[10025]: Failed to read vcn 0x4: Input/output error Mar 9 00:45:18 Tower ntfs-3g[10025]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 9 00:45:18 Tower ntfs-3g[10025]: Failed to read $MFT bitmap: Input/output error Mar 9 00:45:18 Tower kernel: Buffer I/O error on dev sdb1, logical block 222969621, async page read Mar 9 00:45:18 Tower ntfs-3g[10025]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 9 00:45:18 Tower ntfs-3g[10025]: Failed to read vcn 0x4: Input/output error Mar 9 00:45:18 Tower ntfs-3g[10025]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Mar 9 00:45:18 Tower ntfs-3g[10025]: Failed to read $MFT bitmap: Input/output error Mar 9 00:45:18 Tower ntfs-3g[10025]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error

I updated to 8.0.0. Let's see how it goes.

To format an encrypted disk for use in UD. This requires Unraid 6.8 or newer. Choose either XFS or BTRFS encrypted as the format. You will be prompted for a password for this disk. This is not the array password, it is only for the disk being formatted. Enter 'Yes' to format this disk. Go to the UD Settings and you'll see this disk as a selection for setting the password. Enter the password used to format the disk. Mount the disk to verify it can be mounted with the password setting. This disk can now be auto mounted and used like any other UD disk. Notes: I recommend you cut and paste the password(s) to be sure you don't have a typo. Record the password you used for this disk in a safe place. It cannot be recovered. Keep a backup of your flash drive off Unraid. The disk password is stored in the UD settings. The passwords are encrypted in the UD settings file. An SSD disk will have discard disabled. It cannot be trimmed. This is for security reasons. This is not a UD limitation. Unraid 6.8 creates encrypted partitions using LUKSv2. You won't be able to use this disk in any previous version of Unraid. Previous Unraid versions use LUKSv1 and won't be able to mount the disk. If you want to enter the password for a disk on every reboot. Set the disk to not auto mount. Enter the password in UD settings. Mount the disk. Clear the password in UD settings.

You didn’t update ownCloud.

Some changes. You can now format an encrypted disk for use with UD without having an encrypted array, or format a disk with a different password from the array for use in UD. You enter the pasword when the disk is formatted if you want it to be different from the array.

UD disks are handled differently from array disks. UD does not have the disk spin down control or disk health monitoring. Unraid does not have any control over UD disks. A new feature being worked on will allow multiple cache disks. You can then move the UD disk to the array and have spin down control.

UD does no have spin down control.

Works for me.

You'll need to reboot your server: Mar 10 23:55:22 Tower unassigned.devices: Unmount cmd: /sbin/umount -t cifs '//FREENAS/sharedrive' 2>&1 Mar 10 23:55:22 Tower unassigned.devices: Unmount of '//FREENAS/sharedrive' failed. Error message: umount: /mnt/disks/FREENAS_sharedrive: no mount point specified. Mar 10 23:55:23 Tower unassigned.devices: Since there aren't any open files, will force unmount. Mar 10 23:55:23 Tower unassigned.devices: Unmounting '//FREENAS/sharedrive'... Mar 10 23:55:23 Tower unassigned.devices: Unmount cmd: /sbin/umount -t cifs -fl '//FREENAS/sharedrive' 2>&1 Mar 10 23:55:23 Tower unassigned.devices: Unmount of '//FREENAS/sharedrive' failed. Error message: umount: /mnt/disks/FREENAS_sharedrive: no mount point specified. Your remote share lost it's mount point.

Post diagnostics. Can't help without that.

Additional information on encryoted disks in UD: You have to have at least one encrypted disk in the array to format an encrypted disk for the array with UD. Unraid needs to know the password so UD can format the disk. This feature is intended for formatting disks that will end up in the array. You can mount an encrypted disk that has come out of the array. If a dsk is already encrypted, UD can mount it if you set the password in the UD settings for that disk. You don't need an encrypted disk in the array. This feature is intended for backups, etc onto encrypted disks. You can format a luks encrypted disk with UD. You will be prompted for a password when the disk is formatted. To get UD to mount the disk, you need to enter the disk password in UD settings. You don't need an encrypted disk in the array.

Your disks are also running pretty hot.

That's not possible because UD+ is not installed: statistics.sender.plg - 2017.09.22 unassigned.devices.plg - 2020.02.09 unbalance.plg - v2019.10.26 unRAIDServer.plg - 6.8.2 You are having disk issues. This is only a sample of the log: Feb 29 02:42:36 OMICRON kernel: ata10: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 29 02:42:36 OMICRON kernel: ata10.00: link online but device misclassified Feb 29 02:42:40 OMICRON kernel: ata10.00: failed to IDENTIFY (I/O error, err_mask=0x100) Feb 29 02:42:40 OMICRON kernel: ata10.00: revalidation failed (errno=-5) Feb 29 02:42:40 OMICRON kernel: ata10.00: disabled Feb 29 02:42:41 OMICRON kernel: ata10: hard resetting link Feb 29 02:42:51 OMICRON kernel: ata10: softreset failed (1st FIS failed) Feb 29 02:42:51 OMICRON kernel: ata10: hard resetting link Feb 29 02:43:01 OMICRON kernel: ata10: softreset failed (1st FIS failed) Feb 29 02:43:01 OMICRON kernel: ata10: hard resetting link Feb 29 02:43:36 OMICRON kernel: ata10: softreset failed (1st FIS failed) Feb 29 02:43:36 OMICRON kernel: ata10: limiting SATA link speed to 3.0 Gbps Feb 29 02:43:36 OMICRON kernel: ata10: hard resetting link Feb 29 02:43:42 OMICRON kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Feb 29 02:43:42 OMICRON kernel: ata10.00: link online but device misclassified Feb 29 02:43:42 OMICRON kernel: ata10: link online but 1 devices misclassified, device detection might fail Feb 29 02:43:42 OMICRON kernel: sd 10:0:0:0: [sdk] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 29 02:43:42 OMICRON kernel: sd 10:0:0:0: [sdk] tag#6 Sense Key : 0x5 [current] Feb 29 02:43:42 OMICRON kernel: sd 10:0:0:0: [sdk] tag#6 ASC=0x21 ASCQ=0x4 Feb 29 02:43:42 OMICRON kernel: sd 10:0:0:0: [sdk] tag#6 CDB: opcode=0x88 88 00 00 00 00 01 36 aa 01 b8 00 00 01 00 00 00 Feb 29 02:43:42 OMICRON kernel: print_req_error: I/O error, dev sdk, sector 5212078520 Feb 29 02:43:42 OMICRON kernel: md: disk8 read error, sector=5212078456 Feb 29 02:43:42 OMICRON kernel: md: disk8 read error, sector=5212078464 Feb 29 02:43:42 OMICRON kernel: md: disk8 read error, sector=5212078472 Feb 29 02:43:42 OMICRON kernel: md: disk8 read error, sector=5212078480 Recommendations: Solve the disk issues before you do anything else to the array. You'll make it worse. Check cabling and disk controller. Update your plugins. You are way behind.

I keep forgetting that detail.

@Squid Why has UD been blackisted by CA in 6.9? Edit: I see it. Looks like CA hasn't caught up with my plugin update.

Fixed with the latest update.

I'll fix it.

Sorry to be so late to the party, but what file format are you using?

UD now incorporates this functionality, with the exception of multiple partitions.