adrianz

Is that disk on a different controller than the rest? I had the same problem with 4.7 to 5 ages ago (was 4 disks too -- had to rebuild with clean disks and move the data back over). All 4 disks were on a controller that went through a massive driver rewrite so the labels were different. Yes, this disk is on a 2port sata card together with the cache drive, i've rebuild the disk now so it's fixed What is this card name/type? I have one 2-port PCIe x1 Sil3132-based controller with two data drives attached, so that makes me worried :-(

With an update to version 2.42? :-)

Transmission has been updated to version 2.41 https://trac.transmissionbt.com/wiki/Changes#version-2.41 Just sayin' :-)

I've installed glibc before you edited your post and even with the old .conf file Transmission seems to work now :-) I'll try the new package in the morning because it's getting late in CEST time zone.

We're nearly there :-) After installing this package curl seems to be installed properly now, but I still have problem with transmission package, but a different one: /usr/bin/transmission-daemon: /lib/libc.so.6: version `GLIBC_2.11' not found (required by /usr/bin/transmission-daemon) and status: And of course I'd like to thank you, prostuff1, because you're doing an amazing job!

Few problems on unRAID 4.7: When I try to install transmission package I allways get this /usr/bin/transmission-daemon: error while loading shared libraries: libldap-2.4.so.2: cannot open shared object file: No such file or directory In addition to that Transmisssion package has this status: and I can't set the reinstall on reboot option. Same thing with curl package: I don't see the transmission process in top and of course I can't connect to the Web UI :-( Any ideas? I have never installed transmission befor

Yes, there is one ( http://lime-technology.com/wiki/index.php?title=Installing_VirtualBox_in_unRAID ) and judging from the previous posts it's a very good one, but unfortunatelly it misses on some details and background info that is probably obvious for someone who knows his/her way around linux better than I do. Never mind. I'm creating Slackware 12.2 VM on my workstation PC now and we will see later if I have any luck with compiling :-)

Hmmm… an interesting thought. Is Ubuntu OK or do I need a specific linux distro?

I’m thinking about buying this motherboard: http://www.gigabyte.com/products/product-page.aspx?pid=3807#sp and on paper it looks OK. Support for 3TB+ drives, Realtek NIC, 6 onboard SATA ports + 8 from 4 PCIe x1 Sil3132 adapters + 8 from Supermicro AOC-SASLP-MV8 in PCIe x16 slot. Although it has the Backup BIOS Image to HDD function (that nasty HPA thing) enabled by default it can be easily turned off. It also doesn’t have an integrated graphics but for me it’s just a minor inconvenience, not a problem. What do you think?

Hello, First of all, thanks for this great guide. I’m going to install VirtualBox on my unRAID server but I’m waiting for an additional RAM to be delivered. In the meantime I would be very thankful if you could answer some of my questions (sorry, linux newbie here). 1. Does VirtualBox write on flash drive very often? I know it was a problem for the Transmission package and I’ve read the whole thread and found that the web server causes a great number of writes , but if I’m not going to use it I won’t have to worry about my flash drive, right? 2. I have a spare HDD outside of the array that I want to use for non-unRAID purposes like VirtualBox. How should I modify the installation scripts so they use that drive for temporary installation files storage, etc.? 3. Do I need to mount that drive every time I reboot my server (after I create some virtual machines on it)? Because I know that every drive has its own name assigned (sda, sdb, etc.) but sometimes when I add additional drives those names change. unRAID seems to work with that just fine, but what will happen when I create virtual machine on my non-array drive, then I add a HDD to unRAID and it gets the non-array disk’s name? Will VirtualBox be able to recognize that and look for the virtual machine file on the proper drive? 4. Is there any “clean-up” procedure necessary after the installation? Will the kernel source, gcc, etc. be removed automatically after the installation/reboot? 5. Do you think that 4GB RAM and 2.7GHz single core Sempron should be enough for unRAID, unmenu, cache_dirs and one VM – striped down Ubuntu with lxde working 24/7 (Transmission, jDownloader, maybe a lighttpd/php5/mysql server)? I can try to unlock a second core in my Sepron if that would make a noticeable difference. 6. How long does this whole procedure take time (without downloading)? Are we talking minutes or hours? 7. What about upgrading and uninstalling VirtualBox? Is it also that complicated? 8. And the most important one – is my data/unRAID configuration going to be safe during the installation. Should I be extra careful at any particular step?

I know I CAN access my data from the unRAID server during a parity check and probably also write some files to the array, but does it mean I SHOULD do that?

Thanks dgaschk , but I think I messed up After I disconnected the old parity drive from the motherboard I powered up the server and checked the http://tower where I saw ST2000DL300 already assigned to the parity slot (it had blue dot if I'm not mistaken). I thought at that moment unRAID is clever and already forgot about the old parity so I checked the box and pressed the Start button. Now it's finishing Parity-Sync (30 minutes left), so after the parity check i'm going to reconnect the old parity drive and add the second ST2000DL300. But now I think because there was now "missing the parity drive" moment unRAID didn't forget about the old parity drive and may do some strange things when I connect it. Should I be worried? Do I need to do something now, like "Trust my array" procedure?

Hello! Here's my setup: Parity: 2TB WD20EARS Data: 2 × 2TB WD20EARS (disk1 and disk2), 1 × 1TB WD10EARS (disk3), 1 × 2TB HD204UI (disk4) Cache: 2,5" 160GB Samsung HM160HI All of these drives are connected to the motherboard's SATA controller. I need to upgrade my parity drive because it's the slowest drive in my array (it's an old, four-platter version). I already have a new Seagate ST2000DL300 (2TB Barracuda Green) precleared and connected to a Si3132-based 2 ports PCIe x1 SATA controller and a second ST2000DL300 still in a box. I want to use the first ST2000DL300 and replace the old parity drive, then preclear former parity drive (WD20EARS) and use it to upgrade disk3 and then add the second ST2000DL300 to the array and fill the sixth slot form my Plus licence. I'm planning to acomplish all of this with these steps: 1. Parity check 2. Stop the array 3. Power down the server 4. Disconnect the old parity from motherboard and connect the already preacleared ST2000DL300 to that SATA port 5. Disconnect the disk3 from motherboard and connect the old parity to that SATA port 6. Install the second ST2000DL300 and connect it to the Si3132 controller 7. Connect disk3 to the Si3132 controller 8. Power up the server 9. On the Devices tab assign new parity drive to the first ST2000DL300 and the rest of the drive exactly as they used to be (except the old parity, ofcourse - it will be unassigned) 10. Start the array so the parity data can be written to the new drive 11. Start the preclear of the second ST2000DL300 12. When the new parity drive is ready, start preclearing the old one (this time without a jumper) 13. When step 12 is done, stop the array 14. On the Devices tab assign disk3 slot to the old parity drive 15. Start the array so the rebuilding of the data from the old disk3 can begun on the new one 16. When the rebuilding is completed, stop the array for the last time 17. Assign the second ST2000DL300 to the disk5 slot 18. Start the array and wait untill the recalculating of the parity data is finished 19. Lean back and relax because the upgrade is finished Is that OK? Did I miss something? Can I safely perform the upgrade using these steps? Please advise

I understand that, but I'm wondering why for the past 8 months every drive was in a separate group and then out of the blue two of them share a group? Is adding a NIC responsible fot that? How can it be?

Thanks! They were in the same group, so this should help. I've heard about spinup groups but have never used them. I've checked Devices and Shares tabs on my unRAID webpage when I realised what was happening but didn't see anything that could help or be relevant. Only when you point out this I did proper research on wiki and found about links on the Main tab and assigned different spinup groups. But one thing still bothers me - how did this happened in the first place?

Hello! At the moment I have four data drives in my array and around the time I have replaced my on-board NIC with Intel PRO/1000 GT (about a week ago) one very strange thing started to happening. Whenever I try to open a file from disk 4 unRAID automatically spins up drive 3 for no reason because 99% of my data are video files and when I stream it to XBMC I don't see why my player may need to look at something else than requested movie. At least it wasn't neccesary for the last 8 months. Additionally disk 3 spins down at the same time disk 4 does. Can you help me with that? All of the drives are connected to the motherboard's SATA controller. I'm especially worried because I want to replace my parity drive with a faster one, use the old one to upgrade my disk 3 (1TB) and finally add another new 2TB HDD so I can max out my Plus licence. Current specs in my board's signature Syslog: http://cl.ly/8w7f P.S. Sorry for my english - it's not my native language :-)

The drive I just received from NewEgg had a new label design on it and a manufacturing date of 5/11. I think they should surely have fixed it now, but I'm still a little hesitant to use it without flashing it with JP1. I guess I will check its firmware version first. Maybe Sammy has an even newer firmware not available for download that they are using now. At some point in time, JP1 may start making you flash backwards, or start causing problems. Call me an idiot, a daredevil or whatever you want but I've decided NOT to flash my Samsung F4 manufactured in march 2011. I've done all the testing suggested by those SMART utility devs and I couldn't reproduce this bug so I decided to give it a shot. After nearly two months and 1TB of data later I must say that everything is working OK. I'm using my unRAID for storing large Blu-ray rips and streaming them to XBMC and I've been doing great (no glitches, no unreadable files, etc.). Although I would like to test it in a more scientific manner. I have some original files and I want to compare them to the unRAID copies but don't know how to do that in a way that will reveal this particular firmware problem (if it still exists, of course). Any ideas?

Hello! I've recently bought Samsung 2TB HD204UI manufactured in 2011 with serial number different than those listed on Synology wiki, so it should be OK. I know that everyone here recommends flashing this drive with Japanese firmware, but I don't believe messing with firmware when it's not necessarily is a good idea. But to be sure I would like to try to reproduce this bug using instructions found on this webpage: http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlocks. I already have grml 2010.12 Live USB, and don't mind getting my hands dirty with command line, although I have no idea how to check NCQ and disk write cache is enabled on my system - any ideas?

root@Tower:~# hdparm -N /dev/sde /dev/sde: max sectors = 1953525168/7368112, HPA setting seems invalid It looks like I should be fine :-) Now I only have to write a how-to for wiki :-)

OK, I tried to remove HPA from my disk earlier today and I think I've succeeded. First of all I've check parity without correcting – zero errors. Then I stopped the array and executed hdparm -N p1953525168 /dev/sde. The thing is I didn't know (and still don't) what to expect. So I pressed [Enter] and unRAID returned this: /dev/sde: setting max visible sectors to 1953525168 (permanent) max sectors = 1953525168/7368112, HPA setting seems invalid I've tried hdparm -N /dev/sde and all I got was the last line from the previous command. I was pretty confused at that moment because response was (at least for me) inconclusive. After that I decide to reboot my computer using HDAT2 boot CD, but this program clearly stated that WD10EARS does not have HPA. When I rebooted array was stopped and unRAID reported new disk (orange dot). To start the array I had to tick the checkbox, so the data rebuilding could be started. And after about five hours – zero errors. The final step was a parity check but this time with correcting. And here a strange thing happened – I was told to expect some errors but once again unRAID stated that everything went fine. So now I'm a little worried. Is my disk HPA-free or did I screw something up?

OK, so what should I do now? I've done a small research on the forum and found some info but I don't feel very comfortable with this. Would you mind helping me, please? :-) I've check my syslog and found this: Dec 10 15:38:06 Tower kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Dec 10 15:38:06 Tower kernel: ata5.00: HPA detected: current 1953523055, native 1953525168 Dec 10 15:38:06 Tower kernel: ata5.00: ATA-8: WDC WD10EARS-00Y5B1, 80.00A80, max UDMA/133 Dec 10 15:38:06 Tower kernel: ata5.00: 1953523055 sectors, multi 0: LBA48 NCQ (depth 31/32), AA Dec 10 15:38:06 Tower kernel: ata5.00: configured for UDMA/133 I've seen it before, but I thought preclear could handle this. Never mind. Now I need to connect to my server via telnet and execute these commands, right? hdparm -N p1953525168 /dev/sde hdparm -N /dev/sde But shall I stop the array first? Parity check? Do I need to remove this disk form the array or restart my server? Will my data left intact? If not – can it be rebuild automatically? Or should I do that manually in some special way? How long you think it will take (1TB drive but only 15GB of data)? Do I need to preclear this disk after removing HPA? Does HPA on this disk corrupts in any way my parity data? I've been using unRAID for about 4 months (1,5 with this drive) and never had any errors after parity check. I would be really thankful for step-by-step instructions. And I promise to put them on the wiki by the end of the week :-)

So, does it? I have one disk in my unRAID array that previously used to be in my Gigabyte-based HTPC with HPA turned on. When I was adding this disk to my unRAID I assumed that preclear deals with this problem. But while I was reading the unRAID 4.7 announcement thread I saw that some people have problems with HPA reappearing after the update, so it made me wonder. So can you confirm that preclear removes HPA?

I'm going to buy my first UPS for my first unRAID build (Sempron 140, 6 WD Green HDDs, Corsair vx450w PSU) and I'm thinking about APC Back-UPS RS Pro 550 ( http://www.apc.com/products/resource/include/techspec_index.cfm?base_sku=BR550GI&total_watts=300 ) – is it enough for my build? I don't have long blackouts in my neighbourhood but 1-2 seconds long power outages are quite common. So I need it to keep powering my server for about a minute and after that to send shutting-down signal to unRAID. Is 550VA enough for 6 HDDs? If yes, how many additional drives I can safely add?

Yeah, I'm an Intel guy ;-) Where I live the cheapest socket 1156 combo is 40% more expensive than E3300 + Asus P5QL-CM. And thanks for the heads-up, Rajahal – I won't have any problem with returnig vx450w and my unRAID won't be a mission-critical server, so I think I'll stay with this model.

Wow! Thanks for all your comments – unRAID has a great community! I've done a proper research this time and found Asus P5QL-CM http://www.asus.com/product.aspx?P_ID=KO1Q2EGHFX3qBo5U&templete=2 – it's a little bit more expensive and has more power hungry chipset (G43) but it supports 6 SATAII ports out-of-the-box and has Realtek NIC. What do you think? Do Asus boards have problems similar to Gigabyte's HPA?