September 1, 20223 yr Hi All, Was very excited to move into the SAS solution world, but wondering if I'm having some controller issues. Behavior: Upon reboot, not finding all disks, dropping parity disk. Requiring multiple reboots, or physical removal and reinsertion, to recognize the drives. Seems to happen most with Seagate drives that are mixed in with some WD. Hardware: Lenovo M720Q RocketRAID 2722 (Marvell 88SE9485) Bios VT-d disabled External Sans Digital 8 bay Diagnostics attached. I hope it's not the card, because it's a short length and half height card that fits in my micro chasis and I haven't seen any LSI variants that fit that bill. Many thanks. unraid-diagnostics-20220901-0824.zip
September 1, 20223 yr Community Expert Marvell controllers are not recommended, but the diags are just after rebooting, not seeing any disk/controller related issues so far.
September 1, 20223 yr Author 7 hours ago, JorgeB said: Marvell controllers are not recommended, but the diags are just after rebooting, not seeing any disk/controller related issues so far. Thanks Jorge. When I first booted the system I see a warning. Once I remove and replace in the same position it is recognized. Any thoughts on if this warning is related? Sep 1 07:11:35 unraid kernel: ACPI: Early table checksum verification disabled Sep 1 07:11:35 unraid kernel: floppy0: no floppy controllers found Sep 1 07:11:35 unraid kernel: i915 0000:00:02.0: [drm] failed to retrieve link info, disabling eDP Sep 1 07:11:35 unraid kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Sep 1 07:11:35 unraid kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Sep 1 07:11:35 unraid kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Sep 1 07:11:35 unraid kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Sep 1 07:11:35 unraid kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Sep 1 07:11:35 unraid kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Sep 1 07:11:35 unraid kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Sep 1 07:11:35 unraid kernel: ata10.00: failed to IDENTIFY (I/O error, err_mask=0x4) Sep 1 07:11:35 unraid kernel: ata10.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) Sep 1 07:11:35 unraid kernel: ata10.00: failed to IDENTIFY (I/O error, err_mask=0x4) Sep 1 07:11:35 unraid kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Sep 1 07:11:35 unraid kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Sep 1 07:11:35 unraid kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Sep 1 07:11:35 unraid kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Sep 1 07:11:35 unraid kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Sep 1 07:11:35 unraid kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Sep 1 07:11:35 unraid kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Sep 1 07:11:35 unraid kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Sep 1 07:11:35 unraid kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 Sep 1 07:11:35 unraid mcelog: failed to prefill DIMM database from DMI data
September 2, 20223 yr Community Expert 9 hours ago, Kboogie said: Enter sas_scsi_recover_host busy: 0 failed: 0 These are normal mostly during initialization with controllers based on this chip, it's the same with the SAS2LP.
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.