Spudkins

hmm odd. Ok so i deleted the old supervisord log and took a fresh screenshot of my settings just before starting the docker which generated this supervisord.log. Hopefully those match now supervisord.txt

I wonder if anyone can help, i'm trying to set this up with SlickVPN but having no luck i believe I've entered all the settings correct and placed the ovpn file in the correct place but no matter what i do or change i cant get the web ui to load so i guess I've done something wrong i cant see. gw1.fra2.slickvpn.com.txt supervisord.txt

well i tried swapping the drive location to use the cable from my parity drive but it is still Unmountable. haven't tried running a reiserfsck with it connected differently.

your right, once i ran it with partition number reiserfsck --check /dev/sdf1 i got the following output The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (1344): (Input/output error).

Ok so i followed that link and worked through it, reiserfsck --fix-fixable was a no go and it is recommending a rebuild. the wiki page talks about the answers needing to be perfect so i guess i need help from someone with more experience, not sure what options need to be selected.

just deactivated my parity and used the cable from that for my cache, disk is still unmountable

My luck of late seems to stink, my server was running smoothly for the last 4 years. However these last 2 weeks everything seems to want to break. I had just copied about 100gb of data over to my cache and was watching something that hadn't been moved over to the array yet when i heard a beeping coming from my box, i shut it down to investiage. Upon restarting i noticed my cache is showing as unmountable and unraid is asking me to format it. Not sure if they drive is totally dead or what. i have attached a SMART extended self test result which is showing some read failures. anyway to salvage what is on the disk? VB0250EAVER_9VMXPV81-20151116-2247.txt

Thank you all, you have all been very helpful. Old drive is back in and parity-sync is underway. Looking through my user shares all my data is there so i haven't lost anything which is good. As my wife just pointed out to me when she saw my post count i've been a member/reader of the forum since 2011 but until a week ago never had a need to make a post. I was in no doubt someone would come to my rescue. My daughter would thank you all too if she could, she was a bit disappointed when she couldn't watch the AristoCats for the 100th time today as it was on the old disk1 keep being awesome people!

hold on, i just thought of something, when you say make sure parity is old parity. Hasn't it been changed since removing old drive when i formatted the new drive? during step 4 will it rebuild parity with the data from the disks or rebuild disks with parity data which would be missing everything that was on the old disk wouldn't it?

Thanks, sounds fairly straight forward, hopefully i wont be able to able to find new ways to mess it up further and i can turn this flub up into a nice learning experience

Ahh thank you trurl, that makes sense Right as i'm not comfortable using CLI and i cant seem to view my individual drives i'm going to go with johnnie.black's suggestion and put my old disk back in. I presume the new config is needed to stop the old disk being rebuilt with the new blank disks contents when it is reassigned to disk 1. so couple of questions before i do this in case i mess up anything else. my new config steps should be 1. shut down array and replace disk1 with the old disk 2. start up server and reassign the old disk but not start the array (which would start a rebuild wouldn't it) 3. go into tools > new config 4. then go and start array and do a new parity sync is that the right steps to take? also would i be best formatting the replacement drive back to reiserf now before i do the new config/put old disk back in? just thinking so i dont have to worry about formatting when my parity has been resynced and messing it up again. But then i should be safe as i will be formatting it as a none assigned disk so it shouldn't sync with parity until its added. Sorry i just want to be extra safe so i'm imagining the worse

Thank you for the reply. Ah so basically my parity was updated to remove the files that were stored on disk1 after the the empty new disk was formatted. Trying to think of the easiest way to mount the old disk. My server has a cache drive which i guess i could disable and then use that slot for the old disk. I should be able to start the array with the old disk added as a none assigned drive right? then for the actual copying of the date, when i upgraded my sever from v5 to v6 i lost the ability to see the individual drives when i view my server in windows file explorer, i can only see my user share. i would feel most comfortable copying files from disks using windows interface but i guess i could use unraid CLI i.e cp -r -v /mnt/sdf /mnt/sdb where sdb is my new disk1 and sdf is my cache drive i would replace with the old drive. would that be the best method/code to use?

Help, I'm not sure what i did wrong but i upgraded one of my drives for a larger one. However after the data rebuild the disk is still completely empty. How do i recover the data from the old disk? i still have the old disk which should still have all the original data on and my parity should still be from the check i did just before replacing the disk so surely its still on there as well. i would really appreciate any advice or help thank you. Edit: ok i think i know where i flubbed up, i formatted the replacement drive as xfs when the old one was reiserf i read in https://lime-technology.com/forum/index.php?topic=37490.0 how that would cause a problem. so my new question is can i reformat the drive back to reiserf and somehow do the rebuild again? or is the data gone as the new disk has be mounted and accepted into the array.

Thank you, got it fixed had a look in network settings and saw DNS settings were wrong, changed and now I can install plugins and docker list is populated

Hello, so i took the plunge and upgraded my server to v6 but ran into some problems getting everything up and running. So i started on the docker guide as i wanted to set up sabnzbd/sickrage again but i cant seem to install any dockers or plugins. I added the repositories but when i click add container and try to select a template i have nothing to select. Its worth noting that i also tried to install the powerdown plugin but that didn't seem to complete and the 'check for updates' on plugin tab doesn't result in more than 1 line of text so i'm not sure if its a connection problem with my server. Any help would be greatly appreciated, i'm one of those people that set up my server years ago and it just worked so never really had a reason to mess around with it so my knowledge level is in the 'noob' range Some screenshots in case my description isn't clear enough: https://dl.dropboxusercontent.com/u/55712704/Screenshot%20(3).png https://dl.dropboxusercontent.com/u/55712704/Screenshot%20(4).png Edit: while not an error message seen on the docker tab this is the result i mentioned when trying to add a plugin plugin: installing: https://github.com/dlandon/unraid-snap/raw/master/powerdown-x86_64.plg plugin: downloading https://github.com/dlandon/unraid-snap/raw/master/powerdown-x86_64.plg plugin: downloading: https://github.com/dlandon/unraid-snap/raw/master/powerdown-x86_64.plg ... done Warning: simplexml_load_file(): /tmp/plugins/powerdown-x86_64.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): /tmp/plugins/powerdown-x86_64.plg:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 plugin: xml parse error