fonzie

So is this fork of sonarr designed strictly for movies or will it also work for TV shows? I'm just wondering if it is only a couchpotato replacement or also a sonarr replacement.

Are you saying that if I were to replace a failed drive with a new one, I don't have to run a preclear? Can I simply "Verify all the Disk" on the preclear plugin to test the new drive and immediately start rebuilding?

I use this all the time to write NTFS drives. This plugin only mounts the drive so unRAID can access it, and possibly share it on the network. The copying part is up to you. Do you know how to do the copy? No, I do not know how to do the copy. I would like some kind of command line to input so that unRAID will do the move for me. I feel that this would be the fastest way. The only way I would know how to do it is by mounting the drive and then accessing it remotely through Windows Explorer, but that would defeat the purpose of mounting it in unRAID in the first place because Windows Explorer would work as the "middle man" and cause the copy to bottleneck.

I want to temporarily put my empty NTFS Windows hard drive in my unRAID and set it up as an unassigned disk to quickly copy my media from my unRAID onto this disk. Then I want to put that disk back into my Windows machine and have it read it. Is this the proper plugin to accomplish that? If so, what are the steps to make sure this goes smoothly? The reason I want to put it directly in my unRAID machine for the copy is because my network transfer speed is too slow and I have a lot of data to copy over. thanks

I installed this plugin for two purposes: 1.) changing file system from reiserfs to xfs 2.) replacing cache drive without losing information Now after reading through this thread, I realize that this plugin is perfect for my first goal, but I don't think is capable of helping me out with my second goal. I don't see the ability to transfer anything from a cache share, so I'm assuming that's not possible. I want to know what the easiest way of transferring all of my current files that I have running on my cache drive (appdata, downloads, etc) to a disk drive temporarily while I add a new cache drive and format it as xfs. A plugin or docker would be best. Using MC is a little too advanced for me and I don't really grasp command line very well. if unBALANCED can be used for this, please let me know how. thanks.

So looking at the diagnostics file it seems my cache is still throwing out erros, even though unraids file system check showed it was okay. What I want to do is replace my current 500gb reiserfs cache with a new 500gb cache formatted in btrfs. I want to transfer all the current files from my cache drive over to the new one so I don't lose docker settings, etc. First I need to gain write access back to my unRAID and then I'd like to know the steps to do this. I noticed a plugin that was made for this...would it be a good time to use it?

The never ending struggle! It's been a few days since I got everything working, but yesterday my shares reverted to being read-only again!!! I ran reiserfsck on all the disks and none of them came back with corruptions this time (not even the cache). Not sure what the problem could be now. I have attached the latest diagnostics zip: https://drive.google.com/file/d/0BwIaL8ycjqj2b2dNdGVhZjlSYVU/view?usp=sharing

Thanks Squid! The cache did have errors and I cleared them. Gained write access to my shares again. Hopefully this time it is permanent

Well, I spoke to soon. I was able to gain access for a short while, but then my drives went back to being read-only. I ran the NewPerms once more and obtained write access once again...but after a few hours it returned to being read-only for a second time. I have attached the diagnostic zip. https://drive.google.com/file/d/0BwIaL8ycjqj2d21oRFA0R2FLaTQ/view?usp=sharing

woohooo I think I finally got it working! I simply stopped the share and restarted it. I can now create new files on the shares and I'm not getting any read only errors. I was able to invoke the mover and all my cache contents are finally being moved over to the share without giving me any resistance. Glad to be finally done with this nightmare.

I went ahead and ran the NewPerms. First I ran it only on the disk that I rebuilt. I still couldn't add or delete files on my shares. I then ran the NewPerms on my entire array, including the cache drive. Still, I cannot gain write access to my shares. this was the output of the newperms /mnt/cache processing /mnt/cache ... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/cache ... chown -R nobody:users /mnt/cache ... sync /mnt/disk1 processing /mnt/disk1 ... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/disk1 ... chown -R nobody:users /mnt/disk1 ... sync /mnt/disk10 processing /mnt/disk10 ... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/disk10 ... chown -R nobody:users /mnt/disk10 ... sync /mnt/disk2 processing /mnt/disk2 ... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/disk2 ... chown -R nobody:users /mnt/disk2 ... sync /mnt/disk3 processing /mnt/disk3 ... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/disk3 ... chown -R nobody:users /mnt/disk3 ... sync /mnt/disk4 processing /mnt/disk4 ... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/disk4 ... chown -R nobody:users /mnt/disk4 ... sync /mnt/disk5 processing /mnt/disk5 ... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/disk5 ... chown -R nobody:users /mnt/disk5 ... sync /mnt/disk6 processing /mnt/disk6 ... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/disk6 ... chown -R nobody:users /mnt/disk6 ... sync /mnt/disk7 processing /mnt/disk7 ... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/disk7 ... chown -R nobody:users /mnt/disk7 ... sync /mnt/disk8 processing /mnt/disk8 ... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/disk8 ... chown -R nobody:users /mnt/disk8 ... sync /mnt/disk9 processing /mnt/disk9 ... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/disk9 ... chown -R nobody:users /mnt/disk9 ... sync completed, elapsed time: 00:39:15 I'm running out of ideas. Please help me, Obi Wan Kenobi...you're my only hope.

Do I run the NewPerms tool to restore the write settings to my drives? I know that it says only to do this when transitioning from an older version of unRAID, but I don't know what else to do and I need to gain write access back on my unRAID server. This is the syslog when trying to create a new folder within the Never Been Kissed directory Feb 11 18:25:50 media avahi-daemon[10926]: Files changed, reloading. Feb 11 18:25:50 media avahi-daemon[10926]: Service group file /services/smb.service changed, reloading. Feb 11 18:25:50 media emhttp: shcmd (264): pidof rpc.mountd &> /dev/null Feb 11 18:25:50 media emhttp: shcmd (265): /etc/rc.d/rc.atalk status Feb 11 18:25:51 media avahi-daemon[10926]: Service "media" (/services/smb.service) successfully established. Feb 11 18:26:03 media emhttp: shcmd (266): :>/etc/samba/smb-shares.conf Feb 11 18:26:03 media avahi-daemon[10926]: Files changed, reloading. Feb 11 18:26:03 media emhttp: Restart SMB... Feb 11 18:26:03 media emhttp: shcmd (267): killall -HUP smbd Feb 11 18:26:03 media emhttp: shcmd (268): smbcontrol smbd close-share 'Movies' Feb 11 18:26:03 media emhttp: shcmd (269): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service Feb 11 18:26:03 media avahi-daemon[10926]: Files changed, reloading. Feb 11 18:26:03 media avahi-daemon[10926]: Service group file /services/smb.service changed, reloading. Feb 11 18:26:03 media emhttp: shcmd (270): pidof rpc.mountd &> /dev/null Feb 11 18:26:03 media emhttp: shcmd (271): /etc/rc.d/rc.atalk status Feb 11 18:26:04 media avahi-daemon[10926]: Service "media" (/services/smb.service) successfully established. Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:30:30 media sshd[3920]: Accepted none for root from 192.168.1.103 port 50959 ssh2 Feb 11 18:30:59 media shfs/user: shfs_mkdir: create_path: /mnt/cache/Movies/(500) Days of Summer (2009) Movies/(500) Days of Summer (2009)/test folder /mnt/disk7/Movies/(500) Days of Summer (2009) (30) Read-only file system Feb 11 18:31:12 media shfs/user: shfs_mkdir: create_path: /mnt/cache/Movies/(500) Days of Summer (2009) Movies/(500) Days of Summer (2009)/test folder /mnt/disk7/Movies/(500) Days of Summer (2009) (30) Read-only file system

So I got the replacement hard drive, precleared it, rebuilt it, and fixed the filesystem structure on it. I also ran a parity check right after that and there were no sync errors detected. I no longer have a faulty drive or bad SMART reports. I thought I would be okay, but I still cannot create folders within any of my shares. It says I do not have the permission from within Windows File Explorer. Looking at the error log that couchpotato is giving me, it seems like my shares are still set as read-only. How do I fix this? What else could be the problem?

I'm having issues getting the NZBGet docker to start. I used to have it running perfectly without issues until one day it just stopped running. I think it had something to do with filesystem corruption, so I repaired the file system and got out of the "read-only" state I was locked in. I thought that would solve my problems but it has not. I removed the docker container and files. Erased all traces of NZBGet and tried to start fresh. Yet I still cannot get the docker to run. I attached the log file: ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We do accept donations at: https://www.linuxserver.io/donations ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- finding fastest mirror 1. mirror.os6.org Latency: 15 ms Org: os6.org Status: Up to date Speed: 1 Gbps 2. mirrors.namecheap.com Latency: 25 ms Org: NameCheap.com Status: Up to date Speed: 1 Gbps 3. ubuntu.securedservers.com Latency: 26 ms Org: Secured Servers LLC Status: Up to date Speed: 100 Mbps New config file saved to /defaults/sources.list We are now refreshing packages from apt repositories, this *may* take a while Ign http://mirror.os6.org trusty InRelease Get:1 http://mirror.os6.org trusty-updates InRelease [64.4 kB] Get:2 http://mirror.os6.org trusty-security InRelease [64.4 kB] Get:3 http://mirror.os6.org trusty Release.gpg [933 B] Get:4 http://mirror.os6.org trusty Release [58.5 kB] Get:5 http://mirror.os6.org trusty-updates/main Sources [313 kB] Get:6 http://mirror.os6.org trusty-updates/restricted Sources [5,219 B] Get:7 http://mirror.os6.org trusty-updates/universe Sources [186 kB] Get:8 http://mirror.os6.org trusty-updates/multiverse Sources [5,113 B] Get:9 http://mirror.os6.org trusty-updates/main amd64 Packages [875 kB] Get:10 http://mirror.os6.org trusty-updates/restricted amd64 Packages [23.4 kB] Get:11 http://mirror.os6.org trusty-updates/universe amd64 Packages [436 kB] Get:12 http://mirror.os6.org trusty-updates/multiverse amd64 Packages [14.1 kB] Get:13 http://mirror.os6.org trusty-security/main Sources [129 kB] Get:14 http://mirror.os6.org trusty-security/restricted Sources [3,920 B] Get:15 http://mirror.os6.org trusty-security/universe Sources [37.9 kB] Get:16 http://mirror.os6.org trusty-security/multiverse Sources [2,164 B] Get:17 http://mirror.os6.org trusty-security/main amd64 Packages [517 kB] Get:18 http://mirror.os6.org trusty-security/restricted amd64 Packages [20.2 kB] Get:19 http://mirror.os6.org trusty-security/universe amd64 Packages [160 kB] Get:20 http://mirror.os6.org trusty-security/multiverse amd64 Packages [4,643 B] Get:21 http://mirror.os6.org trusty/main Sources [1,335 kB] Get:22 http://mirror.os6.org trusty/restricted Sources [5,335 B] Get:23 http://mirror.os6.org trusty/universe Sources [7,926 kB] Get:24 http://mirror.os6.org trusty/multiverse Sources [211 kB] Get:25 http://mirror.os6.org trusty/main amd64 Packages [1,743 kB] Get:26 http://mirror.os6.org trusty/restricted amd64 Packages [16.0 kB] Get:27 http://mirror.os6.org trusty/universe amd64 Packages [7,589 kB] Get:28 http://mirror.os6.org trusty/multiverse amd64 Packages [169 kB] Fetched 21.9 MB in 4s (4,906 kB/s)

Okay, so if I understand you correctly my process should be: 1. Buy new disk and preclear it 2. rebuild new precleared disk as disk 6 3. try to fix the filesystem with reiserfsck 4. use the old disk 6 which is about to fail as a backup in case some files are lost when repairing the filesystem on the new drive is this correct?

Looking at the SMART report I'm finding these two lines highlighted in yellow which according to my research may mean that my drive is about to or already is failing. Should I even bother with trying to rebuild the file system and likely losing some data while it tries to do so....or should I replace this drive and use my Parity to rebuild the new replacement data drive? # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 187 Reported uncorrect 0x0032 099 099 000 Old age Always Never 1 188 Command timeout 0x0032 100 098 000 Old age Always Never 38655492112

I got this on Disk 6: So I attempted to run the code --rebuild-tree and then I get the following page: reiserfsck 3.6.24 ************************************************************* ** Do not run the program with --rebuild-tree unless ** ** something is broken and MAKE A BACKUP before using it. ** ** If you have bad sectors on a drive it is usually a bad ** ** idea to continue using it. Then you probably should get ** ** a working hard drive, copy the file system from the bad ** ** drive to the good one -- dd_rescue is a good tool for ** ** that -- and only then run this program. ** ************************************************************* Will rebuild the filesystem (/dev/md6) tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do): So I type "Yes" without the quotations and select check, but it just kicks me back to the previous page and doesn't seem do much of anything to rebuild the filesystem on it. What am I doing wrong? And according to the writing up there...I should be backing up the harddrive before doing this filesystem restore?

I have attached my full diagnostics zip. It does seem to be experiencing read-only errors. *Also, I have the inability to start up my VM due to it being read-only I think. media-diagnostics-20160111-1619.zip

Yesterday I found I have suddenly been unable to create new folders in my Movies share. I can delete existing files and view the movies but once I try to create a new folder anywhere within that share, I get a "You need permission to perform this action" notification. I haven't changed security settings or added users or anything like that. In fact, when I first got the issue last night, the first thing I did was remove all the users except root (it didn't help). I also tried running the "take ownership" command from within windows with a registry hack I found online. I ran it in the root of the Movie share, but it ran very quickly and I don't think it actually worked. Because I've run it in the past and the process usually take a while to go through all the files. I read quickly in the forums someone who had a similar issue once before, they posted their syslog and were told that it was a reiserfs problem. Most of my drives are in that format and I also have 3 drives in my array that have given me some concerns over their SMART status. Two of them have a command timeout with a number following it. And another has a command timeout in addition to a "reported uncorrect: 1" Not sure what any of this means or how it can affect me. I am planning on running a parity check tonight and hoping this all gets corrected. If anyone has any advice I would greatly appreciate it.

I got it working somehow after removing the docker and reinstalling several times. I think it had something to do with the linuxserver.io yesterday because I noticed a few of their dockers weren't installing properly. They are all good now.

NzbGet had been working properly for a few months now, until today. It just stopped responding and started shutting itself down even though I have it set to autostart. I checked the logs and it was showing an error with the username and password not matching (I have not changed them). So I backed up the config from the appdata directory and uninstalled the container and data thinking I could do a fresh install and re-input my settings. nzbget still won't start though. Here is what the log shows: ----------------------------------- GID/UID ----------------------------------- User uid: 99 User gid: 100 ----------------------------------- Ign http://mirror.cogentco.com/pub/linux/ubuntu/ trusty InRelease Get:1 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security InRelease [64.4 kB] Get:2 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates InRelease [64.4 kB] Get:3 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty Release.gpg [933 B] Get:4 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/main Sources [128 kB] Get:5 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/restricted Sources [3,920 B] Get:6 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/universe Sources [36.5 kB] Get:7 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/multiverse Sources [2,165 B] Get:8 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/main amd64 Packages [495 kB] Get:9 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/restricted amd64 Packages [20.2 kB] Get:10 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/universe amd64 Packages [158 kB] Get:11 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/multiverse amd64 Packages [4,642 B] Get:12 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/main Sources [309 kB] Get:13 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/restricted Sources [5,219 B] Get:14 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/universe Sources [183 kB] Get:15 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/multiverse Sources [5,116 B] Get:16 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/main amd64 Packages [851 kB] Get:17 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/restricted amd64 Packages [23.4 kB] Get:18 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/universe amd64 Packages [431 kB] Get:19 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/multiverse amd64 Packages [14.1 kB] Get:20 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty Release [58.5 kB] Get:21 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/main Sources [1,335 kB] Get:22 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/restricted Sources [5,335 B] Get:23 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/universe Sources [7,926 kB] Get:24 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/multiverse Sources [211 kB] Get:25 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/main amd64 Packages [1,743 kB] Get:26 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/restricted amd64 Packages [16.0 kB] Get:27 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/universe amd64 Packages [7,589 kB] Get:28 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/multiverse amd64 Packages [169 kB] Fetched 21.9 MB in 10s (2,152 kB/s) Reading package lists... ----------------------------------- GID/UID ----------------------------------- User uid: 99 User gid: 100 ----------------------------------- Ign http://mirror.cogentco.com/pub/linux/ubuntu/ trusty InRelease Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security InRelease Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates InRelease Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty Release.gpg Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/main Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/restricted Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/universe Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/multiverse Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/main amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/restricted amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/universe amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/multiverse amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/main Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/restricted Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/universe Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/multiverse Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/main amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/restricted amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/universe amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/multiverse amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty Release Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/main Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/restricted Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/universe Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/multiverse Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/main amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/restricted amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/universe amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/multiverse amd64 Packages Reading package lists... How can I get it back up and running? and preferably with my old config settings intact. Thanks.

I tried using IE and it worked. thanks for the tip.

I previously had this docker installed and it was working perfectly. But today I am trying to reinstall the couchpotato docker and it doesn't allow me to tick any of the boxes in the settings. I just noticed this behavior today. I tried needo's docker as well and the same issue came up. Does this have something to do with a couchpotato update and not the docker? I am just trying to get CP up and running again. thanks again for all the hard work and maintenance that goes into this.

Just want to make sure everything is fine and dandy with my new precleared hard drive. eb 25 18:10:22 media preclear_disk-diff[12877]: == invoked as: ./preclear_disk.sh -M 4 /dev/sdb Feb 25 18:10:22 media preclear_disk-diff[12877]: == ST2000DL003-9VT166 6YD1RAS4 Feb 25 18:10:22 media preclear_disk-diff[12877]: == Disk /dev/sdb has been successfully precleared Feb 25 18:10:22 media preclear_disk-diff[12877]: == with a starting sector of 64 Feb 25 18:10:22 media preclear_disk-diff[12877]: == Ran 1 cycle Feb 25 18:10:22 media preclear_disk-diff[12877]: == Feb 25 18:10:22 media preclear_disk-diff[12877]: == Using :Read block size = 8225280 Bytes Feb 25 18:10:22 media preclear_disk-diff[12877]: == Last Cycle's Pre Read Time : 5:55:52 (93 MB/s) Feb 25 18:10:22 media preclear_disk-diff[12877]: == Last Cycle's Zeroing time : 5:10:17 (107 MB/s) Feb 25 18:10:22 media preclear_disk-diff[12877]: == Last Cycle's Post Read Time : 12:40:39 (43 MB/s) Feb 25 18:10:22 media preclear_disk-diff[12877]: == Last Cycle's Total Time : 23:47:55 Feb 25 18:10:22 media preclear_disk-diff[12877]: == Feb 25 18:10:22 media preclear_disk-diff[12877]: == Total Elapsed Time 23:47:55 Feb 25 18:10:22 media preclear_disk-diff[12877]: == Feb 25 18:10:22 media preclear_disk-diff[12877]: == Disk Start Temperature: 28C Feb 25 18:10:22 media preclear_disk-diff[12877]: == Feb 25 18:10:22 media preclear_disk-diff[12877]: == Current Disk Temperature: 31C, Feb 25 18:10:22 media preclear_disk-diff[12877]: == Feb 25 18:10:22 media preclear_disk-diff[12877]: ============================================================================ Feb 25 18:10:22 media preclear_disk-diff[12877]: ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb Feb 25 18:10:22 media preclear_disk-diff[12877]: ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Feb 25 18:10:22 media preclear_disk-diff[12877]: Raw_Read_Error_Rate = 115 100 6 ok 98515096 Feb 25 18:10:22 media preclear_disk-diff[12877]: Spin_Retry_Count = 100 100 97 near_thresh 0 Feb 25 18:10:22 media preclear_disk-diff[12877]: End-to-End_Error = 100 100 99 near_thresh 0 Feb 25 18:10:22 media preclear_disk-diff[12877]: Airflow_Temperature_Cel = 69 72 45 near_thresh 31 Feb 25 18:10:22 media preclear_disk-diff[12877]: Temperature_Celsius = 31 28 0 ok 31 Feb 25 18:10:22 media preclear_disk-diff[12877]: Hardware_ECC_Recovered = 36 100 0 ok 98515096 Feb 25 18:10:22 media preclear_disk-diff[12877]: No SMART attributes are FAILING_NOW Feb 25 18:10:22 media preclear_disk-diff[12877]: Feb 25 18:10:22 media preclear_disk-diff[12877]: 0 sectors were pending re-allocation before the start of the preclear. Feb 25 18:10:22 media preclear_disk-diff[12877]: 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. Feb 25 18:10:22 media preclear_disk-diff[12877]: 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. Feb 25 18:10:22 media preclear_disk-diff[12877]: 0 sectors are pending re-allocation at the end of the preclear, Feb 25 18:10:22 media preclear_disk-diff[12877]: the number of sectors pending re-allocation did not change. Feb 25 18:10:22 media preclear_disk-diff[12877]: 0 sectors had been re-allocated before the start of the preclear. Feb 25 18:10:22 media preclear_disk-diff[12877]: 0 sectors are re-allocated at the end of the preclear, Feb 25 18:10:22 media preclear_disk-diff[12877]: the number of sectors re-allocated did not change. preclear.results.txt

Awesome. Thanks Joe!