Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About JP

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Can anyone confirm the steps above are accurate? If possible, I would just like to confirm before attempting it. Thanks for any help.
  2. Thanks for the help. Sadly, I would have screwed this up had not thought to ask all these questions. If there is one thing I've learned before upgrading items like this is to be sure you know exactly what you are doing, before you do it. I've made some small assumptions in the past and they've bitten me. So with this in mind, I think I understand exactly what I need to do now to upgrade my cache drive and return everything to the same state it is now. Please let me know if anything here seems out of place: 1. Shut down all dockers 2. Disable docker 3. Click on the Advanced slider, select the option to delete docker.img and delete docker.img. 3. I don’t have VM, MOVER, or any shares on the cache drive so nothing to do there. 4. Copy the two folders I have from the cache (basically everything on the cache) somewhere to the array via Midnight Commander. 5. Once complete, shut down the server, remove my current cache drive and replace it with the new one. 6. Turn on the server, assign the new cache drive and check off the box to format it. Start the array. 7. Once the format is complete, move the two folders I saved on the array to the new cache drive. 8. Re-enable docker and have docker.img rebuilt in the same location with the same settings and size (they should have been saved...correct?). I should just have to click APPLY and DONE. 9. Go to PREVIOUS APPS under APPS and install all the same docker apps you had before. Little work should be done here since all the previous settings are saved here as well. 10. Start all the same dockers again that I was using before. These steps should return me to the exact same state I had before, only now my cache drive is upgraded to something much bigger (120 GB --> 500 GB). Does this sound accurate?
  3. Thanks for this. The light bulb went off a little bit because now I see where MOVER might help if it is able to easily move the docker.img file to the array and back for you. And I mostly understand what they are saying to recreate the docker.img file. I guess it sort of goes like this: 1. Disable Docker 2. Switch to the Advanced View and check off the box to Delete Docker.img and delete it. 3. Power down server and replace cache drive with new one. 4. Power up server, assign new cache drive, and format it. 5. Enable docker, which should recreate the docker.img file in the same location if I didn't change the path....correct? 6. Then it says in Squid's directions, to re-add the templates. Are the templates the Docker Containers themselves with all my port mappings and volume mappings? Will all those still be there and I simply need to enable the docker containers as I normally would to have them run? This is the part that sort of concerns me because I wouldn't want to have to re-create all this from scratch again.
  4. I appreciate it Johnnie, but I’m still surprised and how complicated this seems to have gotten when it seems to me this is pretty simple. Here is what I thought I might do: 1. Shut down all dockers 2. Disable docker 3. I don’t have VM, MOVER, or any shares on the cache drive so nothing to do there. 4. Copy the two folders I have and the doccker.img file from the cache (everything) safely somewhere to the array. 5. Once complete, shut down the server, remove my current cache drive and replace it with the new one. 6. Turn on the server, assign the new cache drive and check off the box to format it. 7. Once complete, move the two folders and docker.img file from the array to the new cache drive. 8. Enable docker. 9. Turn all dockers back on. Wouldn’t this work perfectly? I can’t figure out why it shouldn’t be as simple as this?
  5. I think I installed a docker some time ago and it (or I) inadvertently had the docker create the share on the array. Regardless, I just deleted it since I was pretty confident it was serving no purpose. Now my user shares look like this: Note that none of the shares are on the cache so I don't see how I could follow the instructions found here: https://wiki.unraid.net/Replace_A_Cache_Drive Specifically, I don't see that steps 3 and 4 apply to me. Since I don't have any user shares on the cache drive then I am forced to move the apps folder containing my docker files and the docker.img file manually and then move it all back to the cache drive once the new drive has been installed and formatted. Basically, invoking MOVER based on those instructions wouldn't do anything. Does this sound right?
  6. Thanks. Sadly, I'm probably definitely in the category of "not have sufficient understanding of how Unraid share, array and cache work." And now I'm more confused than ever because as I look at my setup I don't see how MOVER could help move this data at all. My setup is very simple, a few dockers, no VM, and no MOVER. Let me explain. Below is a list of my shares: The data on my cache drive looks like this: The "For Picture Frame" folder can be disregarded. The appdata share now has me completely confused because when I look at what data that corresponds to from the unraid menu it appears to be nothing but an older folder for an application that has since been deleted. I originally thought the appdata share might correspond to the apps folder on the cache drive, but that doesn't appear to be the case. Ultimately, I know I'm supposed to change any of the user shares I have on the cache to YES for USE CACHE, but from what I'm seeing is the appdata share doesn't corresponded to the data in the apps folder so it wouldn't even be moved. Additionally, my docker.img file is sitting on the root of the cache drive as well so I guess that wouldn't get moved either. Does this make sense? So I'm starting to think the only option for me is to *not* use MOVER and instead move everything to the array manually and then back to the new cache drive. I don't want to screw this up, but to me that seems like the more logical option. Is it?
  7. I found this youtube video that I thought was pretty good about how to upgrade your cache drive. However, the one thing I don't understand is why you have to invoke MOVER to move your data from the cache drive to the array and then back again. I don't typically have MOVER enabled. Wouldn't it be just as easy to manually copy and paste or move the data yourself to the array and then back again? Is MOVER doing anything special that requires you to leverage MOVER to transfer your data and back again versus you manually doing so? In my case I only have my docker.img and an apps folder in the root of my cache drive. It seems simple enough to just move those two things and then copy them back on my own. Confused.
  8. I was able to find documentation around how to replace your cache drive, however, I haven't found anything about how to move from a single cache to a dual cache setup. The reason I'm asking isn't because I technically plan to move to dual cache. I'm asking because I have the need to upgrade a desktop from a sata hdd to a ssd. My current cache in my unraid server is only 120 GB. I now see that 500 GB SSD go pretty cheap so my thought was to ultimately put this new 500 GB SD in my unraid server and leverage the old 120 GB cache drive for my desktop. Is it best to just follow the instructions I have or is it possibly easier to add the 500 GB drive in a dual cache setup and then sort of mimic that the other drive failed by removing it? I assume that one of the main points of going to dual cache is to provide redundancy so it should fall back to the single 500 GB cache just fine. I'm not sure if this make a difference, but I don't use MOVER. I do use DOCKERS, but no VM. Thanks for any guidance.
  9. I must be missing something obvious. How in the world can you add multiple files or folders to the queue? The GUI doesn't support things Windows would like CTRL and SHIFT to add multiple files at once.
  10. Good point. I did try this with the first drive in question, but it would not mount at all. EaseUS's data recovery software was able to pick up the data on the first scan without a problem, but eventually that machine blue-screened so I had to redo the scan. The scanning in this case was evidently causing more damage because after that first scan it was completely unreadable and toast. Now the two other drives I had were able to be scanned and I suspect if I put them in Unassigned Devices now, they could probably be read. Ultimately, these are great tools for me to have in the future should I run into this again, but I'm certainly not hoping for that. Thanks again.
  11. Success! I can't believe my dumb luck. After two days of scanning and getting tech support to try and assist me, the failed data hdd was fully confirmed as toast. There were so many bad sectors on it, it just couldn't be read. I will say EaseUS support was great and they did try to help. I was pretty bummed out and I still don't know why my backup missed this single file, but the file I was hunting down was the birth of my daughter from 12 years ago. Then, since I had already paid for the EaseUS Data Recovery License, I started thinking if I had kept any other hard drives around that I could scan and possibly get something off of them. In my closet I found two failed drives from my unraid server, one from 11 years ago and the other from 10 years ago. I was pretty shocked to find that they both could be scanned just fine. I started looking through hundreds of files. I don't know if all Data Recovery software is like this, but the one thing that is a bit of struggle is that the recovered files are basically lumped together based on their extensions and not what they were actually named. This does help narrow it down, but hunting through hundreds of MP4 or MKV files can get tedious. Ultimately, I couldn't believe it, but I stumbled on the video from one of these incredibly old hard drives. I recovered it, got it back to the proper unraid folder, and put it to my backup again. Still shocked that I found it. Thanks again to all the help here. I sincerely appreciate it.
  12. Well, lesson learned. I think I put too much faith into what I could recover from this drive. First, I took out an old Desktop I had and put the EASEUS Recovery Software on it that Squid recommended. I slaved up the drive and I was shocked how quickly it was finding recoverable data. However, the Desktop was old and after about 3 hours, it blue-screened. This got me thinking I should move to a current stable laptop and leverage a SATA to USB connector. EASEUS recommended almost any product so I waited for those to arrive. I tried two different kinds and they both operated exceedingly slow so I thought it was probably the connection itself and that the recovery software preferred having a direct SATA connection. So I reimaged the old Desktop with Windows 10, reinstalled the recovery software and tried again expecting it to find those files again quickly. It hasn't. I'm about 18 hours into a scan and it has found about 20 gigs. At this rate it will probably take about 2 months to finish and I suspect the end result isn't going to be good. What I should have done instead is ensured the Desktop PC was stable first and give the unstable HDD one chance to recover the data, its optimal chance. I think by attempting the scan more than once, I just invited more damage to the drive and now it is really toast. I don't expect to run into this in the future, but if I do, at least I'll know a better way to approach it. So for now I'm going to mark this post as SOLVED. I'm going to let the scan continue for a couple more days and check its progress. If it still moves this slowly then I'll just throw the drive away and move on. Thanks again for the help.
  13. Just a quick update on what I've done recently. My hope is I can mark this post as SOLVED soon. Squid's recommendation to try data recovery software totally surprised me. I installed on a somewhat old PC I had since I could install the SATA drive directly to it. I tried the Free Version of the software and started a scan. It was pulling up all kinds of files! I really expected to get nothing. Since I knew I probably would want to pull off multiple items, I stopped the scan, and paid for the Pro Version and redid the scan. The scan would take about 5 hours to complete. Now remember what I said earlier about this drive being connected to my unraid server seemed to make it go wonky? When it was plugged in certain hard drives would not be recognized. Since I've had it out everything has been perfectly stable and I've sort of stress tested it. Well, guess what? The PC I was attempting to do the data recovery from "blue screened." Not once, but every time I tried the scan and I tried it in SAFE MODE. It would take about an hour or so, but consistently happen and not complete the scan. I'm beginning to think this drive is just concentrated evil and it destroys everything in its path. As I said, this was an older PC so I guess there could be something wrong with it and it could be coincidence so I'm going to try one last thing and I'm not even sure if this will work, but I've purchased two different SATA to USB docks. I'm going to try and slave the drive to my personal PC, which is a current laptop. I'm not sure if the software will recognize the drive with these docks, but I thought it was worth a try. It should be here tomorrow. I'll provide an update then. Thanks again for the help.
  14. I'm just learning about SAS and it appears these controller cards are indeed SAS cards. So from what I understand, SATA cables / hdds can be connected to a SAS controller card, however, do you have to do anything special to the controller card so that it reads SATA (perhaps in the BIOS)? Or is it just plug and play? Thanks.