November 18, 20178 yr Tested on rc10 and rc12, most likely a bug introduced on rc8 with the partition layout changes, there are 2 bugs in one: bug #1: if the old parity disk was only used post rc8 it won't be partitioned, do the swap procedure, start the array and you get this error at parity copy start: Nov 18 00:03:49 Test emhttpd: error: pswap_dsbl_copy: No such file or directory (2): open: /dev/sdb1 In this example sdb is old parity, parity copy status stays stuck @ 1%, cancel doesn't work, only a reboot. bug #2: old parity was used prior to rc8 so it has a valid partition but new parity is cleared, do the swap procedure, start the array, parity copy starts and goes till 100% and then it stays stuck @ 100%, there's no error in the log, last entry is: Nov 18 00:40:57 Test emhttpd: copy: 99% complete Cancel doesn't work, only a reboot. P.S.: time for bed so can't test with a previously partitioned old and new parity, but would expect that to work on second though probably it won't work also, as the partition should be copied to the new parity? Edited November 18, 20178 yr by johnnie.black
November 21, 20178 yr On 11/17/2017 at 4:45 PM, johnnie.black said: Tested on rc10 and rc12, most likely a bug introduced on rc8 with the partition layout changes, there are 2 bugs in one: bug #1: if the old parity disk was only used post rc8 it won't be partitioned, do the swap procedure, start the array and you get this error at parity copy start: Nov 18 00:03:49 Test emhttpd: error: pswap_dsbl_copy: No such file or directory (2): open: /dev/sdb1 In this example sdb is old parity, parity copy status stays stuck @ 1%, cancel doesn't work, only a reboot. bug #2: old parity was used prior to rc8 so it has a valid partition but new parity is cleared, do the swap procedure, start the array, parity copy starts and goes till 100% and then it stays stuck @ 100%, there's no error in the log, last entry is: Nov 18 00:40:57 Test emhttpd: copy: 99% complete Cancel doesn't work, only a reboot. P.S.: time for bed so can't test with a previously partitioned old and new parity, but would expect that to work on second though probably it won't work also, as the partition should be copied to the new parity? I can't reproduce bug #1 with current release. That is, a device without a partition table plugged into any slot, including parity, will have a partition table written to it upon array Start. It's possible there was a 6.4.0-rc release that didn't do this with Parity but has since been fixed. Nevertheless, added some code that will check for valid partition on parity disk(s) and create if not present. re: copy not finishing - yup, thanks for pointing that out. Fixed in next release.
February 3, 20188 yr I think that this problem has not been fixed. I just tried a parity swap to a brand new 8TB drive. I first tried it on 6.4.0, which got stuck at 100%, and the identification for disk 2 began to fail. I then upgraded to the current RC version, I believe 6.4.1 (this was a few days ago), and the same issue occurred. I then downgraded to 6.3.5, where the same issue occurred. Here are the logs from my server from one of the occurrences: tower-diagnostics-20180201-0532.zip
February 3, 20188 yr Author Parity swap is working fine, you're having issues with the disks on the Marvell controller ending up in a disabled disk: Quote Jan 31 11:18:46 Tower emhttpd: copy: disk1 to disk0 running Jan 31 11:23:00 Tower ntpd[1540]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Jan 31 11:49:22 Tower kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 31 11:49:22 Tower kernel: ata10.00: failed command: IDENTIFY DEVICE Jan 31 11:49:22 Tower kernel: ata10.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 8 pio 512 in Jan 31 11:49:22 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 31 11:49:22 Tower kernel: ata10.00: status: { DRDY } Jan 31 11:49:22 Tower kernel: ata10: hard resetting link Jan 31 11:49:23 Tower kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 31 11:49:23 Tower kernel: ata10.00: configured for UDMA/133 Jan 31 11:49:23 Tower kernel: ata10: EH complete Jan 31 11:49:44 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 31 11:49:44 Tower kernel: ata12.00: failed command: SMART Jan 31 11:49:44 Tower kernel: ata12.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 15 pio 512 in Jan 31 11:49:44 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 31 11:49:44 Tower kernel: ata12.00: status: { DRDY } Jan 31 11:49:44 Tower kernel: ata12: hard resetting link Jan 31 11:49:45 Tower kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 31 11:49:45 Tower kernel: ata12.00: configured for UDMA/133 Jan 31 11:49:45 Tower kernel: ata12: EH complete Jan 31 11:50:05 Tower kernel: ata11.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 31 11:50:05 Tower kernel: ata11.00: failed command: SMART Jan 31 11:50:05 Tower kernel: ata11.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 10 pio 512 in Jan 31 11:50:05 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 31 11:50:05 Tower kernel: ata11.00: status: { DRDY } Jan 31 11:50:05 Tower kernel: ata11: hard resetting link Jan 31 11:50:06 Tower kernel: ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 31 11:50:06 Tower kernel: ata11.00: configured for UDMA/133 Jan 31 11:50:06 Tower kernel: ata11: EH complete Jan 31 12:20:22 Tower kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 31 12:20:22 Tower kernel: ata10.00: failed command: IDENTIFY DEVICE Jan 31 12:20:22 Tower kernel: ata10.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 8 pio 512 in Jan 31 12:20:22 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 31 12:20:22 Tower kernel: ata10.00: status: { DRDY } Jan 31 12:20:22 Tower kernel: ata10: hard resetting link Jan 31 12:20:23 Tower kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 31 12:20:23 Tower kernel: ata10.00: configured for UDMA/133 Jan 31 12:20:23 Tower kernel: ata10: EH complete Jan 31 12:20:44 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 31 12:20:44 Tower kernel: ata12.00: failed command: IDENTIFY DEVICE Jan 31 12:20:44 Tower kernel: ata12.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 21 pio 512 in Jan 31 12:20:44 Tower kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 31 12:20:44 Tower kernel: ata12.00: status: { DRDY } Jan 31 12:20:44 Tower kernel: ata12: hard resetting link Jan 31 12:20:45 Tower kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 31 12:20:50 Tower kernel: ata12.00: qc timeout (cmd 0xec) Jan 31 12:20:50 Tower kernel: ata12.00: failed to IDENTIFY (I/O error, err_mask=0x4) Jan 31 12:20:50 Tower kernel: ata12.00: revalidation failed (errno=-5) Jan 31 12:20:50 Tower kernel: ata12: hard resetting link Jan 31 12:20:50 Tower kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 31 12:20:50 Tower kernel: ata12.00: configured for UDMA/133 Jan 31 12:20:50 Tower kernel: ata12: EH complete Jan 31 12:51:22 Tower kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 31 12:51:22 Tower kernel: ata10.00: failed command: IDENTIFY DEVICE Jan 31 12:51:22 Tower kernel: ata10.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 9 pio 512 in Jan 31 12:51:22 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 31 12:51:22 Tower kernel: ata10.00: status: { DRDY } Jan 31 12:51:22 Tower kernel: ata10: hard resetting link Jan 31 12:51:22 Tower kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 31 12:51:22 Tower kernel: ata10.00: configured for UDMA/133 Jan 31 12:51:22 Tower kernel: ata10: EH complete Jan 31 12:51:43 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 31 12:51:43 Tower kernel: ata12.00: failed command: IDENTIFY DEVICE Jan 31 12:51:43 Tower kernel: ata12.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 13 pio 512 in Jan 31 12:51:43 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 31 12:51:43 Tower kernel: ata12.00: status: { DRDY } Jan 31 12:51:43 Tower kernel: ata12: hard resetting link Jan 31 12:51:43 Tower kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 31 12:51:48 Tower kernel: ata12.00: qc timeout (cmd 0xec) Jan 31 12:51:48 Tower kernel: ata12.00: failed to IDENTIFY (I/O error, err_mask=0x4) Jan 31 12:51:48 Tower kernel: ata12.00: revalidation failed (errno=-5) Jan 31 12:51:48 Tower kernel: ata12: hard resetting link Jan 31 12:51:49 Tower kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 31 12:51:59 Tower kernel: ata12.00: qc timeout (cmd 0xec) Jan 31 12:51:59 Tower kernel: ata12.00: failed to IDENTIFY (I/O error, err_mask=0x4) Jan 31 12:51:59 Tower kernel: ata12.00: revalidation failed (errno=-5) Jan 31 12:51:59 Tower kernel: ata12: limiting SATA link speed to 3.0 Gbps Jan 31 12:51:59 Tower kernel: ata12: hard resetting link Jan 31 12:52:00 Tower kernel: ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jan 31 12:52:00 Tower kernel: ata12.00: configured for UDMA/133 Jan 31 12:52:00 Tower kernel: ata12: EH complete Jan 31 12:52:20 Tower kernel: ata11.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 31 12:52:20 Tower kernel: ata11.00: failed command: IDENTIFY DEVICE Jan 31 12:52:20 Tower kernel: ata11.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in Jan 31 12:52:20 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 31 12:52:20 Tower kernel: ata11.00: status: { DRDY } Jan 31 12:52:20 Tower kernel: ata11: hard resetting link Jan 31 12:52:21 Tower kernel: ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 31 12:52:21 Tower kernel: ata11.00: configured for UDMA/133 Jan 31 12:52:21 Tower kernel: ata11: EH complete Jan 31 13:22:22 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 31 13:22:22 Tower kernel: ata12.00: failed command: IDENTIFY DEVICE Jan 31 13:22:22 Tower kernel: ata12.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 3 pio 512 in Jan 31 13:22:22 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 31 13:22:22 Tower kernel: ata12.00: status: { DRDY } Jan 31 13:22:22 Tower kernel: ata12: hard resetting link Jan 31 13:22:22 Tower kernel: ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jan 31 13:22:22 Tower kernel: ata12.00: configured for UDMA/133 Jan 31 13:22:22 Tower kernel: ata12: EH complete Jan 31 13:22:43 Tower kernel: ata11.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 31 13:22:43 Tower kernel: ata11.00: failed command: IDENTIFY DEVICE Jan 31 13:22:43 Tower kernel: ata11.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 21 pio 512 in Jan 31 13:22:43 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 31 13:22:43 Tower kernel: ata11.00: status: { DRDY } Jan 31 13:22:43 Tower kernel: ata11: hard resetting link Jan 31 13:22:43 Tower kernel: ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 31 13:22:43 Tower kernel: ata11.00: configured for UDMA/133 Jan 31 13:22:43 Tower kernel: ata11: EH complete Jan 31 13:53:22 Tower kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 31 13:53:22 Tower kernel: ata10.00: failed command: IDENTIFY DEVICE Jan 31 13:53:22 Tower kernel: ata10.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 28 pio 512 in Jan 31 13:53:22 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 31 13:53:22 Tower kernel: ata10.00: status: { DRDY } Jan 31 13:53:22 Tower kernel: ata10: hard resetting link Jan 31 13:53:22 Tower kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 31 13:53:23 Tower kernel: ata10.00: configured for UDMA/133 Jan 31 13:53:23 Tower kernel: ata10: EH complete Jan 31 13:53:44 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 31 13:53:44 Tower kernel: ata12.00: failed command: SMART Jan 31 13:53:44 Tower kernel: ata12.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 28 pio 512 in Jan 31 13:53:44 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 31 13:53:44 Tower kernel: ata12.00: status: { DRDY } Jan 31 13:53:44 Tower kernel: ata12: hard resetting link Jan 31 13:53:45 Tower kernel: ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jan 31 13:53:50 Tower kernel: ata12.00: qc timeout (cmd 0xec) Jan 31 13:53:50 Tower kernel: ata12.00: failed to IDENTIFY (I/O error, err_mask=0x4) Jan 31 13:53:50 Tower kernel: ata12.00: revalidation failed (errno=-5) Jan 31 13:53:50 Tower kernel: ata12: hard resetting link Jan 31 13:53:50 Tower kernel: ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jan 31 13:53:50 Tower kernel: ata12.00: configured for UDMA/133 Jan 31 13:53:50 Tower kernel: ata12: EH complete Jan 31 13:54:11 Tower kernel: ata11.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 31 13:54:11 Tower kernel: ata11.00: failed command: IDENTIFY DEVICE Jan 31 13:54:11 Tower kernel: ata11.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 16 pio 512 in Jan 31 13:54:11 Tower kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 31 13:54:11 Tower kernel: ata11.00: status: { DRDY } Jan 31 13:54:11 Tower kernel: ata11: hard resetting link Jan 31 13:54:12 Tower kernel: ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 31 13:54:12 Tower kernel: ata11.00: configured for UDMA/133 Jan 31 13:54:12 Tower kernel: ata11: EH complete Jan 31 14:24:22 Tower kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 31 14:24:22 Tower kernel: ata10.00: failed command: SMART Jan 31 14:24:22 Tower kernel: ata10.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 15 pio 512 in Jan 31 14:24:22 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 31 14:24:22 Tower kernel: ata10.00: status: { DRDY } Jan 31 14:24:22 Tower kernel: ata10: hard resetting link Jan 31 14:24:23 Tower kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 31 14:24:23 Tower kernel: ata10.00: configured for UDMA/133 Jan 31 14:24:23 Tower kernel: ata10: EH complete Jan 31 14:24:44 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 31 14:24:44 Tower kernel: ata12.00: failed command: IDENTIFY DEVICE Jan 31 14:24:44 Tower kernel: ata12.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 10 pio 512 in Jan 31 14:24:44 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 31 14:24:44 Tower kernel: ata12.00: status: { DRDY } Jan 31 14:24:44 Tower kernel: ata12: hard resetting link Jan 31 14:24:45 Tower kernel: ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jan 31 14:24:50 Tower kernel: ata12.00: qc timeout (cmd 0xec) Jan 31 14:24:50 Tower kernel: ata12.00: failed to IDENTIFY (I/O error, err_mask=0x4) Jan 31 14:24:50 Tower kernel: ata12.00: revalidation failed (errno=-5) Jan 31 14:24:50 Tower kernel: ata12: hard resetting link Jan 31 14:24:50 Tower kernel: ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jan 31 14:25:01 Tower kernel: ata12.00: qc timeout (cmd 0xec) Jan 31 14:25:01 Tower kernel: ata12.00: failed to IDENTIFY (I/O error, err_mask=0x4) Jan 31 14:25:01 Tower kernel: ata12.00: revalidation failed (errno=-5) Jan 31 14:25:01 Tower kernel: ata12: limiting SATA link speed to 1.5 Gbps Jan 31 14:25:01 Tower kernel: ata12.00: limiting speed to UDMA/133:PIO3 Jan 31 14:25:01 Tower kernel: ata12: hard resetting link Jan 31 14:25:01 Tower kernel: ata12: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 31 14:25:31 Tower kernel: ata12.00: qc timeout (cmd 0xec) Jan 31 14:25:31 Tower kernel: ata12.00: failed to IDENTIFY (I/O error, err_mask=0x4) Jan 31 14:25:31 Tower kernel: ata12.00: revalidation failed (errno=-5) Jan 31 14:25:31 Tower kernel: ata12.00: disabled
Archived
This topic is now archived and is closed to further replies.