X1pheR

Ok thank you. I also remember that when I copied data from my old server (from RAID5 set so plenty of read speed) to unraid disk1 and disk2 over my gbit network it only went at around 40 MB/s. So that was without a parity drive added to the array. Also copying to the disk shares directly and not using user shares. Are these speeds to be expected? Without a parity drive added to the array you should get about the same speeds as with using a cache drive right? I removed the bad disk1 and replaced it with the warm spare. Then I used initconfig but just to be sure I'm running samsung's ES_Tool utility on all drives now. When they are all done and I've copied the contents for disk1 from my old server again I'll update. Thanks again for all answers.

Thank you both for replying. I was worried nobody would post anything I'll get started with it right away. Besides disk1, are the speeds during preclear_disk for Pre-Read (80 MB/s), Zeroing (50 MB/s) and Post-Read (21 MB/s) normal? Asking just to be sure since they seem low and also very different. Especially pre-read and post-read are like the same right? Only they differ 60 MB/s.

Is it possible this way to completely stop fans from spinning?

GREAT place to start Thanks

Hi, New user here. Just as a warning that the obvious may not seem that obvious to me personally I just discovered unraid little over a week ago now and after some reading on the forums, wiki and such I knew unraid was it for me and I decided to take the plunge and build my first unraid server with hardware from an old gaming pc I still had. I keep an actual overview updated with specs, config and such on google docs for myself but also for support reasons. This is the link. First off I started with a simultaneous preclear_disk of 4 new disks (logs attached). It lasted 32 hours without any errors. In the smartctl report I did however notice an increasing high count of "Hardware_ECC_Recovered" on all drives but after research this seems normal for these Samsung HD154UI drives (correct me if I'm wrong). During preclearing the disk temps didn't exceed 30 degrees and ran at 60 MB/s on average which did seem quite low (again, correct me if I'm wrong) but I would investigate later. The result for all 4 drives was about the same like: [color=blue]Preclear Successful ... Total time 33:08:00 ... Pre-Read time 5:12:22 (80 MB/s) ... Zeroing time 8:11:43 (50 MB/s) ... Post-Read time 19:42:51 (21 MB/s)[/color] Aren't these MB/s values rather low? Anyway. I created the array with adding 2 as data drives without parity drive and copied everything over from my old server. After completion I added the parity drive and started parity-sync. No errors still at this point. Parity sync went fine for a while starting at 110 MB/s and dropping a little to around 90 MB/s when suddenly the horror started. Suddenly it was only around a few hundred KB/s and Sync Errors started occuring and counting up rapidly. The syslog (attached) started showing loads of errors. In unmenu MyMain I checked syslog entries per disk. The parity disk seems normal. Disk 1 and 2 however both report many errors. Disk 4 is not in the array since I use the basic version and is spun down. When I look at smartctl reports per disk I however only see trouble with disk 1 (all disk smartctl reports attached). This rises several questions which I hope anybody can help me with; - What should I obviously do? - Is it so simple that disk1 is bad? Because syslog entries for disk2 also show many errors. Or is this because of the array. - All are new drives. everything went fine, even preclearing for 32 hours. now suddenly errors. is it disk, psu, mem, etc? where should I look. - Is data on disk1 bad and should I replace it with the warm spare (disk4) and rebuild or just copy all data over again from the old server. Please advice and thank you in advance.. UPDATE 1: The parity error count is 8222 now not building up anymore though syslog is still spitting out errors. I also attached a txt with the parity building progress at 3 times I checked. UPDATE 2: It eventually finished and now displays as parity being valid (is this true?). Unmenu says "Parity updated 8222 times to address sync errors". It didn't increase anymore. Anybody who would give me advice as to what to still do, what to check? UPDATE 3: I started a smartctl --test=long /dev/sd* on all disks. disk1 aborts after 20 seconds or so (tried several times). see report below. the other disks are still running the long test. SMART Self-test log structure revision number 1 [color=blue]Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 90% 86 1526120678 # 2 Extended offline Completed: read failure 90% 86 1526120671 # 3 Short offline Completed: read failure 20% 85 1526120671 # 4 Extended offline Aborted by host 90% 85 -[/color] preclear_reports.zip syslog-2011-09-05.zip smartctl_2011-09-05.zip parity_rebuilding_progress.txt

Seeing the date posted indeed Thanks though for replying. I saw them passing by on the physical console. I also rebooted and have not seen the messages since. I also use the free basic edition as I'm new to this all. I guess I'll wait it out Thanks again.

Did you ever find out what the problem was regarding to the error: /usr/sbin/nscd: relocation error: /usr/sbin/nscd: symbol __nss_services_lookup, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference I'm seeing this message 4 times now. Just set up with the b12 release and following the configuration tutorial. done nothing special yet. currently preclearing 4x disks.

Thank you. I thought I'd ask because of the much slower reported speeds. I'll go with b12 then. I recommend starting with 4.7 the Production Stable version and like you stated alot of reading. Once you see and understand the product and what if any extras you want to run, then move on to beta's if required. The learning cure is easier, my 2 cents. But if you want to go straight into the 5.0 Beta's then as Tom stated, you should always be testing under the lastest he has available. Thanks. Though I've already taken the plunge with b12. My current server has a RAID5 set with a drive failed. I searched the internet and by accident came across unraid. After some reading I knew unraid was for me. I already had hardware laying around to setup a new server and after some reading for what I am going to eventually do with unraid I see that 5.0 beta's is the way to go. Already preclearing 4x disks through screen right now. Keeping my thumbs up. No linux experience here, just following the configuration tutorial

Thank you. I thought I'd ask because of the much slower reported speeds. I'll go with b12 then.

I'm a new user who discovered unraid just a week ago. I'm still reading since there is so much of it Also going through my spare parts and seeing what I can use as an unraid server. Likewise I have to choose an unraid version to start with. Seeing the above regarding speed measurements, is it wise to start with b12 or should I do b11 instead?