internetfriend

As a beginner I am ok with those ports! I don't even know how to disable UNMENU at this point (just comment it out in my GO script I guess?) If its ok to mark SAB's port in the go script I'd say do it once the first time to ensure it boots right, then adjust it to 8081, then take it out of the go script. that would work, right?

Is this the best solution for streaming video to your phone? Being able to access the video library instead of music is what I'm looking for. Air Video seems to be a great choice and has an UNRAID package but I have an android phone so no dice on that.

This is seriously awesome. i was going to do the lockstockmods install but this is much more streamlined since it includes couchpotato too. Are you all comfortable selling this wiki off as good to go, or are you still working on pieces? From what I read it looks like its ready to be run through. What about the whole issue with files being given permissions under "nobody" people were talking about in one of the latest SABNZBD releases? Do I even need it? post with fix about it: http://lime-technology.com/forum/index.php?topic=10353.0

Looks like it worked. *552 is that sweet spot on new drives right? http://dl.dropbox.com/u/519591/UNRAID/FIXED.JPG I did it to the parity drive and the drive outside of the array. Next steps are finish this party rebuild, then do the same to the data disk looks like. Man, what a mess. After this I need to find out why my connectivity is dropping!

Tried twice copy/paste, (hdparm -N p3907029168 /dev/sde) and ended up getting the same result each time. Think I should try seatools?

Server Motherboard is fine, its the desktop that was causing problems. my 1TB drives that have never touched the desktop are totally fine. Sigh. Ok I will go 1 at a time per your reccomendation. Thanks Joe! Any thoughts on my weird networking problems? I dont see issues in the syslog when transferring, so I am at a loss. EDIT: Looks like something went wrong. I used the command and rebooted, and now the drive shows up as 1.5TB. Should I use an external tool instead? http://dl.dropbox.com/u/519591/UNRAID/post%20HDPARM%20result.JPG

shameless self reply. Looks like my next steps are to use hdparm -N p3907029168 /dev/XYZ on all three drives since they are identical discs? My question now is how do I get back to normal operation? Do I toast the data drive and tell it to rebuild, and then toast the parity drive and rebuild parity drive again? Or since I dont care about the contents of the data disk, can I use HDPARM on both, and then just hit the button to start building a new parity? What about the one not in the array, can I just do HDPARM and then do preclear like normal? I still have that issue with my transfer drops too, but hopefully this would fix it? thanks all!

I have 3 2tb EARS drives I purchased recently. I needed to format them in my desktop before preclearing them on my server due to some weird shenanigans with it reporting only 1tb. Those issues have been fixed, but the NEW issue seems to be that when I formatted them in my desktop, my gigabyte motherboard (WHILE NOT NOTING ANYTHING IN THE BIOS) installed an HPA on all three. Now with the latest bios installed it has an option to disable HPA, but the damage is done and all three now have HPA on them. 2 of the drives are currently in the array, 1 is a data drive and 1 is parity. the third is connected to the system but hasn't gone through preclear yet.Anything I can do? some images and screenshots attached, along with syslog. Right now the drive in the data drive slow is unimportant so if I need to hose the data on the parity and data drive that is fine. DASH: http://dl.dropbox.com/u/519591/UNRAID/dash.JPG SYSLOG: http://dl.dropbox.com/u/519591/UNRAID/syslog-2011-01-29.txt Errors marked by Unmenu Jan 29 09:23:21 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Jan 29 09:23:21 Tower kernel: ata4.00: HPA detected: current 3907027055, native 3907029168 (Errors) Jan 29 09:23:21 Tower kernel: ata4.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133 (Drive related) Jan 29 09:23:21 Tower kernel: ata4.00: 3907027055 sectors, multi 0: LBA48 NCQ (depth 31/32) (Drive related) Jan 29 09:23:21 Tower kernel: ata4.00: configured for UDMA/133 (Drive related) Jan 29 09:23:21 Tower kernel: ata5.00: HPA detected: current 3907027055, native 3907029168 (Errors) Jan 29 09:23:21 Tower kernel: ata5.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133 (Drive related) Jan 29 09:23:21 Tower kernel: ata5.00: 3907027055 sectors, multi 0: LBA48 NCQ (depth 0/32) (Drive related) Jan 29 09:23:21 Tower kernel: ata5.01: HPA detected: current 3907027055, native 3907029168 (Errors) Jan 29 09:23:21 Tower kernel: ata5.01: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133 (Drive related) Jan 29 09:23:21 Tower kernel: ata5.01: 3907027055 sectors, multi 0: LBA48 NCQ (depth 0/32) (Drive related) Jan 29 09:23:21 Tower kernel: ata5.00: configured for UDMA/133 (Drive related) Jan 29 09:23:21 Tower kernel: ata5.01: configured for UDMA/133 (Drive related) I'm not sure if this is a related issue, but I have noticed my system likes to hang temporarily now when transferring files to the array. Here is a screenshot of my bandwidth when transferring a 6GB file to disk 5, you can see how it drops twice. http://dl.dropbox.com/u/519591/UNRAID/BW.JPG Thanks everyone for the help.

Would you run the check that doesn't correct correct errors, or can I just hit check on the stock UNRAID page? Many thanks as always Joe.

Hi you might remember me from fun posts such as "Why is my 2tb drive reporting as 1tb" and "I had to format this drive in partition magic to get all my space on a new drive wtf" Anyways 2 of my 3 drives have finished a 5 pass preclear, and as far as I see I think I am good. If I didnt have the formatting issue I'd just jam ahead, but thought why not ask. results + smart below: SDC ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VA LUE Seek_Error_Rate = 200 100 0 ok 0 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 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. ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 176 163 021 Pre-fail Always - 6191 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 20 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 150 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 17 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 25 194 Temperature_Celsius 0x0022 120 116 000 Old_age Always - 30 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SDD == Disk /dev/sdd has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VA LUE Seek_Error_Rate = 200 100 0 ok 0 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 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. SMARTT ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 176 166 021 Pre-fail Always - 6158 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 20 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 147 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 17 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 20 194 Temperature_Celsius 0x0022 119 115 000 Old_age Always - 31 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 So if we're good I am going to replace my parity drive and 1 data drive. Are my next steps to replace parity, rebuild, then replace a data drive, and rebuild one more time? thanks all!

Also a lot of times an external drive's warranty is much lower if it isn't voided when you open the case. You can open up a drive and then find out you only have a year warranty vs 3 or 5.

Did you just buy them recently? If you check out newegg, you see that a lot of people in the last month or so complained about DOA disks, but before that it was pretty good reviews. I think maybe WD did a really big bad batch of drives. I'm in the middle of a preclear of 3 of those drives- they all seem to respond, but I am doing heavy clearing/testing to ensure there's no issues down the road.

How do those cards work? I have an adaptec card that just has 4 SATA ports on it, but if I wanted to jump to more I may as well get one of those. Is it as simple as buying that + the breakout cable? Because holy shit if so. is there any performance degradation compared to using a card with the independent ports?

Damn. If that xbmc plays out of the box and has no missing functionality on the apple tv that is amazing...

I was kind of like that, I kept current on releases, but did NOTHING with the functionality. Then one day when I planned to upgrade disks I realized there was all these addons that I run windows counterparts on with my desktop. Now I am installing a cache drive just so I can run addons on it, I dont even care about the speed increase.

Fair enough, 5 cycles underway. Unfortunately I cant knock out all at once, but at least I can get 2 done. Then I get to preclear the last one. Then I get to replace parity and rebuild. Then i get to replace a disk and rebuild. Then i get to replace a disk and rebuild. Then do a parity check. See you all in a month.

I did the same to my other two drives (bought 3) and the fix also worked on them, go figure. I have 2 in the system now. I was going to do 3 for sure, do you think 5 is a little overkill? That's going to take like a week haha.

Alright, so W T F. Here's what I have done so far. Added disk to windows, reported only 1tb in windows xp (jumpered mind you) shut down, ran partition magic from DOS prompt who sees 2TB. Installed an NTFS partition across whole drive. Booted to windows. Windows sees 2TB (WHAT) Boot WD Diagnostic app, Sees 2TB. (WHATx2) Put drive back into UNRAID. Unraid sees 2TB (WHATx3) Here is an HDPARM full and what you asked for earlier (-N) along with a SMART, and what I see in PRECLEAR. /dev/sdc: max sectors = 3907027055/14715056(18446744073321613488?), HPA setting seems invalid (buggy kernel device driver?) HDPARM FULL: http://pastebin.com/TTbtRSUV SMART: http://pastebin.com/FvBkWY8s PRECLEAR: http://dl.dropbox.com/u/519591/UNRAID/Unreal.JPG So I mean, I guess I'm good if this passes preclear, right? Holy hell what a morning.

Haha, well shit. My server is old, its a HP Proliant 110ML so I wouldn't be surprised if there's something funny in the bios. If I drop the drive into my desktop (current tech) and it stays at 1TB then yeah theres a problem. If I do that and it DOES show up at 2TB, what would my next steps be? My bios in the server is pretty much up to date (there's an update but it has nothing to do with this issue and I'd rather not mess with it if I don't need to) and the SATA card has no issue with it, though it happens on both the mobo and the SATA card. If I format it in windows, will PRECLEAR still function or will it assume it has been "used" and not want to function? Or can I just run it again and it wipes it all clean? (Basically does it refuse to run if it finds a NTFS partition) I really hope these aren't fake/busted, they came from Newegg and Newegg usually doesn't do that kind of nonsense. At least I kept all the boxes in case I need to mail them back I suppose. Thanks as always for the help Joe.

SDD /dev/sdd: max sectors = 1953569134/14715056(18446744073321613488?), HPA setting seems invalid (buggy kernel device driver?) SDC /dev/sdc: max sectors = 1953569134/14715056(18446744073321613488?), HPA setting seems invalid (buggy kernel device driver?) I tried pulling the jumper just for grins to see if anything showed up differently, same deal though. I shut down and put in my 3rd (I bought 3) which showed up as SDC as well since I cant run all 3 at once. here is disk 3. /dev/sdc: max sectors = 1953569134/14715056(18446744073321613488?), HPA setting seems invalid (buggy kernel device driver?) they were all manufactured on the same date, and purchased from the same retailer, but I think thats kind of odd for them to all have the same issue dont you think? For grins, here is an HDPARM for one of my data drives, a WD 1tb BLACK model. http://pastebin.com/Mrhqb1F6 /dev/sda: max sectors = 1953525168/7368112(1953525168?), HPA setting seems invalid (buggy kernel device driver?) Yeah so I am at a loss. New server time? haha.

Here is a HDPARM for one of the disks, not sure if this helps... http://pastebin.com/TT3qfLQw User addressable sectors seems right, but the device size is still wrong.

Both. Both are sitting on a SATA card, maybe the card needs an update. Is there a command so I can cancel the preclear and get to the bottom of this? They're both in the post read process of the first cycle. or can I just close the telnet sessions and shut down? EDIT: I quit the telnet session and it reports under the cache drive as 1tb in unraid too. Yeeesh. I'll try booting it from the motherboard and see what happens vs the card. EDIT2: Looks like the motherboard reports the same thing. Not where to go from now!

I am trying to preclear 2 jumpered 2tb EARS drives I received today, but I noticed in the confirmation screen its only reporting 1TB. Is that normal, or is there something strange going on? Screenshot below. http://dl.dropbox.com/u/519591/UNRAID/huh.JPG Kind of concerned!

I ended up deciding to go with a cache drive just for a place to let sabnzbd sickbeard and couchpotato do their work, probably going to skip the user shares though.

That sounds great, I *hope* my server could handle writing to 2 drives at once. Thanks for the answers!