Issues mirroring boot drive due to size.

Urumiko

Dabbler
Joined
Jul 2, 2017
Messages
32
Hi all, Please treat me gentle as I only ever live in the gui.

I usually run my boot drive mirrored across 2 32gb USBs.

One of them kept going bad so i've today replaced it and keep getting the following error, which doesn't seem to make much sense as the kingston is being reported as bigger. I've used discpart to clean the stick and still no joy.

Is there a workaround that will let me shrink the existing boot drive and try again?

I would have no issue doing a fresh install if its easier if someone could tell me how to back up / re import my plex server as that's what takes the most time to set up.

Cheers.

Request Method: POST
Request URL: http://10.0.1.14/system/bootenv/pool/attach/?label=da0p2
Software Version: FreeNAS-11.1-U7 (b45bfcf29)
Exception Type: MiddlewareError
Exception Value: [MiddlewareError: [EFAULT] The device called Kingston DataTraveler 3.0 (28.90 GB, 60604416 sectors does not have enough space to mirror the old device SanDisk Cruzer Fit (29.81 GB, 62521344 sectors). Please use a larger device.]
Exception Location: ./freenasUI/system/forms.py in done, line 299
Server time: Sat, 1 Jun 2019 15:54:18 +0100
Traceback



Request information
GET
Variable Value label'da0p2'
POST
Variable Value __all__''attach_disk'da2'__form_id'form_BootEnvPoolAttachForm' FILES
No FILES data
COOKIES
Variable Value csrftoken'********'sessionid'mpmfasnhf3s0sl3d07guieb0llxecm98'fntreeSaveStateCookie'root%2Croot%2F176%2Croot%2F9' META
Variable Value
 

HoneyBadger

actually does care
Administrator
Moderator
iXsystems
Joined
Feb 6, 2014
Messages
5,112
Unfortunately there's no easy way around this. For data vdevs, FreeNAS tries to avoid this with the 2GB swap partition (which can be disabled temporarily) but it automatically consumes the entire boot device, and I believe it has autoexpand enabled.

The Kingston is possibly more overprovisioned than the SanDisk, so that's why it has fewer sectors. You'll have to seek out a matching device or a larger (64GB) model.

If you're willing to do a fresh install, you should be able to back up your config from inside Plex, and restore it to a new jail. I'm not a Plex user myself so someone else will have to help with the particulars there, sorry.
 

anmnz

Patron
Joined
Feb 17, 2018
Messages
286
This is your boot pool, right? The boot pool is only used by FreeNAS itself. So:

Take a backup of system config (in the GUI at System -> General -> Save Config). Reinstall FreeNAS. Restore the config backup (System -> General -> Upload Config). That's it.

Whatever you have configured in FreeNAS to get Plex working (plugin config, storage mount points, whatever) will be restored from backup and should keep working as if nothing had changed. Your actual Plex data (stuff that you configure inside Plex as opposed to inside FreeNAS) doesn't live on the boot pool so will remain untouched by the reinstall.
 
Top