ScoHo

Thanks, I did read that thread. I'm still baffled as to why it worked for 10 plus years and all of a sudden it stopped working?

So an update after I posted this. I was actually able to connect to the server on that machine by going to the IP address instead of the server name, but only after I created a new user account and connected through that. I still couldn't connect via IP with my original 'root' user account.

So all of a sudden I can't access my server from one of my Windows 10 desktop PCs. I can access it fine from all of my other devices (including Windows 10). Only thing I can think of that is different from the other devices is that the one that doesn't work is a wired connection, all others are WiFi. When I try to access the server, it prompts for username & password (which never happened before outside of the initial connection). So I enter the username & password and get a message that says, "\\FILESERVER is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again." I have tried rebooting both the unRAID server and the Windows machine with no success. I also looked at the thread on this forum about Windows connection issues and tried those suggestions. Obviously it is an issue with my Windows desktop but I have no idea what could have changed. Thought maybe it was due to a Windows Update but I looked at my other Windows machines and they all have the same updates. It worked one day and then all of a sudden didn't work. I also tried a "net use * /delete". I've attached my server diagnostics, but again I think it is something with my Windows 10 machine. fileserver-diagnostics-20201021-1600.zip

Under Manage Files there is currently nothing showing in the /mnt folder. Even /user is not there anymore. If I got to 'Get Files' the folders and files are still there though (as well as under /storage).

Thanks Djoss. Is there a way for me to safely clean up or merge the 2 data sets so Crashplan only shows the /storage one? I guess in the end it doesn't really matter but it kind of bothers me.

Oddly enough when I look at my upload bandwidth used, it says 33 GB in the last 2 days, which isn't nearly as much as the nearly 1 TB I have backed up, but certainly seems like more than the normal amount I would expect. And looking at the times of the heavy upload, it definitely falls in line with when the backup would have been running. The sync is now at 94% (with 56 GB to do). The other thing is when I look under 'Get Files' I see both sets of data - the one under /mnt/user and the one under /storage. The /mnt/user shows my full 938 GB backup size, the /storage shows 923 GB. Is it possible they both theoretically point to the same place but the new path isn't fully synced up yet? Something along those lines must be the case because when I login to my Crashplan account, it says I'm using a total of 990 GB.

They were. But now I just went in to verify and there are no folders under /mnt anymore. Incidentally, somehow my CrashPlan Pro Docker got enabled (I swear I disabled it) and the backup ran this morning and appears to have started the upload as if from scratch. It's already more than half done so I guess it's no big deal at this point. Thought it would take a lot longer to upload about 1 TB of data. But is there anyway for me to go back to to original data set?

Under the old path (/mnt/user), only the folders show under Manage Files, not the files themselves.

So I just went through the process of switching over from Crashplan Home to Crashplan for Small Business. Went through the steps and I'm at the point now where I have everything set up, but due to the change in path I'm worried it will remove all my files from Crashplan Central and try to upload them again. It is saying my backup set contains 979.6 GB (which sounds about right). But then it is saying the next backup has 256,000 files and 980 GB to do. I also noticed when I go into 'Get Files', all of my backed up files are there, but they are still under the old path /mnt/user. I had just gone through and selected them under /root/storage (the new path). So will Crashplan know these are the same files? Or will it remove my current archive and re-upload everything?

I'm in the same boat as you. I'm leaning toward the Backblaze B2 solution while using the CloudBerry Docker in unRaid. Been playing with it with a smaller data set for a few days now and like it so far. Backblaze B2 is not unlimited, but it's really cheap so unless you're backing up 2 TB of data or more, it might be worth looking into. For myself, I backup about 1 TB so Backblaze B2 would be about $5/month for me. There is a $0.02/gb download fee, but I normally don't download much. Below is a breakdown of their pricing, including a calculator. What I may end up doing is just migrating over to Crashplan Pro initially since they're offering it for only $2.50/month for 12 months for existing Crashplan Home customers, and that will buy some more time to evaluate. https://www.backblaze.com/b2/cloud-storage-pricing.html

Trying to set this up with Google Drive and getting the below message when the backup runs. I did enable no-auto-compact. I'm running a fresh backup for the first time so I don't care about losing data on the Google Drive (there isn't any there anyway). Any ideas? "The backup contains files that belong to another operating system. Proceeding with a backup would cause the database to contain paths from two different operation systems, which is not supported. To proceed without losing remote data, delete all filesets and make sure the --no-auto-compact option is set, then run the backup again to re-use the existing data on the remote store."

Apparently I can put a Phenom II in my mobo.

So I've been running a Sempron 140 Sargas Single-Core 2.7 GHz with 4GB of DDR2 memory for several years now. It's done me pretty well, although I don't do that much crazy stuff with it - my only dockers are Crashplan and Plex. Once in a while I get stuttering issues with Plex, although I'm not sure if it's my devices or the server since I only use direct play (no transcoding) since it's always inside my network. The devices I use for Plex are 2 Samsung Smart TVs and an Amazon Fire Stick. Either way, I've been thinking about upgrading the CPU (and I guess the mobo and memory would have to upgrade with it). Was thinking maybe an i5-6500 6MB Skylake Quad-Core 3.2 GHz. Not sure what mobo I should match that up with, but would like something that would ideally allow for 10 drives, although I could get by with 8. I don't do VM and don't plan to, although admittedly I'm not sure what that is used for on an unRAID server? What do people use the VMs for? I notice I don't see much talk about AMD on here. Is there a reason for that? It seems like you get more bang for your buck with something like an AMD FX-9590. Another option I could have if I wanted to save a lot of cash (which I'm guessing wouldn't even be worth it) would be to just upgrade the Sempron to a Phenom II...then I wouldn't have to upgrade the mobo.

Well, turns out it was a bad drive after all. A brand new OCZ Agility 3 solid state drive, that I had connected and activated in unRAID, but wasn't even using it for anything yet - was waiting to upgrade to v5. Ironically I'm now upgraded to v5 sans the cache drive. I just checked OCZ's website and it seems this drive has a 3 year warranty so I should be able to get a replacement. Thanks again to all who helped.

I just hope it's not a bad port on the mobo. I need all the ports I can get!

Thanks mikejp...that seems to have done the trick. I assigned the parity drive and started the parity sync. After that, I'll see what's going on with that cache drive/slot, but it's a relief having everything back online now. Thanks to Joe L, garycase and mikejp for the help. I'll mark this as solved once everything is synced up with no issues. Time to start reading up on v5...

Finally, so good progress. I narrowed it down to an issue with either the SATA1 port or the drive connected to the SATA1 port (which happens to be my cache drive, and is SSD). I will try to confirm which it is by connecting some other drive to the SATA1 port. So with nothing connected to SATA1, I'm able to boot into unRAID and see my 4 data drives and parity drive. I assigned the 4 data drives and started the array, and now can see my shares on my other boxes. The security on v5 must be different because I keep getting "Windows cannot access" errors, so I can't read the shares. Do I need to set something up differently on v5? I set the security to public on all of the shares. I didn't add any additional users, but I never had to do that before with v4.7. I also set my Workgroup name to the correct Windows Workgroup I have set up.

Well, at first I thought I was making progress with the CMOS reset, because after I did it, the BIOS recognized 5 of the 6 drives, and acknowledged the SATA5 & SATA6 ports, but didn't pick up anything in SATA1, even though that's where my cache drive is connected. But then when it boots into unRAID, once it gets to the login, I'm getting those same device lines again (see below). Where that screen shot is now is how it sits forever with a blinking cursor. And I'm still unable to access the web interface. One other thing I tried was booting into a Linux distro from a USB flash drive on that same box, and that didn't work either. Got a lot of the same messages I saw come through when booting up unRAID (ata1: softreset failed (1st FIS failed). But I didn't disconnect any of the drives when doing that. Is there anything else to try? Or is it time to start looking at motherboards?

Not looking good... I wiped the flash drive (after backing it up), copied the Plus.key file over, then ran 'make_bootable' as administrator, ejected the flash drive and inserted into the unRaid box. After taking what seemed longer than usual to get going, it eventually started running Linux/unRAID, and it eventually got to the unRAID login prompt, but before I even was able to login, it started doing something and is now blinking cursor with some variation of /sys/devices/pci0000:00/0000:00:11.0/ata6/host6/scsi_host/host6 (981) And I'm not able to access the web interface . One thing I noticed that's a little disturbing is that when I went into the BIOS before booting, it only seemed to recognize 3 of the 6 attached drives (as Joe even pointed out after looking at my syslog). And I'm not sure why it's not even showing a line for SATA5 & SATA6. Everything also just seems "off" (for lack of a better word). Just getting into the BIOS takes a good 3 minutes or so, and that has never been the case.

Thanks for the clarification. So will I lose all of my shares as well? Or can I copy the shares folder in the config folder over with the key file?

garycase, I'm about to try your suggestion of wiping the flash drive, copying the install files of the latest v5 RC, copying my current key over, and rebuilding the array and I just want to make sure I'm understanding something. All of my drive information is actually stored in that key file? Or is it on the drives themselves? I guess where I'm confused (or worried) is if I completely wipe my flash drive (minus the key file), I'm not losing any important information for drive assignments, parity, etc? In other words, even if I "start over" (so to speak), unRAID will still "know" these drives were part of an array?

I have been wanting to update to v5, but was waiting for the official release...of course I think I remember saying that like 2 years ago. I seem to remember Crashplan is a lot easier to set up with v5 though, is that true?

Thanks garycase. So I take it if I completely rebuild like that I will lose any add-ons I had and will have to reconfigure them? Not a huge deal I suppose, but I do remember struggling a bit with getting Crashplan set up. But I've been wanting to move that to my cache drive anyway so perhaps this would be the motivation to do so.

There are 6 drives in the server (1 parity, 1 cache, 4 data). Below is the latest screen cap I have. That one EARS drive has since been replaced. I also made sure all SATA cables were secure. I don't if the disks show in the disk assignment screen because I can't access the web interface.

I found this thread where someone seemed to have a very similar issue to mine, but he was able to pinpoint it to one bad drive. http://lime-technology.com/forum/index.php?topic=14945.0 Looking at my log file, the section that sticks out to me is: Jun 29 02:37:15 fileserver emhttp: Device inventory: Jun 29 02:37:15 fileserver emhttp: restart_md_driver: stat pci-0000:00:11.0-scsi-2:0:0:0: No such file or directory Jun 29 02:37:15 fileserver emhttp: restart_md_driver: stat pci-0000:00:11.0-scsi-3:0:0:0: No such file or directory Jun 29 02:37:15 fileserver emhttp: restart_md_driver: stat pci-0000:00:11.0-scsi-1:0:0:0: No such file or directory Jun 29 02:37:15 fileserver emhttp: restart_md_driver: stat pci-0000:00:11.0-scsi-4:0:0:0: No such file or directory Jun 29 02:37:15 fileserver emhttp: restart_md_driver: stat pci-0000:00:11.0-scsi-5:0:0:0: No such file or directory Isn't that where it should be picking up that I have 6 drives attached?