You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, thanks for this script and the write up on your blog.
I'm running your script on a new disk under FreeBSD after having 1 of 3 new disks fail on me. (I'm a total noob, and the last thing I expected (trying to rescue my raid from near death) was a problem with the new disk!)
Anyway, I'm now running a burn in on the RMA'd replacement, but I forgot to execute this first: sysctl kern.geom.debugflags=0x10
Should I now:
Kill the bb process and do that now?
Do it now with the bb process running anyway?
Just not do it and don't worry so much?
I read somewhere that after you've set this kernel flag you should un-set it again later (e.g. reboot) to avoid 'problems'... (Note that my pool is currently online (DEGRADED but backed up), as I'm using the freenas box itself to burn in the new disk).
Sorry for the noobs and thanks for any advice,
Dan.
The text was updated successfully, but these errors were encountered:
dbolser
changed the title
Forgot to run sysctl kern.geom.debugflags=0x10 on FreeBSD?
Forgot to set kern.geom.debugflags on FreeBSD?
Mar 8, 2021
Hello, thanks for this script and the write up on your blog.
I'm running your script on a new disk under FreeBSD after having 1 of 3 new disks fail on me. (I'm a total noob, and the last thing I expected (trying to rescue my raid from near death) was a problem with the new disk!)
Anyway, I'm now running a burn in on the RMA'd replacement, but I forgot to execute this first:
sysctl kern.geom.debugflags=0x10
Should I now:
I read somewhere that after you've set this kernel flag you should un-set it again later (e.g. reboot) to avoid 'problems'... (Note that my pool is currently online (DEGRADED but backed up), as I'm using the freenas box itself to burn in the new disk).
Sorry for the noobs and thanks for any advice,
Dan.
The text was updated successfully, but these errors were encountered: