IanMcLeish

Well, sorry mate, you got further than I did. Hopefully someone else will come along g to help you?

I did a preclear on Disk 1 and a new config. The array is back up and writing parity. I wasn't sure what you meant by "can check parity is valid", but if there was another option to rebuild disk 1 I blew it, but perhaps the corruption would have remained anyway as the array wouldn't start with the drive emulated? I had VMs on that drive, but only 2 for messing, so no big loss there. I did lose all my dockers, but I copied appdata to my PC, so I'm hoping after the parity is done and mover runs, I'll reinstall the docker images and then hopefully just paste the appdata over the "new ones" - it would take me an age to get them back to the way they were, though SpaceInvader One would get a lot more ad revenue😃 Thanks for all your help, it is much appreciated.

So I ran that command against disk1 which is listed in array devices as sde, so I ran wipefs -a /dev/sda1 and this gave some output of deleting blocks, I'm sorry I didn't sopy this output. Maybe I did this the wrong way, but I mounted the sde disk1 using unassigned devices and did the wipe there. Was that the wrong thing to do? Anyway, I put the disk back in as Disk 1 into the array, but attempting to start leaves me in the same place - stuck with Disk1 mounting. I attached another syslog download having left the server running overnight, but things seem to stop at the kernel panic error? Can I ask, even if i do a preclear, will the parity drives rebuild the drive corrupted anyway? Has the corruption been "saved" on the parity drives. I am not sure what is on disk 1, and I realise that I should have a backup of stuff, but I was just setting this up after recovering from multiple failing drives on a Windows Homeserver build from 15years ago. It sat idle for a long time. But I suppose for a simpleton like me, it worked. All the drives were precleared when they were put into the system, which I understand significantly stresses them, and I don't know if it is a good idea to do that again when it was done only 2 months ago, but all these drives are first use, and I know drives can fail early on as well. Thanks for all help suugestions so far! Ian unraidnas-syslog-20231230-0459.zip

And many thanks for your reply, much appreciated!

So I will preclear disk one and put it back in?

Please ignore the screen capture, I uploaded an old one when it was working by accident.

My Unraid worked fine after I installed it on version 6.12.4. And I recently upgraded to 6.12.6 a week or so ago, I think. I put everything on ZFS, only because knowing little it seemed to be the way to go? I do have a strange setup because I bought the stuff before I even knew about Unraid, but apart from having to change the USB C cable, which connects the external “DAS” unit to the Protectli computer, because it was causing errors, it has worked without issues for a couple of months. I have a UPS for the Unraid as well, and all was fine until 2 nights ago. In the morning, Jellyfin wasn’t working, and I found I was unable to login to the Unraid GUI remotely, though I was able to ping it. Seeing as it was running in Non GUI mode, all I could do was quick press the power on the computer, and wait. An hour later with no joy, I pressed the button for longer to force a shutdown. Restarting in GUI mode, everything seemed OK, until I attempted to start the array, which seemed to freeze on disk 1 “mounting”. Hours later it was still there, starting the array, and I wasn’t able to cleanly shut it down. I did try shutting down in the terminal, but it wouldn’t so I powered off again. I read a fair bit about pool corruption causing this issue, and I tried to start the array with no pool drives assigned. Fail. As the Disk 1 was the one which was stuck on mounting, I tried to restart the array with that disk removed. Failed. I then (Hard shutdown again) and added the disk 1 back. It is now going to be in emulated mode and all data will be destroyed. I guessed with 2 parity drives that might be ok? Memtest ran for nearly 24 hours with no errors. 11 passes, no errors. We did have a bit of a storm the night things went wrong, but nothing else seemed to be troubled the morning I found the issue, and the UPS powers the Disk cage and Protectli computer. I can’t download diagnostics with the array attempting to start, it won’t complete, but I have downloaded 2 system logs, attached as zips and diagnostics with the array turned off. I also attach results of zpool import, I think this clearly shows an issue with disk 1, but why are there 2 disk ones showing in the result?? I am not sure if this issue is the same as other threads I have been reading about as mine doesn’t obviously involve cache drives, it seems (to me) the main array that has an issue. I shall stop messing with it until someone PLEASE gives me some advice! I am new to this, so I will need simple instructions please! Many thanks, Ian screencapture-192-168-0-10-42a43a9b4c02c56ad8f9e8bba99a59f40828e42f-myunraid-net-Main-2023-12-09-21_34_22.pdf unraidnas-diagnostics-20231229-0814.zip unraidnas-syslog-20231228-1101.zip unraidnas-syslog-20231228-1342.zip zpool import result.txt

As I say I haven't got it to work either. But, did you login to your Dropbox account by clicking the link in the logs? If you haven't done that, and you do, I reckon you will see you are stuck at the same place as me? In the docker tab, click Dropbox and select logs...

I am new, very, and I am not sure where to post this - it may be a pfsense issue, or a Jellyfin issue or something else. Upgraded to 6.12.6, this may or not be relevant, perhaps coincidental. My Jellyfin address was 192.168.0.10:8096 and it was working on various firesticks as clients, but it all stopped working, I noticed this the same day I upgraded. That is likely a coincidence? I run Pfsense on a separate unit, and I set up No IP to update my IP address there using the address carricknamadoo.ddns.net a while ago. I am unaware of changing anything in pfsense of late. Now to get to my Jellyfin I have to find the server at 192.168.0.10:8096/http://carricknamadoo.ddns.net Opening the docker WebUi (BinHex Jellyfin) took me there which gave me the clue the address had changed, as that was the resulting address in the address bar. I have no idea what caused this, but I can get around it using the longer address on my local network, but I would love to know if anyone could suggest a reason as to why? A similar thing happened when I installed Unraid connect - the resulting address was not what was typed, but that didn't break connectivity on my 5 firesticks. This time the address change did. I am posting here as i have no idea if this is a pfsense, jellyfin, or 6.12.6 issue, or even if it an issue at all, but i feel it is to me. Any thoughts or suggestions please? I will move this somewhere else if someone tells me to, but i have no idea where to place it other than here. Thanks.

Did you get Dropbox working!? So, did you login using the link shown in logs and link yur Dropbox account to the app? If you did, how did you manage the error i mentioned? I hope you are further along than I got, if so you should find a Dropbox folder in your shares? But I think you have to set that folder up before installling the dropbox container, as you need to point to it in the install files? But I am as new as you here!

My first post, so I am a total newb. Running Unraid 6.12.4. I tried otherguys Dropbox first, only as it had more downloads, but I couldn't get it working because of the [ALERT]: Dropbox needs to rename your existing folder or file named Dropbox to finish installing. Please close any open documents and try again. I have read what I can about this, and from what I could see Otherguy support seemed to not explain this, so I deleted that container and the Dropbox folder and started again with ken-ji's, this docker, but I have the same problem and no understanding of how to perhaps force a no update to dropbox? As I had read elsewhere, I would have thought forcing a no update would not fix the issue as I read elsewhere that Dropbox would eventually say "nope" to an older piece of software, but I AM A COMPLETE NEWB. Little experience of Linux over the years apart from copy pasting scripts to copy other folks fixes, mostly on a smoothwall server. Watched a lot of SpaceInvader One videos, but though they are excellent, many seem to age quickly as unraid updates. Any suggestions for a complete new guy on this or should I give up? My next thought was binhex-rclone, but I may fair worse with that!? Thank you