SliMat

Hi All, I have just installed and set up My Servers, while it works fine it always shows an error - does anyone know how to fix this; Many thanks

Quick Update - during the reboot process I thought I'd play with the newly free'd up cache disk - so I re-assigned it as a cache disk then un-assigned it (again) and now it appears as assignable in the array 🙂 So... I'll keep checking for pointers on security practices. I currently have 6.8.3 installed as I was trying to use the SAS Spindown plugin which didnt work on my machine with 6.8.3... so I am going to upgrade to 6.9.2 now and play with "My Servers" too.

Hi @itimpi Yes, I had started to look at these and I suspect it was from when my Exchange server was hosted on UnRAID as this became compromised and it looks like someone has been attempting some sort of brute force attack - but, unless I am mistaken I dont see anything recent. I switched to Office365 in January to release me the burden of trying to maintain a creaking Exchange server 🙂 Any pointers on securing UnRAID greatly received!

Hi @itimpi Yes, this UnRAID server is in a datacentre - but it is behind a firewall (Mikrotik router). I do have Plex running which has serveral remote users that access it. I also have Resillo Sync running to synchronise files between two servers. I did have an Exchange Server running which was compromised as a result of a Microsoft vulnerability last November! Also running NextCloud - but this is only used by me and my brother for backing up work files. I also have a webserver/FTP server which allows suppliers to upload their price lists every hour too. I thought having the whole UnRAID box only accesible via a VPN would stop users accessing NextCloud/Plex? I'll have a read up on "My Servers" / "Wireguard" as I dont know anything about these. Would the above explain the remote access attempts you mention?

Hi @trurl I was wondering if the diagnostic file gave you any clues why I cant add the former unused cache disk in to the main array? Thanks

Thanks @trurl Attached. dl380p-rack-diagnostics-20220324-0924.zip

Thanks @trurl Is it best to attach the whole log zip file... or is there a specific file within the zip file to attach?

Hi @trurl Yes, sorry that I havent updated my sig in ages and forgot The machine is a DL380 with 25 x 2.5" SAS disk slots. Currently I have 2 x 2Tb, 5 x 1.2TB, 2 x 1Tb, 2 x 600Gb & 6 x 500Gb SAS disks. Then I also have 2 x 2Tb disks for parity. Yes, the 1.2Tb disks is a spinnig SAS disk, again another reason why I was planning to add to the array. I did explore an SSD cache disk and needed at least a 1Tb SSD as one VM alone was about 300Gb. This was my Exchnage server which is now redundant... so I may be able to get away with a smaller SSD as a cache to keep costs down. I havent looked into this recently... so might re-explore. So, in the meantime its just finding out why the 1.2Tb ex-cache disk isnt showing as available to add to the array. I did wonder if its because its formated BTRFS and not XFS... but I would expect UnRAID to identify the disk and allow a re-format.

Hi @JonathanM No, its not; Which is why I find it odd that its not listed as available to put in a spare slot.

I did look on the cache disk (before I unassigned it as cache disk) and the only folder on there was an old Plex one from when I ran Plex as a docker. It now runs in a VM. So, I deleted the redundant /appdata/plex folder and all still works... also, the server is active right now and everything is working with the cache disk removed.

Hi @JonathanM Yes, I configured them manually... eg; To be honest I havent noticed any real issues with performance - but to be fair I've never moved them to a cache disk to compare. I do have some spare 1.2Tb disks, so perhaps I should send them to the datacentre where my server is installed and get them to add them as I have about 5 or 6 spare disk bays - so could add them and then re-assign this 1.2Tb disk as a cache disk. From memory the reason I never used the cache disk for VMs or dockers is because of the risk of losing all if the disk failed. Thanks

Thanks @trurl I fitted a 1.2Tb cache disk, but have never assigned anything to it. At the moment the server is only being used for Plex, Nextcloud and a couple of webserver VMs for some WordPress websites... I retired my Exchange server and went with Office 365. However at the moment I have 14Tb of media in an 18 disk array (with 2 x 2Tb parity disks). Recently the server is down to a few Gb of space and last night I couldnt watch anything on Plex as it said that there wasnt enough disk space to convert the media. I deleted a couple of box sets and restarted it as a quick fix. So, I got to thinking that as I have a spare 1.2Tb disk assigned as a cache and not actually doing anything I would add it to the array to give me another 1.2Tb of media space. My thoughts are that if I dont knowingly have any speed issues then I obviously dont need a cache disk - especially as its been installed for a couple of years and not been used for anything! Any thoughts, comments?

Hi all I had a 1.2Tb cache disk which I have never used. Now my array is full and I need space I stopped the array and unassigned it as cache disk. Restarted the array and it warned me it would remove the cache disk assignment... which I did. I then expected the disk to be available to add to my array - I added an extra slot (number 19)... but the 1.2Tb disk is listed under "Unassigned Devices" and I can work out how to assign it to the array as its not listed as available to allocate to the slot. I know I am missing something simple - but can anyone offer any pointer? Thanks

👍

Sorry - found it... /boot 🙂

Hi All I tried to roll back to 6.9.1 from 6.9.2 by extracting bzimage, bzroot and bzroot-gui from the 6.9.1 zip and overwriting the originals on my 6.9.2 key... but this didnt seem to work as when I reboot I have no GUI on the LAN. Luckily I renamed the old files, so they are still on my key - however when the machine boots I can login to UnRAID at the command line - but dont know how to access the flash to replace the original files... can anyone point me in the right direction? Thanks

Hi @SimonF I upgraded to 6.9.2 and installed this addon at the same time, so have never used it under 6.9.1 (or earlier)... so I suspect that this is the issue... thanks - I will try to find where the issue is noted and look at the bug post. I may try going back to 6.9.1 - but as this is a production machine I will have to try this late one night when I can take it offline. Thanks

Hi All I have an HP DL380 G8 using the P420i/2Gb controller and an array of 18 disks using a variety of manufacturers. I recently found this addon and thought it would be great as I have 18 disks permanantly spun up... so, I installed it - but none of the disks ever spin down. I have an unused cache disk, so I clicked on spin down but it shows as still spun up - log below; Apr 20 19:58:43 DL380p-Rack kernel: sd 2:0:19:0: [sdu] 2344225968 512-byte logical blocks: (1.20 TB/1.09 TiB) Apr 20 19:58:43 DL380p-Rack kernel: sd 2:0:19:0: [sdu] Write Protect is off Apr 20 19:58:43 DL380p-Rack kernel: sd 2:0:19:0: [sdu] Mode Sense: e7 00 10 08 Apr 20 19:58:43 DL380p-Rack kernel: sd 2:0:19:0: [sdu] Write cache: disabled, read cache: enabled, supports DPO and FUA Apr 20 19:58:43 DL380p-Rack kernel: sdu: sdu1 Apr 20 19:58:43 DL380p-Rack kernel: sd 2:0:19:0: [sdu] Attached SCSI disk Apr 20 19:58:43 DL380p-Rack kernel: BTRFS: device fsid 12ff0c5a-8607-4875-93b9-c90cb75a3929 devid 1 transid 42 /dev/sdu1 scanned by udevd (2160) Apr 20 19:59:08 DL380p-Rack emhttpd: EG001200JWJNQ_WFK27GGJ_35000c500bc3cdd27 (sdu) 512 2344225968 Apr 20 19:59:09 DL380p-Rack emhttpd: import 30 cache device: (sdu) EG001200JWJNQ_WFK27GGJ_35000c500bc3cdd27 Apr 20 19:59:09 DL380p-Rack emhttpd: read SMART /dev/sdu Apr 20 19:59:27 DL380p-Rack emhttpd: shcmd (107): mount -t btrfs -o noatime,space_cache=v2 /dev/sdu1 /mnt/cache Apr 20 19:59:27 DL380p-Rack kernel: BTRFS info (device sdu1): enabling free space tree Apr 20 19:59:27 DL380p-Rack kernel: BTRFS info (device sdu1): using free space tree Apr 20 19:59:27 DL380p-Rack kernel: BTRFS info (device sdu1): has skinny extents Apr 20 19:59:27 DL380p-Rack kernel: BTRFS info (device sdu1): creating free space tree Apr 20 19:59:27 DL380p-Rack kernel: BTRFS info (device sdu1): setting compat-ro feature flag for FREE_SPACE_TREE (0x1) Apr 20 19:59:27 DL380p-Rack kernel: BTRFS info (device sdu1): setting compat-ro feature flag for FREE_SPACE_TREE_VALID (0x2) Apr 20 20:51:34 DL380p-Rack emhttpd: spinning down /dev/sdu Apr 20 20:51:34 DL380p-Rack SAS Assist v0.85: Spinning down device /dev/sdu Apr 20 20:51:38 DL380p-Rack emhttpd: read SMART /dev/sdu Apr 20 20:56:31 DL380p-Rack emhttpd: spinning down /dev/sdu Apr 20 20:56:31 DL380p-Rack SAS Assist v0.85: Spinning down device /dev/sdu Apr 20 20:56:35 DL380p-Rack emhttpd: read SMART /dev/sdu I have seen varying reports of disk incompatibility... but can anyone confirm if this works with the P420, or have I done something wrong? Thanks

Cheers @ConnerVT Guessed that would be the case, but thought I'd better check the process in case there are any quirks. Nice to know though.

Thanks @trurl

Hi @trurl I have finally got a second 2Tb parity disk, which has been precleared, and I am able to get in to my server tomorrow to install it. I just wanted to check, as there doesnt seem to be a lot of info about second parity disks... when I take the array offline to insert it, when I assign the drive is there a "parity 2" option and if so I guess I just select this and spin the array up and it should do everything else? Thanks.

OK - I worked it out... because I was pointing the new installation to the original /mnt/user/nextcloud/ share on UnRAID - I had renamed all my original users folders so that as I added the users back in, it wouldnt delete their original data. However, I started with a test user account from the original installtion, but didnt rename the users data folder as I was going to test it. So, when I entered the original test users details, Nextcloud was trying to create a user folder - but couldnt create it as there was already a user folder there with the same name. So, I changed the test users data folder name (like all the others) and then Nextcloud was able to create the user folder in the new installation and I am now copying their data back into the newly created folders. 🙂

Hi all, I had issues with my original Linuxserver Nexcloud docker after trying to update from v17 to v20 - so today I deleted my mariadb and my original nextcloud docker and started again. I also deleted the /appdata/mariadb/ and /appdata/nextcloud/ folders, so it really is a clean install. Anyway, after recreating the MySQL database and reinstalling NextCloud 20.0.6 all was good. I set up SMTP and then tried to recreate my first user and this is where the problem starts. As soon as I try to add a user I get an error - An error occured during the request. Unable to proceed. Bad request Has anyone else had this error or know how I might be able to fix this? Thanks

Thanks @strike@Tom3@John_M Theres a lot to go through here and to compound it I dont seem able to change (or define during setup) where my Nextcloud VM stores its datafiles... so it may look like I will end up setting up a new Linxserver Nextcloud Docker instead as this worked... but I will look to see if theres any info on how to get my new NextCloud VM to use the mounted \nextcloud share for its file store. I have a lot going on at the moment, including a failed Exchnage server, which is taking priority - but I will feedback what happens in the end in case anyone else stumbles on this post with similar issues. Many thanks for all the great advice and I'll let you know how I get on.

Hi @Tom3 I set permissions to 776 and still get access denied - on the UnRAID server it shows; drwxrwxrw- 1 99 users 108 Oct 3 2019 nextcloud So its odd that with RW permissions I still cant access the share - so it looks like I may have to set everything to 777 recursively for files and folders... obviously going forward when I get NextCloud back online, any new files created will show what UID/GID is being assigned by the Nextcloud VM. Thanks