-
Any help would be greatly appreciated
I have had issues with the connection to this media centre since I started to build it. It drops to 100 mbs all the time. I have changed everything I physically can, bar changing the motherboard, so if there is another network option, I think this is the only option left before changing the MB This has now solved the issue with the cache pool! Thank you for helping me with that! I really do appreciate it.
-
Any help would be greatly appreciated
It came back on with /etc/rc.d/rc.nginx start I have attached the diagnostics. It is strange as to why it is stopping mainmediaserver-diagnostics-20261113-1154.zip
-
Any help would be greatly appreciated
-
Any help would be greatly appreciated
It seems I have a problem. I left the server and have not touched it since yesterday for it to become unreachable. What is strange is Plex and other Docker apps are working fine, like Radarr and Sonarr, but the main dashboard is not reachable.
-
Any help would be greatly appreciated
Here is the output from the last command below: Should I stop the parity check or let it finish before I continue?
-
Any help would be greatly appreciated
I do not have the option to attach files on my account it seems nothing shows up like you have highlighted I have uploaded it to my dropbox again, i am sorry to do it like this but its strange i have no option like you do and i have tried 3 different browsers EDIT: If i click edit post i get the option to drag files and attach. I have attached the diagnostics now :) Here is a screenshot of the reply to this topic box: Here is the Edit post: I am not sure of why my account has this problem NEWmainmediaserver-diagnostics-20261112-0815.zip
-
Any help would be greatly appreciated
I have added it to a Dropbox and created a download link: Diagnostics
-
Any help would be greatly appreciated
I don't seem to have a way to attach the file. I will try uploading to a file sharer and add a link
-
Any help would be greatly appreciated
I am really sorry for the late reply. I work horrid hours, and I have to wait till I get time off to be able to have time to fix issues like these. So I have tried But this gives me an error: ERROR: cannot access '/mnt/cache': No such file or directory WARNING: skipping missing devices check due to failure: No such file or directory ERROR: cannot access '/mnt/cache': No such file or directory This also does not work I have an issue now where the server will not start the array, showing this error: Wrong Pool State cache - too many wrong or missing devices So right now my server is down and not running
-
FlunkyBob started following Any help would be greatly appreciated
-
Any help would be greatly appreciated
I work ungodly hours. I have not forgotten this either. I will have time later today to hopefully get this sorted Thank you to you all for helping me so far
-
Any help would be greatly appreciated
I have checked and tested this morning, and all seems fine apart from the cache disk error showing on the Main My shares are there, although with a warning that the parity is not fully finished, and my Docker apps all work fine
-
Any help would be greatly appreciated
I have set Disk 4 back to the parity drive and started the new config I am however, getting errors coming up like those in the screenshots How should I proceed? I have paused parity sync for the moment
-
Any help would be greatly appreciated
Here is what lsblk -o NAME,SIZE,FSTYPE,SERIAL gave me: NAME SIZE FSTYPE SERIAL loop0 736.1M squashfs loop1 308.3M squashfs sda 58.9G A20052630D650C58 └─sda1 58.9G vfat sdb 18.2T ZVT8EY4P └─sdb1 18.2T xfs sdc 18.2T ZVTASG8C └─sdc1 18.2T xfs sdd 18.2T ZVT894XM └─sdd1 18.2T xfs sde 18.2T ZVT7XXNE └─sde1 18.2T xfs sr0 1024M KLON5PA4401 zram0 0B nvme0n1 931.5G 25014D67B6D2 ├─nvme0n1p1 1M ├─nvme0n1p2 510M vfat ├─nvme0n1p3 127.5G zfs_member └─nvme0n1p4 803.5G nvme1n1 931.5G 25014D647ACC └─nvme1n1p1 931.5G btrfs The NVMe's were there to help with the system to run faster. I must admit the system is very slow and I think this is because of them not being in use, maybe? If this is ok, please let me know if I should continue with step 3. Thank you
-
Any help would be greatly appreciated
Thank you for the quick reply @UnraidSecretaryOffice - I have attached the diagnostics zip to this post. - I unfortunately do not remember the name of the pool. I think it was called 'cache', but I'm not too sure. - I did run it more than once. I feared I did it wrong the first time, and running again it would correct the issue. - I have an older backup of the USB stick, and appdata is backed up by Unraid on the server. As for the "All existing data on this device will be OVERWRITTEN" warning, I did do the tools -> newconfig, as it thought that might allow me to start again with the drives. It was foolish of me, as I should not mess with things I know nothing about. I have got the missing drive back up and showing in the cache pool, and the drive is in the boot pool now, where I originally put it Please see the screenshot: mainmediaserver-diagnostics-20261011-1452.zip
-
Any help would be greatly appreciated
Hiya, I have a big problem I cannot seem to get around. I tried to move to internal boot using one of the NVMe's I have on the system that was in a cache pool. I rebooted the system, and now I have no boot device, no cache pool, and somehow I have a message saying: All existing data on this device will be OVERWRITTEN when the array is started. On my array, which I DO NOT want to happen lol. I am a BIG novice. I set this server up watching a YouTube video 3 years ago and have not touched it bar using it to add my blurays for media storage, so please bear with me as I am not clued up on the Linux and Unraid side of things. If anyone would be able to advise me on how to get around getting things back to normal, I would be forever grateful, as I have A LOT of media I would like to keep This is the message I have about overwriting data: Here are the errors I have with the internal boot: You can see in the unasigned there is an NVMe. I think this was supposed to be in the cache pool. My memory stick is there too but not used as the boot, as I can remove it and it still boots up to unraid. Thank you
FlunkyBob
Members
-
Joined
-
Last visited