April 2Apr 2 Author 20 hours ago, trurl said:What happens if you use the stock go file?Hi @trurl stock go file does indeed help to bring it back to under 2 seconds! The strange thing is, the Go file on my backupserver Epic-Bravo, is the same, except for the starting of the dockers, and the ZFS settings. Epic-Bravo IS quick, so I am very curious what settings cause Epic-Alpha to be slow.
April 2Apr 2 Community Expert 1 hour ago, TallMan206 said:except for the starting of the dockers, and the ZFS settings.These shouldn't be in go
April 2Apr 2 Author 25 minutes ago, trurl said:These shouldn't be in goHi, where should I put them then? I do not want multiple settings in multiple files over my systems where in 3 months I don't know where I changed what. Therefore I did this in ONE file, the GO file.Please, advice me, if you have a better option. Thanks!
April 2Apr 2 Community Expert 4 minutes ago, TallMan206 said:Hi, where should I put them then? I do not want multiple settings in multiple files over my systems where in 3 months I don't know where I changed what. Therefore I did this in ONE file, the GO file.Please, advice me, if you have a better option. Thanks!You would create scripts using the user-scripts plugin and execute them at "First Array Start"
April 2Apr 2 Community Expert 15 minutes ago, MowMdown said:You would create scripts using the user-scripts plugin and execute them at "First Array Start"This is the preferred method for anything you might consider putting in go
April 2Apr 2 Author 15 minutes ago, trurl said:This is the preferred method for anything you might consider putting in goDone. Everything is out of the GO file and into user scripts. Thanks.
April 2Apr 2 Community Expert go runs before the array is started. The only storage that actually exists at that point is /boot (the boot flash drive).
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.