ljh89

You've managed to get a Raspberry Pi? Build looks good, I'd agree with neilt0 about the ram, a 4 GB kit cost around £18 at Scan. I wouldnt worry about getting an IDE compatable motherboard, just buy the add on card and then get rid once your drives give out or you upgrade to sata drives. You shouldnt need any additional cooling as long as the ambient room temp isnt too high. I kept my first sempron unraid in my bedroom at uni and it only needed the fans on while doing the parity check on warm days, was quiet too.

Did you add cd /boot/unmenu ./uu to your go file? Unmenu might not have actually started on your server after the reboot

Check your share settings t see if your are exporting disk shares, sounds like you have no user shares and are not exporting the disks. That would leave you with just the flash share.

There is a unRaid VM floating around on the forums for download, will save you some trouble getting it to work in the first place http://lime-technology.com/forum/index.php?topic=6260.0

Check your unraid server is on the same workgroup as your win7 pc, should show up once they are.

Would it not be eaier to replace parity with your new drive and then swap the old parity with disk 2? No need to reconstuct disk 5 then

He changes his board and cpu from 1155 to 1156 and no mixing them would not work.

Isnt that a line from unmenu that auto installs packages?

I wouldnt have thought it was that bug since you are still getting errors after a second parity check. Are you running non correcting checks? That would explain why the errors keep repeating. I'm not sure what else might be the problem. I'm reletivly new to unRAID and only know about the errors I got through experience

Have you tried reseating your RAM and all connections to harddrives? They tend to be causes of most parity errors. I also had an issue getting thousands of errors, when I worked out the error rate it came out at 1 in 4 once the number stopped increasing. After tearing my build apart and reinstalling everything I still got errors. It was only by chance I remembered I had inlocked the 2nd core on an AMD Sempron 140. Since my system was stable before I unlocked I hadnt bothered to check afterwards, luckily no data loss when I locked the core again. Have you made any hardware changes recently?

AFAIK the only time USB is used is when loading unraid os from the flash drive into the ram, after that your flash drive just sits there. Using USB 3.0 specifically wont speed anything up except load time and even that only fractionally.

The size of the cache drive limits how much data you can copy to the array before you need to invoke the mover script or lose the speed bonus. It all depends on what your keeping on your unraid and how often you add data.

I have my shares mapped as network drives in windows, I assume most people do. To see them type \\TOWER into windows explorer adn the shares should be visable. Then you can move all your data to the shares like you would between harddrives. To do this in linux I think you need to mount the shares but you'll have to find someone with a bit more knowledge than me for that.

Ive been using this one, http://www.scan.co.uk/products/asus-m4a78lt-m-amd-760g-am3-pci-e-20-%28x16%29-ddr3-1600-1800-sata-3gb-s-raid-micro-atx-vga, for a few months with no problems, I think one of Raj's Prototypes uses it too

I recently upgraded a couple of drives in my array, one data and the parity. Now after the data drive had been rebuilt the parity check reported no errors. Shut down and swapped out my parity for a larger drive and rebuilt again. Check parity again and this time get lots of sync errors. My first thought was a faulty drive so I swapped my parity back again to a known good drive. I assumed the sync errors woud go away after a couple of checks but they are still happening. It seems odd that the errors are always 1/4 of the array but I cant find out where they are coming from. I'm only using 3 drives (1TB Seagate, Samsung, Hitatchi) with 4.7. he array has mostly video files which are all playing correctly so I am assuming the data drives to be good and the parity being calculated incorrectly. Has anyone else had this sort of error? or know how to stop it? syslog-2011-07-30.txt

The drives are connected directly to the motherboard, I'll have another look in the bios in the morning see if the forcehdd could help.

Ive been using the free version of unraid for a few months now and so far I have been really impressed, enough to buy the plus licence. In preperation for the additional drives I installed a 3 in 2 hard drive caddie, http://www.scan.co.uk/products/icy-dock-mb973sp-b-sataiii-6gb-s-sata-backplane-up-to-3-drives that I had from an old pc. Now, when I reboot my unraid server the motherboard doesnt recognise the flash drive and I just get a black screen. If I switch off power to the hard drives it boots fine. Now initially I thought the bios had the boot priority wrong but booting to any hard drive is disabled. I've now offically run out of ideas. I'm using Asus M4A78LT-M motherboard with an AMD Sephron cpu. Any idea how to solve this issue?

+1 I'm quite lucky that Scan's warehouse is 2 minutes down the road from my house. Always had excellent service both with retailing and technical support

I build my first unraid system a few weeks ago and everything has been working fine as far as I could tell. I installed a a couple of addons, unmenu and an email notifier, and these all work fine. I had a quick look at the syslog and i noticed a few minor errors and one major one in the boot up. It isnt causing me any problems but I just want them gone! I'm using the 4.7 build of unraid and havnt used linux before so go easy on me if its a simple problem. syslog.txt