twg

Here are the results: root@Tower:~# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes and syslog attached. There are a few errors when mounting the disks, that is when I basically added the disks to the array i think and formatted them... syslog-2011-03-31.zip

the more i read about these cryptic errors the more it seems like it's related to the support of this card in the kernel... if you look around on some other forums, many people have these types of issues with this particular card. Does the 5.0beta use a newer linux kernel ? Wondering if the mvsas driver is updated relative to v4.7. Is everyone that have this issue on this thread running unRaid 4.7 or anyone running 5.0beta ?

i'm still in the middle of transferring 4gigs over so figured can't do any disk performance tests until that's done. I did try reading from the array and over the wired network was getting 55MB/s read.. which is double the speed of reading from the dlink343...

my home network seemed to have worked well... i tested transfer speeds with jumbo frame and without and was faster with jumbo frame. I also made sure that all the devices on the network supports jumbo frames at least up to 6k. Here's the results of the ifconfig eth0 command: eth0 Link encap:Ethernet HWaddr 00:30:67:60:b3:eb inet addr:192.168.0.114 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:6000 Metric:1 RX packets:252614371 errors:0 dropped:0 overruns:0 frame:0 TX packets:168486206 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3576761662 (3.3 GiB) TX bytes:3566925474 (3.3 GiB) Interrupt:27 Base address:0x6000 Seems to be ok... no errors or overruns...

So after going through some issues setting up my unRaid, I finally have her up and running. I have it connected to the network via 1Gig ethernet. I mounted my Dlink 343 NAS directly to the unRaid server and using rsync to copy data over from the NAS to unRaid via a telnet console. I have the unRaid server setup via user shares... and i don't have a parity drive setup so this is unprotected... The data's been copying for 25 hrs now, and averaging ~15MB/s.. there are no errors in the syslog nor in the unRaid status page, and everything seems to be running properly but this seems a bit slow. I'm reading that on avg, people should be getting 25-40MB/s write speeds to unRaid ? I even set the frame size to 6k... (everything on my network has jumbo frames enabled set to 6k) It's a Biostar TA785G3HD motherboard so Realtek chipset, it's connected at 1000Mb/s... via a cat5e cable to the wall, which is connected via cat 5e to a Dlink 1024D switch which is then connected to the Dlink 343 NAS... which is also connected to the switch at 1000Mb/s I know copying from the Dlink 343 I can achieve read speeds around 24-25Mb/s... I can tell my the status that for now, it's writing to the Hitachi 7k2000 drive... so should be a fast drive... any suggestions ? at this rate, it's going to take over 3 days to copy my 4gigs of data over!

I've got two Seagate ST3500320AS drives. I updated the fw on both drives to the latest due to a warning when attempting to preclear them. Now, whenever I cold boot, the drives will have SMART disabled. I can enable SMART using smartctl -a -s on /dev/sdX, but even though I read it's suppose to survive a cold boot, it doesn't. It doesn't seem to affect performance but it's just annoying that I can't see the drive temp via unMenu after a cold boot. This is connected to either the supermicro AOC-SASLP controller or the SIL3134 controller. When connected to the MB SATA controller, the SMART is enabled by default. Any suggestions on how to either have the SMART settings stay or turn it on automatically during a boot ? Create a simple script and put it into /boot/config/go ?

I think I might have solved the issues that I posted (although I have some other sporadic errors showing up in syslog). The corruption above I suspect is due to the log explosion problem and overwriting memory... I've since created a tmpfs drive to hold the syslog files so it doesn't crash my server due to log explosion. The preclearing issues seem to be related to a brand new Hitachi 5k3000 drive, this drive would sporadically show up/not, and even with all other drives removed and only this drive connected it would have problems, regardless of the SATA port I used (Supermicro, or on board MB). I'm going to RMA this drive. Removed this drive and everything preclears fine. As to the SMART values not showing up on the Seagate drives, it's kind of odd, but I think after I flashed with the new firmware that the default is to disable SMART. I can enable it: /boot/smartctl -d ata --smart=on --autosave=on /dev/sde it works fine, but doesn't stay on after a cold reboot. I don't know why, but when connected to the MB sata ports, SMART is enabled by default, guess the MB automatically issues that command. But when connected to the Supermicro and the SIL3132 card, it is disabled. I'll open another post to figure out how to enable SMART on reboot. So I guess this thread can now be deemed SOLVED. Now to my other smaller issues...

I have seen this exact issue today, after preclearing 5 of my new drives using the MB sata ports successfully, I moved the drives to the AOC-SASLP supermicro ports, I got these errors as well but preclear seemed to have started/finished ok. I used the -n option so it skipped the pre and post read however.

So I'm running unRaid 4.7. I'm having some trouble where the logs are exploding and corrupting my unRaid session. I'm trying to track down the issues causing the log explosion and I think I have found it, however, I want to implement this to prevent log explosion from crashing my unRaid (which I think is kind of ridiculous). I found this thread: http://lime-technology.com/forum/index.php?topic=3352.15 I created a script and am calling the script from /boot/config/go But it didn't work, the symbolic link was failing because the syslog file still exists in /var/log, I had to do this instead to get it to work, is this the right approach or is there a better way ? /etc/rc.d/rc.syslog stop mkdir /tmp/log mount tmpfs /tmp/log -t tmpfs cp /var/log/syslog /tmp/log/ rm /var/log/syslog ln -s /tmp/log/syslog /var/log/syslog /etc/rc.d/rc.syslog start

I seem to have run into this recently as well... same symptoms.. syslog file growing very large sometimes to 3+gigs. Same errors in the syslog... unRaid 4.7 as well with the AOC-SASLP controller... I think I might have isolated it to a bad drive. I bought 4 new drives and re-used 2 good drives. 1 of the new drives (Hitachi 5k3000 2TB) seem to be bad, freezing preclears and causing these issues. I've removed that drive and so far pre-clearing all the other drives ok.

Before you start replacing components, I suggest you shut down the other drives and only preclear the new drive. If it works, then could be a weak psu, if it doesn't work then I'd suggest trying preclear again in a different slot to see if its th drive or the controller/cable. I had similar issues trying to preclear 6 new drives, turns out 1 of the new drives was bad and caused syslog explosion which crashed the machie, makig the other drives look bad too.

ok, i'm back to square 1. I'm back from my business trip, ran the memtest for ~5 days and no errors. I rebooted, and noticed that ata3 or one of my new 5k3000 hitachi drives wasn't being recognized by the Supermicro card. I pulled it out and reseated it in the cage and upon reboot it was detected. Checked the syslog, no errors. I then started 4 clearing sessions, one in each telnet session. This morning, I notice that the telnet session for ata3 (or /dev/sdd) had: essage from syslogd@Tower at Fri Mar 25 08:01:07 2011 ... Tower kernel: t eekCo:ls0xmlete } Message from syslogd@Tower at Fri Mar 25 08:01:54 2011 ... Tower kernel: 5<mf Message from syslogd@Tower at Fri Mar 25 08:02:02 2011 ... Tower kernel: 00cs0000: mvsas d-24t:oeerstnorx Message from syslogd@Tower at Fri Mar 25 08:02:14 2011 ... Tower kernel: t eekp._to ee }>ekfCyrent fe Sess 00er 0 porsn0a <osl0xC /CS b004t:tu00 DSkme }m.0!ldecea tn:1 Message from syslogd@Tower at Fri Mar 25 08:02:23 2011 ... Tower kernel: 5<mf Message from syslogd@Tower at Fri Mar 25 08:02:32 2011 ... Tower kernel: s0:0[dA=0S=0 85 0ror, 2:0032 Message from syslogd@Tower at Fri Mar 25 08:02:51 2011 ... Tower kernel: 5<mf The syslog file is very large: -rw-r--r-- 1 root root 2147483647 Mar 25 06:48 syslog I'm wondering if I'm running out of memory ? I have 4 gigs of memory and a 4 gig USB key, results of "free" shows: root@Tower:/var/log# free total used free shared buffers cached Mem: 4115652 3124968 990684 0 817684 2247940 -/+ buffers/cache: 59344 4056308 Swap: 0 0 0 The preclear for sdc, sde and sdg is still running but I also see the weird messages but it gets overwritten when the preclear screen refreshes. Again, similar to before, as I was posting this, preclear for sdc and sde just stopped after 8hrs: ================================================================== 1.9 = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1, partition start on sector 63 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Elapsed Time: 8:25:17 ========================================================================1.9 == == SORRY: Disk /dev/sdc MBR could NOT be precleared == == out4= 00000 == out5= 00000 ============================================================================ dd: reading `/dev/sdc': Input/output error 0+0 records in 0+0 records out 0 bytes (0 B) copied, 0.000674543 s, 0.0 kB/s 0000000 root@Tower:/boot# ================================================================== 1.9 = unRAID server Pre-Clear disk /dev/sde = cycle 1 of 1, partition start on sector 63 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Elapsed Time: 8:27:40 ========================================================================1.9 == == SORRY: Disk /dev/sde MBR could NOT be precleared == == out4= 00000 == out5= 00000 ============================================================================ dd: reading `/dev/sde': Input/output error 0+0 records in 0+0 records out 0 bytes (0 B) copied0000000 , 0.000242271 s, 0.0 kB/s attached is the end of the syslog. Suggestions ? When I try to restart the preclear in the telnet window I get: root@Tower:/boot# ./preclear_disk.sh /dev/sdc BLKRRPART: Input/output error Sorry: Device /dev/sdc is not responding to an fdisk -l /dev/sdc command. You might try power-cycling it to see if it will start responding. root@Tower:/boot# ./preclear_disk.sh /dev/sdd BLKRRPART: Input/output error Sorry: Device /dev/sdd is not responding to an fdisk -l /dev/sdd command. You might try power-cycling it to see if it will start responding. root@Tower:/boot# ./preclear_disk.sh /dev/sde BLKRRPART: Input/output error Sorry: Device /dev/sde is not responding to an fdisk -l /dev/sde command. You might try power-cycling it to see if it will start responding. syslog-2011-03-25-end.txt

Looks like both of the Seagate's precleared and I CAN read the SMART values: ================================================================== 1.9 = unRAID server Pre-Clear disk /dev/sdb = cycle 1 of 1, partition start on sector 63 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 30C, Elapsed Time: 7:08:06 ========================================================================1.9 == ST3500320AS 9QM0YQ4C == Disk /dev/sdb has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 117 6 ok 203556375 Spin_Retry_Count = 100 100 97 near_thresh 35 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 70 67 45 In_the_past 30 Temperature_Celsius = 30 33 0 ok 30 Hardware_ECC_Recovered = 52 49 0 ok 203556375 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ================================================================== 1.9 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 63 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 30C, Elapsed Time: 7:07:46 ========================================================================1.9 == ST3500320AS 9QM0YQ9L == Disk /dev/sdf has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 117 6 ok 187160641 Spin_Retry_Count = 100 100 97 near_thresh 9 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 70 68 45 near_thresh 30 Temperature_Celsius = 30 32 0 ok 30 Hardware_ECC_Recovered = 51 47 0 ok 187160641 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. root@Tower:/boot# smartctl --all /dev/sdb |more smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.11 family Device Model: ST3500320AS Serial Number: 9QM0YQ4C Firmware Version: SD1A User Capacity: 500,107,862,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Mon Mar 21 07:51:41 2011 EDT 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 See vendor-specific Attribute list for marginal Attributes. 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: ( 625) 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: ( 113) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103b) 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 119 099 006 Pre-fail Always - 203556375 3 Spin_Up_Time 0x0003 095 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 114 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 073 060 030 Pre-fail Always - 8633999777 19255_Hours 0x0032 079 079 000 Old_age Always ---More-- 10 Spin_Retry_Count 0x0013 100 099 097 Pre-fail Always - 35 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 116 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 4295032833 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 070 043 045 Old_age Always In_the_past 30 (0 201 34 29) 194 Temperature_Celsius 0x0022 030 057 000 Old_age Always - 30 (0 20 0 0) 195 Hardware_ECC_Recovered 0x001a 046 019 000 Old_age Always - 203556375 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 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.11 family Device Model: ST3500320AS Serial Number: 9QM0YQ9L Firmware Version: SD1A User Capacity: 500,107,862,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Mon Mar 21 07:54:10 2011 EDT 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: ( 634) 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: ( 113) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103b) 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 118 099 006 Pre-fail Always - 187160641 3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 120 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 4334013080 9 Power_On_Hours 0x0032 079 079 000 Old_age Always - 19254 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 9 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 121 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 070 046 045 Old_age Always - 30 (Lifetime Min/Max 29/34) 194 Temperature_Celsius 0x0022 030 054 000 Old_age Always - 30 (0 21 0 0) 195 Hardware_ECC_Recovered 0x001a 045 013 000 Old_age Always - 187160641 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 0_CRC_Error_Count 0x003e 200 200 000 Old_age Always ---More-- SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. Weird that I can read the SMART values now... wonder if its because after flashing with new FW, I never accessed the drive, so perhaps there was no SMART value stored ? I'm going to be gone for 4 days so I'm going to let it run the memtest until i get back...

I didn't read your message in time so wasn't able to copy contents of /tmp over... I ran memtest for 6+ hrs and it seemed ok, will run it for 3-5 days when I leave for business tomorrow, but in the meanwhile, I also fixed the BIOS to set it to AHCI mode (was auto before), shouldn't have made a difference I don't think since I only had 1 drive connected to the MB and the rest were on the Supermicro AOC-SASLP. One thing is weird though, when I checked the SMART results for my Seagate 7200.11 500GB (ST3500320AS) drive, it says the firmware needs to be updated so I checked and updated to the latest SD1A firmware. Now, unRAID via the unMenu can't read anything via SMART off the drives. When I run smartctl on the command line, it gives me the following: === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.11 family Device Model: ST3500320AS Serial Number: 9QM0YQ9L Firmware Version: SD1A User Capacity: 500,107,862,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sun Mar 20 21:21:42 2011 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Error SMART Status command failed I'm running a preclear only on these drives right now and seems to be running... any idea why after the new FW upgrade the SMART info isn't readable anymore ?

So I finally pieced together the hardware for my unRaid build. MB: Biostar TA785G3HD link Memory: Mushkin 2x2GB PC3-10666 link CPU: AMD Athlon II x3 435 link IO: 1x Supermicro AOC-SASLP-MV8 link Cages: 3x iStarUSA BPU-350SATA-BLUE 5 in 3 link Cables: 3ware CBL-SFF8087OCF-05M link HD: 2xHitachi 5k3000 2TB link, 2xHitachi 7k2000 2TB link, 2xSeagate 500GB ST3500320AS Case: Thermaltake v6 link PSU: Corsair CX600 link USB: 4GB Lexar Firefly Jumpdrive link All the drives listed above are in the computer. I only have the free version of unRAID for now. It boots up fine. I did not add any drives to the array. All the 2TB drives are brand new, only the 500GB drive are used, that had a RAID partition from Windows XP which I did not remove. I started preclear on 4 drives last night: sdb - 500GB Seagate sdc - 2TB 7k2000 Hitachi sdd - 2TB 5k3000 Hitachi sde - 2TB 5k3000 Hitachi When I checked this am, the screen for preclearing sdb and sdd are showing tower kernel messages: Message from syslogd@Tower at Sun Mar 20 08:36:10 2011 ... Tower kernel: 44: xb ts)0 000SCd:2:s]D b]x:8080b 803nrev070ex id1]<s:l_eion fo0 Message from syslogd@Tower at Sun Mar 20 08:39:10 2011 ... Tower kernel: b<mf Message from syslogd@Tower at Sun Mar 20 08:39:21 2011 ... Tower kernel: 43valed[e a etoRevs0::. s efl[3!5ascea tuntiateA ae 40tSI ady }:02mvsailed[ta1: ne translation for staoC /CS b00 Message from syslogd@Tower at Sun Mar 20 09:09:54 2011 ... Tower kernel: /000 Message from syslogd@Tower at Sun Mar 20 09:10:05 2011 ... Tower kernel: 43va<>sassot4}:c] Message from syslogd@Tower at Sun Mar 20 09:10:20 2011 ... Tower kernel: 43> etur:tKdm!ld_exru 3ain f eale>ta1rTx> tansabiau satixAD vf! Message from syslogd@Tower at Sun Mar 20 09:10:21 2011 ... Tower kernel: evor763<ma0020. retuor s/ASCid : status=0x00 { } Message from syslogd@Tower at Sun Mar 20 09:10:24 2011 ... Tower kernel: :t0cfail llsk retno anslation for status: 0x00 Message from syslogd@Tower at Sun Mar 20 09:10:49 2011 ... Tower kernel: :t0cfail llsk retno anslation for status: 0x00 Message from syslogd@Tower at Sun Mar 20 09:10:49 2011 ... Tower kernel: /0 tat2esaiS<u=0x000_snt Message from syslogd@Tower at Sun Mar 20 09:11:00 2011 ... Tower kernel: 43va<>sassk 2<te0l<eecutturtaxba1st=4{rea <3>1<s:l_ekerd-1 ssst/rx/ SSA/A sec0:0 -13 trn f 0x40 Message from syslogd@Tower at Sun Mar 20 09:11:11 2011 ... Tower kernel: r <tu]!l_ettkerd-24t:oee nost: ar C0 Message from syslogd@Tower at Sun Mar 20 09:11:36 2011 ... Tower kernel: e_qs Orrd b, -132 Message from syslogd@Tower at Sun Mar 20 09:11:49 2011 ... Tower kernel: :t0sbyte0x0:0: [scurescriptor] Message from syslogd@Tower at Sun Mar 20 09:12:06 2011 ... Tower kernel: /0 tatudy 0_snd ttus=<3>0eesu<:ut: ho]< < Message from syslogd@Tower at Sun Mar 20 09:12:12 2011 ... Tower kernel: : CHSector 0 Message from syslogd@Tower at Sun Mar 20 09:12:14 2011 ... Tower kernel: 5o0ACQ /00/0000 e/iSsector 0 Message from syslogd@Tower at Sun Mar 20 09:12:15 2011 ... Tower kernel: 5o0ACQ 0/00/0000 e/iSsector 0 I haven't played with linux for past 15 years so I don't understand this output or its gibberish/corrupted. I'm viewing this from a Putty telnet session. Anyone make sense of this ? As I was posting this, preclear for sdc and sde showed the following: sdc preclear result: ================================================================== 1.9 = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1, partition start on sector 63 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Elapsed Time: 8:46:32 ========================================================================1.9 == == SORRY: Disk /dev/sdc MBR could NOT be precleared == == out4= 00000 == out5= 00000 ============================================================================ dd: reading `/dev/sdc': Input/output error 0+0 records in 0+0 records out 0 bytes (0 B) copied, 0.000361532 s, 0.0 kB/s 0000000 sde preclear results: ================================================================== 1.9 = unRAID server Pre-Clear disk /dev/sde = cycle 1 of 1, partition start on sector 63 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Elapsed Time: 8:54:47 ========================================================================1.9 == == SORRY: Disk /dev/sde MBR could NOT be precleared == == out4= 00000 == out5= 00000 ============================================================================ dd: reading `/dev/sde': Input/output error 0+0 records in 0+0 records out 0 bytes (0 B) copied, 0.000572331 s, 0.0 kB/s 0000000 I'm going to double check all the connections, reseat all the drives and then run a memtest, but any additional suggestions ? I've also attached the beginning and ending of the syslogs... there seems to be a lot of errors, not sure what it means... syslog-beginsnip1.txt syslog-beginsnip2.txt syslog-endsnip.txt

I have this switch at home and it seems to work well. Only had to reboot it once in the past couple of years.

why use a refurb drive to hold data that is _NOT_ protected ? I would use a refurb drive to hold data that IS protected however.

How did you buy two ? The $20 off is a one time use, not per drive... so you buy 1 drive, it's $20 off, you buy 2 drives, it's still $20 off so $10 off per drive...

Anyone use this drive ? It seems to be the new green barracuda drive from Seagate that's on sale...

Actually, the icy docks according to their website is 8.66" deep, which is on the deeper side of the cages. So the Supermicro's seem to be the longest, followed by the Norco ss-500, then the icy dock, then the iStars then the Athena/SNTs... I'm in the same boat, picked up a Thermaltake v6 after reading on these forums, but after I mounted my MB (Biostar TA785G3+ HD) it seems I only have about 7.5" from front of the case to the edge of the motherboard... I like the SNT, but I'm leary of the brand name, worried about the quality/after sales support... so leaning towards the iStars...

Here in Canada, here are the Athlon II prices: Athlon II x2 (65W): 245 2.9GHz - $54.88CAD 250 3Ghz - $64.99CAD 255 3.1GHz - $67.99CAD 260 3.2GHz - $72.99 However there is a sale: Athlon II x3 (95W): 445 3.1GHz - $79.99 The only downside to the x3 is the higher power consumption, which I don't really care about... but I do have a Corsair CX600 Watt to be used for a 15 drive build... thoughts ?

I'm in the same boat, but I do want to run airVideo which will transcode 1080p stuff, but that's the most cpu intensive task, could I still use the Sempron or should I use another processor ? And if another, I already have an AM3 MB, so which cpu to get? Thx