Paul Rockliffe

Just coming back to this now, I managed to work through ddrescue, which identified a number of errors on disk 4. I emptied another disk and cloned to that disk, however that disk now will not mount, with the log stating, "Metadata corruption detected at xfs_btree_sbloc........" I've run through the clone process twice now, with the same result both time. I've run xfs repair too, that finds no Super Blocks. What should my next steps be?

OK, thanks. it's not a problem to remove Disk 4 entirely, I have space on the array. What's the process for getting as much of the data off that drive and onto other drives on the array as possible?

Sorry, I meant that in my array setup under devices I have the option for both Parity 1 or Parity 2. If I put the drive in Parity 1 it is disabled, if it's in Parity 2 it is rebuilding. The drive is physically connected the same way and in the same slot, it's purely an UnRaid setup thing. I think,

Thanks, I meant a bug in that I have never managed to get the Parity drive to initiate a rebuild in slot 1, it would always either be disabled immediately or very soon after. In slot 2 it immediately started to rebuild and is still rebuilding now without being disabled. I'm not sure what's what with the drive with errors, it doesn't make sense to me that it says it unmountable, but is otherwise appears active in the array and is green, the parity rebuild has read the whole thing now and shows 2,114 read errors. As you can probably tell, I don't really know what I'm doing with this, but if I know the best course of action from where I am then I think I understand enough to follow it. I've attached diagnostics. Thanks! unraid-diagnostics-20231022-1004.zip

I've been struggling with my Parity drive for a while now, it shows absolutely fine in the logs, in SMART tests and if I remove it and put it in another machine it tests and performs faultlessly. But setting it as parity and turning on the array would cause it to be disabled. I've just removed it from Parity Device 1 and put it in Parity Device 2 and now it is happily rebuilding. It's run for 5 hours now, so I'm fairly confident that it'll be OK. Is this a bug, or something that has happened to others before? Secondly, while I've had no parity one of my drives has started showing errors. It's been working fine, but showing maybe 500 errors, then a few days ago it started reporting that it is "Unmountable: Unsuported or not file system." As Parity rebuilds it is reading the drive though. Will the rebuild be good enough that I can swap that drive out for a new one and have it rebuild most of the data, or is that just lulling me into a false sense of security? Thanks!

I should add that stopping the array doesn't work anymore, the only way to get the array offline is to set it not to start automatically on boot and to then reboot the server. Not sure if that's relevant, but it's an issue that appears to have arisen at the same time.

My Parity device has become disabled. I have removed the device from the system, removed it from the configuration and then reinstalled it, it immediately goes disabled when the Array is started. SMART doesn't appear to show any issues, all I can see is that it has 8097 writes, 0 reads and 1024 errors. What's the process for working out how to get it back online, or whether it's a faulty drive?

Hello, I have been having problems with Next Cloud for a while now, caused by the Docker being updated two major versions as I didn't realise the issue with that. I've been around the houses trying to get this sorted out and got it to the point where NextCloud appears to be working, but accessing the WebUI internally gives me a 404 Not Found error relating to nginx and accessing the Console, again internally gives me a 502 error, bad gateway. I'm not getting any errors in the logs for either NextCloud or MariaDB and I'm not really sure what I need to do now to make any more progress. What I would like to do now is remove the Docker entirely and start again, but I do not want to lose my database and files as they are now. Is there an easy way to do this, or do I need to persist with solving my actual issues and then update things a major release at a time to get back up to date?

Thanks, yeah, I realised I was reading the paths wrong and tried moving the config file. I've got both my cameras up and running in Frigate now and just working through Home Assistant/MQTT now. Thanks again!

I'm setting up Frigate on UnRaid, I've setup the Docker Container without changing the config file path and I've added config.yml in appdata>frigate>config>config.yml. I've used the template for config.yml, only changing the rtsp address so the config.yml file should be suitable. When I start Frigate the log shows "[Errno 2] No such file or directory: '/config/config.yml'" I'm struggling to make progress from this point, the file is there and as I understand things it's in the correct place. Is this an error that would occur if there's an issue with the file contents? What should I be checking to sort this issue out? Thanks

Morning, I have a quick question, well quick in that I know if there's nothing obvious when I ask it that I need to go away and read the manuals when I have a bit more time. I am setting up Swag and was following the Spaceinvader One YouTube video for LetsEncrypt. I've done everything in the video, but appreciate it's quite old now and I'm having issues. I am using my own domain, I've setup DuckDNS and all of the subdomain forwarding is working as far as I can tell. I setup Swag with the subdomains, "www,nextcloud,sonarr,radarr" and these are configured on my domain host to forward to DuckDNS. I have configured the proxy-conf files as per the YouTube instructions. All my subdomains began with 502 errors except www, which correctly displays a website I dropped into the www folder in swag. I played around with a few things, didn't get anywhere, then I resetup resolver.conf. Now Nextcloud is working, but sonarr and radarr both return the www website that I setup. I feel like someone that knows what they're doing might be able to point out some really obvious thing I need to change, but unfortunately that isn't me! Does anyone have a quick-fix before I start trying to learn this properly? Thanks

I want to install this: https://hub.docker.com/r/dchesterton/texecom2mqtt I don't really know where to start! Can anyone give me some quick pointers so I at least know what I need to put into Google? Cheers

I've got an odd problem and wondering if anyone can help. Yesterday my internet want really slow, it's usually about 70 down, 20 up, stored test was showing 6 down and 1 up instead! I've discovered that the reason for this is that Deluge is constantly pulling 50-80mb/s. I have Google WiFi which is showing me device by device usage and the problem starts and ends when I turn the Docker container on and off. When I open the console I can see it's really only downloading in the 5-10 mb/s range and there's nothing in the downloads folder that cous account for the 50Gb that I can see Deluge generated in a few hours yesterday. I don't really know where to start with this, so hoping someone had some hints of advice? Thanks.

Did you get this fixed? I had the same issue around the same time, but before I got around to fixing it UnRaid stopped recognising I had any Dockers, I didn't have them backed up and I haven't had time to set everything back up. Then yesterday UnRaid decided I did have Dockers setup, everything started working again, except Sonarr, which is throwing the same error on opening the Console and I can't access the GUI. I can still access it via my mobile app, so it is still doing something, but I can't add new programs, so it does look like there's an issue with the database. Is there a way to fix it or, worse-case, reinstall it and flatten the database?

The log is doing a lot of this: UnRaid kernel: ata3.00: Link offline, clearing class 1 to NONE UnRaid kernel: ata3: SATA link down (SStatus 0 SControl 300)