mtseymour

Members
  • Posts

    13
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed
  • URL
    http://mtseymour.ca
  • Location
    Vancouver, BC

mtseymour's Achievements

Noob

Noob (1/14)

1

Reputation

  1. OMG YES! Thank you so much! This worked! I deleted the vdisk and re-enabled dockers, then added containers and got them back! thank you!!
  2. Hey there, Thank you so much, that has brought my cache drive back, and i can see all of the data in it, but when i point Default appdata storage location to /mnt/cache/appdata (where I can see all of my dockers) and try to start docker, it still comes up with no dockers. Am I still able to recover them at this point?
  3. hey there, So I am trying to upgrade a kingston 240GB ssd to a 800GB intel ssd for my cache drive and I think I screwed up big time. I misunderstood the instructions and how primary and secondary storage worked. I thought that the way it worked was that if you had data on your cache drive as primary, it would spill over to your array if your cache became full if you had your array as secondary. with that flawed logic in my head, this would never work, i thought: as step four from here: So what I did instead was I did: cp -a /mnt/cache/. /mnt/disk12/temp_backup/ after that completed, I shut down, installed the new disk, but it showed me this: I went ahead and clicked yes and started the array, and when i did cp -a /mnt/disk12/temp_backup/. /mnt/cache/ everything looked like it was going to work, except for the fact that there was an error, it said something like "cannot copy swap, text in use" or something similar. I should have screenshotted it, but it said something to that effect. I went to my dockers and found nothing there. I attempted to correct the paths from /mnt/user/ back to /mnt/cache (where I had them before the drive swap) and it just would not start no matter what. I attempted to do an appdata backup/restore plugin restore but it wouldnt work either. So, just wanting my dockers to work again I attempted putting the old cache drive back in, but of course when i boot up the array doesnt come online and it says that the cache drive is missing. selecting the original (smaller) cache drive says its "wrong". Selecting no drive gives me the option of starting the array, but says "Start will remove the missing cache disk and then bring the array on-line. Yes, I want to do this" Can anyone assist me in fixing this? I know its my own fault, I dont have anyone to blame but myself. The thing is tho, I dont care about any of the data on the array except for the dockers. they lived on the cache drive, and backups of them were made to the array. If it makes things simpler I dont mind wiping everything if i can just get a couple of the dockers back again. Diagnostics attached monte3-diagnostics-20240327-2131.zip
  4. in an attempt to keep things simple, I have removed the fiber card. I really just need my old IP settings back. The IP was originally set to 192.168.0.2.. one of my dockers wont seam to run without eth0 being that IP When I try to set eth0 to 192.168.0.2 it says eth0 disconnected, check cable. Currently it is auto connected DHCP to 192.168.101.68 Diags attached monte3-diagnostics-20231120-1311.zip
  5. Sorry for not giving more details. Here are the current settings when i ifconfig: br0:: ip: 192.168.0.2 gateway: 192.168.1.1 subnet mask: 255.255.252.0 broadcast 0:0:0:0 dns: 192.168.1.4 and 192.168.1.7 and eth0 shows: eth0 UP, broadcast,running, multicast but has no IP information Pinging from my laptop to 192.168.0.2 times out pinging from unraid to google.com times out pinging from unraid to 192.168.1.1 or any other LAN IP times out pinging 192.168.0.2 from itself pings back fine .... when I play with the network settings this is what i find........... when I enable another network card I am able to ping it but i still dont get internet when I change the static IP address to automatic on eth0 i get a 169. address when i change the IP settings of eth0 to automatic I get 192.168.1.x IP but I still cant ping out I really dont understand. Everything was working perfectly fine up until I installed the fiber card. I checked on my notes from 6 months ago on a different unraid server; I installed a fiber card into it and the networking stopped working. even after playing with it for several hours I was still unable to ping anything or get any internet, so I ended up taking out the fiber card, unfortunately. This was on a completely different server with all totally different hardware including a different fiber card. Is there some bug that occurs when installing a fiber card? It just odd that I get the exact same 2 results from installing a fiber card. Thank you for any and all help everyone is providing
  6. Diagnostics attached. Other details that might help: When I ifconfig i get the proper IP address in eth0 along with the proper subnet mask and gateway. When I ping myself I get a reply, but if I ping anywhere on the internet it times out. I Think that when I pinged my router at 192.168.1.1 I got a reply, if im remembering correctly. I can go back into the server room later today to confirm this. thank you for your help! monte3-diagnostics-20231114-1213.zip
  7. Hey everyone, I installed a Mellanox ConnectX-3 Pro Dual Port 10Gb SFP + card into my unraid server and now networking has disappeared. the IP was 192.168.0.2 and it still shows thats what the IP is, but i cant ping it, nor can i ping out from the server. I remember having this issue with another unraid server, and my solution at the time was to remove the fiber card and stick to 1gb ethernet. How can I make this work with the fiber card?
  8. Thank you JonathanM that was incredibly quick reply!
  9. I actually figured out how to do this myself. For anyone needing to know: I went to tools and then to new config, and applied it, then i started the array with parity valid.
  10. Hi everyone, So we migrated to a supermicro server with 5 fewer drive bays than in our old server. I really dont care about any of the data on the drives that we cant install. My main concern is with the docker data. If I understand things correctly, the docker data resides on the cache drive, and the cache drive is one of the drives that is showing up and allocated correctly. The parity drive is also allocated correctly. The 5 drives that are not showing up are more recently added drives and they didnt have much data, if any, that we need. Drives 1 through 6 are allocated correctly, drives 7, 8, 9, 10 and 11 are missing, drives 12 and 13 are allocated correctly and the cache drive and parity drives are also allocated correctly. I am currently getting "Too many wrong and/or missing disks!" error. How can i chop off the missing disks and get the array started again? I am only concerned with getting the dockers running again. None of the other information is important diagnostics attached Thank you in advance monte3-diagnostics-20231108-1526.zip
  11. Hi there, I would like to request the feature that notifications from unraid be sent to MS Teams. In the past I have had it set up via slack to let the several admin users of my unraid server know about notifications, but we have recently moved to teams. Is there any way the notifications could be sent to microsoft teams?