Is there a way I can configure unraid from the commandline to either:

a) don't start the array on boot?, or

b) pass additional flags to the btrfs mount command?

 

I had a two-drive "raid 1"-style btrfs cache array. One of the drives flaked out due to drive flakyness and dropped out of the array. I rebooted, and immediately upon coming back up it automatically started a 'btrfs balance'.

 

The btrfs balance is now stuck, btrfs/disk errors filling up the syslog, and the balance can't be cancelled (either via web UI or command line), because the 'cancel' command waits until it has finished balancing the current block -- and balance is stuck not making forward progress because disk errors.

 

If I could manage the disks in the webUI, I could un-assign/re-assign the cache disks as needed with good drives.  But I can't cleanly stop the array once it's started, because /mnt/cache can't be unmounted, because it's still balancing and automatically starts balancing on boot -- so the webui spins forever trying to stop.

 

The other option is to pass skip_balance on mount:

The balance operation is cancellable by the user. The on-disk state of the filesystem is always consistent so an unexpected interruption (eg. system crash' date=' reboot) does not corrupt the filesystem. The progress of the balance operation is temporarily stored and will be resumed upon mount, unless the mount option skip_balance is specified.[/quote']

Is there a way I can configure unraid from the commandline to either:

a) don't start the array on boot?, or

 

edit config/disk.cfg on the flash drive...  change startArray from "yes" to "no"

Thanks, that did the trick

 

A latent btrfs bug prevented me from non-destructively fixing the problem ("a raid1 pool can be mounted degraded as rw only once, after that it's read only unless you have all the disks present") -- which I didn't know until too late, and could no longer 'fix' the existing pool or convert from raid1 to single.

 

Copied everything off and working on rebuilding manually though