*New 11.3 series Release:
2019-10-05: XigmaNAS 11.3.0.4.6928 - released, 11.2 series are soon unsupported!

*New 12.0 series Release:
2019-10-05: XigmaNAS 12.0.0.4.6928 - released!

*New 11.2 series Release:
2019-09-23: XigmaNAS 11.2.0.4.6881 - released!

We really need "Your" help on XigmaNAS https://translations.launchpad.net/xigmanas translations. Please help today!

Producing and hosting XigmaNAS costs money. Please consider donating for our project so that we can continue to offer you the best.
We need your support! eg: PAYPAL

Drives getting disconnected

Hard disks, HDD, RAID Hardware, disk controllers, SATA, PATA, SCSI, IDE, On Board, USB, Firewire, CF (Compact Flash)
Forum rules
Set-Up GuideFAQsForum Rules
Post Reply
skyhawk3355
NewUser
NewUser
Posts: 2
Joined: 30 Apr 2019 19:30
Status: Offline

Drives getting disconnected

#1

Post by skyhawk3355 » 30 Apr 2019 19:40

Hi all,
not sure if this is the right forum but here we are.
a few days ago i started a fresh server with a hb 1235. perviously all drives and pools were working flawlessly. most of the drives were still connected directly to the nas, but a few were through the das. now, all but 2 drives are connected through the das and im getting IO errors and drives getting disconnected. I'm not sure if this is a das error, or an hba error (hba im using is an LSI 9201-16e). below is a section of the log where the drives get disconnected.
any advice would be great

Code: Select all

Apr 30 12:59:52 nas4free kernel: mps0: Reinitializing controller,
Apr 30 12:59:52 nas4free kernel: mps0: Unfreezing devq for target ID 33
Apr 30 12:59:52 nas4free kernel: mps0: Firmware: 07.00.00.00, Driver: 21.02.00.00-fbsd
Apr 30 12:59:52 nas4free kernel: mps0: IOCCapabilities: 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
Apr 30 12:59:52 nas4free kernel: mps_config_set_dpm_pg0: request for header completed with error 16mps0: mps_reinit finished sc 0xfffffe0000e81000 post 4 free 3
Apr 30 12:59:52 nas4free kernel: mps_config_set_dpm_pg0: request to write page completed with error 0
Apr 30 12:59:53 nas4free kernel: mps0: SAS Address for SATA device = 90823520a9a692a2
Apr 30 12:59:54 nas4free kernel: mps0: SAS Address for SATA device = 90853523a5a693a7
Apr 30 12:59:54 nas4free kernel: mps0: SAS Address for SATA device = 3b2e5c2f69854645
Apr 30 12:59:54 nas4free kernel: mps0: SAS Address for SATA device = 827181a806b7f45
Apr 30 12:59:54 nas4free kernel: mps0: SAS Address for SATA device = 3137360886658c98
Apr 30 12:59:55 nas4free kernel: mps0: SAS Address for SATA device = d24d312a797d4436
Apr 30 12:59:55 nas4free kernel: mps0: SAS Address for SATA device = 90853523aeaa93a2
Apr 30 12:59:55 nas4free kernel: mps0: SAS Address for SATA device = 90853728a5a993a8
Apr 30 12:59:55 nas4free kernel: mps0: SAS Address for SATA device = 3d3649149aa57d81
Apr 30 12:59:56 nas4free kernel: mps0: SAS Address for SATA device = 45744040c6b5b094
Apr 30 12:59:56 nas4free kernel: mps0: SAS Address for SATA device = 17f8bfc2fe10fcfb
Apr 30 12:59:56 nas4free kernel: mps0: SAS Address from SATA device = 90823520a9a692a2
Apr 30 12:59:56 nas4free kernel: mps0: SAS Address from SATA device = 90853523a5a693a7
Apr 30 12:59:57 nas4free kernel: (da8:mps0:0:30:0): Invalidating pack
Apr 30 12:59:57 nas4free kernel: (da7:mps0:0:29:0): Invalidating pack
Apr 30 12:59:57 nas4free kernel: (da6:mps0:0:28:0): Invalidating pack
Apr 30 12:59:57 nas4free kernel: (da1:mps0:0:20:0): Invalidating pack
Apr 30 12:59:57 nas4free kernel: (da0:mps0:0:16:0): Invalidating pack
Apr 30 12:59:57 nas4free kernel: da8 at mps0 bus 0 scbus0 target 30 lun 0
Apr 30 12:59:57 nas4free kernel: da8: <ATA WDC WD2003FYPS-2 5G11> s/n WD-WCAVY6380566 detached
Apr 30 12:59:57 nas4free kernel: da7 at mps0 bus 0 scbus0 target 29 lun 0
Apr 30 12:59:57 nas4free kernel: da7: <ATA TOSHIBA HDWD120 ACF0> s/n 87BDGJ1AS detached
Apr 30 12:59:57 nas4free kernel: da6 at mps0 bus 0 scbus0 target 28 lun 0
Apr 30 12:59:57 nas4free kernel: da6: <ATA ST2000DM001-1ER1 CC25> s/n Z8E00LBG detached
Apr 30 12:59:57 nas4free kernel: da1 at mps0 bus 0 scbus0 target 20 lun 0
Apr 30 12:59:57 nas4free kernel: da1: <ATA WDC WD2003FYPS-2 5G11> s/n WD-WCAVY6139660 detached
Apr 30 12:59:57 nas4free kernel: da0 at mps0 bus 0 scbus0 target 16 lun 0
Apr 30 12:59:57 nas4free kernel: da0: <ATA WDC WD20EARX-32P AB51> s/n WD-WCAZAE722971 detached
Apr 30 12:59:57 nas4free kernel: ses1 at mps0 bus 0 scbus0 target 18 lun 0
Apr 30 12:59:57 nas4free kernel: ses1: <XYRATEX HB-1235-E6EBD 221a> s/n SHU0946164L57LG detached
Apr 30 12:59:57 nas4free kernel: ses0 at mps0 bus 0 scbus0 target 17 lun 0
Apr 30 12:59:57 nas4free kernel: ses0: <XYRATEX HB-1235-E6EBD 221a> s/n SHU0946164L57LG detached
Apr 30 12:59:57 nas4free kernel: (ses1:mps0:0:18:0): Periph destroyed
Apr 30 12:59:57 nas4free kernel: (ses0:mps0:0:17:0): Periph destroyed
Apr 30 12:59:57 nas4free kernel: mps0: SAS Address from SATA device = 3b2e5c2f69854645
Apr 30 12:59:57 nas4free kernel: (da8:mps0:0:30:0): Periph destroyed
Apr 30 12:59:57 nas4free kernel: (da7:mps0:0:29:0): Periph destroyed
Apr 30 12:59:57 nas4free kernel: (da6:mps0:0:28:0): Periph destroyed
Apr 30 12:59:57 nas4free kernel: (da1:mps0:0:20:0): Periph destroyed
Apr 30 12:59:57 nas4free kernel: (da0:mps0:0:16:0): Periph destroyed
Apr 30 12:59:57 nas4free ZFS: vdev state changed, pool_guid=17838852604565205097 vdev_guid=17914782875691510270
Apr 30 12:59:57 nas4free ZFS: vdev is removed, pool_guid=17838852604565205097 vdev_guid=17914782875691510270
Apr 30 12:59:57 nas4free ZFS: vdev state changed, pool_guid=17838852604565205097 vdev_guid=15423329939497057609
Apr 30 12:59:57 nas4free ZFS: vdev is removed, pool_guid=17838852604565205097 vdev_guid=15423329939497057609
Apr 30 12:59:57 nas4free ZFS: vdev state changed, pool_guid=17838852604565205097 vdev_guid=9730662704926799003
Apr 30 12:59:57 nas4free ZFS: vdev is removed, pool_guid=17838852604565205097 vdev_guid=9730662704926799003
Apr 30 12:59:57 nas4free ZFS: vdev state changed, pool_guid=17838852604565205097 vdev_guid=6124991185139961170
Apr 30 12:59:57 nas4free ZFS: vdev is removed, pool_guid=17838852604565205097 vdev_guid=6124991185139961170
Apr 30 12:59:57 nas4free ZFS: vdev state changed, pool_guid=17838852604565205097 vdev_guid=15263644336524338806
Apr 30 12:59:57 nas4free ZFS: vdev is removed, pool_guid=17838852604565205097 vdev_guid=15263644336524338806
Apr 30 12:59:57 nas4free kernel: mps0: SAS Address from SATA device = 827181a806b7f45
Apr 30 12:59:57 nas4free kernel: mps0: SAS Address from SATA device = 3137360886658c98
Apr 30 12:59:57 nas4free kernel: mps0: SAS Address from SATA device = d24d312a797d4436
Apr 30 12:59:57 nas4free kernel: da0 at mps0 bus 0 scbus0 target 28 lun 0
Apr 30 12:59:57 nas4free kernel: da0: <ATA ST2000DM001-1ER1 CC25> Fixed Direct Access SPC-3 SCSI device
Apr 30 12:59:57 nas4free kernel: da0: Serial Number Z8E00LBG
Apr 30 12:59:57 nas4free kernel: da0: 600.000MB/s transfers
Apr 30 12:59:57 nas4free kernel: da0: Command Queueing enabled
Apr 30 12:59:57 nas4free kernel: da0: 1907729MB (3907029168 512 byte sectors)
Apr 30 12:59:57 nas4free kernel: da0: quirks=0x8<4K>
Apr 30 12:59:58 nas4free kernel: mps0: SAS Address from SATA device = 90853523aeaa93a2
Apr 30 12:59:58 nas4free kernel: mps0: SAS Address from SATA device = 90853728a5a993a8
Apr 30 12:59:58 nas4free kernel: da1 at mps0 bus 0 scbus0 target 29 lun 0
Apr 30 12:59:58 nas4free kernel: da1: <ATA TOSHIBA HDWD120 ACF0> Fixed Direct Access SPC-3 SCSI device
Apr 30 12:59:58 nas4free kernel: da1: Serial Number 87BDGJ1AS
Apr 30 12:59:58 nas4free kernel: da1: 300.000MB/s transfers
Apr 30 12:59:58 nas4free kernel: da1: Command Queueing enabled
Apr 30 12:59:58 nas4free kernel: da1: 1907729MB (3907029168 512 byte sectors)
Apr 30 12:59:58 nas4free kernel: mps0: SAS Address from SATA device = 3d3649149aa57d81
Apr 30 12:59:58 nas4free kernel: mps0: SAS Address from SATA device = 45744040c6b5b094
Apr 30 12:59:58 nas4free kernel: da6 at mps0 bus 0 scbus0 target 20 lun 0
Apr 30 12:59:58 nas4free kernel: da6: <ATA WDC WD2003FYPS-2 5G11> Fixed Direct Access SPC-3 SCSI device
Apr 30 12:59:58 nas4free kernel: da6: Serial Number WD-WCAVY6139660
Apr 30 12:59:58 nas4free kernel: da6: 300.000MB/s transfers
Apr 30 12:59:58 nas4free kernel: da6: Command Queueing enabled
Apr 30 12:59:58 nas4free kernel: da6: 1907729MB (3907029168 512 byte sectors)
Apr 30 12:59:59 nas4free kernel: mps0: SAS Address from SATA device = 17f8bfc2fe10fcfb
Apr 30 12:59:59 nas4free kernel: ses0 at mps0 bus 0 scbus0 target 18 lun 0
Apr 30 12:59:59 nas4free kernel: ses0: <XYRATEX HB-1235-E6EBD 221a> Fixed Enclosure Services SPC-3 SCSI device
Apr 30 12:59:59 nas4free kernel: ses0: Serial Number SHU0946164L57LG
Apr 30 12:59:59 nas4free kernel: ses0: 600.000MB/s transfers
Apr 30 12:59:59 nas4free kernel: ses0: Command Queueing enabled
Apr 30 12:59:59 nas4free kernel: ses0: SCSI-3 ENC Device
Apr 30 12:59:59 nas4free kernel: ses1 at mps0 bus 0 scbus0 target 17 lun 0
Apr 30 12:59:59 nas4free kernel: ses1: <XYRATEX HB-1235-E6EBD 221a> Fixed Enclosure Services SPC-3 SCSI device
Apr 30 12:59:59 nas4free kernel: ses1: Serial Number SHU0946164L57LG
Apr 30 12:59:59 nas4free kernel: ses1: 600.000MB/s transfers
Apr 30 12:59:59 nas4free kernel: ses1: Command Queueing enabled
Apr 30 12:59:59 nas4free kernel: ses1: SCSI-3 ENC Device
Apr 30 12:59:59 nas4free kernel: da7 at mps0 bus 0 scbus0 target 30 lun 0
Apr 30 12:59:59 nas4free kernel: da7: <ATA WDC WD2003FYPS-2 5G11> Fixed Direct Access SPC-3 SCSI device
Apr 30 12:59:59 nas4free kernel: da7: Serial Number WD-WCAVY6380566
Apr 30 12:59:59 nas4free kernel: da7: 300.000MB/s transfers
Apr 30 12:59:59 nas4free kernel: da7: Command Queueing enabled
Apr 30 12:59:59 nas4free kernel: da7: 1907729MB (3907029168 512 byte sectors)
Apr 30 12:59:59 nas4free kernel: ses0: da6,pass2: SAS Device Slot Element: 1 Phys at Slot 1, Not All Phys
Apr 30 12:59:59 nas4free kernel: ses0:  phy 0: SATA device
Apr 30 12:59:59 nas4free kernel: ses0:  phy 0: parent 50050cc10adb9f3f addr 50050cc10adb9f1e
Apr 30 12:59:59 nas4free kernel: ses0: da7,pass9: SAS Device Slot Element: 1 Phys at Slot 5, Not All Phys
Apr 30 12:59:59 nas4free kernel: ses0:  phy 0: SATA device
Apr 30 12:59:59 nas4free kernel: ses0:  phy 0: parent 50050cc10adb9f3f addr 50050cc10adb9f1f
Apr 30 12:59:59 nas4free kernel: ses0: da1,pass1: SAS Device Slot Element: 1 Phys at Slot 6, Not All Phys
Apr 30 12:59:59 nas4free kernel: ses0:  phy 0: SATA device
Apr 30 12:59:59 nas4free kernel: ses0:  phy 0: parent 50050cc10adb9f3f addr 50050cc10adb9f1c
Apr 30 12:59:59 nas4free kernel: da8 at mps0 bus 0 scbus0 target 16 lun 0
Apr 30 12:59:59 nas4free kernel: da8: <ATA WDC WD20EARX-32P AB51> Fixed Direct Access SPC-3 SCSI device
Apr 30 12:59:59 nas4free kernel: da8: Serial Number WD-WCAZAE722971
Apr 30 12:59:59 nas4free kernel: da8: 600.000MB/s transfers
Apr 30 12:59:59 nas4free kernel: da8: Command Queueing enabled
Apr 30 12:59:59 nas4free kernel: da8: 1907729MB (3907029168 512 byte sectors)
Apr 30 12:59:59 nas4free kernel: da8: quirks=0x8<4K>
Apr 30 12:59:59 nas4free kernel: ses0: da8,pass10: SAS Device Slot Element: 1 Phys at Slot 8, Not All Phys
Apr 30 12:59:59 nas4free kernel: ses0:  phy 0: SATA device
Apr 30 12:59:59 nas4free kernel: ses0:  phy 0: parent 50050cc10adb9f3f addr 50050cc10adb9f21
Apr 30 13:00:02 nas4free kernel: mps0: mpssas_prepare_remove: Sending reset for target ID 32
Apr 30 13:00:04 nas4free kernel: (probe0:mps0:0:32:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID 138 terminated ioc 804b loginfo 31111000 scsi 0 state c xfer 0
Apr 30 13:00:04 nas4free kernel: (probe0:mps0:0:32:0): INQUIRY. CDB: 12 00 00 00 24 00
Apr 30 13:00:04 nas4free kernel: mps0: Unfreezing devq for target ID 32
Apr 30 13:00:04 nas4free kernel: (probe0:mps0:0:32:0): CAM status: CCB request completed with an error
Apr 30 13:00:04 nas4free kernel: (probe0:mps0:0:32:0): Retrying command
Apr 30 13:00:15 nas4free kernel: mps0: SAS Address for SATA device = 17f8bfc2fe10fcfb
Apr 30 13:00:15 nas4free kernel: mps0: SAS Address from SATA device = 17f8bfc2fe10fcfb
Apr 30 13:00:19 nas4free kernel: mps0: mpssas_prepare_remove: Sending reset for target ID 32
Apr 30 13:00:20 nas4free kernel: (probe0:mps0:0:32:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID 404 terminated ioc 804b loginfo 31111000 scsi 0 state c xfer 0
Apr 30 13:00:20 nas4free kernel: (probe0:mps0:0:32:0): INQUIRY. CDB: 12 00 00 00 24 00
Apr 30 13:00:20 nas4free kernel: mps0: Unfreezing devq for target ID 32
Apr 30 13:00:20 nas4free kernel: (probe0:mps0:0:32:0): CAM status: CCB request completed with an error
Apr 30 13:00:20 nas4free kernel: (probe0:mps0:0:32:0): Retrying command
Apr 30 13:00:23 nas4free kernel: mps0: SAS Address for SATA device = 17f8bfc2fe10fcfb
Apr 30 13:00:23 nas4free kernel: mps0: SAS Address from SATA device = 17f8bfc2fe10fcfb
Apr 30 13:00:27 nas4free kernel: mps0: mpssas_prepare_remove: Sending reset for target ID 32
Apr 30 13:00:28 nas4free kernel: (probe0:mps0:0:32:0): INQUIRY. CDB: 12 00 00 00 24 00 length 36 SMID 548 terminated ioc 804b loginfo 31111000 scsi 0 state c xfer 0
Apr 30 13:00:28 nas4free kernel: (probe0:mps0:0:32:0): INQUIRY. CDB: 12 00 00 00 24 00
Apr 30 13:00:28 nas4free kernel: mps0: Unfreezing devq for target ID 32
Apr 30 13:00:28 nas4free kernel: (probe0:mps0:0:32:0): CAM status: CCB request completed with an error

cookiemonster
Advanced User
Advanced User
Posts: 163
Joined: 23 Mar 2014 02:58
Location: UK
Status: Offline

Re: Drives getting disconnected

#2

Post by cookiemonster » 30 Apr 2019 22:31

It sure looks like a hardware problem. Welcome to the forum.
It might not be a faulty HBA but a lose connection. I'd venture a guess it'll be an elimination process to isolate heating, pci slot, etc.
Main: Xigmanas 11.2.0.4 x64-full-RootOnZFS on Supermicro X8DT3. zroot on mirrorred pair of CRUCIAL_CT64M225. Memory: 24GB ECC; 2 Xeon E5645 CPUs; Storage: (HBA) - LSI SAS 9211-4i with 3 SATA x 1 Tb in raidZ1, 1 x 3 Tb SAS drive as single stripe.
Spare1: HP DL580 G5; 128 GB ECC RAM; 4 CPU; 8 x 500 GB disks on H210i
Spare2: HP DL360 G7; 6 GB ECC RAM; 1 Xeon CPU; 5 x 500 GB disks on H210i
Spare3: HP DL380 G7; 24 GB ECC RAM; 2 Xeon E5645 CPUs; 8 x 500 GB disks on IBM M1015 flashed to LSI9211-IT

Flanker_27
NewUser
NewUser
Posts: 4
Joined: 25 Jun 2019 18:23
Status: Offline

Re: Drives getting disconnected

#3

Post by Flanker_27 » 26 Jun 2019 18:13

Yeah, check the temperature. The friend who taught me what a NAS was does run into it quite often, especially since he's living in a warm place... sure, it's a 8 to 15 degree Celsius difference compared to more temperate climates, but that's still 8 to 15 degrees and it will make the difference between "hot, but alright" and "overheating".

skyhawk3355
NewUser
NewUser
Posts: 2
Joined: 30 Apr 2019 19:30
Status: Offline

Re: Drives getting disconnected

#4

Post by skyhawk3355 » 26 Jun 2019 18:43

just so i'm not one of those guys who never responds;
It was a sync issue under datasets. basically what i think happened was because i was transfering a lot of data at once the sync overflowed and errored out. After disabling sync i haven't had any issues.

Flanker_27
NewUser
NewUser
Posts: 4
Joined: 25 Jun 2019 18:23
Status: Offline

Re: Drives getting disconnected

#5

Post by Flanker_27 » 27 Jun 2019 17:39

Ok, great, thanks for the feedback, it's always nice to see updates to see what works and what doesn't!
By the way, speaking of what works and doesn't under high temperatures, is there a way to make sure everything stays cool even under high temperatures when the computer is running? The thing is that my parents are planning to buy a house in Cyprus there for when they retire, and now that I told them about my NAS project, they want one as well... Sure, they'll have a/c there, but we can't necessarily rely on it to do everything.

Post Reply

Return to “Hard disk & controller”