Super_Chicken

Cable wiggling worked. Running the diagnostics gave me a 404 though.

Hi there, My disk 8 failed the other day and I've replaced it with a new 2tb drive. For whatever reason it is taking 24 days to rebuild going at <1mbps to repair. I'm assuming it's a slow connection somewhere. I have 2 esata 4 drive enclosures so I'm used to lousy speeds, but in this case it's exceptionally slow. Server log is too large to attach: https://www.dropbox.com/s/gsuhfbd9vjge5pm/server%20log.txt?dl=0

If you don't have your appdata in either a hidden folder on cache (name starting with .) or in a share set to Use cache disk: Only, then it will get moved to the array. Nothing to do with permissions. I have mine in an hidden folder (.programs and .downloads) I deleted the entire admin folder for SAB and it seems to have fixed it. I believe my history file (18tb) got corrupted.

Click into each drive on the right hand side and you can see which drives had which share. You will need to remake each share and tag each drive appropriately.

When did setting an appdata share as cache only become something to do? I got my unraid machine off a friend at V5 and has it on V6b12 for the longest time. I've upgraded to V6rc3 and now my sab no longer works due to the permissions issue and I feel this is the reason.

Offer open only to those who helped you or to all users in general? [/quote Ohoh, here come all the lurkers! I swapped out the second older sata card and hooked up the HP sas expander through the Areca, all drives are being recognized by unraid which is great.

Updated to RC3 and reloaded all my disks in. Started it up and everything is there. You guys are champs I appreciate the help. If anyone lived near Toronto I'd have you over for beer and steaks! Now that it's up, I'm going to check to make sure everything loads nicely. I may fiddle to see if these hard drives are recognized through my HP SAS expander, through the Areca. That would be ideal!

Thanks, I've followed the guide and names are now shown for all my drives. It looks like I am unable to start my array. It's showing that I have too many drives attached. Even when I none are in any of the drop downs. I'm wondering if changing hardware has corrupted my pro key?

It looks like it's a similar issue like this one: http://lime-technology.com/forum/index.php?topic=30956.0 Except it's when I have more than 8-9 drives. I took out the two 4tb drives and the rest still went unrecognized.

So in testing this out, it looks like moving the drives from one to the other is fine. I did it using a demo license and 3 hard drives, moved data onto the disks and moved from one machine to another and no problems. In moving over my actual hardware it now looks like I'm encountering the following issue. The areca/HP sas expander is able to pass on all 21 drives (1 cache, 1 parity, 19 data drives). During my test scenario with 21 other drives, windows was able to see them. Then when I tested with 3 of those test drives they worked fine in unraid. However it looks like unraid is unable to resolve more than 8/9 of them, giving them wonky "(sd#)" titles and not showing the actual serial's. So I cannot line up the data drives the way they previously were. Any advice?

Absolutely, I'll test tonight on a separate machine and report my findings. While I putter around in the demo environment I may upgrade to RC3 on my main server. Thanks for the help.

Okay awesome, I just worry because my test with the areca was to confirm that it sees the hard drives and they wake up and sleep nicely. I don't want to port all the hard drives and USB key over to the new H/W only to boot it up and then have unraid see nothing. Then when I JBOD each one on the areca, they are passed through but unraid tries to format them for whatever reason. Then if I have to move them back to the old hardware they may still not work and I'm left losing everything. (I have the important stuff backed up, but I'd rather not rerip and re-encode all my media. I do have 3 machines ( including the future areca server), that I suppose I could run the demo on with 3 drives, then move them to new hardware to see if it still boots up and plays nicely with the areca, before doing it on my system. Also provided the above works beautifully, does anyone foresee any problems upgrading to RC3 first. Then attempting to move over all the hardware? I'm currently using APC on v6 now and noticed it doesn't work as nicely on v5 either, so ultimately I don't need the stable v5 version.

My current Unraid 6b12 system is currently on an older motherboard, cpu etc. I had got it from a friend and had issues day one with it and how he set up sab and sickbeard and couch potato. The hard drives (4tb, 3tb, 2tb) are connected through the mobo sata spots, pci sas cards, pci sata cards, esata drive enclosures etc. It's a mess and it's slow and inconsistent when moving files around. I currently got new hardware, including an areca 1880i and hp sas expander off a friend who was using it for another server running windows with areca doing the raid. I ran the demo of the stable unraid 5 on the areca hardware with a few spare hard drives connected to the areca in JBOD passthough and it's been stable for the last 2 months. I'm just wondering what is the best way of porting over all my existing data to the new system? The two options I'm thinking are as follows: 1) Buy a second usb key with another pro license. Load the areca with a 3-4 new 4tb drives, and migrate the data over from my old server. As I empty drives off my current server, pull them and add them into the new server. This would be the most time consuming, but I have all the important data already backed up. 2) The second option and I'm not sure if I can do this or not. Would simply be to move all the hard drives over, as well as my existing usb and it boots up and recognizes all the drives. I'm unsure if my areca doing JBOD would cause unraid to see the drive any differently causing them to not be recognized. I appreciate any feedback from others who have done this and have any experience with using an areca for unraid. I had read some stories about compatibility between unraid and areca cards being used. I am also still on the fence if I should use unraid 5.0.6 stable, or the latest unraid 6. I only use APC, sab, sick beard, couch potato, and would eventually use plex and crashplan down the line.

So to followup and mark this as solved. It looks like the issue was in my Go script. "cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c" for whatever reason was at the bottom. I originally had it commented out. With it commented out I can boot and it will auto start the array load my services and mount the shares no problem. No hick-ups at anymore. Thanks for your help!

Yeah, I'm tempted to move everything off the server for now and start fresh on it. This way I can figure out what's going on from the get-go versus slowly figuring stuff out as my friend decides to enlighten me about it. Thanks for your help.

So go is autorun even if the array is not auto started? I have to ask my friend why I would have to manually start go to get the extra services to work as well then. Is running it a second time the issue that is causing tower:80 to no longer load? And if so what has changed from 10 to 12 that is now causing this?

Sorry the attachments were originally too large so I had trimmed the wrong one. I fixed them both in the zip now. - The "works fine" is the full log. - The "broken after go" is a copy along with the new lines after running the go script. What I'm doing is I boot the PC. wait about 7-10 minutes to be able to log into "tower:80" on a browser. I then start the array (I don't have it auto starting). The shares then work and I can access files, as intended. But from what my friend instructed me the services haven't started. Thus I'll log into Tower and use "cd ../boot/config" "go" to run the go script to start up sabnzb, sickbeard, and couch potato, and a few others. This was what I would do and all would be fine in B10, but in B12 it now crashes the tower:80 so I can no longer spin down and power down the server safely using the web gui.

So my friend gave me his server and it's been running fine. He came over and updated beta 6 from to 10 to 12. As well as sabnzb and a few other plugins. The array and shares still work same as before. I like the new look on tower:80, and tower:8080 perform both the same. As soon as I telnet in and run the "go" script it kills the tower:80 page fully. Attached are my two log sessions, the first is normal operation. Then I ran the "go" script and you can see the difference in just the bottom lines. Anyone have recommendations on how to begin trouble shooting this to correct the problem. syslog-2014-12-15.zip

I'm having the same issue. A friend of mine gave me his unraid server and went and updated everything before giving me it. It was on v6 10 and moved up to 12. Now after running the go script the tower:80 will stop working after about 20 minutes. 8080 will continue to work no problem, along with shares and everything else.