JonathanM

User Customizations · June 21, 2013

Not today, I've got a very busy afternoon/evening.

Darn, there goes your streak of sub 1 hour response times.

June 14, 2013

Config, categories, folder/path.

June 14, 2013

Pretty sure the shots you posted have nothing to do with getting files moved after they are finished. Sickbeard is the one doing the moving, and it only moves tv shows that are in your list in Sickbeard, so it's to be expected that movies stay.

April 12, 2013

I don't want to send my Dropbox metadata to StorageMadeEasy.

So basically you create an account and add all of the storage resources you wish to make accessible from the interface (even drobbox accounts) when you install the client on your computer

I'm trying to be diplomatic here, but it really sounds like xlordnashx is a salesman from this sme place. He doesn't even listen to the valid point made here, in that sme would have to have all your account details from your other existing accounts that you want to use. Sounds like a security nightmare waiting to happen.

I'm genuinely curious here, xlordnashx, what unraid version are you currently running?

February 25, 2013

There's loads of companies that'll make custom items for you, just buy one from there. Obviously it won't go directly to Tom (Limetech's owner(?)) but least you'll have one.

If you want the profits to go to tom, I think the better thing to do would just to be to donate to him & then buy the badge elsewhere.

If you use the official lime logo and unraid text, you may be violating trademark. Not saying you can't get them made, just that it's not nice, and may not be legal where you live. You really need to get Tom's permission before doing it.

User Customizations · December 14, 2012

I was hoping there was some preclear script command to clear enough of the disk to fool unraid into thinking it is empty and not do another full preclear on the disk.

If you did add the preclear signature without clearing the disk, you would definitely corrupt any subsequent disk rebuilds until a full correcting parity check was run. Is the data on your other disks important to you?

User Customizations · September 24, 2012

Most bioses have an option for "resume on powerloss". Whenever power is gone you can choose between "on / off / last state".

If you put that on "on" and setup a cheap power/timer clock between pc and wall socket you can get what you want :

01:00 shut down array and power down system

01:30 cut power using the timer

06:00 restore power using timer

On restore of power system will turn on abd boot into unraid.

What is my major issue with this is that I allmost always have to do manual stuff to get the system to shudown without a parity check on restart.

You can't just cut the power on the unraid server, i assume you're using a UPS in this scenario, which will do a clean powerdown when you cut power. Besides the fact that you are abusing the UPS this way, there is a bigger risk. Normally, in case of a power loss, you not only want to powerdown the unraid server in a clean way ASAP, but after that is done, also shutdown the UPS. If you don't, in case the power returns for like a minute or a few seconds and powers down AGAIN, you will be in the middel of starting up your unraid server again (because your using 'resume on powerloss') and you can't do a nice powerdown since the UPS probably is empty or near empty... this is why you do NOT want to resume on powerloss. Just stay off.

So, do not use the UPS as a handy on/off switch... it's an emergency device, treat it as such.

While I fully agree with what you said regarding a UPS, that is not what was being recommended. Nowhere in the original post was UPS mentioned, but it should have been. The timer use case would be directly on the server power cord, on the OUTPUT of the UPS, not the wall side of the UPS. I agree that a UPS should always be used with a server, and the original suggestion should have made clear which SIDE of the UPS the timer should be controlling. With a properly sized and controlled UPS, resume on powerloss can be applied with minimal risk.

July 6, 2012

If you have a PCI ethernet card, I'd try that and turn off the motherboard ports. Realtek ethernet support seems to be spotty at best. Intel based cards usually work better.

User Customizations · February 23, 2012

Hey guys, I'm trying to download the preclear_disk.sh file from the firs thread and when I click the download link it just downloads me an index.php file, it's like the link is broken or something.

I'm very new to unRAID so excuse me if I'm doing something wrong

The link in http://lime-technology.com/forum/index.php?topic=2817.msg23246#msg23246 this post works fine for me. Which post are you referring to?

User Customizations · January 12, 2009

Update on clearing 3 new 1.5 Seagates. In the original post, I had just unzipped a fresh install of 4.4.2, installed the smart libraries, and kicked off the script. It precleared 2 out of three disks successfully. I then pulled the USB stick, added the newest bubbaraid and enabled it, and booted bubbaraid. The disk assignments changed, and I suspect I may have given you status on the wrong drive. I looked at the current syslog, and it seems the disk that failed the preclear the first time through may be bad. When I originally ran the script, the drives were sdb, sdc, and sdd. Now they are sda, sdb, and sdc. sda seems to be sick.

Jan 12 13:20:25 Tower preclear_disk-start[6674]: 1 Raw_Read_Error_Rate 0x000f 117 100 006 Pre-fail Always - 235560959
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 7
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 5 Reallocated_Sector_Ct 0x0033 095 095 036 Pre-fail Always - 220
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 220180
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 67
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 7
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 187 Reported_Uncorrect 0x0032 041 041 000 Old_age Always - 59
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 4295032833
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 189 High_Fly_Writes 0x003a 076 076 000 Old_age Always - 24
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 190 Airflow_Temperature_Cel 0x0022 067 065 045 Old_age Always - 33 (Lifetime Min/Max 28/33)
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 195 Hardware_ECC_Recovered 0x001a 044 044 000 Old_age Always - 235560959
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 18
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 18
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: SMART Error Log Version: 1
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ATA Error Count: 65 (device log contains only the most recent five errors)
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ^ICR = Command Register [HEX]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ^IFR = Features Register [HEX]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ^ISC = Sector Count Register [HEX]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ^ISN = Sector Number Register [HEX]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ^ICL = Cylinder Low Register [HEX]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ^ICH = Cylinder High Register [HEX]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ^IDH = Device/Head Register [HEX]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ^IDC = Device Command Register [HEX]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ^IER = Error register [HEX]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ^IST = Status register [HEX]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: Powered_Up_Time is measured from power on, and printed as
Jan 12 13:20:25 Tower preclear_disk-start[6674]: DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
Jan 12 13:20:25 Tower preclear_disk-start[6674]: SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: Error 65 occurred at disk power-on lifetime: 7 hours (0 days + 7 hours)
Jan 12 13:20:25 Tower preclear_disk-start[6674]: When the command that caused the error occurred, the device was active or idle.
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: After command completion occurred, registers were:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ER ST SC SN CL CH DH
Jan 12 13:20:25 Tower preclear_disk-start[6674]: -- -- -- -- -- -- --
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 04 71 04 81 87 80 e0 Device Fault; Error: ABRT
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: Commands leading to the command that caused the error were:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
Jan 12 13:20:25 Tower preclear_disk-start[6674]: -- -- -- -- -- -- -- -- ---------------- --------------------
Jan 12 13:20:25 Tower preclear_disk-start[6674]: a1 00 00 00 00 00 a0 00 07:00:26.454 IDENTIFY PACKET DEVICE
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ec 00 00 00 00 00 a0 00 07:00:26.442 IDENTIFY DEVICE
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 00 00 00 00 00 00 00 04 07:00:26.243 NOP [Abort queued commands]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 00 00 00 00 00 00 00 ff 07:00:25.911 NOP [Abort queued commands]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: a1 00 00 00 00 00 a0 00 07:00:20.959 IDENTIFY PACKET DEVICE
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: Error 64 occurred at disk power-on lifetime: 7 hours (0 days + 7 hours)
Jan 12 13:20:25 Tower preclear_disk-start[6674]: When the command that caused the error occurred, the device was active or idle.
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: After command completion occurred, registers were:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ER ST SC SN CL CH DH
Jan 12 13:20:25 Tower preclear_disk-start[6674]: -- -- -- -- -- -- --
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 04 71 04 81 87 80 e0
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: Commands leading to the command that caused the error were:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
Jan 12 13:20:25 Tower preclear_disk-start[6674]: -- -- -- -- -- -- -- -- ---------------- --------------------
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ec 00 00 00 00 00 a0 00 07:00:26.442 IDENTIFY DEVICE
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 00 00 00 00 00 00 00 04 07:00:26.243 NOP [Abort queued commands]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 00 00 00 00 00 00 00 ff 07:00:25.911 NOP [Abort queued commands]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: a1 00 00 00 00 00 a0 00 07:00:20.959 IDENTIFY PACKET DEVICE
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ec 00 00 00 00 00 a0 00 07:00:20.936 IDENTIFY DEVICE
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: Error 63 occurred at disk power-on lifetime: 7 hours (0 days + 7 hours)
Jan 12 13:20:25 Tower preclear_disk-start[6674]: When the command that caused the error occurred, the device was active or idle.
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: After command completion occurred, registers were:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ER ST SC SN CL CH DH
Jan 12 13:20:25 Tower preclear_disk-start[6674]: -- -- -- -- -- -- --
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 04 71 04 81 87 80 e0 Device Fault; Error: ABRT
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: Commands leading to the command that caused the error were:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
Jan 12 13:20:25 Tower preclear_disk-start[6674]: -- -- -- -- -- -- -- -- ---------------- --------------------
Jan 12 13:20:25 Tower preclear_disk-start[6674]: a1 00 00 00 00 00 a0 00 07:00:20.959 IDENTIFY PACKET DEVICE
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ec 00 00 00 00 00 a0 00 07:00:20.936 IDENTIFY DEVICE
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 00 00 00 00 00 00 00 04 07:00:20.729 NOP [Abort queued commands]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 00 00 00 00 00 00 00 ff 07:00:20.395 NOP [Abort queued commands]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: a1 00 00 00 00 00 a0 00 07:00:15.534 IDENTIFY PACKET DEVICE
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: Error 62 occurred at disk power-on lifetime: 7 hours (0 days + 7 hours)
Jan 12 13:20:25 Tower preclear_disk-start[6674]: When the command that caused the error occurred, the device was active or idle.
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: After command completion occurred, registers were:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ER ST SC SN CL CH DH
Jan 12 13:20:25 Tower preclear_disk-start[6674]: -- -- -- -- -- -- --
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 04 71 04 81 87 80 e0
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: Commands leading to the command that caused the error were:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
Jan 12 13:20:25 Tower preclear_disk-start[6674]: -- -- -- -- -- -- -- -- ---------------- --------------------
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ec 00 00 00 00 00 a0 00 07:00:20.936 IDENTIFY DEVICE
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 00 00 00 00 00 00 00 04 07:00:20.729 NOP [Abort queued commands]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 00 00 00 00 00 00 00 ff 07:00:20.395 NOP [Abort queued commands]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: a1 00 00 00 00 00 a0 00 07:00:15.534 IDENTIFY PACKET DEVICE
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ec 00 00 00 00 00 a0 00 07:00:15.421 IDENTIFY DEVICE
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: Error 61 occurred at disk power-on lifetime: 7 hours (0 days + 7 hours)
Jan 12 13:20:25 Tower preclear_disk-start[6674]: When the command that caused the error occurred, the device was active or idle.
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: After command completion occurred, registers were:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ER ST SC SN CL CH DH
Jan 12 13:20:25 Tower preclear_disk-start[6674]: -- -- -- -- -- -- --
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 04 71 04 81 87 80 e0 Device Fault; Error: ABRT
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: Commands leading to the command that caused the error were:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
Jan 12 13:20:25 Tower preclear_disk-start[6674]: -- -- -- -- -- -- -- -- ---------------- --------------------
Jan 12 13:20:25 Tower preclear_disk-start[6674]: a1 00 00 00 00 00 a0 00 07:00:15.534 IDENTIFY PACKET DEVICE
Jan 12 13:20:25 Tower preclear_disk-start[6674]: ec 00 00 00 00 00 a0 00 07:00:15.421 IDENTIFY DEVICE
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 00 00 00 00 00 00 00 04 07:00:15.213 NOP [Abort queued commands]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 00 00 00 00 00 00 00 ff 07:00:14.888 NOP [Abort queued commands]
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 35 00 00 ff ff ff ef 00 06:59:14.132 WRITE DMA EXT
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: SMART Self-test log structure revision number 1
Jan 12 13:20:25 Tower preclear_disk-start[6674]: No self-tests have been logged. [To run self-tests, use: smartctl -t]
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 13:20:25 Tower preclear_disk-start[6674]: SMART Selective self-test log data structure revision number 1
Jan 12 13:20:25 Tower preclear_disk-start[6674]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 1 0 0 Not_testing
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 2 0 0 Not_testing
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 3 0 0 Not_testing
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 4 0 0 Not_testing
Jan 12 13:20:25 Tower preclear_disk-start[6674]: 5 0 0 Not_testing
Jan 12 13:20:25 Tower preclear_disk-start[6674]: Selective self-test flags (0x0):
Jan 12 13:20:25 Tower preclear_disk-start[6674]: After scanning selected spans, do NOT read-scan remainder of disk.
Jan 12 13:20:25 Tower preclear_disk-start[6674]: If Selective self-test is pending on power-up, resume after 0 minute delay.
Jan 12 13:20:25 Tower preclear_disk-start[6674]:
Jan 12 15:34:25 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 12 15:34:25 Tower kernel: ata4.00: BMDMA stat 0x64
Jan 12 15:34:25 Tower kernel: ata4.00: cmd 25/00:00:00:8d:58/00:01:5d:00:00/e0 tag 0 dma 131072 in
Jan 12 15:34:25 Tower kernel: res 51/40:00:a5:8d:58/40:00:5d:00:00/00 Emask 0x9 (media error)
Jan 12 15:34:25 Tower kernel: ata4.00: status: { DRDY ERR }
Jan 12 15:34:25 Tower kernel: ata4.00: error: { UNC }
Jan 12 15:34:25 Tower kernel: ata4.00: configured for UDMA/133
Jan 12 15:34:25 Tower kernel: ata4.01: configured for UDMA/133
Jan 12 15:34:25 Tower kernel: ata4: EH complete
Jan 12 15:34:28 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 12 15:34:28 Tower kernel: ata4.00: BMDMA stat 0x64
Jan 12 15:34:28 Tower kernel: ata4.00: cmd 25/00:00:00:8d:58/00:01:5d:00:00/e0 tag 0 dma 131072 in
Jan 12 15:34:28 Tower kernel: res 51/40:00:a5:8d:58/40:00:5d:00:00/00 Emask 0x9 (media error)
Jan 12 15:34:28 Tower kernel: ata4.00: status: { DRDY ERR }
Jan 12 15:34:28 Tower kernel: ata4.00: error: { UNC }
Jan 12 15:34:28 Tower kernel: ata4.00: configured for UDMA/133
Jan 12 15:34:28 Tower kernel: ata4.01: configured for UDMA/133
Jan 12 15:34:28 Tower kernel: ata4: EH complete
Jan 12 15:34:31 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 12 15:34:31 Tower kernel: ata4.00: BMDMA stat 0x64
Jan 12 15:34:31 Tower kernel: ata4.00: cmd 25/00:00:00:8d:58/00:01:5d:00:00/e0 tag 0 dma 131072 in
Jan 12 15:34:31 Tower kernel: res 51/40:00:a5:8d:58/40:00:5d:00:00/00 Emask 0x9 (media error)
Jan 12 15:34:31 Tower kernel: ata4.00: status: { DRDY ERR }
Jan 12 15:34:31 Tower kernel: ata4.00: error: { UNC }
Jan 12 15:34:31 Tower kernel: ata4.00: configured for UDMA/133
Jan 12 15:34:31 Tower kernel: ata4.01: configured for UDMA/133
Jan 12 15:34:31 Tower kernel: ata4: EH complete
Jan 12 15:34:34 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 12 15:34:34 Tower kernel: ata4.00: BMDMA stat 0x64
Jan 12 15:34:34 Tower kernel: ata4.00: cmd 25/00:00:00:8d:58/00:01:5d:00:00/e0 tag 0 dma 131072 in
Jan 12 15:34:34 Tower kernel: res 51/40:00:a5:8d:58/40:00:5d:00:00/00 Emask 0x9 (media error)
Jan 12 15:34:34 Tower kernel: ata4.00: status: { DRDY ERR }
Jan 12 15:34:34 Tower kernel: ata4.00: error: { UNC }
Jan 12 15:34:34 Tower kernel: ata4.00: configured for UDMA/133
Jan 12 15:34:34 Tower kernel: ata4.01: configured for UDMA/133
Jan 12 15:34:34 Tower kernel: ata4: EH complete
Jan 12 15:34:37 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 12 15:34:37 Tower kernel: ata4.00: BMDMA stat 0x64
Jan 12 15:34:37 Tower kernel: ata4.00: cmd 25/00:00:00:8d:58/00:01:5d:00:00/e0 tag 0 dma 131072 in
Jan 12 15:34:37 Tower kernel: res 51/40:00:a5:8d:58/40:00:5d:00:00/00 Emask 0x9 (media error)
Jan 12 15:34:37 Tower kernel: ata4.00: status: { DRDY ERR }
Jan 12 15:34:37 Tower kernel: ata4.00: error: { UNC }
Jan 12 15:34:37 Tower kernel: ata4.00: configured for UDMA/133
Jan 12 15:34:37 Tower kernel: ata4.01: configured for UDMA/133
Jan 12 15:34:37 Tower kernel: ata4: EH complete
Jan 12 15:34:40 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 12 15:34:40 Tower kernel: ata4.00: BMDMA stat 0x64
Jan 12 15:34:40 Tower kernel: ata4.00: cmd 25/00:00:00:8d:58/00:01:5d:00:00/e0 tag 0 dma 131072 in
Jan 12 15:34:40 Tower kernel: res 51/40:00:a5:8d:58/40:00:5d:00:00/00 Emask 0x9 (media error)
Jan 12 15:34:40 Tower kernel: ata4.00: status: { DRDY ERR }
Jan 12 15:34:40 Tower kernel: ata4.00: error: { UNC }
Jan 12 15:34:40 Tower kernel: ata4.00: configured for UDMA/133
Jan 12 15:34:40 Tower kernel: ata4.01: configured for UDMA/133
Jan 12 15:34:40 Tower kernel: sd 4:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
Jan 12 15:34:40 Tower kernel: sd 4:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Jan 12 15:34:40 Tower kernel: Descriptor sense data with sense descriptors (in hex):
Jan 12 15:34:40 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Jan 12 15:34:40 Tower kernel: 5d 58 8d a5
Jan 12 15:34:40 Tower kernel: sd 4:0:0:0: [sda] ASC=0x11 ASCQ=0x4
Jan 12 15:34:40 Tower kernel: end_request: I/O error, dev sda, sector 1566084517
Jan 12 15:34:40 Tower kernel: Buffer I/O error on device sda, logical block 195760564
Jan 12 15:34:40 Tower kernel: Buffer I/O error on device sda, logical block 195760565
Jan 12 15:34:40 Tower kernel: Buffer I/O error on device sda, logical block 195760566
Jan 12 15:34:40 Tower kernel: Buffer I/O error on device sda, logical block 195760567
Jan 12 15:34:40 Tower kernel: Buffer I/O error on device sda, logical block 195760568
Jan 12 15:34:40 Tower kernel: Buffer I/O error on device sda, logical block 195760569
Jan 12 15:34:40 Tower kernel: Buffer I/O error on device sda, logical block 195760570
Jan 12 15:34:40 Tower kernel: Buffer I/O error on device sda, logical block 195760571
Jan 12 15:34:40 Tower kernel: Buffer I/O error on device sda, logical block 195760572
Jan 12 15:34:40 Tower kernel: Buffer I/O error on device sda, logical block 195760573
Jan 12 15:34:40 Tower kernel: ata4: EH complete
Jan 12 15:34:40 Tower kernel: sd 4:0:0:0: [sda] 2930277168 512-byte hardware sectors (1500302 MB)
Jan 12 15:34:40 Tower kernel: sd 4:0:0:0: [sda] Write Protect is off
Jan 12 15:34:40 Tower kernel: sd 4:0:0:0: [sda] Mode Sense: 00 3a 00 00
Jan 12 15:34:40 Tower kernel: sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 12 15:34:42 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

I assume the failures at 7 hours are when the preclear failed the first time.

User Customizations · January 12, 2009

I'm kicking off another set of 3 preclears on all 3 disks. We'll see in a couple days.

User Customizations · January 12, 2009

What do you get if you type:

preclear_disk.sh -t /dev/sdb

I'll be shocked if it does not indicate the clearing worked as it was supposed to.

I'm a bit at a loss to figure out what is happening... You also had off numbers with your elapsed time calculation. It is almost as if the "shell" was having memory problems.

We you doing anything else at the time the preclear was occurring to the same disk? Did you reset the time-zone and/or time when pre-clear was in progress?

Could you have had a second preclear_disk.sh running on the same disk at the same time?

If the output of the preclear_disk.sh -t /dev/sdb indicates it is cleared, then you might want to look at your syslog for any indications of disk read errors. Something made it think the data was different the last time it looked.

Joe L.

root@Tower:/boot/scripts# preclear_disk.sh -t /dev/sdb
Pre-Clear unRAID Disk
########################################################################
Device Model:     ST31500341AS
Serial Number:    9VS0HE2T
Firmware Version: CC1H
User Capacity:    1,500,301,910,016 bytes

Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              63  2930277167  1465138552+   0  Empty
Partition 1 does not end on cylinder boundary.
########################################################################
============================================================================
==
== DISK /dev/sdb IS PRECLEARED
==
============================================================================
root@Tower:/boot/scripts#

All I did was boot the server, install the smartctl libraries, install the preclear script, and kick it off in three different telnet windows on the three different drives. 2 completed successfully, 1 didn't.

User Customizations · January 12, 2009

The first disk didn't complete successfully. What logs and or other info do I need to look at to figure out why?

Type:

fdisk -l /dev/sdb

dd if=/dev/sdb count=1 | od -x -A d

Post the output of both commands.

Joe L.

Tower login: root

Linux 2.6.27.7-unRAID.

root@Tower:~# fdisk -l /dev/sdb

Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes

255 heads, 63 sectors/track, 182401 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk identifier: 0x00000000

Device Boot Start End Blocks Id System

/dev/sdb1 1 182402 1465138552+ 0 Empty

Partition 1 does not end on cylinder boundary.

root@Tower:~# dd if=/dev/sdb count=1 | od -x -A d

1+0 records in

1+0 records out

512 bytes (512 B) copied, 0.000298241 s, 1.7 MB/s

0000000 0000 0000 0000 0000 0000 0000 0000 0000

*

0000448 0000 0000 0000 003f 0000 7af1 aea8 0000

0000464 0000 0000 0000 0000 0000 0000 0000 0000

*

0000496 0000 0000 0000 0000 0000 0000 0000 aa55

0000512

root@Tower:~#

User Customizations · January 10, 2009

The first disk didn't complete successfully. What logs and or other info do I need to look at to figure out why?

User Customizations · January 10, 2009

What "telnet" client are you using? Are you using "putty" or the command built into windows? I'm in the same time-zone as you, so my server should act the same.

This was the stock w2k command line telnet. I normally use putty, but this server is not on my home lan.

User Customizations · January 10, 2009

This is a fresh (as in rolled 1/2 hour before use) install of 4.4.2 with the only customizations being the download and install of the smartctl libraries, and download of the new york timezone file. Timezone is set to custom in the configuration. The date command as you specified returned 1231549459 as of 8:05 eastern.

User Customizations · January 9, 2009

I just kicked off three telnet preclear sessions on three new 1.5TB drives.

Is the time display supposed to show the dashes?

JonathanM

Posts

Joined

Last visited

Days Won

Content Type

Profiles

Forums

Downloads

Store

Gallery

Bug Reports

Documentation

Landing

Posts posted by JonathanM

cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up

Moving movies with SABnzbd (SOLVED)

Moving movies with SABnzbd (SOLVED)

Plugin Feature Request: Cloud Storage unRAID Hybrid Storage Appliance

unRAID Case Badge

Re: preclear_disk.sh - a new utility to burn-in and pre-clear disks for quick add

Scheduled Power off/Power on, Restart possible?

Areca ARC-1300ix-16 support

Re: preclear_disk.sh - a new utility to burn-in and pre-clear disks for quick add

Re: preclear_disk.sh - a new utility to burn-in and pre-clear disks for quick add

Re: preclear_disk.sh - a new utility to burn-in and pre-clear disks for quick add

Re: preclear_disk.sh - a new utility to burn-in and pre-clear disks for quick add

Re: preclear_disk.sh - a new utility to burn-in and pre-clear disks for quick add

Re: preclear_disk.sh - a new utility to burn-in and pre-clear disks for quick add

Re: preclear_disk.sh - a new utility to burn-in and pre-clear disks for quick add

Re: preclear_disk.sh - a new utility to burn-in and pre-clear disks for quick add

Re: preclear_disk.sh - a new utility to burn-in and pre-clear disks for quick add