SliMat

server-diagnostics-20231117-1823.zip

Hi All I am in the process of building a new production server... at the moment it is just a blank shell - so this is not important and if its going to be hard to fix, I will just wipe everything and start again, although a solution may help others where this is critical to them Anyway, this is whats happened - I have built the server and assigned a 6Tb parity disk (xfs), 5 x 6Tb array disks(xfs) and a 500Gb SSD(btrfs) cache disk. Set everything up and moved /appdata, /domains and /system on the cache disk. All 'was' working fine. I then changed the RAID card and re-assigned all the disks in the correct slots and used tools->new config to clear the array and reassign them. I ticked the "parity is valid" box as no data has changed. Anyway, now when I start the array it all comes online fine - but the cache disk shows as File System "auto" and shows as unmountable: unsupported or no file system! obviously my /appdata /domains and /system shares are missing as they should be on the cache disk. Is there a fix for this, or am I better just wiping the USB key and starting from scratch again? Thanks in advance

Thanks @itimpi - I was looking for a new Tut to cover the new terminology and didn't find this as there is so much information pertaining to the old terminology. I will change mine to Primary Storage - Cache and Secondary Storage none as I want the performance. Also I will enable Exclusive Shares as this is not something I have seen before. I will also have a read of the above information and if there is anything I think could be clearer I will let you know. Many thanks

Thanks - that seemed the logical setting, but I just wanted to make sure as previously the settings haven't been intuitive. I guess the default setting is cache->array for normal shares that use the cache.

Hi all I have never really bothered with a cache disk and am building a new production machine, so thought I would fit a 500Gb SSD as a cache disk and then mirror this. I plan to run my dockers and VMs on here. Anyway, all the info I can find on setting up a cache disk use the terminology Cache Prefer / Cache Always / Cache Yes / Cache No - which I always found confusing. In the lateset versions this has changed and now in the share options I see Primary Storage Array/Cache and then Secondary Storage Array/Cache... which initially seems far more logical. I want the cache disk to store my appdata/system shares so, I think, I want to set Primary Storage to Cache and then the secondary storage to array (in case the cache disk fills up)... is that right? If so, when I set this, the default mover action is set to Cache -> Array... which, to me, implies that it will by default try and move anything on the cache disk to the array... which I dont think is what I need in this instance. So, am I better off setting secondary storage to None, so that as long as there is space on the cache disk everything will be fine? Is there a revised Tut anywhere which someone can point me to so I can configure this the correct way? I do plan to add a second 500Gb SSD as a mirror before I install this machine, so imagine I just add this as a pool device and then expect there to be a mirror option? Any advice greatly received. Thanks

Thanks @JorgeB I hoped it would be easy... and this machine has never had its key replaced. I have only ever changed one key, on another production machine - as it was over 10 years old and had been faultless, but decided to change the key in vase it decided to fail due to old age Thanks

Hi all OK, this is not quite as the subject appears as what I need to do is a bit more complicated than just transferring everything to a new USB key. I have a production server which I need to migrate from and have not found an easy way to do this... so, what I plan to do is build the replacement server and set up all my apps/dockers/vms etc. When its all up and running I will take this to the datacentre where my production box is hosted and then copy the data from the old machine to the shares on the new machine over the LAN. When this is done, the new machine will be used to replace the machine which is being decommissioned. However as I intend to set the new server up using a trial key, I would like to transfer the licence from the key in the old server to the key in the new machine, but without copying settings etc over. I just need it to activate my trial key so the new server works as I have prepared it offsite. Can anyone tell me if this is simple and how to do it? Many thanks

Ah OK... I was a bit impatient and saw it didnt show in my previous apps list... so I did a clean install and then copied the original /appdata/vaultwarden folder to the 'restored' server - everything worked fine and all my data was there - EXCEPT the organisational vaults - but none the less its proved to me the importance of backing up /appdata and has given me confidence that in the event of a failure I should be able to recover individuals data hopefully. Thanks for the info @itimpi

Thanks @itimpi I do have a local UnRAID machine here, which has never had Vaultwarden installed on it... I am guessing if I copy the /appdata/vaultwarden folder to this machine it would show up as a previous app and I could then 'restore' it and see if all the data is present? That would be an exact restore scenario as its on a completely different machine

No, I dont see anything for config data - these are all the allocations I see;

Ah, thanks. I wasn't sure - but if so, that makes it a lot easier... so I am guessing that my data for vaultwarden is in the appdata folder;

Hi all Am I right in thinking that any dockers installed and the data that they contain is stored in docker.img? I ask this as I am using vaultwarden and want to back up the data in it, in case of a complete failure. While you can export data from individual vaults, you cant export data from organizational vaults... so I was wondering if I took a snapshot of the docker.img and appdata - would this be enough to recover it to a new machine? I guess that with docker.img and the appdata folder you would be able to recover all the dockers and their data if there was a total loss of my UnRAID machine? If this is right, according to Midnight Commander I have the following locations showing docker.img; /mnt/disk1/system/docker /mnt/user0/system/docker /mnt/user/system/docker Am I correct in thinking that these will be the same file and are just symlinked showing it in 3 places? Any help appreciated.

Hi All I have a server in a datacentre which is primarily being used for Plex and Nextcloud. I dont have any VMs and am running the following dockers; adminer binhex-privoxyvpn binhex-radarr binhex-sonarr MariaDB-Official nextcloud NginixProxyManager PlexMediaServer resillo-sync vaultwarden I have to replace the hardware and the simplest way to get the data from one box to the other is to download to the new machine here at my house. So, my plan is to create identical shares on the new box and then download the data from the corresponding share on the production box. This is all pretty straight-forward. However I am trying to pre-plan how to recreate dockers etc. Ideally I would love to just arrive at the DC and swap the USB key from the old server to the new one and boot it up - but suspect this is far too simple 🤣 Can anyone set me in the right direction? Thanks

Shows what I know... many thanks

Hi @iXNyNe - can you clarify whether you mean use the 'apply update' option from the Docker menu in UnRAID, or to use the 'Open Updater' option from the administrator settings menu within the Nextcloud container? I am guessing its the latter... but just wanted to make 100% sure I do this correctly as nearly everytime I've ever done an update I have ended up deleting the Nextcloud docker and having to start from scratch Many thanks

Hi @Joshwaaa - What do you mean about the power usage? Did you want to know the power consumption of the server? Obviously this will depend on the number of disks fitted and I dont think this has anything to do with the critical BIOS failure.

OK - user error... sorry for wasting peoples time... I had connected the LAN cable to the wrong physical port on the server as I have multiple network cards But still - this may prompt people to check twice

Hi All I am hoping someone can help as I am really struggling with this now... I run UnRAID on an HP ML310e G8 and usually access the server through ILO... but boot with no GUI. However I physically re-sited my server today and when it booted it immediately shutdown... I wasnt sure what was going on, so forced a reboot - only when it crashed half way through booting up did I realise that the UPS was unplugged and the first time it booted, it identified this and shut down safely - the second time it crashed out as the UPS ran out of juice Anyway, since then when I boot it up there is no WebGUI on my LAN and my Mikrotik router doesn't see the IP address in the DHCP lease list. Although I am pretty sure its set to staic IP, so this may be a red herring... but its not listed anyway! From the host machine I get to the UnRAID command line login and can login with root & my_password. To try and fix it, I rebooted and selected boot with GUI and it takes me to the login screen. When I login I get a screen saying unable to connect to localhost... I have read a little and saw someone mentioned deleting /config/ssl/* - so I actually renamed /config/ssl to config/ssl-old and created an empty /config/ssl directory (I dont like just deleting things I am not 100% sure about!!) - my understanding was that this may generate new .pem files and fix this... it didnt fix the problem... I have also tried pinging the expected IP address on my LAN and just get a destination host unreachable error. I have also checked that the cat5 cable and switch are OK too I have also noticed that even though I cant access anything... all the disks are spun up which makes me think UnRAID is running a parity check due to the unclean shutdown?!?! So, can anyone help? Many thanks in advance.

Yes, thanks I used SpaceInvaderOnes tut years ago, so may start again tomorrow. I did chmod the updater directory to 777 too as this was where it flagged the write permissions error to, but it still errored... so I decided to start again Thanks

Thanks @malebron I did go down this route myself, but when I ran updater I got a write permissions error... so I have just deleted the docker entirely and started again - which is going to take hours to set up, but as I have been on this for over 2 weeks so far, I guessed it would still be quicker The only query I have now, is when I started the installation it warned me that I 'chose' SQLite as the database... which I didnt as there was no option to use MariaDB which is still installed from my previous NextCloud docker. Any ideas how to switch from SQLite... or, if it's OK to just use this anyhow? Thanks

I must be missing something as I have been trying every which way to get Nextcloud working again, but the 'update' just keeps failing saying that the installed version is higher than the upgrade... Any thoughts before I delete the Nextcloud docker and give up? Thanks

As soon as I change docker repository back to; lscr.io/linuxserver/nextcloud:latest The docker 'updates' and when I check the log file it shows; Cant start nextcloud because the version... Also when I change the repository to; lscr.io/linuxserver/nextcloud:version-26.0.2 It shows that NextCloud is running in log, well it actually DOESNT say it cant start it... so I assume its running - but I still have no Web UI ?!?!

Thanks @iXNyNe OK, my docker was turned off when I changed the image, when I started it, it did an update.... then when I ran: docker exec -it nextcloud updater.phar I get: I assume I should say no to update, as its a downgrade, then change back to original image and hopefully all be good?

Morning all, I am hoping this is a simple fix, but I lost connection to my Linuxserver/NextCloud WebUI a few weeks ago and have only just got round to looking at it. I thought it was a proxy issue till I realised that the WebUI couldnt be accessed from the IP address either. Twice while trying to access it I noticed an update showing as available in UnRAID, so have updated it. Today I finally logged in to UnRAID to take a look at the log files and get this; I have already tried running: docker exec -it nextcloud-2022 occ update But get this error: Could not open input file: /app/www/public/occ Any pointers on how to update this as it seems that the Update facility within the UnRAID docker section is not sufficient... I dont really want to have to delete everything and start all over again as I have done this several times historically and it seems my NextCloud spends more time down than up Thanks in advance

OK... I thought as all mover does is moves the files, it wouldnt hurt to move them using MC... so I moved the ones which seemed stuck onto the cache disk and now it shows as all my dockers & VMs on the SSD cache And its all working perfectly again