fitbrit

In unmenu's MyMain the disk 10 has HPA? next to it, and shows up as Unknown 4T.

Part two of syslog syslog-2013-05-31_part_2.txt

Recently a couple of 2TB drives started showing up as read-only. I decided to replace them with 3 and 4 TB drives, and then check the old drives and maybe preclear and add them back to the array if they are ok. Today I replaced disk10, a Hitachi 2TB, with a Seagate 4 TB drive. My Parity drive is a 4 TB WD Black drive. The new Seagate drive was recognised immediately. On the Main page I try to check the box and start the array, to rebuild the data. However, instead of starting the process, unraid returns me to the same screen again with the array stopped ad infinitum. Is there anything I can do? Any clues as to what might be happening? Syslog attached. Is unraid rejecting the new disk because it possibly appears to be larger than the parity, for example? (It shows 4Tb for both). syslog-2013-05-31_part_1.txt

Thanks for the advice. I might try that eventually. I have a decent WD Black drive as parity and it would be a shame to choke it. However, the fact remains that the parity check speed is slower in RC8, with the same config as I currently have, compared to RC4.

My parity drive is on the motherboard, which is what I believed is the best way to do it.

Sorry, was away for a few days. Hardware: Norco 4224. 20 data drives, now mostly Hitachi 2 TB Green, some 1.5 TB WD Greens (EADS). Parity is a 2TB WD Black Asus P5Q Premium motherboard 2x AOC-SASLP-MV8 Controllers Parity, plus drives 1-9 are on mobo, the rest on the PCIex4 controllers.

I just installed RC8, and noticed that parity check speed is a painful 25 MBps compared with the 40 MBps of RC4. Anyone else seeing this?

Thank you very much for your response. Sorry it took me so long to see this.

Update: I am back to 5rc3, and disks are showing again. Still wondering what's up, though.

Background I upgraded from 4.7 to 5rc3. I had some problems with being able to access the user shares, had to keep remapping them to drives etc. I decided to go back to 4.7 while trying to get answers here on what I may have done wrong. I copied over bzimage and bzroot. Restarted and suddenly all disks were redballed. Under devices, the disks are all in the correct places and are assigned the right slots. See attachment in next message. I deleted the shadow, password and smbpassword files from the flash/config folder, suspecting that these files from 5rc3 may be interfering with the ability of 4.7 to see the disks properly. No go. I tried copying the 5rc3 bzroot and bzimage files back, hoping to get a clean start again. That too showed all disks as missing. Finally, I went back to 4.7. I'm assuming that I just need to run an "initconfig - trust my parity" to get back to normal. However, I don't want to do it without getting the experts to give em the go-ahead. Thanks for any comments/suggestions. syslog.txt

I'm migrating my current server with 20 data disks + parity + cache to a new Norco 4224 case. The PSU I've chosen is this: http://www.corsair.com/power-supply-units/professional-series-gold-power-supply-units/professional-series-gold-ax750-80-plus-gold-certified-fully-modular-power-supply.html It has 62A on a single +12V rail I'll be running two supermicro PCIex4 SAS port cards, plus 8 drives off the motherboard. Should this PSU have sufficient power for all drives and fans in a standard 4224? Thanks for any opinions/ recommendations.

Oh... not available in Canadian iTunes store.

Using the microphone? Ah... yes, very cool! Thanks for the response.

Sounds very cool, but I don't want to have to transfer files to my iPhone first. Would be great working on a PC. Could be good for unRAID to when one has to fix a ReiserFS and is left with meaninglessly labeled video files in Lost&Found.

Hi Peter, May I ask why you specifically asked about the Antec PSU. My current server PSU is an Antec 650W, and I've had a few problems with multiple simultaneous failed disks and other errors. I'm switching the whole server to new hardware shortly, including a better PSU, but I just wondered whether you'd encountered inherent problems with the Antecs. Sorry for threadjack, OP. There have been 2 or 3 others who have reported odd disk issues here that went away after replacing their Antec supply. Peter Thanks for the information. I'll relegate my Antec to HTPC use eventually, where no real data is actually stored.

Hi Peter, May I ask why you specifically asked about the Antec PSU. My current server PSU is an Antec 650W, and I've had a few problems with multiple simultaneous failed disks and other errors. I'm switching the whole server to new hardware shortly, including a better PSU, but I just wondered whether you'd encountered inherent problems with the Antecs. Sorry for threadjack, OP.

I just replaced the failed disk too. After the rebuild, I got this in the main window: (Last checked on 2/15/2012 10:31:32 AM, finding 7621830 errors.) Unmenu says: Parity updated 7621830 times to address sync errors. Should I be worried? Is my (greenballed) array protected now, at least? I'm prepared to have lost some data from before; it's from here on out that I'm concerned. None of the drives showed any errors during the rebuild. Should I be worried. Log file attached. I have a lot of duplicate files, notifications of which have been removed from the end of the syslog.. syslog.txt

Thanks, guys. I've rebuilt the filesystem... almost done.

I had a corrupted ReiserFS on one disk and another failed before I could fix it. I have transferred as much data from these drives to external ones as I could. Some files failed, and I'm ok with this. Now the question is how to proceed. Should I repair the FS first (only fixable with rebuild tree), or try to rebuild the data of the failed drive first?

Off-topic... is this RFD willy?

The external boxes have been great. It's the PITA internal drives that have been a bugger and dying frequently. I'm looking forward to my 4224 becoming operational soon!

Well it seems that the drive is now redballed. No SMART data. No idea what went wrong with it, but that's the fourth WD drive to redball in one week. I guess I'll just remove it, see what data I can recover off it and add back to the other array disks. For sure I cannot rebuild this disk properly because at least 3.3% of it wasn't able to be read when building parity, and if I'm right that could mean any number of files were affected if they're written in a fragmented way, right?

I'm really sorry - somehow some information got lost from my original post, above the code excerpt from the syslog. I must have accidentally deleted it during an edit. I'll fix it.

Any recommendations on how to proceed are welcomed.

Now that the 75% mark has been passed (over the 1.5TB point), the errors have stopped and parity is being written to again as expected. Any solutions? Should I replace the drive after parity is built, and recover most of the data that way. Then see what I can get out of the drive, from the 18-20 GB that were not able to be read during parity build, by other means?