SliMat

Members
  • Posts

    267
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • Location
    UK
  • Personal Text
    Heat Is The Enemy!!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

SliMat's Achievements

Contributor

Contributor (5/14)

7

Reputation

  1. 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
  2. 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
  3. 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
  4. 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.
  5. 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.
  6. 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. 🙂
  7. 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
  8. 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.
  9. 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
  10. Hi @Tom3@John_M OK, the /mnt/user/nextcloud share on the UnRAID server was 770... I tried 776 but was still getting permission denied - unsurprisingly I set the nextcloud folder permissions to 777 and was allowed in - but I have noticed files are 775 which means I will be able to read and not write to them. Also I am not keen on setting 777 permissions unless absolutely needed. The /mnt/user/nextcloud folder ownership on UnRAID is; drwxrwx--- 1 nobody users 108 Oct 3 2019 nextcloud/ so, is the best/safest way to give my new VM full read/write to this share and all its files/folders to chmod 777 recursively (simple), or to change the UID & GID of the VM's user to nobody:users (99:100 ?). If this is the best way - I have the user I login with and the unused root account... do I need to create a "nobody" user and a "users" group? If so, how do I do this? This nextcloud server is only being used for family - so I dont have any real concerns about security so if 777 recursively is simplest and reasonably safe then I can do this. Many thanks Many thanks
  11. Thanks @John_M - hopefully I may get a chance to play with this later tonight and see how it goes
  12. Thanks @Tom3 - I'll have a play tonight when I get a chance and test it out.