Jump to content

Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

dlandon

By dlandon
in Plugin Support

Recommended Posts

Recommended

Posted by dlandon,

If you are seeing unexplained disk or remote share activity, it may be due to cache dirs caching all folders.  For those of you using the Cache Dirs plugin, you need to specify folders to be included so UD mounted disks and shares do not get included automatically.  This can also apply to pool disks.  It's really the best practice to specify the included folders so you control what is actually being cached.
Recommended by Squid

0 reactions

Go to this post
Recommended

Posted by dlandon,

New release of UD.  The changes are: - Add ability to spin down a disk by sdX.  You don't have to spin down disks by name= any more.  This is still available for spinning down a disk from a User Script because you won't know the correct sdX as it changes on reboot. - Add the ability to detach a disk when a UD script is finished using 'rc.unassigned'.  This detaches the disk from Unraid and should provide a potentially safer way to remove a USB device.  Applies to USB disks only. -
Recommended by SpencerJ
  • Upvote
  • Like

2 reactions

Go to this post
Recommended

Posted by dlandon,

There is a new feature in UD to help with plugins that need a mount point folder.  UD now creates a mount folder '/mnt/addons'.  This folder should be used to mount your plugin devices to prevent FCP warnings and keep your mounts separated from UD.  It is recommended you switch to this new folder for your addon and custom mounts.  You are welcome to leave the mounts at '/mnt/disks' or '/mnt/remotes'.  Things will still work, but if you request support for UD issues, you will be asked to remove t

UD is now creating a mount point folder for plugins and addons

Recommended by dlandon

0 reactions

Go to this post
Recommended

Posted by dlandon,

The recent changes to the way UD checks for remote servers being online were done to eliminate the inappropriate way UD was managing remote server names trying to get around local DNS name lookup issues.  The way it works now is using several methods to lookup server names after an IP address is found to have an open SMB or NFS port when searching for servers.  Nmblookup and avahi are used to find the names.  The issue comes when UD tries to verify the server is online with the servername and no
Recommended by dlandon

0 reactions

Go to this post
l3gion Rookie

l3gion

Posted
Posted (edited)
On 10/6/2024 at 3:23 PM, dlandon said:

Go to a command line and enter the command 'ud_diagnostics', then post the /flash/logs/ud_diagnostics.zip file.  Also post the Unraid diagnostics.

Hi again,

I found out the issue was because I wasn't detaching the drives before disconnecting them from the server. After the detach of one of the 2 drives I have, my second one was also able to re-connect, odd.

With regular USB sticks I never had to detach, but seems to be necessary for external Nvme drives, the button is a bit hidden away in the drive properties, maybe making the detach button available in the device list page next to the mount button would be nice :)

 

Thank you.

Edited by l3gion
Link to comment
  • Replies 11.2k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

dlandon
dlandon

It's that self healing feature I built into UD.  It just fixes itself.

dlandon
dlandon

New release of UD.  Changes: When changing the mount point (which is also the share name), the mount point is checked for a duplicate of a user share or another UD device.  Samba cannot handle

dlandon
dlandon

Major new release of UD: "Where are the switches?"  The "Pass Through", "Read Only", "Automount", and "Share" switches have been moved to a new Edit Settings dialog.  This is also where the sc

Posted Images

dlandon Veteran

dlandon

Posted
  • Author
Posted
18 minutes ago, l3gion said:

Hi again,

I found out the issue was because I wasn't detaching the drives before disconnecting them from the server. After the detach of one of the 2 drives I have, my second one was also able to re-connect, odd.

With regular USB sticks I never had to detach, but seems to be necessary for external Nvme drives, the button is a bit hidden away in the drive properties, maybe making the detach button available in the device list page next to the mount button would be nice :)

 

Thank you.

You can detach the device programatically in a script.  Go to the UD page and click on the help icon and look at the rc.unassigned script commands for how to do it.

 

It's also included in the default UD device script, but is commented out.

 

Just be sure the device is fully unmounted first.

Link to comment
timc6896 Noob

timc6896

Posted
Posted (edited)
14 hours ago, dlandon said:

Post ud_diagnostics by going to a command line and executing the command 'ud_diagnostics' and then post the '/flash/logs/ud_diagnostics.log file'.  Also post Unraid diagnostics.

 

 

Edited by timc6896
This set of logs captures when everything was working to the behavior that I'm seeing where the drives are not accessible because they have changed to "Reboot" instead off spundown.
Link to comment
dlandon Veteran

dlandon

Posted
  • Author
Posted
3 hours ago, timc6896 said:

Here's what I'm looking at

B60F405B-74B3-421E-AEA0-A1E81652174C.jpeg

It looks like your expander is reporting disk partitions incorrectly, or Linux is confused about partiutions.  For example: 

[/dev/sdq]
ACTION="add"
DEVLINKS="/dev/disk/by-id/ata-HUH728080ALE601_VJGU11NX-part1 /dev/disk/by-id/wwn-0x5000cca261cb613b-part1 /dev/disk/by-label/_VJGU11NX /dev/disk/by-partuuid/ba941532-6339-466e-b184-207d8dca3dc7 /dev/disk/by-path/pci-0000:00:10.0-sas-exp0x50030480004c4cbf-phy26-lun-0-part1 /dev/disk/by-uuid/3d1454c4-d04d-40f4-90ef-07979c3a2eb6"
DEVNAME="/dev/sdcq1"
DEVPATH="/devices/pci0000:00/0000:00:10.0/host4/port-4:0/expander-4:0/port-4:0:277/end_device-4:0:277/target4:0:315/4:0:315:0/block/sdcq/sdcq1"
DEVTYPE="partition"

Is reporting partition '/dev/sdcq1' on disk '/dev/sdq'.

  

[/dev/sdcb]
ACTION="add"
DEVLINKS="/dev/disk/by-id/ata-HUH728080ALE601_VJGU11NX-part1 /dev/disk/by-id/wwn-0x5000cca261cb613b-part1 /dev/disk/by-label/_VJGU11NX /dev/disk/by-partuuid/ba941532-6339-466e-b184-207d8dca3dc7 /dev/disk/by-path/pci-0000:00:10.0-sas-exp0x50030480004c4cbf-phy26-lun-0-part1 /dev/disk/by-uuid/3d1454c4-d04d-40f4-90ef-07979c3a2eb6"
DEVNAME="/dev/sdcq1"

Is reporting partition '/dev/sdcq1' on disk '/dev/sdcb'.

 

Try downgrading to a version of Unraid that you think may have worked.  Also try Unraid 7.0 beta and see if that works.

 

EDIT: So I found this situation is a bug in UD, but not sure how it could cause your issue.

Link to comment
JorgeB Grand Master

JorgeB

Posted
Posted
3 hours ago, timc6896 said:

Here's what I'm looking at

 

Multiple disks dropped offline at the same:

  

Oct 12 01:54:35 unRaid1 kernel: sd 4:0:0:0: [sdc] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c84)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x000a), sas_addr(0x50030480004c4c84)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:1:0: [sdd] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:1:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c85)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x000b), sas_addr(0x50030480004c4c85)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:2:0: [sde] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:2:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c86)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x000c), sas_addr(0x50030480004c4c86)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:3:0: [sdf] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:3:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c87)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x000d), sas_addr(0x50030480004c4c87)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:4:0: [sdg] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:4:0: [sdg] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c88)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x000e), sas_addr(0x50030480004c4c88)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:5:0: [sdh] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:5:0: [sdh] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c89)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x000f), sas_addr(0x50030480004c4c89)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:6:0: [sdi] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:6:0: [sdi] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c8a)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0010), sas_addr(0x50030480004c4c8a)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:7:0: [sdj] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:7:0: [sdj] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c8b)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0011), sas_addr(0x50030480004c4c8b)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:8:0: device_unblock and setting to running, handle(0x0012)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:9:0: [sdl] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:9:0: [sdl] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c8d)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0013), sas_addr(0x50030480004c4c8d)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(1)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:10:0: device_unblock and setting to running, handle(0x0014)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:11:0: [sdn] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:11:0: [sdn] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c8f)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0015), sas_addr(0x50030480004c4c8f)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(3)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:12:0: [sdo] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:12:0: [sdo] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c90)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0016), sas_addr(0x50030480004c4c90)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(4)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:13:0: device_unblock and setting to running, handle(0x0017)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:14:0: device_unblock and setting to running, handle(0x0018)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:15:0: [sdr] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:15:0: [sdr] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c93)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0019), sas_addr(0x50030480004c4c93)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(7)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:16:0: [sds] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:16:0: [sds] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c94)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x001a), sas_addr(0x50030480004c4c94)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(8)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:17:0: [sdt] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:17:0: [sdt] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c95)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x001b), sas_addr(0x50030480004c4c95)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(9)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:18:0: [sdu] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:18:0: [sdu] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c96)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x001c), sas_addr(0x50030480004c4c96)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(10)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:19:0: device_unblock and setting to running, handle(0x001d)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:21:0: [sdx] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:21:0: [sdx] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c99)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x001f), sas_addr(0x50030480004c4c99)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(13)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:22:0: [sdy] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:22:0: [sdy] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c9a)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0020), sas_addr(0x50030480004c4c9a)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(14)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:23:0: [sdz] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:23:0: [sdz] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c9b)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0021), sas_addr(0x50030480004c4c9b)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(15)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:24:0: [sdaa] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:24:0: [sdaa] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c9c)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0022), sas_addr(0x50030480004c4c9c)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(16)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:25:0: device_unblock and setting to running, handle(0x0023)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:26:0: [sdac] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:26:0: [sdac] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c9e)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0024), sas_addr(0x50030480004c4c9e)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(18)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:27:0: [sdad] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:27:0: [sdad] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c9f)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0025), sas_addr(0x50030480004c4c9f)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(19)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:28:0: device_unblock and setting to running, handle(0x0026)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:29:0: [sdaf] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:29:0: [sdaf] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4ca1)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0027), sas_addr(0x50030480004c4ca1)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(21)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:30:0: [sdag] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:30:0: [sdag] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4ca2)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0028), sas_addr(0x50030480004c4ca2)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(22)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:31:0: device_unblock and setting to running, handle(0x0029)
Oct 12 01:54:36 unRaid1 kernel: mpt3sas_cm0: log_info(0x31110e05): originator(PL), code(0x11), sub_code(0x0e05)

 

And then reconnected again with a different ID:

  

Oct 12 01:54:37 unRaid1 kernel: mpt3sas_cm0: handle(0xe) sas_address(0x50030480004c4c88) port_type(0x1)
Oct 12 01:54:38 unRaid1 kernel: mpt3sas_cm0: log_info(0x31110e05): originator(PL), code(0x11), sub_code(0x0e05)
Oct 12 01:54:58 unRaid1 kernel: scsi 4:0:71:0: Direct-Access     ATA      WDC WD140EDGZ-11 0A85 PQ: 0 ANSI: 6
Oct 12 01:54:58 unRaid1 kernel: scsi 4:0:71:0: SATA: handle(0x000e), sas_addr(0x50030480004c4c88), phy(8), device_name(0x0000000000000000)
Oct 12 01:54:58 unRaid1 kernel: scsi 4:0:71:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
Oct 12 01:54:58 unRaid1 kernel: scsi 4:0:71:0: qdepth(32), tagged(1), scsi_level(7), cmd_que(1)
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:71:0: Attached scsi generic sg2 type 0
Oct 12 01:54:58 unRaid1 kernel: end_device-4:0:33: add: handle(0x000e), sas_addr(0x50030480004c4c88)
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:71:0: Power-on or device reset occurred
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:71:0: [sdbu] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB)
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:71:0: [sdbu] 4096-byte physical blocks
Oct 12 01:54:58 unRaid1 kernel: mpt3sas_cm0: handle(0xa) sas_address(0x50030480004c4c84) port_type(0x1)
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:71:0: [sdbu] Write Protect is off
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:71:0: [sdbu] Mode Sense: 9b 00 10 08
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:71:0: [sdbu] Write cache: enabled, read cache: enabled, supports DPO and FUA
Oct 12 01:54:58 unRaid1 kernel: sdbu: sdbu1
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:71:0: [sdbu] Attached SCSI disk
Oct 12 01:54:58 unRaid1 kernel: scsi 4:0:72:0: Direct-Access     ATA      ST8000DM004-2CX1 0001 PQ: 0 ANSI: 6
Oct 12 01:54:58 unRaid1 kernel: scsi 4:0:72:0: SATA: handle(0x000a), sas_addr(0x50030480004c4c84), phy(4), device_name(0x0000000000000000)
Oct 12 01:54:58 unRaid1 kernel: scsi 4:0:72:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
Oct 12 01:54:58 unRaid1 kernel: scsi 4:0:72:0: qdepth(32), tagged(1), scsi_level(7), cmd_que(1)
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:72:0: Attached scsi generic sg3 type 0
Oct 12 01:54:58 unRaid1 kernel: end_device-4:0:34: add: handle(0x000a), sas_addr(0x50030480004c4c84)
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:72:0: Power-on or device reset occurred
Oct 12 01:54:58 unRaid1 kernel: mpt3sas_cm0: handle(0xb) sas_address(0x50030480004c4c85) port_type(0x1)
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:72:0: [sdbv] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:72:0: [sdbv] 4096-byte physical blocks
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:72:0: [sdbv] Write Protect is off
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:72:0: [sdbv] Mode Sense: 9b 00 10 08
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:72:0: [sdbv] Write cache: enabled, read cache: enabled, supports DPO and FUA
Oct 12 01:54:58 unRaid1 kernel: sdbv: sdbv1
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:72:0: [sdbv] Attached SCSI disk


 

Just posting a couple to avoid a long scroll, this is usually a power/connection issue

  • Like 1
Link to comment
timc6896 Noob

timc6896

Posted
Posted
15 minutes ago, JorgeB said:

 

Multiple disks dropped offline at the same:

  

Oct 12 01:54:35 unRaid1 kernel: sd 4:0:0:0: [sdc] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c84)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x000a), sas_addr(0x50030480004c4c84)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:1:0: [sdd] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:1:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c85)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x000b), sas_addr(0x50030480004c4c85)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:2:0: [sde] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:2:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c86)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x000c), sas_addr(0x50030480004c4c86)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:3:0: [sdf] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:3:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c87)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x000d), sas_addr(0x50030480004c4c87)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:4:0: [sdg] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:4:0: [sdg] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c88)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x000e), sas_addr(0x50030480004c4c88)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:5:0: [sdh] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:5:0: [sdh] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c89)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x000f), sas_addr(0x50030480004c4c89)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:6:0: [sdi] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:6:0: [sdi] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c8a)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0010), sas_addr(0x50030480004c4c8a)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:7:0: [sdj] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:7:0: [sdj] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c8b)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0011), sas_addr(0x50030480004c4c8b)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:8:0: device_unblock and setting to running, handle(0x0012)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:9:0: [sdl] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:9:0: [sdl] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c8d)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0013), sas_addr(0x50030480004c4c8d)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(1)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:10:0: device_unblock and setting to running, handle(0x0014)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:11:0: [sdn] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:11:0: [sdn] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c8f)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0015), sas_addr(0x50030480004c4c8f)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(3)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:12:0: [sdo] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:12:0: [sdo] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c90)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0016), sas_addr(0x50030480004c4c90)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(4)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:13:0: device_unblock and setting to running, handle(0x0017)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:14:0: device_unblock and setting to running, handle(0x0018)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:15:0: [sdr] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:15:0: [sdr] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c93)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0019), sas_addr(0x50030480004c4c93)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(7)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:16:0: [sds] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:16:0: [sds] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c94)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x001a), sas_addr(0x50030480004c4c94)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(8)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:17:0: [sdt] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:17:0: [sdt] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c95)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x001b), sas_addr(0x50030480004c4c95)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(9)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:18:0: [sdu] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:18:0: [sdu] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c96)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x001c), sas_addr(0x50030480004c4c96)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(10)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:19:0: device_unblock and setting to running, handle(0x001d)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:21:0: [sdx] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:21:0: [sdx] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c99)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x001f), sas_addr(0x50030480004c4c99)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(13)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:22:0: [sdy] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:22:0: [sdy] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c9a)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0020), sas_addr(0x50030480004c4c9a)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(14)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:23:0: [sdz] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:23:0: [sdz] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c9b)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0021), sas_addr(0x50030480004c4c9b)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(15)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:24:0: [sdaa] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:24:0: [sdaa] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c9c)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0022), sas_addr(0x50030480004c4c9c)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(16)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:25:0: device_unblock and setting to running, handle(0x0023)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:26:0: [sdac] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:26:0: [sdac] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c9e)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0024), sas_addr(0x50030480004c4c9e)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(18)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:27:0: [sdad] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:27:0: [sdad] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4c9f)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0025), sas_addr(0x50030480004c4c9f)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(19)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:28:0: device_unblock and setting to running, handle(0x0026)
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:29:0: [sdaf] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:29:0: [sdaf] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4ca1)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0027), sas_addr(0x50030480004c4ca1)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(21)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:30:0: [sdag] Synchronizing SCSI cache
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:30:0: [sdag] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x50030480004c4ca2)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: removing handle(0x0028), sas_addr(0x50030480004c4ca2)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure logical id(0x50030480004c4cbf), slot(22)
Oct 12 01:54:35 unRaid1 kernel: mpt3sas_cm0: enclosure level(0x0000), connector name( 1   )
Oct 12 01:54:35 unRaid1 kernel: sd 4:0:31:0: device_unblock and setting to running, handle(0x0029)
Oct 12 01:54:36 unRaid1 kernel: mpt3sas_cm0: log_info(0x31110e05): originator(PL), code(0x11), sub_code(0x0e05)

 

And then reconnected again with a different ID:

  

Oct 12 01:54:37 unRaid1 kernel: mpt3sas_cm0: handle(0xe) sas_address(0x50030480004c4c88) port_type(0x1)
Oct 12 01:54:38 unRaid1 kernel: mpt3sas_cm0: log_info(0x31110e05): originator(PL), code(0x11), sub_code(0x0e05)
Oct 12 01:54:58 unRaid1 kernel: scsi 4:0:71:0: Direct-Access     ATA      WDC WD140EDGZ-11 0A85 PQ: 0 ANSI: 6
Oct 12 01:54:58 unRaid1 kernel: scsi 4:0:71:0: SATA: handle(0x000e), sas_addr(0x50030480004c4c88), phy(8), device_name(0x0000000000000000)
Oct 12 01:54:58 unRaid1 kernel: scsi 4:0:71:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
Oct 12 01:54:58 unRaid1 kernel: scsi 4:0:71:0: qdepth(32), tagged(1), scsi_level(7), cmd_que(1)
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:71:0: Attached scsi generic sg2 type 0
Oct 12 01:54:58 unRaid1 kernel: end_device-4:0:33: add: handle(0x000e), sas_addr(0x50030480004c4c88)
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:71:0: Power-on or device reset occurred
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:71:0: [sdbu] 27344764928 512-byte logical blocks: (14.0 TB/12.7 TiB)
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:71:0: [sdbu] 4096-byte physical blocks
Oct 12 01:54:58 unRaid1 kernel: mpt3sas_cm0: handle(0xa) sas_address(0x50030480004c4c84) port_type(0x1)
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:71:0: [sdbu] Write Protect is off
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:71:0: [sdbu] Mode Sense: 9b 00 10 08
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:71:0: [sdbu] Write cache: enabled, read cache: enabled, supports DPO and FUA
Oct 12 01:54:58 unRaid1 kernel: sdbu: sdbu1
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:71:0: [sdbu] Attached SCSI disk
Oct 12 01:54:58 unRaid1 kernel: scsi 4:0:72:0: Direct-Access     ATA      ST8000DM004-2CX1 0001 PQ: 0 ANSI: 6
Oct 12 01:54:58 unRaid1 kernel: scsi 4:0:72:0: SATA: handle(0x000a), sas_addr(0x50030480004c4c84), phy(4), device_name(0x0000000000000000)
Oct 12 01:54:58 unRaid1 kernel: scsi 4:0:72:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
Oct 12 01:54:58 unRaid1 kernel: scsi 4:0:72:0: qdepth(32), tagged(1), scsi_level(7), cmd_que(1)
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:72:0: Attached scsi generic sg3 type 0
Oct 12 01:54:58 unRaid1 kernel: end_device-4:0:34: add: handle(0x000a), sas_addr(0x50030480004c4c84)
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:72:0: Power-on or device reset occurred
Oct 12 01:54:58 unRaid1 kernel: mpt3sas_cm0: handle(0xb) sas_address(0x50030480004c4c85) port_type(0x1)
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:72:0: [sdbv] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:72:0: [sdbv] 4096-byte physical blocks
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:72:0: [sdbv] Write Protect is off
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:72:0: [sdbv] Mode Sense: 9b 00 10 08
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:72:0: [sdbv] Write cache: enabled, read cache: enabled, supports DPO and FUA
Oct 12 01:54:58 unRaid1 kernel: sdbv: sdbv1
Oct 12 01:54:58 unRaid1 kernel: sd 4:0:72:0: [sdbv] Attached SCSI disk


 

Just posting a couple to avoid a long scroll, this is usually a power/connection issue

Hmm.. I have tried 3 different enclosures, all with different 850watt power supplies that all work when under an array, but just not under Unassigned devices.  I'm wondering if the 3 drives that swapped out is causing this issue.  They are Advanced Format SAS drivers.

Link to comment
timc6896 Noob

timc6896

Posted
Posted (edited)
2 hours ago, dlandon said:

It looks like your expander is reporting disk partitions incorrectly, or Linux is confused about partiutions.  For example: 

[/dev/sdq]
ACTION="add"
DEVLINKS="/dev/disk/by-id/ata-HUH728080ALE601_VJGU11NX-part1 /dev/disk/by-id/wwn-0x5000cca261cb613b-part1 /dev/disk/by-label/_VJGU11NX /dev/disk/by-partuuid/ba941532-6339-466e-b184-207d8dca3dc7 /dev/disk/by-path/pci-0000:00:10.0-sas-exp0x50030480004c4cbf-phy26-lun-0-part1 /dev/disk/by-uuid/3d1454c4-d04d-40f4-90ef-07979c3a2eb6"
DEVNAME="/dev/sdcq1"
DEVPATH="/devices/pci0000:00/0000:00:10.0/host4/port-4:0/expander-4:0/port-4:0:277/end_device-4:0:277/target4:0:315/4:0:315:0/block/sdcq/sdcq1"
DEVTYPE="partition"

Is reporting partition '/dev/sdcq1' on disk '/dev/sdq'.

  

[/dev/sdcb]
ACTION="add"
DEVLINKS="/dev/disk/by-id/ata-HUH728080ALE601_VJGU11NX-part1 /dev/disk/by-id/wwn-0x5000cca261cb613b-part1 /dev/disk/by-label/_VJGU11NX /dev/disk/by-partuuid/ba941532-6339-466e-b184-207d8dca3dc7 /dev/disk/by-path/pci-0000:00:10.0-sas-exp0x50030480004c4cbf-phy26-lun-0-part1 /dev/disk/by-uuid/3d1454c4-d04d-40f4-90ef-07979c3a2eb6"
DEVNAME="/dev/sdcq1"

Is reporting partition '/dev/sdcq1' on disk '/dev/sdcb'.

 

Try downgrading to a version of Unraid that you think may have worked.  Also try Unraid 7.0 beta and see if that works.

 

EDIT: So I found this situation is a bug in UD, but not sure how it could cause your issue.

Do you know if there's a way for use a previous version of UD?

Edited by timc6896
Just to add to this. Originally when everything was stable, I had 3 Toshiba SAS drives that I know does not spindown because it is in the UD exclusion list. I swapped those 3 Toshiba drives with 3 HGST Advanced Format SAS drives that do spin down.
Link to comment
timc6896 Noob

timc6896

Posted
Posted
4 minutes ago, timc6896 said:

Do you know if there's a way for use a previous version of UD?

Wondering if the reason it was stable was because at least one drive was running all the time.  In my current setup, as long as I leave 39 out of 40 drivers running, everything runs fine.  As soon as I spin down the 40th drive, that's where the problem occurs.  This sounds like a bug in UD?  The same Advanced Format SAS drives works perfectly under the array with all drives spun down.

Link to comment
dlandon Veteran

dlandon

Posted
  • Author
Posted
40 minutes ago, timc6896 said:

Do you know if there's a way for use a previous version of UD?

There's not.

 

35 minutes ago, timc6896 said:

This sounds like a bug in UD?

Probably not.  Looks like your disks are dropping off-line while mounted,

Link to comment
LemonLuddite Noob

LemonLuddite

Posted
Posted
On 1/21/2016 at 3:55 PM, dlandon said:

If you want to pass a device to a VM or Docker, set the 'Pass Through' switch to on.  This will insure that UD does not try to mount the disk.  You can then pass it to a VM or Docker.  Unassigned devices will show it as unmounted after you pass it through to the VM or Docker.

 

So I setup my current config a while back. Cant remember exactly why, maybe ignorance of pass through but I didn't follow this. 

 

What I have:

  • SSD mounted normally within unraid
  • Two vdisks in it passed to a windows VM 

Generally performance is good enough for what I need but patching in windows is pretty glacial. So Im wondering has anyone benchmarked passthrough vs vdisks? If so, is it significant? 

 

Thanks 

Link to comment
alturismo Mentor

alturismo

Posted
Posted
2 hours ago, LemonLuddite said:

So Im wondering has anyone benchmarked passthrough vs vdisks? If so, is it significant? 

yes, actually hard to tell as vdisk with virtio mode ist really really fast ... so benchmarks wont really help alot here, roughly vdisk performance was even higher but ... actually too high which points me too RAM buffering ;)

 

(at least for me) i never could see any issues using vdisks, but i switched my Gaming V; from 2x vdisk to passed disk, now im there what the benchmarks should say with my nvme.

 

i stayed on passed nvme for now (Gaming VM) and still using vdisk for Desktop VM, just to make sure Games cant "suffer" from stuttering loading and so on ... just in case without ever having any issues here.

 

another benefit, i can always boot native in Windows if i ever would need it for "whatever" scenario ...

Link to comment
HansOtto Noob

HansOtto

Posted
Posted
On 10/12/2024 at 4:57 PM, dlandon said:

Go to the settings when the disk is unmounted and save a blank passphrase.  It will then be removed from UD.

 

Actually i have one hdd passed through in UD and i want to mount another one without saving the passphrase. 
How can i save a blank passphrase in this case? Cause it is showing the passed through hdd in the select disk field already.

 

Thanks

 

 

Link to comment
dlandon Veteran

dlandon

Posted
  • Author
Posted
1 hour ago, HansOtto said:

 

Actually i have one hdd passed through in UD and i want to mount another one without saving the passphrase. 
How can i save a blank passphrase in this case? Cause it is showing the passed through hdd in the select disk field already.

 

Thanks

 

 

Click on the drop down and select the disk to clear the passphrase.  The passphrase is by disk.  I suppose I could eliminate a passed through encrypted disk from that drop down.

Link to comment
HansOtto Noob

HansOtto

Posted
Posted
8 minutes ago, dlandon said:

Click on the drop down and select the disk to clear the passphrase.  The passphrase is by disk.  I suppose I could eliminate a passed through encrypted disk from that drop down.

 

does not work for me.. the disk still shows in the dropdown menu... 

 

Link to comment
dlandon Veteran

dlandon

Posted
  • Author
Posted
1 minute ago, HansOtto said:

 

does not work for me.. the disk still shows in the dropdown menu... 

 

Any disk that is unmounted and encrypted will show on that dropdown.  I am making a change to not show one that is passed through.

 

You can ignore that disk in the dropdown.  It will not have a UD passphrase unless you previously set one.  If you save a blank passphrase, that will clear it for that disk device in UD.  Is that not what you are looking for?

Link to comment
slimshizn Contributor

slimshizn

Posted
Posted

Updated to the recent version this afternoon, am getting these in the logs now.

```
Oct 14 18:46:55 Azeroth kernel: sd 7:0:3:0: [sde] tag#2475 Sense Key : 0x1 [current] [descriptor]
Oct 14 18:46:55 Azeroth kernel: sd 7:0:3:0: [sde] tag#2475 ASC=0x18 ASCQ=0x4
Oct 14 18:46:57 Azeroth kernel: sd 7:0:3:0: [sde] tag#2545 Sense Key : 0x1 [current] [descriptor]
Oct 14 18:46:57 Azeroth kernel: sd 7:0:3:0: [sde] tag#2545 ASC=0x18 ASCQ=0x4
Oct 14 18:47:00 Azeroth kernel: sd 7:0:3:0: [sde] tag#2546 Sense Key : 0x1 [current] [descriptor]
Oct 14 18:47:00 Azeroth kernel: sd 7:0:3:0: [sde] tag#2546 ASC=0x18 ASCQ=0x4
Oct 14 18:47:07 Azeroth kernel: sd 7:0:3:0: [sde] tag#2433 Sense Key : 0x1 [current] [descriptor]
Oct 14 18:47:07 Azeroth kernel: sd 7:0:3:0: [sde] tag#2433 ASC=0x18 ASCQ=0x4
```

Odd thing is, this isn't even a UD. Any reason why the update would start to cause those logs? Thanks!

Link to comment
dlandon Veteran

dlandon

Posted
  • Author
Posted
37 minutes ago, slimshizn said:

Updated to the recent version this afternoon, am getting these in the logs now.

```
Oct 14 18:46:55 Azeroth kernel: sd 7:0:3:0: [sde] tag#2475 Sense Key : 0x1 [current] [descriptor]
Oct 14 18:46:55 Azeroth kernel: sd 7:0:3:0: [sde] tag#2475 ASC=0x18 ASCQ=0x4
Oct 14 18:46:57 Azeroth kernel: sd 7:0:3:0: [sde] tag#2545 Sense Key : 0x1 [current] [descriptor]
Oct 14 18:46:57 Azeroth kernel: sd 7:0:3:0: [sde] tag#2545 ASC=0x18 ASCQ=0x4
Oct 14 18:47:00 Azeroth kernel: sd 7:0:3:0: [sde] tag#2546 Sense Key : 0x1 [current] [descriptor]
Oct 14 18:47:00 Azeroth kernel: sd 7:0:3:0: [sde] tag#2546 ASC=0x18 ASCQ=0x4
Oct 14 18:47:07 Azeroth kernel: sd 7:0:3:0: [sde] tag#2433 Sense Key : 0x1 [current] [descriptor]
Oct 14 18:47:07 Azeroth kernel: sd 7:0:3:0: [sde] tag#2433 ASC=0x18 ASCQ=0x4
```

Odd thing is, this isn't even a UD. Any reason why the update would start to cause those logs? Thanks!

If you remove UD, do they continue?

Link to comment
HansOtto Noob

HansOtto

Posted
Posted (edited)
10 hours ago, dlandon said:

Any disk that is unmounted and encrypted will show on that dropdown.  I am making a change to not show one that is passed through.

 

You can ignore that disk in the dropdown.  It will not have a UD passphrase unless you previously set one.  If you save a blank passphrase, that will clear it for that disk device in UD.  Is that not what you are looking for?

Thanks for your fast reply! 

I have an SSD passed through and haven't saved a passphrase for it, that is ok. 

But i want to mount another encrypted disk to unraid for onetime only without saving the passphrase in UD. 



 

Edited by HansOtto
Link to comment
dlandon Veteran

dlandon

Posted
  • Author
Posted
5 hours ago, HansOtto said:

Thanks for your fast reply! 

I have an SSD passed through and haven't saved a passphrase for it, that is ok. 

But i want to mount another encrypted disk to unraid for onetime only without saving the passphrase in UD. 



 

Set the passphrase for the disk in UD settings.  Mount the disk and run your tasks.  Unmount the disk.  Then go to the UD settings and clear the passphrase.

 

I'm making a change in the UD passphrase settings to show "*****" when a password is set, and blank when the password is clear.

Link to comment
datahorder Noob

datahorder

Posted
Posted

hello everyone,

in addition to my array, i have a 2TB disk in my system which i share with unassigned devices.
when i recently changed my caching SSD i unplugged the 2TB drive (i was at my 6 Disks limit). With my ssd change finished i wanted to reconnect my 2TB drive.
i can see it showing up in the unassigned disk devices list, but i only see the format button no mount option. 

right now i am back to 6 disk (including the 2TB drive) and i deleted the old caching SSD in the "Historical Unassigned Devices" list.

does anybody have an idea how i can mount this device again?

 

 

Link to comment
dlandon Veteran

dlandon

Posted
  • Author
Posted
On 10/18/2024 at 11:23 AM, datahorder said:

hello everyone,

in addition to my array, i have a 2TB disk in my system which i share with unassigned devices.
when i recently changed my caching SSD i unplugged the 2TB drive (i was at my 6 Disks limit). With my ssd change finished i wanted to reconnect my 2TB drive.
i can see it showing up in the unassigned disk devices list, but i only see the format button no mount option. 

right now i am back to 6 disk (including the 2TB drive) and i deleted the old caching SSD in the "Historical Unassigned Devices" list.

does anybody have an idea how i can mount this device again?

 

 

In a command line type 'ud_diagnostics' then post the /flash/logs/ud_diagnostics.zip file.  Also post a screen shot of the UD page showing that disk.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Go to topic listing
×
×
  • Create New...