Latest News:
*New 11.2 series Release:
2019-06-20: XigmaNAS 11.2.0.4.6766 - released!

*New 12.0 series Release:
2019-06-20: XigmaNAS 12.0.0.4.6766 - released!

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

Producing and hosting XigmaNAS cost money, please consider a donation to our project so we can continue to offer you the best.
We need your support! eg: PAYPAL

Random disconnection of disks

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
bitman
NewUser
NewUser
Posts: 3
Joined: 12 Dec 2017 09:29
Status: Offline

Random disconnection of disks

#1

Post by bitman » 12 Dec 2017 09:33

Hello everyone. I need your help!
There was a problem with disconnecting disks from the system, or its complete inaccessibility. OS NAS4Free 11.1.0.4.4994 running as a virtual machine (version 13) under Vmware-ESXi-6.5d.0-5310538-Custom-Cisco-6.5.0.1. The system was completely reinstalled and configured from scratch, but it did not solve the problem!
The regularity of the appearance of the problem is not clear, when a problem occurs, all disks are disconnected and the following message is output to the console:

Code: Select all

kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
kernel: (da1:mpt0:0:1:0): Retrying command (per sense data)
kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
kernel: (da1:mpt0:0:1:0): Retrying command (per sense data)
kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
kernel: (da1:mpt0:0:1:0): Retrying command (per sense data)
kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
kernel: (da1:mpt0:0:1:0): Retrying command (per sense data)
kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
kernel: (da1:mpt0:0:1:0): Error 5, Retries exhausted
kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
kernel: (da1:mpt0:0:1:0): Retrying command (per sense data)
kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
kernel: (da1:mpt0:0:1:0): Retrying command (per sense data)
kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
kernel: (da1:mpt0:0:1:0): Retrying command (per sense data)
kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
kernel: (da1:mpt0:0:1:0): Retrying command (per sense data)
kernel: (ada0:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 40 00 21 00 40 00 00 00 00 00 00
kernel: (ada0:ahcich1:0:0:0): CAM status: ATA Status Error
kernel: (ada0:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 02 (NM )
kernel: (ada0:ahcich1:0:0:0): RES: 41 02 00 00 00 00 00 00 00 00 00
kernel: (ada0:ahcich1:0:0:0): Retrying command
kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
kernel: (da1:mpt0:0:1:0): Error 5, Retries exhausted
kernel: (ada0:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 08 38 1b 29 40 00 00 00 00 00 00
kernel: (ada0:ahcich1:0:0:0): CAM status: ATA Status Error
kernel: (ada0:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 02 (NM )
kernel: (ada0:ahcich1:0:0:0): RES: 41 02 00 00 00 00 00 00 00 00 00
kernel: (ada0:ahcich1:0:0:0): Retrying command

Full system boot log:

Dec 12 10:06:57	kernel: ahcich3: <AHCI channel> at channel 3 on ahci0
Dec 12 10:06:57	kernel: ahcich4: <AHCI channel> at channel 4 on ahci0
Dec 12 10:06:57	kernel: ahcich5: <AHCI channel> at channel 5 on ahci0
Dec 12 10:06:57	kernel: ahcich6: <AHCI channel> at channel 6 on ahci0
Dec 12 10:06:57	kernel: ahcich7: <AHCI channel> at channel 7 on ahci0
Dec 12 10:06:57	kernel: ahcich8: <AHCI channel> at channel 8 on ahci0
Dec 12 10:06:57	kernel: ahcich9: <AHCI channel> at channel 9 on ahci0
Dec 12 10:06:57	kernel: ahcich10: <AHCI channel> at channel 10 on ahci0
Dec 12 10:06:57	kernel: ahcich11: <AHCI channel> at channel 11 on ahci0
Dec 12 10:06:57	kernel: ahcich12: <AHCI channel> at channel 12 on ahci0
Dec 12 10:06:57	kernel: ahcich13: <AHCI channel> at channel 13 on ahci0
Dec 12 10:06:57	kernel: ahcich14: <AHCI channel> at channel 14 on ahci0
Dec 12 10:06:57	kernel: ahcich15: <AHCI channel> at channel 15 on ahci0
Dec 12 10:06:57	kernel: ahcich16: <AHCI channel> at channel 16 on ahci0
Dec 12 10:06:57	kernel: ahcich17: <AHCI channel> at channel 17 on ahci0
Dec 12 10:06:57	kernel: ahcich18: <AHCI channel> at channel 18 on ahci0
Dec 12 10:06:57	kernel: ahcich19: <AHCI channel> at channel 19 on ahci0
Dec 12 10:06:57	kernel: ahcich20: <AHCI channel> at channel 20 on ahci0
Dec 12 10:06:57	kernel: ahcich21: <AHCI channel> at channel 21 on ahci0
Dec 12 10:06:57	kernel: ahcich22: <AHCI channel> at channel 22 on ahci0
Dec 12 10:06:57	kernel: ahcich23: <AHCI channel> at channel 23 on ahci0
Dec 12 10:06:57	kernel: ahcich24: <AHCI channel> at channel 24 on ahci0
Dec 12 10:06:57	kernel: ahcich25: <AHCI channel> at channel 25 on ahci0
Dec 12 10:06:57	kernel: ahcich26: <AHCI channel> at channel 26 on ahci0
Dec 12 10:06:57	kernel: ahcich27: <AHCI channel> at channel 27 on ahci0
Dec 12 10:06:57	kernel: ahcich28: <AHCI channel> at channel 28 on ahci0
Dec 12 10:06:57	kernel: ahcich29: <AHCI channel> at channel 29 on ahci0
Dec 12 10:06:57	kernel: pcib3: <ACPI PCI-PCI bridge> at device 21.0 on pci0
Dec 12 10:06:57	kernel: pcib3: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib4: <ACPI PCI-PCI bridge> at device 21.1 on pci0
Dec 12 10:06:57	kernel: pcib4: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib5: <ACPI PCI-PCI bridge> at device 21.2 on pci0
Dec 12 10:06:57	kernel: pcib5: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib6: <ACPI PCI-PCI bridge> at device 21.3 on pci0
Dec 12 10:06:57	kernel: pcib6: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib7: <ACPI PCI-PCI bridge> at device 21.4 on pci0
Dec 12 10:06:57	kernel: pcib7: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib8: <ACPI PCI-PCI bridge> at device 21.5 on pci0
Dec 12 10:06:57	kernel: pcib8: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib9: <ACPI PCI-PCI bridge> at device 21.6 on pci0
Dec 12 10:06:57	kernel: pcib9: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib10: <ACPI PCI-PCI bridge> at device 21.7 on pci0
Dec 12 10:06:57	kernel: pcib10: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib11: <ACPI PCI-PCI bridge> at device 22.0 on pci0
Dec 12 10:06:57	kernel: pcib11: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pci3: <ACPI PCI bus> on pcib11
Dec 12 10:06:57	kernel: vmx0: <VMware VMXNET3 Ethernet Adapter> port 0x5000-0x500f mem 0xfd3fc000-0xfd3fcfff,0xfd3fd000-0xfd3fdfff,0xfd3fe000-0xfd3fffff irq 19 at device 0.0 on pci3
Dec 12 10:06:57	kernel: vmx0: Ethernet address: 00:0c:29:9b:d4:04
Dec 12 10:06:57	kernel: pcib12: <ACPI PCI-PCI bridge> at device 22.1 on pci0
Dec 12 10:06:57	kernel: pcib12: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib13: <ACPI PCI-PCI bridge> at device 22.2 on pci0
Dec 12 10:06:57	kernel: pcib13: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib14: <ACPI PCI-PCI bridge> at device 22.3 on pci0
Dec 12 10:06:57	kernel: pcib14: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib15: <ACPI PCI-PCI bridge> at device 22.4 on pci0
Dec 12 10:06:57	kernel: pcib15: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib16: <ACPI PCI-PCI bridge> at device 22.5 on pci0
Dec 12 10:06:57	kernel: pcib16: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib17: <ACPI PCI-PCI bridge> at device 22.6 on pci0
Dec 12 10:06:57	kernel: pcib17: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib18: <ACPI PCI-PCI bridge> at device 22.7 on pci0
Dec 12 10:06:57	kernel: pcib18: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib19: <ACPI PCI-PCI bridge> at device 23.0 on pci0
Dec 12 10:06:57	kernel: pcib19: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib20: <ACPI PCI-PCI bridge> at device 23.1 on pci0
Dec 12 10:06:57	kernel: pcib20: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib21: <ACPI PCI-PCI bridge> at device 23.2 on pci0
Dec 12 10:06:57	kernel: pcib21: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib22: <ACPI PCI-PCI bridge> at device 23.3 on pci0
Dec 12 10:06:57	kernel: pcib22: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib23: <ACPI PCI-PCI bridge> at device 23.4 on pci0
Dec 12 10:06:57	kernel: pcib23: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib24: <ACPI PCI-PCI bridge> at device 23.5 on pci0
Dec 12 10:06:57	kernel: pcib24: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib25: <ACPI PCI-PCI bridge> at device 23.6 on pci0
Dec 12 10:06:57	kernel: pcib25: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib26: <ACPI PCI-PCI bridge> at device 23.7 on pci0
Dec 12 10:06:57	kernel: pcib26: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib27: <ACPI PCI-PCI bridge> at device 24.0 on pci0
Dec 12 10:06:57	kernel: pcib27: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib28: <ACPI PCI-PCI bridge> at device 24.1 on pci0
Dec 12 10:06:57	kernel: pcib28: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib29: <ACPI PCI-PCI bridge> at device 24.2 on pci0
Dec 12 10:06:57	kernel: pcib29: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib30: <ACPI PCI-PCI bridge> at device 24.3 on pci0
Dec 12 10:06:57	kernel: pcib30: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib31: <ACPI PCI-PCI bridge> at device 24.4 on pci0
Dec 12 10:06:57	kernel: pcib31: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib32: <ACPI PCI-PCI bridge> at device 24.5 on pci0
Dec 12 10:06:57	kernel: pcib32: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib33: <ACPI PCI-PCI bridge> at device 24.6 on pci0
Dec 12 10:06:57	kernel: pcib33: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: pcib34: <ACPI PCI-PCI bridge> at device 24.7 on pci0
Dec 12 10:06:57	kernel: pcib34: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: acpi_acad0: <AC Adapter> on acpi0
Dec 12 10:06:57	kernel: atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
Dec 12 10:06:57	kernel: atkbd0: <AT Keyboard> irq 1 on atkbdc0
Dec 12 10:06:57	kernel: kbd0 at atkbd0
Dec 12 10:06:57	kernel: atkbd0: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: psm0: <PS/2 Mouse> irq 12 on atkbdc0
Dec 12 10:06:57	kernel: psm0: [GIANT-LOCKED]
Dec 12 10:06:57	kernel: psm0: model IntelliMouse, device ID 3
Dec 12 10:06:57	kernel: acpi_syscontainer0: <System Container> on acpi0
Dec 12 10:06:57	kernel: orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xc9fff,0xca000-0xcbfff,0xcc000-0xccfff,0xdc000-0xdffff,0xe0000-0xe7fff on isa0
Dec 12 10:06:57	kernel: sc0: <System console> at flags 0x100 on isa0
Dec 12 10:06:57	kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Dec 12 10:06:57	kernel: vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Dec 12 10:06:57	kernel: ppc0: cannot reserve I/O port range
Dec 12 10:06:57	kernel: acpi_throttle0: <ACPI CPU Throttling> numa-domain 0 on cpu0
Dec 12 10:06:57	kernel: coretemp0: <CPU On-Die Thermal Sensors> numa-domain 0 on cpu0
Dec 12 10:06:57	kernel: coretemp0: Tj(target) value 0 does not seem right.
Dec 12 10:06:57	kernel: acpi_throttle1: <ACPI CPU Throttling> numa-domain 0 on cpu1
Dec 12 10:06:57	kernel: acpi_throttle1: failed to attach P_CNT
Dec 12 10:06:57	kernel: device_attach: acpi_throttle1 attach returned 6
Dec 12 10:06:57	kernel: coretemp1: <CPU On-Die Thermal Sensors> numa-domain 0 on cpu1
Dec 12 10:06:57	kernel: coretemp1: Tj(target) value 0 does not seem right.
Dec 12 10:06:57	kernel: acpi_throttle2: <ACPI CPU Throttling> numa-domain 0 on cpu2
Dec 12 10:06:57	kernel: acpi_throttle2: failed to attach P_CNT
Dec 12 10:06:57	kernel: device_attach: acpi_throttle2 attach returned 6
Dec 12 10:06:57	kernel: coretemp2: <CPU On-Die Thermal Sensors> numa-domain 0 on cpu2
Dec 12 10:06:57	kernel: coretemp2: Tj(target) value 0 does not seem right.
Dec 12 10:06:57	kernel: acpi_throttle3: <ACPI CPU Throttling> numa-domain 0 on cpu3
Dec 12 10:06:57	kernel: acpi_throttle3: failed to attach P_CNT
Dec 12 10:06:57	kernel: device_attach: acpi_throttle3 attach returned 6
Dec 12 10:06:57	kernel: coretemp3: <CPU On-Die Thermal Sensors> numa-domain 0 on cpu3
Dec 12 10:06:57	kernel: coretemp3: Tj(target) value 0 does not seem right.
Dec 12 10:06:57	kernel: ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present;
Dec 12 10:06:57	kernel: to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
Dec 12 10:06:57	kernel: ZFS filesystem version: 5
Dec 12 10:06:57	kernel: ZFS storage pool version: features support (5000)
Dec 12 10:06:57	kernel: Timecounters tick every 10.000 msec
Dec 12 10:06:57	kernel: iSCSI boot driver version 0.2.13
Dec 12 10:06:57	kernel: nvme cam probe device init
Dec 12 10:06:57	kernel: ugen0.1: <0x15ad UHCI root HUB> at usbus0
Dec 12 10:06:57	kernel: ugen1.1: <0x15ad EHCI root HUB> at usbus1
Dec 12 10:06:57	kernel: uhub0: <0x15ad UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
Dec 12 10:06:57	kernel: uhub1: <0x15ad EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
Dec 12 10:06:57	kernel: uhub0: 2 ports with 2 removable, self powered
Dec 12 10:06:57	kernel: ugen0.2: <VMware VMware Virtual USB Mouse> at usbus0
Dec 12 10:06:57	kernel: ugen0.3: <vendor 0x0e0f VMware Virtual USB Hub> at usbus0
Dec 12 10:06:57	kernel: uhub2 on uhub0
Dec 12 10:06:57	kernel: uhub2: <VMware Virtual USB Hub> on usbus0
Dec 12 10:06:57	kernel: uhub1: 6 ports with 6 removable, self powered
Dec 12 10:06:57	kernel: uhub2: 7 ports with 7 removable, self powered
Dec 12 10:06:57	kernel: da0 at mpt0 bus 0 scbus2 target 0 lun 0
Dec 12 10:06:57	kernel: da0: <VMware Virtual disk 2.0> Fixed Direct Access SPC-4 SCSI device
Dec 12 10:06:57	kernel: da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit)
Dec 12 10:06:57	kernel: da0: Command Queueing enabled
Dec 12 10:06:57	kernel: da0: 1572864MB (3221225472 512 byte sectors)
Dec 12 10:06:57	kernel: da0: quirks=0x140<RETRY_BUSY,STRICT_UNMAP>
Dec 12 10:06:57	kernel: da1 at mpt0 bus 0 scbus2 target 1 lun 0
Dec 12 10:06:57	kernel: da1: <VMware Virtual disk 2.0> Fixed Direct Access SPC-4 SCSI device
Dec 12 10:06:57	kernel: da1: 320.000MB/s transfers (160.000MHz, offset 127, 16bit)
Dec 12 10:06:57	kernel: da1: Command Queueing enabled
Dec 12 10:06:57	kernel: da1: 1258291MB (2576980376 512 byte sectors)
Dec 12 10:06:57	kernel: da1: quirks=0x140<RETRY_BUSY,STRICT_UNMAP>
Dec 12 10:06:57	kernel: ada0 at ahcich1 bus 0 scbus4 target 0 lun 0
Dec 12 10:06:57	kernel: cd0 at ahcich0 bus 0 scbus3 target 0 lun 0
Dec 12 10:06:57	kernel: ada0: <VMware Virtual SATA Hard Drive 00000001> ATA-6 SATA 2.x device
Dec 12 10:06:57	kernel: cd0: <NECVMWar VMware SATA CD00 1.00> Removable CD-ROM SCSI device
Dec 12 10:06:57	kernel: cd0: Serial Number 00000000000000000001
Dec 12 10:06:57	kernel: cd0: 600.000MB/s transfers (SATA 3.x, UDMA2, ATAPI 12bytes, PIO 8192bytes)
Dec 12 10:06:57	kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present
Dec 12 10:06:57	kernel: ada0: Serial Number 01000000000000000001
Dec 12 10:06:57	kernel: ada0: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 8192bytes)
Dec 12 10:06:57	kernel: ada0: Command Queueing enabled
Dec 12 10:06:57	kernel: ada0: 8192MB (16777216 512 byte sectors)
Dec 12 10:06:57	kernel: Trying to mount root from ufs:/dev/ufsid/59eb5709da2140df [rw]...
Dec 12 10:06:57	kernel: WARNING: / was not properly dismounted
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Retrying command (per sense data)
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Retrying command (per sense data)
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Retrying command (per sense data)
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Retrying command (per sense data)
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Error 5, Retries exhausted
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Retrying command (per sense data)
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Retrying command (per sense data)
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Retrying command (per sense data)
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Retrying command (per sense data)
Dec 12 10:06:57	kernel: (ada0:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 40 00 21 00 40 00 00 00 00 00 00
Dec 12 10:06:57	kernel: (ada0:ahcich1:0:0:0): CAM status: ATA Status Error
Dec 12 10:06:57	kernel: (ada0:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 02 (NM )
Dec 12 10:06:57	kernel: (ada0:ahcich1:0:0:0): RES: 41 02 00 00 00 00 00 00 00 00 00
Dec 12 10:06:57	kernel: (ada0:ahcich1:0:0:0): Retrying command
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): READ(10). CDB: 28 00 99 99 94 10 00 00 10 00
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): CAM status: SCSI Status Error
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI status: Check Condition
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): SCSI sense: HARDWARE FAILURE asc:44,0 (Internal target failure)
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Actual Retry Count: 3
Dec 12 10:06:57	kernel: (da1:mpt0:0:1:0): Error 5, Retries exhausted
Dec 12 10:06:57	kernel: (ada0:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 08 38 1b 29 40 00 00 00 00 00 00
Dec 12 10:06:57	kernel: (ada0:ahcich1:0:0:0): CAM status: ATA Status Error
Dec 12 10:06:57	kernel: (ada0:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 02 (NM )
Dec 12 10:06:57	kernel: (ada0:ahcich1:0:0:0): RES: 41 02 00 00 00 00 00 00 00 00 00
Dec 12 10:06:57	kernel: (ada0:ahcich1:0:0:0): Retrying command
Dec 12 10:06:57	kernel: VMware memory control driver initialized
Dec 12 10:06:57	kernel: vmx0: link state changed to UP
Dec 12 10:06:57	kernel: uhid0 on uhub0
Dec 12 10:06:57	kernel: uhid0: <VMware> on usbus0
Dec 12 10:06:57	kernel: uhid1 on uhub0
Dec 12 10:06:57	kernel: uhid1: <VMware> on usbus0
Dec 12 10:07:03	kernel: ada0
Dec 12 10:07:03	proftpd[1930]: 172.17.7.3 - ProFTPD 1.3.6 (stable) (built Fri Dec 1 2017 16:52:33 CET) standalone mode STARTUP
Dec 12 10:07:06	nmbd[2050]: [2017/12/12 10:07:06.260392, 0] ../lib/util/become_daemon.c:124(daemon_ready)
Dec 12 10:07:06	nmbd[2050]: STATUS=daemon 'nmbd' finished starting up and ready to serve connections
Dec 12 10:07:06	nmbd[2050]: [2017/12/12 10:07:06.260641, 0] ../source3/nmbd/nmbd_become_dmb.c:294(become_domain_master_browser_bcast)
Dec 12 10:07:06	nmbd[2050]: become_domain_master_browser_bcast:
Dec 12 10:07:06	nmbd[2050]: Attempting to become domain master browser on workgroup LO on subnet 172.17.7.3
Dec 12 10:07:06	nmbd[2050]: [2017/12/12 10:07:06.260665, 0] ../source3/nmbd/nmbd_become_dmb.c:307(become_domain_master_browser_bcast)
Dec 12 10:07:06	nmbd[2050]: become_domain_master_browser_bcast: querying subnet 172.17.7.3 for domain master browser on workgroup LO
Dec 12 10:07:06	smbd[2051]: [2017/12/12 10:07:06.342827, 1] ../source3/profile/profile_dummy.c:30(set_profile_level)
Dec 12 10:07:06	smbd[2051]: INFO: Profiling support unavailable in this build.
Dec 12 10:07:06	smbd[2052]: [2017/12/12 10:07:06.451038, 1] ../source3/smbd/files.c:218(file_init_global)
Dec 12 10:07:06	smbd[2052]: file_init_global: Information only: requested 233478 open files, 59392 are available.
Dec 12 10:07:06	smbd[2052]: [2017/12/12 10:07:06.604325, 0] ../lib/util/become_daemon.c:124(daemon_ready)
Dec 12 10:07:06	smbd[2052]: STATUS=daemon 'smbd' finished starting up and ready to serve connections
Dec 12 10:07:10	transmission-daemon[2208]: Stranger Things 2 - LostFilm.TV No data found! Ensure your drives are connected or use "Set Location". To re-download, remove the torrent and re-add it. (torrent.c:537)
Dec 12 10:07:12	lighttpd[2498]: (server.c.1412) server started (lighttpd/1.4.48)
Dec 12 10:07:13	login: login on ttyv0 as root
Dec 12 10:07:14	nmbd[2050]: [2017/12/12 10:07:14.486071, 0] ../source3/nmbd/nmbd_become_dmb.c:112(become_domain_master_stage2)
Dec 12 10:07:14	nmbd[2050]: *****
Dec 12 10:07:14	nmbd[2050]:
Dec 12 10:07:14	nmbd[2050]: Samba server FS is now a domain master browser for workgroup LO on subnet 172.17.7.3
Dec 12 10:07:14	nmbd[2050]:
Dec 12 10:07:14	nmbd[2050]: *****
Dec 12 10:07:30	nmbd[2050]: [2017/12/12 10:07:30.171091, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Dec 12 10:07:30	nmbd[2050]: *****
Dec 12 10:07:30	nmbd[2050]:
Dec 12 10:07:30	nmbd[2050]: Samba name server FS is now a local master browser for workgroup LO on subnet 172.17.7.3
Dec 12 10:07:30	nmbd[2050]:
Dec 12 10:07:30	nmbd[2050]: *****

bitman
NewUser
NewUser
Posts: 3
Joined: 12 Dec 2017 09:29
Status: Offline

Re: Random disconnection of disks

#2

Post by bitman » 20 Dec 2017 18:29

Any body halp me?

User avatar
raulfg3
Site Admin
Site Admin
Posts: 4901
Joined: 22 Jun 2012 22:13
Location: Madrid (ESPAÑA)
Contact:
Status: Offline

Re: Random disconnection of disks

#3

Post by raulfg3 » 20 Dec 2017 19:54

difficult to help.


try to find the error in the hardware , i suspect from some cable or controller that do not fit correctly in his plug.

try to change type disk from SCSI to SATA , perhaps helps.....
12.0.0.4 - BETA (revision 6625)+OBI on SUPERMICRO X8SIL-F 8GB of ECC RAM, 12x3TB disk in 3 vdev in RaidZ1 = 32TB Raw size only 22TB usable

Wiki
Last changes
Old Wiki

bitman
NewUser
NewUser
Posts: 3
Joined: 12 Dec 2017 09:29
Status: Offline

Re: Random disconnection of disks

#4

Post by bitman » 21 Dec 2017 07:48

I note that the remaining virtual machines on these same physical disks work without such failures. Changes in the hardware were not made in the previous 2 years. Everything was fine until a certain point when the system was updated. In addition to everything else, the drive on which the SATA system N4F is installed, and in the log is won, that it is also affected by a general malfunction.

Dec 12 10:06:57 kernel: (ada0: ahcich1: 0: 0: 0): WRITE_FPDMA_QUEUED. ACB: 61 40 00 21 00 40 00 00 00 00 00 00
Dec 12 10:06:57 kernel: (ada0: ahcich1: 0: 0: 0): CAM status: ATA Status Error
Dec 12 10:06:57 kernel: (ada0: ahcich1: 0: 0: 0): ATA status: 41 (DRDY ERR), error: 02 (NM)
Dec 12 10:06:57 kernel: (ada0: ahcich1: 0: 0: 0): RES: 41 02 00 00 00 00 00 00 00 00 00
Dec 12 10:06:57 kernel: (ada0: ahcich1: 0: 0: 0): Retrying commands

So, that probably there is a matter in the software or the kernel.
Guys, I'm asking for help!

User avatar
raulfg3
Site Admin
Site Admin
Posts: 4901
Joined: 22 Jun 2012 22:13
Location: Madrid (ESPAÑA)
Contact:
Status: Offline

Re: Random disconnection of disks

#5

Post by raulfg3 » 21 Dec 2017 09:05

you do not lose anything if unplug and replug ada0 to be totally sure that conection is good and phisical error dissapear.

if ada0 lose connection and is the disk when O.S. resides, this can affect all the V.M. and VM SCSI Disk, so please revise ada0
12.0.0.4 - BETA (revision 6625)+OBI on SUPERMICRO X8SIL-F 8GB of ECC RAM, 12x3TB disk in 3 vdev in RaidZ1 = 32TB Raw size only 22TB usable

Wiki
Last changes
Old Wiki

User avatar
STAMSTER
experienced User
experienced User
Posts: 80
Joined: 23 Feb 2014 15:58
Status: Offline

Re: Random disconnection of disks

#6

Post by STAMSTER » 20 Jan 2018 01:28

I think FreeBSD v11 is the culprit somehow.

Take a look at this: https://lists.freebsd.org/pipermail/fre ... 07189.html


I have pFsense (also based on FreeBSD) router running on my ESXi 6.5 as VM - and something similar just happened. When router was on FreeBSD 10.x it worked perfectly for 6+ months.

Messages in dmesg:
Jan 20 00:00:35 kernel mpt0: request 0xfffffe0000f35670:36447 timed out for ccb 0xfffff80026098000 (req->ccb 0xfffff80026098000)
Jan 20 00:00:35 kernel mpt0: request 0xfffffe0000f355d8:36446 timed out for ccb 0xfffff8002609e000 (req->ccb 0xfffff8002609e000)
Jan 20 00:00:35 kernel mpt0: request 0xfffffe0000f35540:36445 timed out for ccb 0xfffff800260a1800 (req->ccb 0xfffff800260a1800)
Jan 20 00:00:35 kernel mpt0: request 0xfffffe0000f354a8:36444 timed out for ccb 0xfffff8002609e800 (req->ccb 0xfffff8002609e800)
Jan 20 00:00:35 kernel mpt0: request 0xfffffe0000f35410:36443 timed out for ccb 0xfffff80026165800 (req->ccb 0xfffff80026165800)
Jan 20 00:00:35 kernel mpt0: attempting to abort req 0xfffffe0000f35f58:36462 function 0
Jan 20 00:00:35 kernel mpt0: mpt_wait_req(1) timed out
Jan 20 00:00:35 kernel mpt0: mpt_recover_commands: abort timed-out. Resetting controller
Jan 20 00:00:35 kernel mpt0: mpt_cam_event: 0x0
Jan 20 00:00:35 kernel mpt0: mpt_cam_event: 0x0
Jan 20 00:00:35 kernel mpt0: completing timedout/aborted req 0xfffffe0000f35f58:36462
Jan 20 00:00:35 kernel mpt0: completing timedout/aborted req 0xfffffe0000f35ec0:36461
Jan 20 00:00:35 kernel mpt0: completing timedout/aborted req 0xfffffe0000f35e28:36460
Jan 20 00:00:35 kernel mpt0: completing timedout/aborted req 0xfffffe0000f35d90:36459
Jan 20 00:00:35 kernel mpt0: completing timedout/aborted req 0xfffffe0000f35cf8:36458

FYI: this issue seems to occur only when ESXi host is under heavy I/O load.
rIPMI

antperval
NewUser
NewUser
Posts: 2
Joined: 11 Jul 2019 08:50
Status: Offline

Re: Random disconnection of disks

#7

Post by antperval » 11 Jul 2019 09:01

Hi all,

I'm sorry for answering an old post, but we're experiencing same issue in one of our enclosures. System continously sets one of the disks as REMOVED and marks pool as degraded. We cannot even see the device in /dev. A reboot solves the issue for a while, but sooner or later it's back again. We have replaced the disk a couple of times, so we don't think disk is the problem.

We have contacted with hardware manufacturer (supermicro) to test if it's a hardware issue but in the meantime we would like to investigate if problem could come from OS.

Did you manage to fix the issue? please could you help us?

Thank you very much in advance.

User avatar
raulfg3
Site Admin
Site Admin
Posts: 4901
Joined: 22 Jun 2012 22:13
Location: Madrid (ESPAÑA)
Contact:
Status: Offline

Re: Random disconnection of disks

#8

Post by raulfg3 » 11 Jul 2019 12:46

in my experience, enclosures are responible in 100% of the disconnction, so I fnally opted to plug directly to sata ports ( using sata cable, but eliminating the enclosure).

perhaps some good brands works well, but i have problems with 2 diferents brands.
12.0.0.4 - BETA (revision 6625)+OBI on SUPERMICRO X8SIL-F 8GB of ECC RAM, 12x3TB disk in 3 vdev in RaidZ1 = 32TB Raw size only 22TB usable

Wiki
Last changes
Old Wiki

antperval
NewUser
NewUser
Posts: 2
Joined: 11 Jul 2019 08:50
Status: Offline

Re: Random disconnection of disks

#9

Post by antperval » 12 Jul 2019 11:45

Hi raulfg3,

Thank you very much. We are waiting for hardware manufacturer final response althought they bet for a backplane problem. In the meantime we can try to replace cables or reconnect them as we have some pieces here and it will be easier for us to test this replacement instead replacing backplane.
I'm on holiday for some days but I will update the post if we find a good solution for the issue.

Regards,

Post Reply

Return to “Hard disk & controller”