Jump to content

dlandon

Community Developer
  • Posts

    10,397
  • Joined

  • Last visited

  • Days Won

    20

Everything posted by dlandon

  1. Your disk went offline and the back online: Dec 11 13:01:57 Gerwig kernel: sd 7:0:1:0: attempting task abort! scmd(00000000b8fc9a6f) Dec 11 13:01:57 Gerwig kernel: sd 7:0:1:0: [sdc] tag#2292 CDB: opcode=0x85 85 06 20 00 d8 00 00 00 00 00 4f 00 c2 00 b0 00 Dec 11 13:01:57 Gerwig kernel: scsi target7:0:1: handle(0x000a), sas_address(0x50030480010d2f0d), phy(13) Dec 11 13:01:57 Gerwig kernel: scsi target7:0:1: enclosure logical id(0x50030480010d2f3f), slot(1) Dec 11 13:01:57 Gerwig kernel: sd 7:0:1:0: device_block, handle(0x000a) Dec 11 13:01:59 Gerwig kernel: sd 7:0:1:0: device_unblock and setting to running, handle(0x000a) Dec 11 13:01:59 Gerwig kernel: sd 7:0:1:0: [sdc] Synchronizing SCSI cache Dec 11 13:01:59 Gerwig kernel: sd 7:0:1:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Dec 11 13:02:00 Gerwig kernel: scsi 7:0:1:0: task abort: SUCCESS scmd(00000000b8fc9a6f) Dec 11 13:02:00 Gerwig kernel: mpt2sas_cm0: removing handle(0x000a), sas_addr(0x50030480010d2f0d) Dec 11 13:02:00 Gerwig kernel: mpt2sas_cm0: enclosure logical id(0x50030480010d2f3f), slot(1) Dec 11 13:02:03 Gerwig kernel: scsi 7:0:15:0: Direct-Access ATA ST12000VN0008-2P SC61 PQ: 0 ANSI: 6 Dec 11 13:02:03 Gerwig kernel: scsi 7:0:15:0: SATA: handle(0x000a), sas_addr(0x50030480010d2f0d), phy(13), device_name(0x0000000000000000) Dec 11 13:02:03 Gerwig kernel: scsi 7:0:15:0: enclosure logical id (0x50030480010d2f3f), slot(1) Dec 11 13:02:03 Gerwig kernel: scsi 7:0:15:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) -> Dec 11 13:02:03 Gerwig kernel: sd 7:0:15:0: Power-on or device reset occurred Dec 11 13:02:03 Gerwig kernel: sd 7:0:15:0: Attached scsi generic sg2 type 0 Dec 11 13:02:03 Gerwig kernel: sd 7:0:15:0: [sdp] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB) Dec 11 13:02:03 Gerwig kernel: sd 7:0:15:0: [sdp] 4096-byte physical blocks Dec 11 13:02:03 Gerwig kernel: sd 7:0:15:0: [sdp] Write Protect is off Dec 11 13:02:03 Gerwig kernel: sd 7:0:15:0: [sdp] Mode Sense: 7f 00 10 08 Dec 11 13:02:03 Gerwig kernel: sd 7:0:15:0: [sdp] Write cache: enabled, read cache: enabled, supports DPO and FUA Dec 11 13:02:03 Gerwig kernel: sdp: sdp1 Dec 11 13:02:03 Gerwig kernel: sd 7:0:15:0: [sdp] Attached SCSI disk I'm not a disk or controller expert, so I can't help with the problem you are having. Maybe @JorgeB can help. He is the disk and controller guru.
  2. If you have UD remote shares mounted, unmount them one at a time and see if the log entries go away.
  3. Read the recommended post at the top of this forum to see if it applies to you.
  4. Read the recommended post at the top of this forum to see if that applies to you.
  5. Looks like you are using an old version of UD. You should update it.
  6. UD can still be used, but a pool device is a better way.
  7. The message in the status line won't go away until you stop and restart the server. Unraid will overwrite the status line message. Or you can reboot the server.
  8. I just released an update to today's release that will cut down on the slowness of UD in certain circumstances, and stop some of the time out errors in the log. UD should be more responsive now.
  9. Disk devices will be mounted at /mnt/disks/. Remote shares (NFS and SMB), will mount at /mnt/remotes/. The are mounts of shares from a remote server or computer system. Some users mount remote media for an app like Plex. They would map the remote media mount point in a Plex Docker Container so it would be available to Plex. You will have to provide your diagnostics before I could help with the fstrim issue.
  10. No. If you have the latest version, you are good to go.
  11. No. All UD configuration settings are retained.
  12. New release of UD: - Beginning with 6.9, you can now spin up/down disks by clicking on the disk ball the same as array devices. - Added a switch to show/hide Historical Devices. Show all/none disk partitions has been moved to a UD Setting. - Do some updates to status to background tasks to improve responsiveness.
  13. Your disk has a problem: Dec 9 15:11:48 NAS unassigned.devices: Adding disk '/dev/mapper/WDC_WD100EMAZ-00WJTA0_2YJ4RU7D'... Dec 9 15:11:49 NAS kernel: usb 7-4: reset SuperSpeedPlus Gen 2 USB device number 2 using xhci_hcd Dec 9 15:11:49 NAS kernel: sd 8:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 Dec 9 15:11:49 NAS kernel: sd 8:0:0:0: [sdf] tag#0 CDB: opcode=0x88 88 00 00 00 00 04 8c 3f fc 08 00 00 00 08 00 00 Dec 9 15:11:49 NAS kernel: print_req_error: I/O error, dev sdf, sector 19532872712 Dec 9 15:11:49 NAS unassigned.devices: Mount drive command: /sbin/mount -o rw,noatime,nodiratime '/dev/mapper/WDC_WD100EMAZ-00WJTA0_2YJ4RU7D' '/mnt/disks/WDC_WD100EMAZ-00WJTA0_2YJ4RU7D' Dec 9 15:11:49 NAS kernel: XFS (dm-3): Mounting V5 Filesystem Dec 9 15:11:50 NAS kernel: usb 7-4: reset SuperSpeedPlus Gen 2 USB device number 2 using xhci_hcd ### [PREVIOUS LINE REPEATED 5 TIMES] ### Dec 9 15:11:51 NAS kernel: sd 8:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 Dec 9 15:11:51 NAS kernel: sd 8:0:0:0: [sdf] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 02 80 00 9a 8a 00 00 08 00 00 00 Dec 9 15:11:51 NAS kernel: print_req_error: I/O error, dev sdf, sector 10737457802 Dec 9 15:11:51 NAS kernel: usb 7-4: reset SuperSpeedPlus Gen 2 USB device number 2 using xhci_hcd ### [PREVIOUS LINE REPEATED 5 TIMES] ### Dec 9 15:11:52 NAS kernel: sd 8:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 Dec 9 15:11:52 NAS kernel: sd 8:0:0:0: [sdf] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 02 80 00 a2 8a 00 00 08 00 00 00 Dec 9 15:11:52 NAS kernel: print_req_error: I/O error, dev sdf, sector 10737459850 Dec 9 15:11:52 NAS kernel: XFS (dm-3): xfs_do_force_shutdown(0x1) called from line 1270 of file fs/xfs/xfs_buf.c. Return address = 000000000e68283a Dec 9 15:11:52 NAS kernel: XFS (dm-3): I/O Error Detected. Shutting down filesystem Dec 9 15:11:52 NAS kernel: XFS (dm-3): Please umount the filesystem and rectify the problem(s) Dec 9 15:11:52 NAS kernel: XFS (dm-3): metadata I/O error in "xlog_bwrite" at daddr 0x280008a4a len 8192 error 5 Dec 9 15:11:52 NAS kernel: XFS (dm-3): failed to locate log tail Dec 9 15:11:52 NAS kernel: XFS (dm-3): log mount/recovery failed: error -5 Dec 9 15:11:52 NAS kernel: XFS (dm-3): log mount failed Dec 9 15:11:53 NAS unassigned.devices: Mount of '/dev/mapper/WDC_WD100EMAZ-00WJTA0_2YJ4RU7D' failed. Error message: mount: /mnt/disks/WDC_WD100EMAZ-00WJTA0_2YJ4RU7D: can't read superblock on /dev/mapper/WDC_WD100EMAZ-00WJTA0_2YJ4RU7D. Dec 9 15:11:53 NAS unassigned.devices: Partition 'WDC_WD100EMAZ-00WJTA0_2YJ4RU7D' could not be mounted.
  14. The Dashboard is managed by Unraid. UD only manages the Main/Unassigned Devices. It is only a display issue. it does not affect UD operation.
  15. Start by removing the preclear plugin. As a note to everyone, preclear has a background task (rc.diskinfo) that does some disk I/O that can be problematic to UD. This task runs even when a preclear is not happening. If you are not preclearing any disks, please remove the plugin.
  16. That's the way it works right now. Once I get feedback that it is working on 6.9, I'll enable it for 6.8.3.
×
×
  • Create New...