Terpinol

Members
  • Posts

    16
  • Joined

  • Last visited

Recent Profile Visitors

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

Terpinol's Achievements

Newbie

Newbie (1/14)

2

Reputation

1

Community Answers

  1. Thanks, I'll look into these options. Appreciate the advice guys!
  2. I can install docker containers on my Unraid server while accessing it remotely using My Servers, but I can't view the docker GUIs. The WebUI command tries to open a local (192.168.x.x) URL and eventually times out. However, I can access the docker containers via the Console command and I can view their logs, so I know I can communicate with them, just can't get their WebUI to come up. Am I missing something?
  3. Thanks for the further clarifications, trurl. It's clearer to me now what New Config does, and as a result, I was able to finally get the old disks added into the new array. And after another long parity rebuild, all seems to be well now. Thanks to you and ChatNoir for your patient help, it means a lot to a new guy - appreciate it.
  4. Okay, unfortunately I'm back. I followed the procedure outlined above, but it doesn't appear to have worked quite right, in my case at least. I added two additional drives from my old array (one old parity drive, the other containing data). They showed up on the new server as unattached storage. Actually, *all* the drives, old and new, initially appeared as unattached drives, but I was able to add the original three (one parity, 2 data) back into the array without any problem. But when I attempted to add either of the two "old" server drives to the array, I got the error, "You may not add new disk(s) and also remove existing disk(s)." I rebooted the server, but the error persisted. Finally, I read on another forum post that the error was because I needed to "... let the parity sync finish before adding new disks (or doing a new config), you cant add new disks while parity is not green." So, I left the parity to sync overnight and it finished without errors. However, when I try to add my data disk to the array, I get a warning that "all data on this device will be overwritten when the array is started." So, I'm back to square one. I can't seem to find a way to add the old data disk from my old array into this new array without losing its data, even though I did a New Config on it beforehand. Any advice on how to add the data disk, or do I have to resort to copying the data over? (If I have to do that, it's not the end of the world, just annoying and time-consuming, considering the data's already there.) Thx.
  5. No. My plan is to migrate only the mechanical drives into the new box. The old box will be retired. Yes it is. Thanks for the detailed advice, ChatNoir, much appreciated! The procedure you outlined is precisely what I'm looking to do. I'm assuming that the "preserve current assignment" option for array slots and pool slots preserves the current state only for *new* drives that are already installed and configured in the array, leaving the data drive from the old server as an unassigned device, correct? (Which I would then assign as an additional data disk in the new array?) Sorry if I'm being overly cautious/detailed here, but I'd rather not lose this data if possible. While I do have backups of it, it would be a pain to reconstitute. As for the old parity drive, yes, I would like to repurpose that as an additional data drive. I guess after adding it to the new box, it should also appear as an unassigned device like the data drive, except it will show as needing formatting. (Whereas the old data drive should *not* indicate that, right?) After all that, the parity drive will be updated to recognize the added drives. If I've got all that correct, I'll take a deep breath and go for it. Thanks again!
  6. Thanks trurl. Just to be clear, though, in my case I should run New Config on the old server, not the new one, right? If I choose to "have the system preserve some of the current assignments" will that cause confusion with the new vs. old parity drive?
  7. TLDR; Is there a way to successfully move array drives from one unraid server into a new unraid server without them interfering with the new array? BACKGROUND: I have an old server box that I installed a trial version of unraid on last month. It has three 4TB data drives in the array (2 data, one parity). Deciding the old server is too anemic, I built a new computer to be my unraid server. I installed three new 4TB drives in it and configured them similarly as the old server, along with two cache SSDs. Since my old trial license is now expired, I created a new trial license on a new flash drive. All is up and running on the new server and it's configured fine. Now, I'd like to migrate (or just add) the data from the old array into my new array and then add the old 4TB disks to the new array. Is this possible by just adding the 3 old drives as unattached storage and then using something like Krusader to copy the files? Or can I even just attach the drives to the new server and add them to the array directly without having to copy data? I'm also worried that the old parity drive from my old server will try to assert itself as a parity drive in the new server. (The other two drives I'm not as worried about since they were just data disks in the array.) Thx for any helpful advice!
  8. I'm not sure why it didn't occur to me earlier, but I got it fixed. For others who may have this problem, just remotely connect to the server on a browser that DOES support popups, and problem solved. If you don't know the server's IP address, boot up in command line and the IP address is shown near the end.
  9. About a month ago, I installed Unraid on an old PC that I had planned to use as my server. However, after using it for a while, I decided to upgrade to some new hardware. I installed Unraid on a new flash drive so I could keep the old flash drive in case I needed to access something on the old PC (for moving my data over). But I'm stuck. The new installation prompts me to either create a new account or log into an existing unraid.net account. When I try logging in using my existing unraid.net credentials, it fails with an incorrect login ID or password error. (This is the same login ID and password that I use successfully to log in via a different PC.) Suspecting the problem was with 2FA, I disabled the authenticator 2FA. But I can't get rid of the security questions 2FA. Maybe Firefox browser included with Unraid doesn't support pop-ups? I tried creating an app password, but I get the same error. So, I'm still stuck being unable to log in to my unraid.net account on my new server and can't proceed with configuring it. I'm probably missing something stupid/obvious, but I need some advice. Thanks.
  10. Thanks for the quick clarifications, itimpi. Much appreciated!
  11. Hi all, Apologies if this question has already been asked and answered, but I couldn't find it via search. My new Unraid server has 4 storage devices attached to the array. I just updated my installation to 6.10.0-rc2 in order to access the new My Servers feature. After rebooting, I got a pop-up warning that the trial key includes all pro functionality only up until expiration. (Presumably, it reverts to basic functionality then?) That pop-up brought to mind this question: are tiers predicated only on the number of attached storage devices, or do new features such as My Servers put it into another pricing tier? I suspect the former, but just want to make sure. Thanks!
  12. Yes, I did. After connecting to the GUI, I had a 192.168 local address. Seems to be working fine now. Thx for the check-in.
  13. FYI, I was finally able to get into the Unraid UI using the unraid gui option on the main menu. Not sure what the problem was earlier, but it appears to be working okay now.
  14. More info: I got an IP address starting with 169, which I've read means the server isn't communicating with my router. I'll try troubleshooting from this angle.