-
Disk disabled, content emulated after power outage
Finally found another cable - now the SMART is there, but with read errors. :-/ opportunity-diagnostics-20251223-1251.zip
-
Disk disabled, content emulated after power outage
Sorry - forgot about that when I posted. It's attached. I just picked up a replacement just in case - didn't wanna risk needing a disk over the holidays, when stores are closed. opportunity-diagnostics-20251222-0957.zip
-
Disk disabled, content emulated after power outage
Unfortunately I had another thing trip the relay at home taking my server offline. When it restarted, one disk is reporting 3000+ errors and unRAID disabled it and says it's contents is emulated. I'm not able to get a SMART status from it, as it just says: Smartctl open device: /dev/sdf failed: INQUIRY failedWhen selecting the disk, it says: Partition format: MBR read errorThe syslog keeps spamming lines like these: I'm wondering if it's "just" a filesystem error, and if I should try to format the disk and rebuild or if I should just replace the disk. What would you suggest?
-
-
6.12.11: Issues with accessing containers from the internet after switching to IPvlan in Docker
My server had a few crashes a couple of months back, and the "Fix common problems" plugin suggested, that macvlan might cause issues, and that I should use IPvlan instead. So I switched, and I haven't had any crashes since then, but I am not able to access to my containers from the internet as I used to. A quick overview of my network: router --> nginx proxy manager (running as a container in unraid on it's own IP) --> nextcloud (also running as a container in unraid on it's own IP). Perhaps I should mention, that I had issues looking up the DNS names from inside my network, so I added a DNS rewrite in Adguard Home so service.mynetwork.home -> 192.168.xxx.xxx. This issue has been there long before I switching to IPvlan - I believe it is a setting my router doesn't support. In the router I have opened ports for 80/443 pointing towards Nginx-Proxy-Manager, but I don't hit the container anymore. I have tried opening ports towards other containers, but none of them work. If I open a port towards another machine in my network it works great, so I am almost certain it has something to do with me changing Docker to use IPvlan. Can one of you help me debug further, or even better, suggest a solution?
RazziaDK
Members
-
Joined
-
Last visited