January 31, 200917 yr Hey Guys, I've been running my UnRaid system for about a month now... very exciting... But every once in a while (couple times a week) my Unraid box quits serving up files for a minute or two. Jan 30 16:23:47 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 30 16:23:47 Tower kernel: ata3.00: BMDMA stat 0x64 Jan 30 16:23:47 Tower kernel: ata3.00: cmd 25/00:00:a7:5c:90/00:03:4b:00:00/e0 tag 0 dma 393216 in Jan 30 16:23:47 Tower kernel: res 51/40:00:f3:5c:90/40:00:4b:00:00/00 Emask 0x9 (media error) Jan 30 16:23:47 Tower kernel: ata3.00: status: { DRDY ERR } Jan 30 16:23:47 Tower kernel: ata3.00: error: { UNC } Jan 30 16:23:48 Tower kernel: ata3.00: configured for UDMA/133 Jan 30 16:23:53 Tower kernel: ata3.01: qc timeout (cmd 0x27) Jan 30 16:23:53 Tower kernel: ata3.01: failed to read native max address (err_mask=0x4) Jan 30 16:23:53 Tower kernel: ata3.01: HPA support seems broken, skipping HPA handling Jan 30 16:23:53 Tower kernel: ata3.01: revalidation failed (errno=-5) Jan 30 16:23:53 Tower kernel: ata3: hard resetting link Jan 30 16:23:53 Tower kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 30 16:23:53 Tower kernel: ata3.00: configured for UDMA/133 Jan 30 16:23:53 Tower kernel: ata3.01: configured for UDMA/133 Jan 30 16:23:53 Tower kernel: ata3: EH complete Jan 30 16:23:58 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 30 16:23:58 Tower kernel: ata3.00: BMDMA stat 0x64 Jan 30 16:23:58 Tower kernel: ata3.00: cmd 25/00:00:a7:5c:90/00:03:4b:00:00/e0 tag 0 dma 393216 in Jan 30 16:23:58 Tower kernel: res 51/40:00:f3:5c:90/40:00:4b:00:00/00 Emask 0x9 (media error) Jan 30 16:23:58 Tower kernel: ata3.00: status: { DRDY ERR } Jan 30 16:23:58 Tower kernel: ata3.00: error: { UNC } Jan 30 16:23:58 Tower kernel: ata3.00: configured for UDMA/133 Jan 30 16:23:58 Tower kernel: ata3.01: configured for UDMA/133 Jan 30 16:23:58 Tower kernel: ata3: EH complete Jan 30 16:24:01 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 30 16:24:01 Tower kernel: ata3.00: BMDMA stat 0x64 Jan 30 16:24:01 Tower kernel: ata3.00: cmd 25/00:00:a7:5c:90/00:03:4b:00:00/e0 tag 0 dma 393216 in Jan 30 16:24:01 Tower kernel: res 51/40:00:f3:5c:90/40:00:4b:00:00/00 Emask 0x9 (media error) Jan 30 16:24:01 Tower kernel: ata3.00: status: { DRDY ERR } Jan 30 16:24:01 Tower kernel: ata3.00: error: { UNC } Jan 30 16:24:01 Tower kernel: ata3.00: configured for UDMA/133 Jan 30 16:24:01 Tower kernel: ata3.01: configured for UDMA/133 Jan 30 16:24:01 Tower kernel: ata3: EH complete Jan 30 16:24:05 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 30 16:24:05 Tower kernel: ata3.00: BMDMA stat 0x64 Jan 30 16:24:05 Tower kernel: ata3.00: cmd 25/00:00:a7:5c:90/00:03:4b:00:00/e0 tag 0 dma 393216 in Jan 30 16:24:05 Tower kernel: res 51/40:00:f3:5c:90/40:00:4b:00:00/00 Emask 0x9 (media error) Jan 30 16:24:05 Tower kernel: ata3.00: status: { DRDY ERR } Jan 30 16:24:05 Tower kernel: ata3.00: error: { UNC } Jan 30 16:24:05 Tower kernel: ata3.00: configured for UDMA/133 Jan 30 16:24:05 Tower kernel: ata3.01: configured for UDMA/133 Jan 30 16:24:05 Tower kernel: ata3: EH complete Jan 30 16:24:08 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 30 16:24:08 Tower kernel: ata3.00: BMDMA stat 0x64 Jan 30 16:24:08 Tower kernel: ata3.00: cmd 25/00:00:a7:5c:90/00:03:4b:00:00/e0 tag 0 dma 393216 in Jan 30 16:24:08 Tower kernel: res 51/40:00:f3:5c:90/40:00:4b:00:00/00 Emask 0x9 (media error) Jan 30 16:24:08 Tower kernel: ata3.00: status: { DRDY ERR } Jan 30 16:24:08 Tower kernel: ata3.00: error: { UNC } Jan 30 16:24:08 Tower kernel: ata3.00: configured for UDMA/133 Jan 30 16:24:08 Tower kernel: ata3.01: configured for UDMA/133 Jan 30 16:24:08 Tower kernel: ata3: EH complete Jan 30 16:24:12 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 30 16:24:12 Tower kernel: ata3.00: BMDMA stat 0x64 Jan 30 16:24:12 Tower kernel: ata3.00: cmd 25/00:00:a7:5c:90/00:03:4b:00:00/e0 tag 0 dma 393216 in Jan 30 16:24:12 Tower kernel: res 51/40:00:f3:5c:90/40:00:4b:00:00/00 Emask 0x9 (media error) Jan 30 16:24:12 Tower kernel: ata3.00: status: { DRDY ERR } Jan 30 16:24:12 Tower kernel: ata3.00: error: { UNC } Jan 30 16:24:12 Tower kernel: ata3.00: configured for UDMA/133 Jan 30 16:24:12 Tower kernel: ata3.01: configured for UDMA/133 Jan 30 16:24:12 Tower kernel: sd 3:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 Jan 30 16:24:12 Tower kernel: sd 3:0:0:0: [sdb] Sense Key : 0x3 [current] [descriptor] Jan 30 16:24:12 Tower kernel: Descriptor sense data with sense descriptors (in hex): Jan 30 16:24:12 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Jan 30 16:24:12 Tower kernel: 4b 90 5c f3 Jan 30 16:24:12 Tower kernel: sd 3:0:0:0: [sdb] ASC=0x11 ASCQ=0x4 Jan 30 16:24:12 Tower kernel: end_request: I/O error, dev sdb, sector 1267752179 Jan 30 16:24:12 Tower kernel: ata3: EH complete Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752112/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752120/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752128/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752136/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752144/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752152/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752160/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752168/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752176/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752184/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752192/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752200/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752208/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752216/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752224/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752232/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752240/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752248/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752256/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752264/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752272/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752280/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752288/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752296/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752304/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752312/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752320/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752328/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752336/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752344/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752352/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752360/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752368/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752376/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752384/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752392/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752400/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752408/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752416/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752424/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752432/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752440/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752448/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752456/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752464/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752472/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752480/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752488/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752496/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752504/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752512/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752520/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752528/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752536/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752544/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752552/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752560/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752568/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752576/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752584/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752592/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752600/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752608/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752616/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752624/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752632/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752640/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752648/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752656/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752664/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752672/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752680/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752688/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752696/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752704/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752712/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752720/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752728/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752736/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752744/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752752/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752760/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752768/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752776/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752784/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752792/0, count: 1 Jan 30 16:24:12 Tower kernel: md: disk0 read error Jan 30 16:24:12 Tower kernel: handle_stripe read error: 1267752800/0, count: 1 Jan 30 16:24:12 Tower kernel: sd 3:0:0:0: [sdb] 2930277168 512-byte hardware sectors (1500302 MB) Jan 30 16:24:12 Tower kernel: sd 3:0:0:0: [sdb] Write Protect is off Jan 30 16:24:12 Tower kernel: sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jan 30 16:24:12 Tower kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 30 16:24:12 Tower kernel: sd 3:0:1:0: [sdc] 2930277168 512-byte hardware sectors (1500302 MB) Jan 30 16:24:12 Tower kernel: sd 3:0:1:0: [sdc] Write Protect is off Jan 30 16:24:12 Tower kernel: sd 3:0:1:0: [sdc] Mode Sense: 00 3a 00 00 Jan 30 16:24:12 Tower kernel: sd 3:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 30 16:24:12 Tower kernel: sd 3:0:0:0: [sdb] 2930277168 512-byte hardware sectors (1500302 MB) Jan 30 16:24:12 Tower kernel: sd 3:0:0:0: [sdb] Write Protect is off Jan 30 16:24:12 Tower kernel: sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jan 30 16:24:12 Tower kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 30 16:24:12 Tower kernel: sd 3:0:1:0: [sdc] 2930277168 512-byte hardware sectors (1500302 MB) Jan 30 16:24:12 Tower kernel: sd 3:0:1:0: [sdc] Write Protect is off Jan 30 16:24:12 Tower kernel: sd 3:0:1:0: [sdc] Mode Sense: 00 3a 00 00 Jan 30 16:24:12 Tower kernel: sd 3:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 30 17:25:55 Tower emhttp: shcmd (139): /usr/sbin/hdparm -y /dev/sdf >/dev/null Jan 30 17:49:55 Tower emhttp: shcmd (140): /usr/sbin/hdparm -y /dev/sdc >/dev/null Jan 30 17:49:55 Tower emhttp: shcmd (141): /usr/sbin/hdparm -y /dev/sdg >/dev/null Jan 30 17:49:55 Tower emhttp: shcmd (142): /usr/sbin/hdparm -y /dev/hdk >/dev/null Jan 30 17:49:56 Tower emhttp: shcmd (143): /usr/sbin/hdparm -y /dev/hdl >/dev/null Jan 30 19:45:57 Tower emhttp: shcmd (144): /usr/sbin/hdparm -y /dev/hde >/dev/null Jan 30 19:52:57 Tower emhttp: shcmd (145): /usr/sbin/hdparm -y /dev/hdl >/dev/null Jan 30 20:42:17 Tower dhcpcd[1126]: sending DHCP_REQUEST for 192.168.0.101 to 192.168.0.1 Jan 30 20:42:17 Tower dhcpcd[1126]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Jan 30 20:42:17 Tower dhcpcd[1126]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Jan 30 20:42:17 Tower dhcpcd[1126]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Jan 30 20:42:17 Tower dhcpcd[1126]: DHCP_ACK received from (192.168.0.1) Jan 30 21:15:44 Tower kernel: r8169: eth0: link up I've managed to get Unmenu up, so I have my syslog. Any idea what this means or how to fix it? Thanks, Russell
January 31, 200917 yr It looks like you have, unfortunately, developed a cluster of uncorrectable media errors on sdb, attached to ata3.00, probably the parity drive. I would use UnMenu to get a SMART report for that drive, and run a SMART long test on it, then get another SMART report for it. Depending on what you find out, you may be able to continue using this drive, assuming all of the bad sectors are remapped, and there aren't too many, and more do not continue to show up. Otherwise, you should RMA it. It appears you have 2 1.5TB drives on the same ata3 'channel'. That usually means that they are configured in some sort of IDE emulation mode (often 2 drives per channel). We generally recommend an AHCI or native SATA mode (only 1 drive per channel). An emulation mode is usually OK, except that one of its weaknesses is that resets go to the whole channel, to both drives, not just the one drive. In this case, when the hard reset is issued, it is occasionally causing problems (and extra delays) with the *other* drive, the good drive sdc on ata3.01, on the same ata3 'channel'.
January 31, 200917 yr Author Rob, Thanks for the quick - and thorough reply... Unfortunately, I'm not an unRaid guru, so I don't understand some of what you wrote. 1. I have no idea what the sdb attached to ata3.00 is. 2. I have run a simple report for the Parity drive: Statistics for /dev/sdb ST31500341AS_9VS030FN smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ST31500341AS Serial Number: 9VS030FN Firmware Version: CC1J User Capacity: 1,500,301,910,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sat Jan 31 17:58:30 2009 Local time zone must be set--see zic m SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 249) Self-test routine in progress... 90% of test remaining. Total time to complete Offline data collection: ( 617) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 109 099 006 Pre-fail Always - 227439761 3 Spin_Up_Time 0x0003 096 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 116 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 072 060 030 Pre-fail Always - 4314607553 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 683 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 69 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 082 082 000 Old_age Always - 18 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 106 190 Airflow_Temperature_Cel 0x0022 066 056 045 Old_age Always - 34 (Lifetime Min/Max 33/34) 194 Temperature_Celsius 0x0022 034 044 000 Old_age Always - 34 (0 23 0 0) 195 Hardware_ECC_Recovered 0x001a 043 030 000 Old_age Always - 227439761 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 227401338454620 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 621785230 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 2436578562 SMART Error Log Version: 1 ATA Error Count: 18 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 18 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:47:06.898 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:47:06.817 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:47:06.796 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:47:06.776 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:47:06.726 READ NATIVE MAX ADDRESS EXT Error 17 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:47:03.711 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:47:03.630 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:47:03.590 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:47:03.575 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:47:03.449 READ NATIVE MAX ADDRESS EXT Error 16 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:46:59.842 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:46:59.761 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:46:59.741 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:46:59.722 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:46:59.671 READ NATIVE MAX ADDRESS EXT Error 15 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:46:56.726 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:46:56.644 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:46:56.624 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:46:56.604 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:46:56.474 READ NATIVE MAX ADDRESS EXT Error 14 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:46:52.226 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:46:52.164 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:46:52.144 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:46:52.112 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:46:52.084 READ NATIVE MAX ADDRESS EXT SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Self-test routine in progress 90% 683 - # 2 Short offline Completed without error 00% 430 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. It sounds like you want me to run the Long Test, then another Short Test and post those results? I am working on it and will post when done. 3. I don't know what the channels are that you're referring to. I have a 1.5TB SATA plugged into every physical SATA port I've got (Unraid unofficial MB has six). Disk status Model / Serial No. Temperature Size Free Reads Writes Errors parity ata-ST31500341AS_9VS030FN 34°C 1,465,138,552 - 110,489 17,521 0 disk1 ata-ST31500341AS_9VS0AYB5 35°C 1,465,138,552 592,936,624 121,155 17,455 0 disk2 ata-ST31500341AS_9VS0DQQS 34°C 1,465,138,552 746,008,796 92,646 8 0 disk3 ata-ST31500341AS_9VS0ML12 34°C 1,465,138,552 1,247,249,764 95,570 34 0 disk4 ata-ST31500341AS_9VS0TQS0 32°C 1,465,138,552 1,455,733,820 92,408 8 0 disk5 ata-ST31500341AS_9VS0T89T 31°C 1,465,138,552 1,143,951,056 92,431 8 0 disk6 ata-WDC_WD2500JB-32EVA0_WD-WMAEH1071163 31°C 244,198,552 120,109,572 91,861 9 1 disk7 ata-WDC_WD1200JB-00DUA3_WD-WMACM1394461 * 117,220,792 115,160,548 91,358 8 0 disk8 ata-WDC_WD1600BB-00FTA0_WD-WCAES1307903 32°C 156,290,872 147,735,592 71,418 8 0 disk9 ata-WDC_WD1600BB-00FTA0_WD-WCAES1306899 30°C 156,290,872 150,983,928 71,423 8 0 disk10 ata-WDC_WD1600BB-00FTA0_WD-WMAEP3189051 30°C 156,290,872 18,835,908 92,588 8 0 Just for the heck of it, I've got 5 old IDE drives plugged in too. Is there a better way to configure this? (I can lose all the IDEs if that's suggested) Being the official MB, I suspect that it's capable of this AHCI thing you're talking about. How do I set that SAFELY? Thank you for all your help, Rob. Russell
January 31, 200917 yr 1. I have no idea what the sdb attached to ata3.00 is. I am almost positive you found it, when you started a Short test on the parity drive. It is usually best to attach the entire syslog, rather than just a piece. If I had access to the whole syslog, I could have confirmed that it was the parity drive, but the piece you included made it seem most likely that the parity drive (disk0) was /dev/sdb. It sounds like you want me to run the Long Test, then another Short Test and post those results? Getting a SMART report is not the same as running a SMART Short test, please see the Troubleshooting page, Obtaining a SMART report section. What would be better now is to grab another SMART report when the Short test finishes (should be done now), then run the Long test, then grab one more SMART report for comparison. The SMART report you included is rather troubling, rather unusual too, and I can't claim much expertise, would like to hear from others. There are NO reallocated or pending sectors recorded, yet it has 'reported' 18 UNC errors. The Reported_Uncorrect attribute VALUE has dropped 18, the RAW_VALUE has risen 18, and the ATA Error Count has recorded 18 errors, displaying the last 5 as UNC errors (Error: UNC at LBA = 0x0fffffff), which usually mean bad unreadable sectors. The value 0x0fffffff just seems too coincidental to me, is probably invalid. In addition to that, the Seek_Error_Rate (a PRE_FAIL item) is unusually high, High_Fly_Writes looks bad (VALUE = 001), and Head_Flying_Hours looks very wrong, all of which make me suspect you have mechanical problems with the drive. The SMART Long test should confirm whether there are real media errors or not, and the changes in the SMART reports may confirm increasing numbers in the mechanical parameters. It's early, and we should wait for your testing to finish, but my early opinion is that this drive may not be mechanically sound. 3. I don't know what the channels are that you're referring to. Ignore me, I should have tried to be clearer. When you have a chance, I would check the BIOS settings, and look for an AHCI setting for the onboard SATA ports. Your 5 IDE drives should be fine, although I could say better if we could see a full syslog.
January 31, 200917 yr Author Rob, Thanks for sticking with me on this one. Apparently Tom is out of file space - maybe he should get some unRaid hooked up to his webhost! - so I've posted my complete syslog on my own webserver: http://www.russellschutte.com/syslog-2009-01-31.txt I think my system is still running the long report. The following two lines have been in my SMART statistics for my parity drive for a few hours: Self-test execution status: ( 249) Self-test routine in progress... 90% of test remaining. I've already sent Seagate 20 bucks for an RMA box - so if we find something, I'm ready to go. I have six of these drives (1.5TB SATA) - How can I propery evaluate each without pestering you? (seems that all this testing may use up the reasonable life of the drives too!) I will try the BIOS setting when the parity is done rebuilding from this whole mess. (Non-responsive system - after several minutes I pulled the plug... only to now realize that it can go down for about five minutes and somehow come back alive!) Thanks again for your help, Russell
February 1, 200917 yr Kernel command line: initrd=bzroot acpi=off BOOT_IMAGE=bzimage Since I believe you said that you had one of the 'official' motherboards, you should not need to turn off ACPI. Is there a reason you need or want it off? Jan 31 19:56:33 Tower kernel: hdk: WDC WD1600BB-00FTA0, ATA DISK drive Jan 31 19:56:33 Tower kernel: hdl: WDC WD1600BB-00FTA0, ATA DISK drive Jan 31 19:56:33 Tower kernel: hdk: host side 80-wire cable detection failed, limiting max speed to UDMA33 Jan 31 19:56:33 Tower kernel: hdk: UDMA/33 mode selected Jan 31 19:56:33 Tower kernel: hdl: host side 80-wire cable detection failed, limiting max speed to UDMA33 Jan 31 19:56:33 Tower kernel: hdl: UDMA/33 mode selected Looks like the cable with the 2 WD 160GB drives is bad, or only a 40 wire cable, should be a flat 80 wire cable. The current cable will work, but performance with these drives will be bad. And parity checks can not go faster than the slowest drive. Jan 31 22:46:56 Tower login[1398]: ROOT LOGIN on `tty1' Jan 31 22:47:49 Tower kernel: ------------[ cut here ]------------ Jan 31 22:47:49 Tower kernel: WARNING: at net/sched/sch_generic.c:219 dev_watchdog+0xf0/0x16d() Jan 31 22:47:49 Tower kernel: NETDEV WATCHDOG: eth0 (r8169): transmit timed out Jan 31 22:47:49 Tower kernel: Modules linked in: md_mod ide_disk ata_piix sata_sil libata pdc202xx_new ide_core r8169 Jan 31 22:47:49 Tower kernel: Pid: 0, comm: swapper Not tainted 2.6.27.7-unRAID #3 Jan 31 22:47:49 Tower kernel: [] warn_slowpath+0x61/0x86 Jan 31 22:47:49 Tower kernel: [] lock_timer_base+0x19/0x35 [ more snipped ] ... Very shortly after you logged in, this happened. This is either the second or third time I have seen this, from the recent kernel, and I can't pretend to know what is so important about a 'transmit timed out' error, that it needs a '[ cut here ]', a current module listing, and a full execution trace. There is certainly nothing abnormal about a transmission timeout in a communications link, undesirable perhaps, but not noteworthy from a debug standpoint. I would ignore it, unless it keeps happening. I have six of these drives (1.5TB SATA) - How can I propery evaluate each without pestering you? That's what the UnMENU MyMain Smart view is great for, check it out. It will give you a good overview of the SMART status of each of your drives, all on one screen. Then add the SmartHistory addon, to monitor changes in SMART parameters. I think my system is still running the long report. The following two lines have been in my SMART statistics for my parity drive for a few hours: Self-test execution status: ( 249) Self-test routine in progress... 90% of test remaining. It doesn't look like it is getting refreshed. You have to request another SMART report to check the current status.
February 1, 200917 yr Author Since I believe you said that you had one of the 'official' motherboards, you should not need to turn off ACPI. Is there a reason you need or want it off? Of course there's a reason I turned it off... I have no idea what ACPI is... but I couldn't boot when it was on: http://lime-technology.com/forum/index.php?topic=2917.30 Looks like the cable with the 2 WD 160GB drives is bad, or only a 40 wire cable, should be a flat 80 wire cable. The current cable will work, but performance with these drives will be bad. And parity checks can not go faster than the slowest drive. You are right, I have 40 wire cables - that's all I have laying around. But if it'll speed up my parity checks I should probably go fetch some 80 wire cables. Will do. Very shortly after you logged in, this happened. This is either the second or third time I have seen this, from the recent kernel, and I can't pretend to know what is so important about a 'transmit timed out' error, that it needs a '[ cut here ]', a current module listing, and a full execution trace. There is certainly nothing abnormal about a transmission timeout in a communications link, undesirable perhaps, but not noteworthy from a debug standpoint. I would ignore it, unless it keeps happening. This is WAY over my head... I don't even know if you're talking about network or internal communication. I can't think of much unique in my environment - except that I have my Router configured to only allow specific MAC addresses on the network. Can't imagine this would be related... but it's the only unique thing I can think of. (Network specifics: Comcast Cable Router, DLink DIR-655 Wireless Router (10/100/1000), two PCs, two laptops, my UnRaid box, a Linksys 10/100 for my printers - three HP Color LaserJets, an HP InkJet and an Epson InkJet, a 2TB TeraStation and a few 500 GB SATA USB drives). It doesn't look like it is getting refreshed. You have to request another SMART report to check the current status. Maybe I don't know how to do this... I've gone to the unMenu Disk Mgmt "tab", selected the drive and clicked "SMART Statistics" button. Even getting SMART Statistics for another drive and then repeating the process for the Parity Drive, I get the same results. Continued thanks and worship, Russell
February 1, 200917 yr Read the troubleshooting page. See my sig for a link. You do not want to use 40 wire cables. They are only for CD ROMS. The troubleshooting page explains this and has a link to a picture of each. ACPI has to do with power management. I always leave it off on a desktop. AHCI (easily confused with ACPI because the acronym is similar) is a mode of communicating with a SATA drive, and is normally preferred to IDE emulation.
February 1, 200917 yr Author Ooops... I gave the wrong thread... I meant this one: http://lime-technology.com/forum/index.php?topic=2993.0 How should I have ACPI configured? Disable in a file like I have now? Disabled in BIOS? Or should it be ON? (and then how do I boot?) I presume my AHCI settings are fine? I appreciate the cable photos... I think I might have some of those around... Will make the swap next time I power down. Thanks, Russell
February 1, 200917 yr Author Hi Rob (and others), I'm still trying to keep my machine from this temporary lockup scenario. (Hasn't happened yet today - no idea why/when it will happen again). 1. Should I turn off ACPI in the BIOS? If it should be on and I should take the off command out of the config file, then how will I boot? (Thread with issue: http://lime-technology.com/forum/index.php?topic=2993.0) 2. I'm still not sure what any of this means: Very shortly after you logged in, this happened. This is either the second or third time I have seen this, from the recent kernel, and I can't pretend to know what is so important about a 'transmit timed out' error, that it needs a '[ cut here ]', a current module listing, and a full execution trace. There is certainly nothing abnormal about a transmission timeout in a communications link, undesirable perhaps, but not noteworthy from a debug standpoint. I would ignore it, unless it keeps happening. 3. Looks like my parity drive has finsihed its test: Statistics for /dev/sdb ST31500341AS_9VS030FN smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ST31500341AS Serial Number: 9VS030FN Firmware Version: CC1J User Capacity: 1,500,301,910,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sun Feb 1 17:04:44 2009 Local time zone must be set--see zic m SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 617) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 114 099 006 Pre-fail Always - 61037472 3 Spin_Up_Time 0x0003 097 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 117 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 072 060 030 Pre-fail Always - 4314836576 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 706 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 70 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 082 082 000 Old_age Always - 18 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 106 190 Airflow_Temperature_Cel 0x0022 069 056 045 Old_age Always - 31 (Lifetime Min/Max 30/35) 194 Temperature_Celsius 0x0022 031 044 000 Old_age Always - 31 (0 23 0 0) 195 Hardware_ECC_Recovered 0x001a 042 030 000 Old_age Always - 61037472 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 138791868170867 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 688106022 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 380438803 SMART Error Log Version: 1 ATA Error Count: 18 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 18 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:47:06.898 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:47:06.817 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:47:06.796 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:47:06.776 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:47:06.726 READ NATIVE MAX ADDRESS EXT Error 17 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:47:03.711 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:47:03.630 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:47:03.590 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:47:03.575 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:47:03.449 READ NATIVE MAX ADDRESS EXT Error 16 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:46:59.842 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:46:59.761 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:46:59.741 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:46:59.722 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:46:59.671 READ NATIVE MAX ADDRESS EXT Error 15 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:46:56.726 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:46:56.644 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:46:56.624 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:46:56.604 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:46:56.474 READ NATIVE MAX ADDRESS EXT Error 14 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:46:52.226 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:46:52.164 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:46:52.144 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:46:52.112 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:46:52.084 READ NATIVE MAX ADDRESS EXT SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 697 - # 2 Extended offline Aborted by host 90% 691 - # 3 Extended offline Aborted by host 90% 691 - # 4 Extended offline Aborted by host 90% 684 - # 5 Short offline Aborted by host 10% 684 - # 6 Short offline Completed without error 00% 430 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. Thank you for the heads up on the UnMenu MyMain SMART view... I had not noticed the different views on the UnMenu screen. I do have some RED stuff, which I assume is bad? I guess I really need a simple "Hey dumby, this drive is about to go kaput!" Are there any such parameters? Here's what I've got: parity reported_uncorrect=18 high_fly_writes=106 head_flying_hours=5.63199e+13 attribute_241=710947365 attribute_242=580524298 ata_error_count=18 disk1 high_fly_writes=26 head_flying_hours=1.99742e+14 attribute_241=727920893 attribute_242=3.80085e+09 disk2 reallocated_sector_ct=1 high_fly_writes=29 head_flying_hours=9.48372e+13 attribute_241=2124379804 attribute_242=3.80353e+09 disk3 spin_retry_count=1 high_fly_writes=7 head_flying_hours=1.83825e+13 attribute_241=422153528 attribute_242=3.10692e+09 disk4 high_fly_writes=7 head_flying_hours=1.64815e+14 attribute_241=2.94021e+09 attribute_242=4.04113e+09 disk5 high_fly_writes=6 head_flying_hours=5.01137e+13 attribute_241=3.83558e+09 attribute_242=3.44896e+09 disk6 reallocated_sector_ct=16 reallocated_event_count=15 current_pending_sector=1 udma_crc_error_count=78 multi_zone_error_rate=51 ata_error_count=4 disk7 nothing disk8 nothing disk9 reallocated_sector_ct=13 reallocated_event_count=13 disk10 ata_error_count=2 Does it look like I should RMA/replace my parity drive? How about the others? [i tried to do my own homework. I found nothing I could understand for "ata_error_count" on google. From what I understand the "reallocated_sector_ct" reflects bad areas of the drive - fewer is better - but what's acceptable? Seems to me that depending on the size of the drive, a larger number of bad sectors would be acceptable?] I'm learning more, begrudgingly, everyday - I've now used Putty to get my Syslog when unMenu wouldn't respond (new thread: http://lime-technology.com/forum/index.php?topic=3246.0 Thanks again, Russell
February 2, 200917 yr 3. Looks like my parity drive has finsihed its test: Statistics for /dev/sdb ST31500341AS_9VS030FN smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ST31500341AS Serial Number: 9VS030FN Firmware Version: CC1J User Capacity: 1,500,301,910,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sun Feb 1 17:04:44 2009 Local time zone must be set--see zic m SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 617) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 114 099 006 Pre-fail Always - 61037472 3 Spin_Up_Time 0x0003 097 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 117 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 072 060 030 Pre-fail Always - 4314836576 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 706 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 70 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 082 082 000 Old_age Always - 18 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 106 190 Airflow_Temperature_Cel 0x0022 069 056 045 Old_age Always - 31 (Lifetime Min/Max 30/35) 194 Temperature_Celsius 0x0022 031 044 000 Old_age Always - 31 (0 23 0 0) 195 Hardware_ECC_Recovered 0x001a 042 030 000 Old_age Always - 61037472 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 138791868170867 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 688106022 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 380438803 SMART Error Log Version: 1 ATA Error Count: 18 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 18 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:47:06.898 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:47:06.817 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:47:06.796 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:47:06.776 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:47:06.726 READ NATIVE MAX ADDRESS EXT Error 17 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:47:03.711 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:47:03.630 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:47:03.590 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:47:03.575 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:47:03.449 READ NATIVE MAX ADDRESS EXT Error 16 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:46:59.842 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:46:59.761 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:46:59.741 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:46:59.722 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:46:59.671 READ NATIVE MAX ADDRESS EXT Error 15 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:46:56.726 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:46:56.644 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:46:56.624 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:46:56.604 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:46:56.474 READ NATIVE MAX ADDRESS EXT Error 14 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:46:52.226 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:46:52.164 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:46:52.144 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:46:52.112 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:46:52.084 READ NATIVE MAX ADDRESS EXT SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 697 - # 2 Extended offline Aborted by host 90% 691 - # 3 Extended offline Aborted by host 90% 691 - # 4 Extended offline Aborted by host 90% 684 - # 5 Short offline Aborted by host 10% 684 - # 6 Short offline Completed without error 00% 430 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. It looks like you ran a couple of short tests on the drive successfully, but that a couple of long tests didn't complete (stopped at 90%). Not sure what happened there. Drive "errors" are not always an indication of a bad drive. A bad or loose cable can cause requests from the computer to get corrupted. So if the computer is asking for sector 7, and the command is corrupted and it thinks the computer is asking for a huge sector number that doesn't even exist, the drive is going to issue an error. It looks like that may have been what happened on this drive with its 18 errors. You have 106 high fly writes. I am not sure how serious these are. My understanding is that there is a detection if the heads get a little too high, and that once detected the drive stops the operation so that the head doesn't get "too high" and cause a real problem. I would monitor and read about this, but not necessarily be overly concerned. There is nothing here that is overly alarming to me. I would double check the cable and plug in securely if it is loose. If it seem secure I would replace it with a fresh cable. Thank you for the heads up on the UnMenu MyMain SMART view... I had not noticed the different views on the UnMenu screen. I do have some RED stuff, which I assume is bad? I guess I really need a simple "Hey dumby, this drive is about to go kaput!" Are there any such parameters? Here's what I've got: parity reported_uncorrect=18 high_fly_writes=106 head_flying_hours=5.63199e+13 attribute_241=710947365 attribute_242=580524298 ata_error_count=18 disk1 high_fly_writes=26 head_flying_hours=1.99742e+14 attribute_241=727920893 attribute_242=3.80085e+09 disk2 reallocated_sector_ct=1 high_fly_writes=29 head_flying_hours=9.48372e+13 attribute_241=2124379804 attribute_242=3.80353e+09 disk3 spin_retry_count=1 high_fly_writes=7 head_flying_hours=1.83825e+13 attribute_241=422153528 attribute_242=3.10692e+09 disk4 high_fly_writes=7 head_flying_hours=1.64815e+14 attribute_241=2.94021e+09 attribute_242=4.04113e+09 disk5 high_fly_writes=6 head_flying_hours=5.01137e+13 attribute_241=3.83558e+09 attribute_242=3.44896e+09 disk6 reallocated_sector_ct=16 reallocated_event_count=15 current_pending_sector=1 udma_crc_error_count=78 multi_zone_error_rate=51 ata_error_count=4 disk7 nothing disk8 nothing disk9 reallocated_sector_ct=13 reallocated_event_count=13 disk10 ata_error_count=2 Reallocated sectors can be an indication of real problems. The number of them is not as important as whether the number is increasing. It is not ususual for a drive to have 1 or 2, maybe even up to 100 or more reallocated sectors very early in its lifetime, and if that number doesn't change, the drive is likely fine. But if every time you do a parity check your reallocated sector counts are increasing, even if only by 1 or 2 sectors, than it is likely that the drive is on a downward spiral. Now if you had 1000 reallocated sectors I'd be nervous, but I don't see anything to worry about here. I already described high fly writes. I have a few of these as well. Your parity drive at 106 is on the high side of what I've seen, but again nothing to be overly concerned about IMO. ata_error_count is a made up attribute name, but represents the total number of errors found on the drive. As described above, these errors frequently have more to do with bad cabling than actual drive problems. But you need to look at the specific errors on the disk to know for sure. Of all of your drives, disk6 is the most worrisome. Pending sectors means bad sectors that have been found but not remapped yet. UnRAID should force the issue and cause these to be remapped if parity is enabled. It could be that running a parity check would fix this. The multi-zone-error-count at 51 means that you've had errors writing sectors, and the udma-error-count means that you are getting CRC errors. I'd start by replacing its cable, but continue to watch this drive carefully. If these numbers rise, post back. Does it look like I should RMA/replace my parity drive? How about the others? [i tried to do my own homework. I found nothing I could understand for "ata_error_count" on google. From what I understand the "reallocated_sector_ct" reflects bad areas of the drive - fewer is better - but what's acceptable? Seems to me that depending on the size of the drive, a larger number of bad sectors would be acceptable?] I'm learning more, begrudgingly, everyday - I've now used Putty to get my Syslog when unMenu wouldn't respond (new thread: http://lime-technology.com/forum/index.php?topic=3246.0 Thanks again, Russell It is hard to look at these attributes and make the kind of instant judgement you are requesting. I've tried to give you some insights of things to look at and common causes. Also, at the bottom of the smart view, there is information on each of the attributes that is very helpful. Many attributes, especially those that have gargantuan values, are not intelligible and don't really tell us anything. Hope this helps. Feel free to post back with more questions. I'd recommend running a full smart report on disk6 and posting it here.
February 2, 200917 yr Could the following Aborted by host operations be due to emhttp forcing a spin down? What is the current spin down time? It may need to be temporarily adjusted to 3 hours. Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 697 - # 2 Extended offline Aborted by host 90% 691 - # 3 Extended offline Aborted by host 90% 691 - # 4 Extended offline Aborted by host 90% 684 - # 5 Short offline Aborted by host 10% 684 - # 6 Short offline Completed without error 00% 430 -
February 2, 200917 yr Besides the possibility of drive errors or bad drives, it's been documented that the Seagate 1.5T drives tend to become non-responsive for short periods of time when serving data. Apparently, all the 7200.11 drives can but the 1.5T size is the most prone to doing it. If these drives are used in a RAID array the hang is long enough for the RAID controller to dump the drive and flag it as being failed. In a single file system per drive application it's really just an annoyance. I've seen some SATA link resets in my syslog on my 1T drives and I believe it's the same issue. I've never had a hang-up of a minute or 2 but have seen maybe 5 seconds. Peter
February 3, 200917 yr Sorry, tied up elsewhere, not very good at staying on top of things. But you have had excellent help from others. 1. Should I turn off ACPI in the BIOS? If it should be on and I should take the off command out of the config file, then how will I boot? I wasn't aware of your need for acpi=off, that's why I asked. Continue to boot with ACPI off, but check now and then for a BIOS upgrade for your motherboard. If you do upgrade the BIOS, then try again to boot with ACPI on. It's not that big a deal, nothing to worry about, but ACPI is a Good Thing, can be very useful for power management, *IF* it is working. It's like buying a car with a sunroof, then discovering it won't open. Everything will work fine, but you won't be able to take advantage of something you actually paid for, *if* you decide you do want to use it. Many people with sunroofs don't bother ever using them, and most users who have a working ACPI don't knowingly use it. You might mention the exact motherboard model and revision, and the exact BIOS version, so others with that board can compare with theirs, and perhaps comment. I *think* an ACPI problem is typically fixed by upgrading to a newer BIOS. 2. I'm still not sure what any of this means: Very shortly after you logged in, this happened. This is either the second or third time I have seen this, from the recent kernel, and I can't pretend to know what is so important about a 'transmit timed out' error, that it needs a '[ cut here ]', a current module listing, and a full execution trace. There is certainly nothing abnormal about a transmission timeout in a communications link, undesirable perhaps, but not noteworthy from a debug standpoint. I would ignore it, unless it keeps happening. I tend to want to provide more info, rather than less, in case you are interested in more. But as I said, you can ignore this, unless it continues happening. It didn't seem to cause any problems, but I couldn't help noting it, as a very recent and unusual series of lines. Just ignore it for now. Probably the next kernel or driver release will handle it better. I guess I really need a simple "Hey dumby, this drive is about to go kaput!" Are there any such parameters? Nope! As Brian said, this is a VERY inexact and young science, and we are all learning, building collective experience with these drives. There are lots of expert arguments out there about the relative importance of the different SMART attributes, and their changes. I think your occasional lockups are the only real problem you have. The SMART numbers just mean that you will want to monitor a couple of your drives, and Brian has dealt well with that. I would still like to see a SMART long test of the Parity drive (and Disk 6), but if you start one, disable spin down in the unRAID Settings tab first (just during these tests). I think WeeboTech had a brilliant idea about those 90% aborts.
February 3, 200917 yr Could the following Aborted by host operations be due to emhttp forcing a spin down? What is the current spin down time? It may need to be temporarily adjusted to 3 hours. Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 697 - # 2 Extended offline Aborted by host 90% 691 - # 3 Extended offline Aborted by host 90% 691 - # 4 Extended offline Aborted by host 90% 684 - # 5 Short offline Aborted by host 10% 684 - # 6 Short offline Completed without error 00% 430 - Brilliant idea! Should be tested. If it proves to be true, and it sure sounds plausible, perhaps Joe and Brian should add appropriate warnings around the start of SMART long tests, in UnMENU and MyMain. I would suggest temporarily disabling spin down, or increasing it to 5 hours on terabyte drives, 3 hours may not be enough?
February 3, 200917 yr Author Just for the record.... You guys absolutely ROCK! (Not since the early ColdFusion 3.5/4.0 days have I seen such an active peer-to-peer support group.) BJP999, thanks for the education in these drives... I've got all new cables on my drives, but the IDEs are leftover old drives - #6 was previously a "roadie" USB drive. I've just done a parity check, so I will rerun the SMART on #6 and see if it still has UnMapped Sectors. RobJ had mentioned a SMART History tool - but I've not been able to investigate that yet... Sounds like a printout of the SMART results should be stored for later comparison. Weebo, the drives have the default spindown set - I think it's 1 hour. Also, if I read that correctly, doesn't it say 90% REMAINING... not 90% complete? Is lionelhutz on to something? I know there's been 1.5TB issues (bastards!)... but these aren't really running in a RAID environment. When it happens, I think I lose all my drives - not just the one that may have delayed - or even the pair on the same controller... I think I lose it all. If it's important to know this, I can keep a sharper eye on it. RobJ, you hit it on the head... I didn't even know I might have drive problems... my problem is the lockups - which last for MINUTES before UnRaid is responsive again. Several minutes - five, six, seven even. Disappointingly, PhotoShop won't wait that long - and I have 10-15GB single files - they take a considerable amount of time to save as it is! I have always worked directly on my storage solution (previously a TeraStation) because I appreciate the immediate redundancy... But maybe I need to work on my files directly on a local hard disk and then copy them to my UnRaid. Any other ideas how to correct the lockup issue? Does this sound like the 1.5TB Seagate problem? Thanks, Russell
February 3, 200917 yr I obviously can't diagnose your issue, but I think it is likely that your problems are related to a marginal cable. Read about my nightmare that turned out to be a flakey port on the motherboard, which needed a locking cable. Prior to the experience described in the post I had all kinds of hangs and other problems. It might be something else, but this would be my first guess. Cleaning up your install and experimenting with replacing cables is cheap and a good thing to do even if it turns out not to be the problem. http://lime-technology.com/forum/index.php?topic=3070.0 Good luck!
February 3, 200917 yr Author I can confirm that when I have this lockup issue - none of my drives are available, the UnRaid web interface is not available, hitting \\tower fails, and Telnet (Putty) connections fail as well... This lockup lasts for MANY minutes - about 15 minutes tonight! I would really appreciate it if we could lock this problem down. I don't have much hair left to pull out. Here's tonight's SysLog: http://www.russellschutte.com/syslog-2009-02-03.txt Problem happened vaguely around 10:32PM (7:32 in the log - for whatever reason, the time change doesn't stick). Not sure if it is related, but my system (from the UnRaid web interface) also will not shut down or reboot - choosing either seems to stop all the drives after a few minutes and I just power it off). Thanks so much for reviewing this mess. Russell
February 3, 200917 yr No, the Segate problem documented would not cause a 15 minute hang. It sounds like you are losing the computer off the network. Maybe we should back-up and re-think this a little. The only thing of significance around 7:32pm (is this Feb 2, 19:30 then???) is that the IP address lease was renewed at 19:25. It doesn't seem to be a hardware issue. Maybe it's a network setup issue so I would check the following. Make sure you have the same "Workgroup" name in all the computers and unRAID and the router. Make sure another computer is not using the IP address 192.168.0.104. Make sure the submask is 255.255.255.0 Peter
February 3, 200917 yr I can confirm that when I have this lockup issue - none of my drives are available, the UnRaid web interface is not available, hitting \\tower fails, and Telnet (Putty) connections fail as well... This lockup lasts for MANY minutes - about 15 minutes tonight! I would really appreciate it if we could lock this problem down. I don't have much hair left to pull out. Here's tonight's SysLog: http://www.russellschutte.com/syslog-2009-02-03.txt Problem happened vaguely around 10:32PM (7:32 in the log - for whatever reason, the time change doesn't stick). Not sure if it is related, but my system (from the UnRaid web interface) also will not shut down or reboot - choosing either seems to stop all the drives after a few minutes and I just power it off). Thanks so much for reviewing this mess. Russell This does not feel like a drive issue. Drive issues usually have tell-tale signs in the syslog. Although there are some issues in the syslog from the time the system booted on Feb 1, there are no other drive reported issues. This leads me to believe that the linux drivers dealt with the issues. When you have one of these "outages", are you able to go to the unRAID console and access the telnet session from there? I expect the answer is "yes". The final line in your syslog indicates that ntpd cannot find a server. That is indicative of a networking issue. That's what I think is happening here. You also had some sort of network event 2 hours earlier, but it seems to have overcome that problem (ntpd is able to find a server about a minute later). It is interesting that only a couple minutes before the ntpd "no servers reachable" message, the syslog announced that eth0 link is up. This is odd, because there is no indication that the link went down. Are you having any other networking issues? If this happens again (after trying to access the server from the console), try unplugging the power from your router and switch (if you have a separate switch) for about 30 seconds and see if the problem goes away. I am suspecting something like this is the problem. Another possibility is the gigabit lan chip/card in your unRAID server is either failing or the Linux drivers are not 100% working with it. Still another possibility is that some power saving mode is turning off the LAN port (I have never seen this happen, but it popped in my head so thought I would mention it). RobJ is much more experienced with these logs than I. Maybe he will have other thoughts after reviewing.
February 3, 200917 yr Author Lionel, I will check those things when I get home from work today... it's possible that I have a device with a static IP (a printer) in that range... not good odds, but possible. The "workgroup" part, I've NEVER seen a place to put that into either my router or my UnRaid box. I'll do some searching. BJP999, I'm not sure what you mean by "at the UnRaid console"... I have not connected a keyboard and monitor yet... but I cannot connect to it with Putty... So maybe a network problem is likely? Or a pretty solid lockup. I'll hook up a keyboard and monitor and see what I can find out tonight if it happens again. I'm not having any other network issues - my TeraStation is always accessible... each computer can hit the Internet just fine... I have a lot of printers (five), so I'm not sure I can print to each of them... but I can try that too. Thank you guys for helping on this one... This is a tough one for a newbie like me (about one month of UnRaid running). Russell
February 3, 200917 yr Missing workgroup is a good thought. I would not think it would cause intermittent problems, but maybe. To change it from unRAID, go to the tower web gui (normally http://tower). Go to the "Settings" page. It is the 3rd item on the settings page, very easy to miss . Duplicate IPs can definitely cause problems. Good thing to check. Again, not sure if you'd get intermittent results, but maybe. The "console" means to use the directly attached keyboard and monitor on the unRAID server itself. It seems you are running headless, which makes this a little harder, but I recommend you hook this up. If the console is still active when the system appears unresponsive on the network, it pretty much isolates this as a networking issue. If the whole system is freezing up, that tend to indicate a drive is dropping (either the data cable is loose, the power cable is loose, or a drive is failing). Hopefully it is a networking thing.
February 3, 200917 yr I'm thinking it's an IP conflict. Here's a good thread. http://lime-technology.com/forum/index.php?topic=1820.0 Go to the last page and last post to read the solution first. It looks like a conflicting IP does not show up in the syslogs. One other thing is to try some other name besides "workgroup" as the workgroup setting. I read a thread where a network with an Xbox was having problems while using "workgroup". Peter
February 6, 200917 yr Author Hi Guys, I haven't gotten to the network part of things - but I do have my two SMART reports after running a LONG test: Parity Drive: Statistics for /dev/sdb ST31500341AS_9VS030FN smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ST31500341AS Serial Number: 9VS030FN Firmware Version: CC1J User Capacity: 1,500,301,910,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Fri Feb 6 16:12:43 2009 Local time zone must be set--see zic m SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 617) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 116 099 006 Pre-fail Always - 106970627 3 Spin_Up_Time 0x0003 094 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 126 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 072 060 030 Pre-fail Always - 4315389148 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 826 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 72 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 082 082 000 Old_age Always - 18 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 107 190 Airflow_Temperature_Cel 0x0022 068 056 045 Old_age Always - 32 (Lifetime Min/Max 23/35) 194 Temperature_Celsius 0x0022 032 044 000 Old_age Always - 32 (0 23 0 0) 195 Hardware_ECC_Recovered 0x001a 055 030 000 Old_age Always - 106970627 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 62680752718557 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1013416461 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3676624574 SMART Error Log Version: 1 ATA Error Count: 18 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 18 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:47:06.898 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:47:06.817 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:47:06.796 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:47:06.776 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:47:06.726 READ NATIVE MAX ADDRESS EXT Error 17 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:47:03.711 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:47:03.630 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:47:03.590 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:47:03.575 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:47:03.449 READ NATIVE MAX ADDRESS EXT Error 16 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:46:59.842 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:46:59.761 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:46:59.741 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:46:59.722 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:46:59.671 READ NATIVE MAX ADDRESS EXT Error 15 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:46:56.726 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:46:56.644 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:46:56.624 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:46:56.604 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:46:56.474 READ NATIVE MAX ADDRESS EXT Error 14 occurred at disk power-on lifetime: 666 hours (27 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 00 ff ff ff ef 00 9d+19:46:52.226 READ DMA EXT 27 00 00 00 00 00 e0 00 9d+19:46:52.164 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 9d+19:46:52.144 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 9d+19:46:52.112 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 9d+19:46:52.084 READ NATIVE MAX ADDRESS EXT SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 800 - # 2 Extended offline Completed without error 00% 796 - # 3 Short offline Completed without error 00% 697 - # 4 Extended offline Aborted by host 90% 691 - # 5 Extended offline Aborted by host 90% 691 - # 6 Extended offline Aborted by host 90% 684 - # 7 Short offline Aborted by host 10% 684 - # 8 Short offline Completed without error 00% 430 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
February 6, 200917 yr Author And Drive SIX: Statistics for /dev/hdi WDC_WD2500JB-32EVA0_WD-WMAEH1071163 smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: Western Digital Caviar SE family Device Model: WDC WD2500JB-32EVA0 Serial Number: WD-WMAEH1071163 Firmware Version: 15.05R15 User Capacity: 250,059,350,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 6 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Fri Feb 6 16:13:18 2009 Local time zone must be set--see zic m SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (7599) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. No General Purpose Logging support. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 95) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 200 173 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0007 115 107 021 Pre-fail Always - 4775 4 Start_Stop_Count 0x0032 100 100 040 Old_age Always - 325 5 Reallocated_Sector_Ct 0x0033 198 198 140 Pre-fail Always - 17 7 Seek_Error_Rate 0x000b 200 200 051 Pre-fail Always - 0 9 Power_On_Hours 0x0032 082 082 000 Old_age Always - 13278 10 Spin_Retry_Count 0x0013 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0013 100 100 051 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 274 194 Temperature_Celsius 0x0022 124 253 000 Old_age Always - 26 196 Reallocated_Event_Count 0x0032 184 184 000 Old_age Always - 16 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0012 200 200 000 Old_age Always - 0 199 UDMA_CRC_Error_Count 0x000a 200 253 000 Old_age Always - 78 200 Multi_Zone_Error_Rate 0x0009 198 155 051 Pre-fail Offline - 77 SMART Error Log Version: 1 ATA Error Count: 4 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 4 occurred at disk power-on lifetime: 116 hours (4 days + 20 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 da ed 32 e0 Error: Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 00 00 25 00 00 00 01 00 00:06:19.200 NOP [Abort queued commands] 00 00 32 00 00 2f e9 00 00:06:19.200 NOP [Abort queued commands] 00 00 25 00 00 00 03 00 00:06:19.200 NOP [Abort queued commands] 00 00 32 00 00 2f e2 00 00:06:19.200 NOP [Abort queued commands] 00 00 25 00 00 00 01 00 00:06:19.200 NOP [Abort queued commands] Error 3 occurred at disk power-on lifetime: 979 hours (40 days + 19 hours) When the command that caused the error occurred, the device was doing SMART Offline or Self-test. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 da ed 32 e0 Error: Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 00 00 25 00 00 00 03 00 01:40:34.600 NOP [Abort queued commands] 00 00 32 00 00 bf e7 00 01:40:34.600 NOP [Abort queued commands] 00 00 25 00 00 00 01 00 01:40:34.600 NOP [Abort queued commands] 00 00 32 00 00 bf de 00 01:40:34.600 NOP [Abort queued commands] 00 00 25 00 00 00 04 00 01:40:34.600 NOP [Abort queued commands] Error 2 occurred at disk power-on lifetime: 375 hours (15 days + 15 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 80 69 c3 ea e0 Error: Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 00 00 40 00 00 80 00 00 00:09:50.900 NOP [Abort queued commands] 00 00 40 00 00 80 00 00 00:09:50.900 NOP [Abort queued commands] 00 00 ea 00 00 3f c1 00 00:09:50.900 NOP [Abort queued commands] 00 00 40 00 00 80 00 00 00:09:50.900 NOP [Abort queued commands] 00 00 ea 00 00 bf bf 00 00:09:50.900 NOP [Abort queued commands] Error 1 occurred at disk power-on lifetime: 199 hours (8 days + 7 hours) When the command that caused the error occurred, the device was doing SMART Offline or Self-test. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 80 17 fa 47 e0 Error: Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 00 00 25 00 00 80 00 00 5d+06:46:18.850 NOP [Abort queued commands] 1a 00 47 00 00 d5 f8 00 5d+06:46:18.850 RECALIBRATE [RET-4] 00 00 25 00 00 80 00 00 5d+06:46:18.850 NOP [Abort queued commands] 1a 00 47 00 00 55 f7 00 5d+06:46:18.850 RECALIBRATE [RET-4] 00 00 25 00 00 80 00 00 5d+06:46:18.850 NOP [Abort queued commands] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 156 - # 2 Extended offline Completed without error 00% 147 - # 3 Short offline Completed without error 00% 132 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. I've also looked into the SMARTHistory Addon (http://lime-technology.com/wiki/index.php?title=UnRAID_Add_Ons#SmartHistory). Unfortunately, I'm afraid this installation is WAY over my head - rated at "moderate." Any ideas where I can get myself up to speed? Thank you guys for your ongoing support... I'll work on the network things this weekend and report back so anyone with similar issues can reference this forum. LionelHutz, the thread you provided (http://lime-technology.com/forum/index.php?topic=1820.0) sounds basically identical to the issues I've been having... I suspect I must have a static IP printer here on my network and somehow DHCP goes ahead and gives that address to my UnRaid box sometimes? I have five network printers - and a TeraStation which might also be static - (yes, just a home configuration), I'll investigate. I haven't had the problem now in a few days, making it hard to troubleshoot some of these solutions - but I'll work it hard this weekend and have some results. Thanks, Russell
Archived
This topic is now archived and is closed to further replies.