bkbt Posted August 9 Share Posted August 9 Hello! After losing power from a hurricane one of my disks from my array has been moved from my array and is now in my unassigned device section. I've never expected this but it has broken my array. Aug 9 13:19:03 Tower kernel: ata11: SATA max UDMA/133 abar m2048@0xf7610000 port 0xf7610200 irq 58 Aug 9 13:19:03 Tower kernel: ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Aug 9 13:19:03 Tower kernel: ata11.00: ATA-8: HITACHI HUS724020ALA640, P6KULBWW, MF6ONS00, max UDMA/133 Aug 9 13:19:03 Tower kernel: ata11.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 32), AA Aug 9 13:19:03 Tower kernel: ata11.00: configured for UDMA/133 Aug 9 13:19:03 Tower kernel: sd 11:0:0:0: [sdg] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) Aug 9 13:19:03 Tower kernel: sd 11:0:0:0: [sdg] Write Protect is off Aug 9 13:19:03 Tower kernel: sd 11:0:0:0: [sdg] Mode Sense: 00 3a 00 00 Aug 9 13:19:03 Tower kernel: sd 11:0:0:0: [sdg] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Aug 9 13:19:03 Tower kernel: sdg: sdg1 Aug 9 13:19:03 Tower kernel: sd 11:0:0:0: [sdg] Attached SCSI removable disk Aug 9 13:19:03 Tower kernel: ata11.00: exception Emask 0x10 SAct 0x1 SErr 0x380000 action 0x6 frozen Aug 9 13:19:03 Tower kernel: ata11.00: irq_stat 0x08000000, interface fatal error Aug 9 13:19:03 Tower kernel: ata11: SError: { 10B8B Dispar BadCRC } Aug 9 13:19:03 Tower kernel: ata11.00: failed command: READ FPDMA QUEUED Aug 9 13:19:03 Tower kernel: ata11.00: cmd 60/f8:00:08:09:00/00:00:00:00:00/40 tag 0 ncq dma 126976 in Aug 9 13:19:03 Tower kernel: ata11.00: status: { DRDY } Aug 9 13:19:03 Tower kernel: ata11: hard resetting link Aug 9 13:19:03 Tower kernel: ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Aug 9 13:19:03 Tower kernel: ata11.00: configured for UDMA/133 Aug 9 13:19:03 Tower kernel: sd 11:0:0:0: [sdg] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Aug 9 13:19:03 Tower kernel: sd 11:0:0:0: [sdg] tag#0 Sense Key : 0x5 [current] Aug 9 13:19:03 Tower kernel: sd 11:0:0:0: [sdg] tag#0 ASC=0x21 ASCQ=0x4 Aug 9 13:19:03 Tower kernel: sd 11:0:0:0: [sdg] tag#0 CDB: opcode=0x28 28 00 00 00 09 08 00 00 f8 00 Aug 9 13:19:03 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2312 op 0x0:(READ) flags 0x80700 phys_seg 31 prio class 0 Aug 9 13:19:03 Tower kernel: ata11: EH complete Aug 9 13:19:03 Tower kernel: ata11.00: exception Emask 0x10 SAct 0x1000 SErr 0x180000 action 0x6 frozen Aug 9 13:19:03 Tower kernel: ata11.00: irq_stat 0x08000000, interface fatal error Aug 9 13:19:03 Tower kernel: ata11: SError: { 10B8B Dispar } Aug 9 13:19:03 Tower kernel: ata11.00: failed command: READ FPDMA QUEUED Aug 9 13:19:03 Tower kernel: ata11.00: cmd 60/f8:60:08:0a:00/01:00:00:00:00/40 tag 12 ncq dma 258048 in Aug 9 13:19:03 Tower kernel: ata11.00: status: { DRDY } Aug 9 13:19:03 Tower kernel: ata11: hard resetting link Aug 9 13:19:03 Tower kernel: ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Aug 9 13:19:03 Tower kernel: ata11.00: configured for UDMA/133 Aug 9 13:19:03 Tower kernel: sd 11:0:0:0: [sdg] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Aug 9 13:19:03 Tower kernel: sd 11:0:0:0: [sdg] tag#12 Sense Key : 0x5 [current] Aug 9 13:19:03 Tower kernel: sd 11:0:0:0: [sdg] tag#12 ASC=0x21 ASCQ=0x4 Aug 9 13:19:03 Tower kernel: sd 11:0:0:0: [sdg] tag#12 CDB: opcode=0x28 28 00 00 00 0a 08 00 01 f8 00 Aug 9 13:19:03 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2568 op 0x0:(READ) flags 0x80700 phys_seg 58 prio class 0 Aug 9 13:19:03 Tower kernel: ata11: EH complete Aug 9 13:19:03 Tower kernel: ata11.00: exception Emask 0x10 SAct 0x10000000 SErr 0x180000 action 0x6 frozen Aug 9 13:19:03 Tower kernel: ata11.00: irq_stat 0x08000000, interface fatal error Aug 9 13:19:03 Tower kernel: ata11: SError: { 10B8B Dispar } Aug 9 13:19:03 Tower kernel: ata11.00: failed command: READ FPDMA QUEUED Aug 9 13:19:03 Tower kernel: ata11.00: cmd 60/08:e0:00:08:00/00:00:00:00:00/40 tag 28 ncq dma 4096 in Aug 9 13:19:03 Tower kernel: ata11.00: status: { DRDY } Aug 9 13:19:03 Tower kernel: ata11: hard resetting link Aug 9 13:19:04 Tower kernel: ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Aug 9 13:19:04 Tower kernel: ata11.00: configured for UDMA/133 Aug 9 13:19:04 Tower kernel: sd 11:0:0:0: [sdg] tag#28 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Aug 9 13:19:04 Tower kernel: sd 11:0:0:0: [sdg] tag#28 Sense Key : 0x5 [current] Aug 9 13:19:04 Tower kernel: sd 11:0:0:0: [sdg] tag#28 ASC=0x21 ASCQ=0x4 Aug 9 13:19:04 Tower kernel: sd 11:0:0:0: [sdg] tag#28 CDB: opcode=0x28 28 00 00 00 08 00 00 00 08 00 Aug 9 13:19:04 Tower kernel: blk_update_request: I/O error, dev sdg, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Aug 9 13:19:04 Tower kernel: ata11: EH complete Aug 9 13:19:04 Tower kernel: ata11: limiting SATA link speed to 3.0 Gbps Aug 9 13:19:04 Tower kernel: ata11.00: exception Emask 0x10 SAct 0x200 SErr 0x180000 action 0x6 frozen Aug 9 13:19:04 Tower kernel: ata11.00: irq_stat 0x08000000, interface fatal error Aug 9 13:19:04 Tower kernel: ata11: SError: { 10B8B Dispar } Aug 9 13:19:04 Tower kernel: ata11.00: failed command: READ FPDMA QUEUED Aug 9 13:19:04 Tower kernel: ata11.00: cmd 60/f8:48:08:02:00/01:00:00:00:00/40 tag 9 ncq dma 258048 in Aug 9 13:19:04 Tower kernel: ata11.00: status: { DRDY } Aug 9 13:19:04 Tower kernel: ata11: hard resetting link Aug 9 13:19:04 Tower kernel: ata11: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Aug 9 13:19:04 Tower kernel: ata11.00: configured for UDMA/133 Aug 9 13:19:04 Tower kernel: sd 11:0:0:0: [sdg] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Aug 9 13:19:04 Tower kernel: sd 11:0:0:0: [sdg] tag#9 Sense Key : 0x5 [current] Aug 9 13:19:04 Tower kernel: sd 11:0:0:0: [sdg] tag#9 ASC=0x21 ASCQ=0x4 Aug 9 13:19:04 Tower kernel: sd 11:0:0:0: [sdg] tag#9 CDB: opcode=0x28 28 00 00 00 02 08 00 01 f8 00 Aug 9 13:19:04 Tower kernel: blk_update_request: I/O error, dev sdg, sector 520 op 0x0:(READ) flags 0x80700 phys_seg 56 prio class 0 Aug 9 13:19:04 Tower kernel: ata11: EH complete Aug 9 13:20:08 Tower emhttpd: HITACHI_HUS724020ALA640_P6KULBWW (sdg) 512 3907029168 Aug 9 13:20:08 Tower emhttpd: read SMART /dev/sdg Aug 9 13:21:18 Tower emhttpd: HITACHI_HUS724020ALA640_P6KULBWW (sdg) 512 3907029168 Aug 9 13:21:18 Tower kernel: mdcmd (7): import 6 sdg 64 1953514552 0 HITACHI_HUS724020ALA640_P6KULBWW Aug 9 13:21:18 Tower kernel: md: import disk6: (sdg) HITACHI_HUS724020ALA640_P6KULBWW size: 1953514552 Aug 9 13:21:18 Tower emhttpd: read SMART /dev/sdg Aug 9 13:21:28 Tower emhttpd: HITACHI_HUS724020ALA640_P6KULBWW (sdg) 512 3907029168 Aug 9 13:21:28 Tower emhttpd: read SMART /dev/sdg Aug 9 13:22:24 Tower emhttpd: HITACHI_HUS724020ALA640_P6KULBWW (sdg) 512 3907029168 Aug 9 13:22:24 Tower kernel: mdcmd (7): import 6 sdg 64 1953514552 0 HITACHI_HUS724020ALA640_P6KULBWW Aug 9 13:22:24 Tower kernel: md: import disk6: (sdg) HITACHI_HUS724020ALA640_P6KULBWW size: 1953514552 Aug 9 13:22:24 Tower emhttpd: read SMART /dev/sdg Aug 9 13:22:27 Tower emhttpd: HITACHI_HUS724020ALA640_P6KULBWW (sdg) 512 3907029168 Aug 9 13:22:28 Tower emhttpd: read SMART /dev/sdg Aug 9 13:49:13 Tower emhttpd: read SMART /dev/sdg What steps should I take with this? I've never had to rebuild from parity. Thanks! Quote Link to comment
JonathanM Posted August 9 Share Posted August 9 Attaching diagnostics to your next post in this thread would be a start. Your first screenshot doesn't show any missing disks, what was the layout before this happened? Quote Link to comment
bkbt Posted August 9 Author Share Posted August 9 Hi @JonathanM I'll do that now That drive I believe was Disk 6 in my array. I'll have to find my screenshot of the array setup. tower-diagnostics-20240809-1626.zip Quote Link to comment
JorgeB Posted August 10 Share Posted August 10 According to the diags (and the screenshot), there's no missing or disabled array disk, so not sure what the issue is, please expand Quote Link to comment
Recommended Posts
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.