Arbadacarba

Funny enough, the docker I was trying to set on it's own IP was Heimdall... So now she has links for all the pertinent Cameras and tool.

Check that your ports are not duplicated... Did you by any chance chage Plex's port from 32400 to maybe 80? so you would not have to use the port?

Could it be a static DNS in the network config that kicks you out after a while?

Vr2Io is exactly right: Settings - Docker Turn Docker off - Apply Host access to custom networks: Enabled Turn Docker On - Apply Figured that out today trying to do the exact same thing so that my wife doesn't have to input ports

Would that happen if you had a share called lxc and had it set to the wrong "Use Cache Pool" setting?

Does the Mikrotik show anything in the logs?

This is where we are at the moment. Same problem, it was fixed and then promptly broken again. What are you trying to alias? Here's the other thread:

Aaannnd Found It I guess the trick is not to read through the relevant thread, it's to read through ALL the threads.

I'm not running a reverse proxy - I just want simple access from within my network so that my wife can quickly have links available for external cameras and the baby monitor... Plus give myself a launching point for all my internal servers and dockers. I am playing with the idea of putting many of my dockers on their own IP addresses so that they can be accessed by name and without having to enter port numbers. It seems to work, except that the advanced apps give errors on testing and if already configured they just do not show any live data.

My own build includes 7 HDDs. I have ended up segmenting them by types of Data so that only one disk has to spin up at any given time. Disc 1 - 10TB - Television Disc 2 - 10TB - Anime, Audio Books, Comedy, Comics, Documents, E-Books, Graphics, Public, Software Disc 3 - 10TB - Music, Photos, Videos Disc 4 - 12TB - Movies Disc 5 - 14TB - overflow Disc 6 - 16TB - Backup Disc 7 - Unpopulated Parity - 18TB The advantages of not having all drives spin up when data is pulled from one category, and the fact that I can lose only 20% of my available storage. On the down side I have to move the largest drive into the Array every time I buy a larger drive... But I can live with that.

On the one hand it depends on how irreplaceable the data you are housing on the server is... If you are just experimenting I would say turn OFF the Parity drive until you have added drives. On the other hand, If you are adding drives slowly over time and are worried about the data, then let it go ahead. I would try not to fret over parity sync using drive life... My system tends toward up times in excess of 100 days, but occasionally I do something silly and it ends up re-syncing parity... You just have to go with it. Arbadacarba

Syslog server allows you to set your folder... Generally not the Flash Disk... Also it sets a Max file size and since it is only a text log you wouldn't get anywhere near 15GB... Or 1GB really

Any chance you are running Shinobi? I've been fighting with this for a while and finally tried shutting Shinobi down... Suddenly it works.

Considered wiring a Cap into the 12V rail at the plug for the Hotswap bay, but tried plugging a separate cable in for it rather than running it off the cable that I had in place... Seems to be holding now. Yay, time to start building the parity again.

I end up with A LOT of external drives, and use SMART to determine when to retire them: Gives you a rough idea of how long a drive has been in use. Arbadacarba

I looked through a bit above and didn't see a similar problem: I have been using my internal docking bay (with hot swap enabled on the Sata controller) to clone and resize various drives over the past few days, but I've run into a snag... If I plug any drive in it mounts on it's own and appears to have the same structure as the last one I used but if I try to look at the OS partition with Krusader it shows up as empty. I'm assuming a reboot will fix it, and I am due to install some hardware tonight, but I'd love to know if there was a way to reset Unassigned Devices without a reboot. jupiter-diagnostics-20220622-1900.zip

That was my read as well... So even if I use a seperate cable it will not isolate the one drive from the external bays.

The Power Supply is a beQuiet 1000W that is nowhere near the limits... Is there a way to see if the drive looses power? I wonder if using a separate line for the Parity drive might help... I don't think it should, if I'm reading the manual correctly, but maybe just moving it a little farther away... Worth a shot.

The Power Supply is a beQuiet 1000W that is nowhere near the limits... Is there a way to see if the drive looses power?

Yes, it's on a hot swap capable Sata connection I've been using this bay as hot swap for over 4 years... Though the Sata controller has changed a few times over the years. The current connection is on the NZXT Mainboard and the port is set to Hot Plug in BIOS. IOMMU group 5:[8086:43d2] 00:17.0 SATA controller: Intel Corporation Device 43d2 (rev 11) [7:0:0:0] disk ATA TOSHIBA MQ01ABD1 2D /dev/sda 1.00TB [8:0:0:0] disk ATA Samsung SSD 870 1B6Q /dev/sdc 2.00TB [9:0:0:0] disk ATA Samsung SSD 870 1B6Q /dev/sdd 2.00TB The Samsung Drives are my Cache Drives My Array is entirely connected to a Dell Perc 310: IOMMU group 18:[1000:0072] 06:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) [3:0:0:0] disk ATA ST14000NE0008-2J EN01 /dev/sde 14.0TB [3:0:1:0] disk ATA ST12000VN0007-2G SC60 /dev/sdf 12.0TB [3:0:2:0] disk ATA ST10000NE0004-1Z EN01 /dev/sdg 10.0TB [3:0:3:0] disk ATA ST10000VN0008-2P SC61 /dev/sdh 10.0TB [3:0:4:0] disk ATA ST10000VN0008-2P SC61 /dev/sdi 10.0TB [3:0:5:0] disk ATA ST10000VN0004-1Z SC60 /dev/sdj 10.0TB The First Drive is my Parity... The only differentce with the Parity drive is that it is mounted to a seperate plate from the other Array disks, and there is a short Sata extension cable connected... AND IT"S ON THE SAME POWER LEAD AS THE REMOVABLE BAY!!! (OK thought of that as I typed...)

Further input for interests sake: I mounted a drive using Unassigned Devices and instantly lost the parity drive to a read error... The unassigned drive is inserted in a slot load tray above my parity drive, and not in the best of health. (Hence the reason I'm trying to access it.) This slot load bay is also in use when I was launching the VM's that I thought were causing me the problem before... I'm waiting on the replacement drive this week. Oh the drive the system is repeatedly warning about is the drive I mounted to do data recovery on. jupiter-diagnostics-20220621-0933.zip

Thanks for taking a look... I didn't think I was doing it wrong, but it seemed to coincide. I suppose it's possible I'm getting vibration... There is an extension on that connection that I should possibly get rid of. Or at the very least check it for solid connection. oh, and I have definitely passed through the wrong controller back when I was first setting things up.

It's just weird that it's all of a sudden an issue... But there's always a chance ive degraded some connection with the other things I've been doing... I was just concerned that I was casuing it by connecting another /Dev/SD$ in a vm config.

For now I've installed a USB wifi Dongle that seems to be working, but I really would like to use the one inside the machine.

OK, So I've had this happen twice... And I feel like I was doing similar things both times... Namely starting a VM that I use for Cloning Unnasigned drives... I've been trying to improve the tools I use and I think it might be something I've done... But I don't see the mistake I'm making. Recently on Jun 20 12:59:32 - My Parity drive suffered a read error and fell offline. I had this happen once before in the last week or so and ran the extended smart tests with no failures... Further the Disk that failed is my newest disk but has been running without fail for several months. I put it back in service and rebuilt the parity with no trouble but it just did it again today while I was trying to edit a couple of the VM's that I'm using (Clonzilla and GPartEd). Thanks for any input. I'm ordering a new 18tb EXOS to install as parity, and I will RMA the 14TB jupiter-diagnostics-20220620-1322.zip