Jomp

This might be of interest to you: http://forums.overclockers.com.au/showthread.php?t=897770

I typed that incorrectly, my apologies. It should have said that I can't write to the LAST 68Gigs of a 2000Gig drive. That makes quite a bit of difference. I can fill all my other drives right up to the limit, but for whatever reason, this one can only fill to 97%. Regardless of the size you are unable to write to, we still need the same outputs from the same commands I listed earlier in order to diagnose what is happening. (glad it is only the last 68Gig.) No, it is not a normal occurrence. Joe L. As the transfer stalls, the webgui will show read after read on the drive and top shows the free memory slowing being eaten up until it gets very low and then the transfer will fail. After all this, unraid won't flag a write error and nothing shows up in the syslog. *EDIT: On a different 2000GB disk that has 20GB free, I just tried to transfer a 8GB file. It fails to start the first time, just shows a few thousand reads on the webgui. After trying to transfer the file a second time, it starts and finishes. Could this be an OSX SMB implantation thing? *EDIT 2: Weird. In trying to prove or disprove the OSX theory, I just fired up my virtualized Windows 7 install on the same machine. It paused for a while at the 68GB point that OSX always stalls on, but then moved on and completed the transfer. I then deleted that file and OSX can now write past the 68GB point. So strange.

SMART: 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 113 100 006 Pre-fail Always - 52415474 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 291 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 067 060 030 Pre-fail Always - 6050107 9 Power_On_Hours 0x0032 094 094 000 Old_age Always - 5432 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 72 183 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 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 071 066 045 Old_age Always - 29 (Lifetime Min/Max 25/34) 194 Temperature_Celsius 0x0022 029 040 000 Old_age Always - 29 (0 13 0 0) 195 Hardware_ECC_Recovered 0x001a 051 035 000 Old_age Always - 52415474 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 - 198491913586650 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3706874541 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 2381941921 Hdparm: root@Media:~# hdparm -i /dev/sde /dev/sde: Model=ST32000542AS , FwRev=CC35 , SerialNo= 6XW0GPDT Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4 BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=?16? CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=18446744073321613488 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 AdvancedPM=yes: unknown setting WriteCache=enabled Drive conforms to: unknown: ATA/ATAPI-4,5,6,7 * signifies the current active mode root@Media:~# hdparm -N /dev/sde /dev/sde: max sectors = 18446744073321613488/14715056, HPA setting seems invalid Nothing shows up in the syslog about it at all..

Is this a common occurrence, not being able to fill a disk up completely? Is it something that others have experienced? I'll post the SMART and hdparm if they are still relevent. I'm not sure they still are, since I essentially wrote my problem backwards.

I typed that incorrectly, my apologies. It should have said that I can't write to the LAST 68Gigs of a 2000Gig drive. That makes quite a bit of difference. I can fill all my other drives right up to the limit, but for whatever reason, this one can only fill to 97%.

One of my drives can't be written past a certain point. It's a 2tb drive that I can't write beyond 68gb or so. I know it's not good to fill them up that much but I'm more curious about the why, since I can fill the rest of my drives much closer to the 2tb limit. It's just this one hard drive that won't fill up. It passed a fscheck and a long SMART test. This happens during any type of data copy like an OSX smb copy, cp from other unraid drives, etc. The copy will stall at the same point, with the webgui showing lots of reads before the copy eventually fails. Any ideas?

Do pay attention to these two raw numbers, though: 197 Current_Pending_Sector 198 Offline_Uncorrectable

Seagates are known for crazy Raw_Read_Error_Rate and Seek_Error_Rate counts. My oldest has a seek error rate of... 38715245524.

Just an FYI, my sale drive came in today. I had to force an update, unlike the others that auto-updated.

You can force an upgrade: http://niallbest.com/seagate-2tb-st32000542as-cc35-firmware-upgrade/ http://stx.lithium.com/t5/Barracuda-XT-Barracuda-and/Idle-clicking-of-Seagate-Barracuda-LP-HDs-and-DOA-issues/m-p/55298#M20418 This thread finally got me motivated tonight. I updated all 12 of the drives in my server. Thankfully they all went without a hitch, parity check running right now. Serial numbers ranged from 5X-9X and firmware numbers from CC32-CC34. I was only able to use the onboard intel sata chipset (it was in AHCI mode). The onboard JMicro ports and the adaptec 1430 did not work.

Yeah, I have 12 of the 2TB 5900rpm Seagates running, not a problem with any of them. Well, one has a few more high fly writes than I'd like to see, but it's still far below the failing threshold. Overall I've been pleased with them. I'll keep buying them until 4TB drives come on the market.

If he upsizes again, I really hope it'll include 23 data drives + 1 parity as an option. As one who doesn't use a cache drive, an additional data drive in that slot would be great.

Nice indeed. I was pretty pleased when it booted up with two SASLP's installed and HPA being disabled by default. Unfortunately I don't use either fan control or S3, so I haven't tested them.

I will put pictures up when it comes in though!

Update: All the hardware listed in the top post is stable and working great. You can put two AOC-SASLP-MV8's in the GA-EP45-UD3P motherboard. Not a bad way to get 24 ports. HPA is disabled by default, so even if the BIOS gets reset for some reason, no HPA will be added to the disks. Just waiting on August for the RPC-4224 to ship and for Tom to hopefully add 3 more data device slots.

I'm still sitting on my hardware. Everything seems to point to another month or two for it to be released.