jeff.lebowski

I have Deluge running on one of my servers, but want to install a second instance on a different server. The first obstacle is the daemon port; I don't believe it can be the same (58846) as the existing installation. Unless I've added port forward rules to my router that weren't necessary. It's very likely... ;) And the incoming TCP/UDP ports; do they have to be different than the existing install? If yes, the value on the "Container Port" line cannot be edited. Is changing the Host Port and Default Value enough for each configuration? Thanks!

My plan is to edit line 123 of skintext . py to display something other than Queue. Like the old days when people had custom header images on the server gui. But I don't know where to begin. Is this even possible?

Is the new one v 2.2.8?

I went ahead and got started this morning, following the steps in my previous comment. Everything's going fine. Without a parity disk, I'm averaging 145 MB/s for a copy from unassigned disk to the array. Haven't figured out how to use a queue function like in Total Commander, but I'd like to be present for each transfer anyway. It's only 10.8 TB, as I stated before. backup flash drive power down and remove old disks, then installing new disks power up and assign the correct disk to UD, then the others to array slots, leaving parity unassigned confirm the filesystem for each disk is set to xfs start array and format disks when prompted copy data from UD to each disk move UD to parity and rebuild copy over another 41 TB from a different server using SMB shares < this is where I am now (so slow, but only 6 TB left) shut down that old server DONE

Version 6.12.4 I bought six 18TB disks to replace MANY smaller ones and consolidate two servers. When they delivered I started the process of replacing/rebuilding one disk at a time and replaced parity and one data disk before I was reminded about Unassigned Devices. I installed a third new disk and added it to UD, then copied all array data (it's only 10.8TB) to it. Here's where I'm not sure what to do. I was going to BACKUP THE FLASH DRIVE, remove all old disks, install new disks as xfs, add the new larger parity disk to the array, then use the new config tool. Once that's done, transfer to the array from the 1st UD disk that contains all of the data, then move that disk to the parity position, and let it rebuild. Any missing steps? Is there a better solution?

Awesome. I always copy instead of move for stuff like this. Thanks!

I’ll look at DFM, but will probably be using MC.

So there is some manual work to do with the data on the leftover disks? Transfer it to the new larger disks, I mean.

On one server, I'm planning on replacing the entire array of smaller disks with larger disks and those smaller ones will be removed from the array. I guess I'm not fully understanding the process. After all of the swap and rebuild processes (parity is first) are complete, I'll eventually run out of new disks to install but still have older disks in the server case. Now what? There isn't another machine to use temporarily, unfortunately.

Your download path should be to a cache disk, so: /mnt/cache/Downloads/sonarr/ The Container path should be default: /data Your media paths should be /mnt/Media/TV and /mnt/Media/Films The container path should also be default: /media

/boot/logs is the location, but the flash drive isn't being seen when plugged into my desktop. It just flashes. 🤬 I'm just about done, anyway. In the time I've wasted this week trying to get back to the old config, I could have re-downloaded most of the files instead.

Mistype error on my part: Pro2.key is my actual filename. One server has Pro1.key, another has Pro1.key, and the fourth also has Pro1.key. But the server would still be accessible by ping or GUI even if the license file was incorrectly named/didn't exist. It did just before my latest step.

I dragged over the entire old working flash and rebooted, but there is no access over the LAN. Here is the result of ifconfig and the contents of network.cfg, as seen through MC. Anything weird in these? Disks are still not connected to the backplane if that matters.

After a few days off from troubleshooting (and busy time at work), Subdivisions is once again booting. Albeit from a fresh flash drive install on a different flash drive. I copied out the entire contents of the working flash drive to my desktop, then copied the old files from my desktop (Pro2.ky and super.dat) onto the flash, rebooted and now we're getting somewhere. I can see the missing disks although my pro license apparently isn't being seen. All disks are out of the chassis for faster boots while this whole thing has been going on. Can I simply move over the entire flash contents now that we know things are working?

I'm monitoring the boot process using IPMI. It has worked earlier in my troubleshooting, it will display NO SIGNAL when the server is off, but IPMI shows a blank screen when I power it up. So it would appear to be working correctly. At this point, not even the freshest of fresh OS install on even a different flash drive will boot. By booting, I mean showing some kind of progress in IPMI. Maybe I grab a spare monitor so I can watch the server also not boot from that? haha