BostonJon

Just ran into this issue as well, have Verizon Fios and the default DNS was preventing the public url from resolving. Changed to Cloudflare DNS, and works like a charm!

Hey, just wanted to update that I've found one of my underlying issues turned out to be bad ram. Ran memtest and started hitting errors pretty quickly. I installed new RAM today, and am dealing with some residual corrupt data, but everything seems better already. No hard feeling on how things went, I was pretty frustrated, and I've been reading other forum responses, and I do see that y'all really are trying to help, so thanks for that.

Hey, I'll be honest I haven't read your edit, and any of the follow up comments, but I don't need the suggestion that the only issue here is that I'm not doing exactly what you told me to do while you're not listening to what I'm trying to say. You need to understand that I'm listening to multiple sources here, you're one of them, unraid docs are another, I'm listening to the suggestions from the tools, and I'm coming to the table with my experiences. I'm trying to put all of it together and come up with answers. Right now I feel pretty confident that I can get my data back without having to keep going on with this thread, and I'm really disappointed how this went from an amazing interaction to an awful one. The effort of trying to communicate with you has become really more than I can handle right now, I'd rather try it on my own for now. If I have no other choice I'll reach out again.

Hey, sounds like you're having a bad time now, so I'll just go ahead and look for help elsewhere.

I guess I'm still trying to figure out how I ended up wiping all the data, since I didn't intend to do that. I'm trying to figure out what exactly it was so I could avoid it going forward. I thought it was the formatting, but it sounds like you're saying it's not that, so now I don't know what happened to result in the data disappearing.

Thinking about the timeline now, I'm actually thinking that the files were gone after I did the format last night, not the one this afternoon. I only ever formatted the new disk, the old one is still untouched after I removed it.

I didn't unassign the old drive before powering down. Maybe I'm still confused here, but after I initially uploaded my diagnostics, you mentioned that the disk2 was still not mounted. At this point, I did what I thought was the right move by formatting the disk to mount it. The disk was mounted, but then the files were gone. If I had said "no" at this point, how would you have suggested that I solve the unmountable disk issue?

I think this is what I was really looking for here. https://wiki.unraid.net/Replacing_a_Data_Drive I definitely made more than just a hardware mistake, as I expected to be able to just allow the data to come back from parity. One of the main selling points for me was the ability to restore data if a disk failed, and this was kind of a run through of that for me. In the end, I didn't follow the steps right to trigger a rebuild.

I'm definitely missing something. So you're saying that the rebuild will build everything, including the filesystem, so the format is not necessary. Then why was UNRaid saying that the disk is unmountable, and offers formatting as a solution? I'm still curious about what the right option was here, since when a disk does fail and I need to replace it I don't want to make the same mistake again. What should I do when replacing a disk, and it says it's unmountable and suggest formatting, but I want to ultimately restore the files from parity? Is there a guide I should be referencing?

Thanks for the response. It appears that the timing of the format is what caused my issues. I understand that formatting the disk would clear the filesystem. I expected UNRAid to format the disk, then add it to the array, and then start the repair. What it sounds like happens is that the format happens while the array is online, so that gets written to the parity disk as well. For clarity, can you confirm that if I had formatted the disk with the array offline that I would've been okay at that point? Ultimately, what I want to know are the steps I should take when a drive actually fails and I need to replace it.

Oh interesting. The new drive does not have any file on it, and I had formatted it last night, but I see that I needed to format it again. It's now mounted, and parity is running. The old drive *did* have files on it, and I'm noticing that they are all now missing from /mnt/user. Is it possible to reconnect the old drive to restore them? I also have those files backed up on another drive, so I could restore them once parity is complete if necessary, tower-diagnostics-20211121-1549.zip

I did everything you suggested, and everything is looking much better! Parity sync is processing at a much more reasonable speed of 132.4 MB/sec, and will be done in less than a day. Docker is responding again, and I can start/stop containers. I've attached another diagnostic in case you see anything else I need to do. Thanks for all the help, this was really starting to frustrate me! tower-diagnostics-20211121-1335.zip

Also, if the objective of adding the old drive back in is to get the SMART report, here's on I pulled down last night before doing the swap. tower-smart-20211120-1708.zip

If it matters, the ssd cache drives are on the pcie controller, and all hdds are all connected to the mobo.

So my mobo only has 6 sata ports. To add the old one back, and to stop using the pcie card, I'd need to remove either one of the cache or parity drives. Is removing a cache drive okay at this point?