Jump to content

  • Drives being disabled when stopping array or restarting when drives are asleep

    SavellM

    By SavellM

      • Urgent

    Hey guys,

     

    Linking this here as it may be related to RC2.

    I've had 3 drives being disabled so far (and all Seagate ones) when shutting down/restarting/stopping array.

    My best guess is they are not waking up quick enough for the stop commands. 

     

    They are all attached to a backplane and all passed SMART extended, and also a pre-clear/erase with verify.

    So drives do look ok as best as I am aware. 

     

    Not sure if there needs to be a delay put in for sleeping drives or something?

    I'm marking it as 'Urgent' as its disabling drives out of the array. To get them back you have to remove them from array and re-add back. 

    Which isnt great, and may lead to data loss.

     

    Go to reports Prereleases

    User Feedback

    Recommended Comments

    JorgeB

    JorgeB 8,750

    Posted

    Unraid sends the spin up command before unmount, the main issue appears to be these errors right after the spin up command:


      

    Feb  9 09:18:56 Odin emhttpd: Spinning up all drives...
Feb  9 09:18:56 Odin emhttpd: spinning up /dev/sdm
Feb  9 09:18:56 Odin emhttpd: spinning up /dev/sdj
Feb  9 09:18:56 Odin emhttpd: spinning up /dev/sdg
Feb  9 09:18:56 Odin emhttpd: spinning up /dev/sdr
Feb  9 09:18:56 Odin emhttpd: spinning up /dev/sdf
Feb  9 09:18:56 Odin emhttpd: spinning up /dev/sds
Feb  9 09:18:56 Odin emhttpd: spinning up /dev/sdn
Feb  9 09:18:56 Odin emhttpd: spinning up /dev/sdo
Feb  9 09:18:56 Odin emhttpd: spinning up /dev/sdi
Feb  9 09:19:12 Odin kernel: sd 1:0:16:0: attempting task abort!scmd(0x00000000826327ac), outstanding for 15458 ms & timeout 15000 ms
Feb  9 09:19:12 Odin kernel: sd 1:0:16:0: [sdr] tag#2325 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e3 00
Feb  9 09:19:12 Odin kernel: scsi target1:0:16: handle(0x001a), sas_address(0x5003048001f32ea4), phy(36)
Feb  9 09:19:12 Odin kernel: scsi target1:0:16: enclosure logical id(0x5003048001f32ebf), slot(20)
Feb  9 09:19:12 Odin kernel: scsi target1:0:16: enclosure level(0x0000), connector name(     )
Feb  9 09:19:12 Odin kernel: sd 1:0:16:0: device_block, handle(0x001a)
Feb  9 09:19:14 Odin kernel: sd 1:0:16:0: device_unblock and setting to running, handle(0x001a)
Feb  9 09:19:14 Odin kernel: sd 1:0:16:0: [sdr] Synchronizing SCSI cache
Feb  9 09:19:14 Odin kernel: sd 1:0:16:0: [sdr] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Feb  9 09:19:14 Odin rc.diskinfo[9313]: SIGHUP received, forcing refresh of disks info.
Feb  9 09:19:14 Odin kernel: scsi 1:0:16:0: task abort: SUCCESS scmd(0x00000000826327ac)
Feb  9 09:19:14 Odin kernel: sd 1:0:17:0: attempting task abort!scmd(0x000000008c9f9c76), outstanding for 18152 ms & timeout 15000 ms
Feb  9 09:19:14 Odin kernel: sd 1:0:17:0: [sds] tag#2446 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e3 00
Feb  9 09:19:14 Odin kernel: scsi target1:0:17: handle(0x001b), sas_address(0x5003048001f32ea6), phy(38)
Feb  9 09:19:14 Odin kernel: scsi target1:0:17: enclosure logical id(0x5003048001f32ebf), slot(22)
Feb  9 09:19:14 Odin kernel: scsi target1:0:17: enclosure level(0x0000), connector name(     )
Feb  9 09:19:14 Odin kernel: mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x5003048001f32ea4)
Feb  9 09:19:14 Odin kernel: mpt3sas_cm0: removing handle(0x001a), sas_addr(0x5003048001f32ea4)
Feb  9 09:19:14 Odin kernel: mpt3sas_cm0: enclosure logical id(0x5003048001f32ebf), slot(20)
Feb  9 09:19:14 Odin kernel: mpt3sas_cm0: enclosure level(0x0000), connector name(     )
Feb  9 09:19:15 Odin kernel: sd 1:0:17:0: device_block, handle(0x001b)
Feb  9 09:19:15 Odin kernel: sd 1:0:17:0: task abort: SUCCESS scmd(0x000000008c9f9c76)

     

    To me this looks more like an LSI or (LSI + those specific drives) issue, can you test with v6.8.3 to see if it doesn't happen?

    SavellM

    SavellM 21

    Posted

    I cant roll back as it was a new server install that I used RC2 for :( 

    It doesnt have the previous version as an option.

    JorgeB

    JorgeB 8,750

    Posted

    You can still download v6.8.3, extract all the bz* files to the flash drive overwriting existing ones, then reboot.



    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
    Add a comment...

    ×   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.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...