AndyGJ

Members
  • Posts

    5
  • Joined

  • Last visited

AndyGJ's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Perfect, that's the kind of reassurance I as looking for thank you, appreciate it! I've got a few VM's with passthrough but not so many that a bit of manual config would be a burden. Possibly time to invest in a separate USB controller card while I'm doing a bit of re-engineering. I was a little concerned there was some aspect of the configuration that was not held on the stick or some other gotcha, sounds like a win.
  2. Hi guys, I have outgrown my old dell T20 and am about to upgrade to a T620. The 620 will arrive with a single 6TB disk and 7 spare hot swap bays vs the 4 x 4TB in my T20. My intention, if this is a viable option, is to slot the old disks in the new machine, and rebuild the array using the new disk as parity. I've done the drive fandango a few times with my T20 so I'm fairly familiar with the general process of adding disks to the array, but I'm not familiar with moving unraid to new hardware. I've got a compatible HBA to use in the 620 already so shouldn't be a concern on that side. My current mental process is something like this: 1) Test new machine with either trial unraid or an entirely different OS to make sure its functional and the HBA card is ok. 2) Mark the hard disk identifier / positions just in case from the T20. 3) Power down the T20, move the hard disks into the 620. 4) Move the usb stick containing unraid to the new hardware, boot it, upgrade licence level appropriately. This is the bit where I'm unsure of if I'm about to wreck myself. Is this already a bad idea? Should I expect unraid to effectively see my old array + a new disk? That is what I'm expecting based on my prior experience, but did not find too much direct information for this scenario on a google expedition. I'm looking to avoid buying extra disks for the new build immediately so would prefer the cold move vs a hot copy over the network, but if that is the consensus advice I'm willing to adjust the plan if my way is terrible!
  3. Ok, my bad - turns out this is the error when you typo your password! Sorry guys. Was blinded by the port being different - although I was right, I WAS doing something dumb!
  4. This is with the port box saying 80, but to try and give an extra option this is the result of two attempts, one with port 80 which I would expect would work, and one with it set to 443 just to see if it alters the debug. Pretty weird, its as if the port box is being ignored. I'm guessing I'm doing something dumb here! No reverse proxy, no port redirection. No docker containers listening on that port either, and I can load the unraid UI on port 80 before and after running this debug.
  5. Hi, just bought the app and I'm struggling to add my server. I can access unraids webUI from my phone in its current environment. Just updated to 6.6.0, but this issue also affected the previous version. Adding the server using http manually, causes the following debug info (what I think are the relevant bits, if the full thing is needed I'll get you that later on). failed to connect to <unraid server ip>:2382 The server error information below this seems to be getting a http 401, with the body html returning mentioning nginx. From what I've read, thats the port the plugin listens on. I tried installing the plugin, and yet the situation is the same.