camprman
-
Posts
33 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by camprman
-
-
On 5/9/2023 at 9:27 PM, shwa87 said:
I agree, I posted a request in the lsio forum (https://discourse.linuxserver.io/t/un-deprecate-nzbget-or-start-a-new-one) but it doesn't look good, at least until Paul can get ramped up on development.
Thank you for trying. I understand their requirements. It doesn't change that I prefer NZBGet, and I'll continue to use it for as long as I possibly can.
-
There has been a fork with the NZBGet: https://github.com/nzbget-ng/nzbget Details:
Note: this repo is a fork of the original github project nzbget/nzbget originally written by @hugbug. He deserves all the credit for this software.
Since he has now archived the project, I've combined my changes (surgical fixes to accomodate the intentially-malformed 'wtf' NZB headers, which result in the infamous 'abc.xyz' file names) and merged several pull requests from the original repo.
Paul, 2022.11.28
I'm hoping that LinuxServer will point to the fork. I'm guessing no, but I can hope.
-
Were you able to resolve this? If so, what did you have to do?
-
-
Do you still have a 1015 available?
-
Ok, we can close. I don't have an answer as to why it was this way, but I said screw it, backed up the USB, and wiped it clean. Put my pro key back on and booted. Just have to redo some stuff, including drives, but it's functional, and with a clean boot.
-
I just upgraded from 6.1.9 to 6.3.5. I have 4 SDD drives in the cache pool or at least I did. Now I'm seeing unassigned under Cache, and while I can see the drives, I can't select them. I tried creating a New Config, but again I can't select any drives for cache. I'm sure I'm missing something, just not sure what. Please help
-
You need to start in maintenance mode and run xfs_repair on disk2.
If array is set to autostart disable it by editing disk.cfg on your flash drive (in the config folder):
change startArray="yes" to "no"
Then:
https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_XFS
I found this and it has gotten me to where I can repair. Johnnie I owe you a drink.
-
But to answer your question no WebUI at all, until I found the advice I needed to at least get it to maintenance.
-
Within 5 minutes I found a post advising how to get the server into maintenance mode. I am at that point, so at the very least, I have a little light.
-
I am stuck. I have searched here and while others have had the error and suggested running xfs_repair, I'm not able to see it run. I have no webpage, so I can't put it into maintenance mode, and while I'm able to telnet in, when I enter the command and hit return, nothing appears to happen. Attached is a screenshot of the error.
-
Thank you johnnie.black. That would have been the absolute worst. I ran reiserfsck on both disk8 and disk9 with no corruptions and not having to do any rebuilds. New drives should be here tomorrow.
-
Here you go. The device is sdl.
-
Just my fear of losing files. I'm not afraid that the swap-disable feature will delete data so much as I'm worried about Mr. Murphy.
-
I've been very lucky over the years, but my luck has finally ran out. I knew I had a drive failing but being on a fixed income, I had to wait to buy a new drive. The drive has now failed, and without looking or thinking I bought 2 new 4tb drives. Right now my parity drive is 3tb and the drive that has gone down is also 3tb.
From all that I've read it appears that since I didn't think before I ordered my only option is to do a swap-disable. Right now the emulated drive is functional as expected, but I just don't have the room to try to copy everything off before doing the swap. I'm more than a little nervous, and just wonder if there is anything I can do short of copying before doing the swap-disable?
I suppose you could say I'm a little overwhelmed at the moment.
6.12.1 issues
in General Support
Posted · Edited by camprman
I'm having the same issues. I looked to see if my cache were going to read only, but so far I'm not having that issue. I'm attaching my diagnostics after a reboot, and trying to update a docker. Thank you!
ETA: I can write to cache, so I don't know what's going on.
tower-diagnostics-20230628-2056.zip