-
Parity drive errors
Appreciate the help on this. Ive had a disk on order but figured Id get confirmation that the disk should be replaced.
-
Parity drive errors
The extended SMART test finished with the following: Errors occurred - Check SMART report And the smart report is attached. I figure the drive is failing but wanted to get some outside eyes on it. nasty-smart-20220103-0609.zip
-
Parity drive errors
The SMART error log shows multiple of the following: Error 19682 occurred at disk power-on lifetime: 7386 hours (307 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 13d+14:04:53.753 READ DMA EXT 25 00 40 ff ff ff ef 00 13d+14:04:53.007 READ DMA EXT 25 00 40 ff ff ff ef 00 13d+14:04:53.002 READ DMA EXT 25 00 40 ff ff ff ef 00 13d+14:04:52.987 READ DMA EXT 25 00 40 ff ff ff ef 00 13d+14:04:52.899 READ DMA EXT
-
Parity drive errors
I noticed there are disk errors on the parity drive. Ive also attached the diagnostic bundle. Below is a snip of the syslog: Jan 2 14:59:46 NASty kernel: md: disk0 read error, sector=3546822248 Jan 2 14:59:46 NASty kernel: md: disk0 read error, sector=3546822256 Jan 2 14:59:46 NASty kernel: md: disk0 read error, sector=3546822264 Jan 2 14:59:46 NASty kernel: md: disk0 read error, sector=3546822272 Jan 2 14:59:46 NASty kernel: md: disk0 read error, sector=3546822280 Jan 2 14:59:46 NASty kernel: md: disk0 read error, sector=3546822288 Jan 2 14:59:46 NASty kernel: md: disk0 read error, sector=3546822296 Jan 2 14:59:46 NASty kernel: md: disk0 read error, sector=3546822304 Jan 2 14:59:46 NASty kernel: ata4: EH complete Jan 2 15:00:14 NASty kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 2 15:00:14 NASty kernel: ata4.00: irq_stat 0x40000001 Jan 2 15:00:14 NASty kernel: ata4.00: failed command: READ DMA EXT Jan 2 15:00:14 NASty kernel: ata4.00: cmd 25/00:40:60:8c:8b/00:05:d3:00:00/e0 tag 16 dma 688128 in Jan 2 15:00:14 NASty kernel: res 51/40:00:80:8d:8b/00:00:d3:00:00/00 Emask 0x9 (media error) Jan 2 15:00:14 NASty kernel: ata4.00: status: { DRDY ERR } Jan 2 15:00:14 NASty kernel: ata4.00: error: { UNC } Jan 2 15:00:14 NASty kernel: ata4.00: configured for UDMA/133 Jan 2 15:00:14 NASty kernel: sd 4:0:0:0: [sde] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=3s Jan 2 15:00:14 NASty kernel: sd 4:0:0:0: [sde] tag#16 Sense Key : 0x3 [current] Jan 2 15:00:14 NASty kernel: sd 4:0:0:0: [sde] tag#16 ASC=0x11 ASCQ=0x4 Jan 2 15:00:14 NASty kernel: sd 4:0:0:0: [sde] tag#16 CDB: opcode=0x88 88 00 00 00 00 00 d3 8b 8c 60 00 00 05 40 00 00 Jan 2 15:00:14 NASty kernel: blk_update_request: I/O error, dev sde, sector 3549138304 op 0x0:(READ) flags 0x4000 phys_seg 132 prio class 0 Jan 2 15:00:14 NASty kernel: md: disk0 read error, sector=3549138240 Jan 2 15:00:14 NASty kernel: md: disk0 read error, sector=3549138248 Jan 2 15:00:14 NASty kernel: md: disk0 read error, sector=3549138256 Jan 2 15:00:14 NASty kernel: md: disk0 read error, sector=3549138264 nasty-diagnostics-20220102-1826.zip
-
0sider joined the community
-
2nd license registration
I purchased a 2 license pack and only registered one of the licenses. I have the order number/invoice and was wondering if I could still register my 2nd license.
0sider
Members
-
Joined
-
Last visited