allow user to determine boot partition size w/ embedded

[jamaroney]

My embedded install is on a HDD, with swap and data partitions as well. When first installing, I can select the size of my swap partition, but I can't change (make larger) the size of the boot partition. If I could choose, say 4GB, then that would cover me for future upgrades as they get larger (such as 9.2.0.1), so I can just keep doing simple upgrades instead of a fresh install whenever there's a major firmware change.

[alexey123]

No need resize boot partition. It have 512M, this size is more than enough

[jamaroney]

Well, the boot size had to be increased for this latest release, so there's no guarantees that it won't happen again in the future.

Upgrading to 9.2.0.1 would have been much simpler if my boot HDD already had a larger system partition. And with an unreliable CD Drive, my otherwise fine older laptop doesn't like fresh installs.

[uniss]

No need resize boot partition. It have 512M, this size is more than enough

I'm looking at extended gui page and it says: size of md0 is 100% occupied. How (and where), in this case, I could setup virtualbox?

Code: Select all

$ df -h
Filesystem                                    Size    Used   Avail Capacity  Mounted on
/dev/md0                                      223M    223M      0B   100%    /
/dev/ufsid/542f00690e440337                   6.8G     12k    6.2G     0%    /mnt/Flash
/dev/ufsid/52636ea2f3d5dfb0                   3.5T    2.3T      1T    70%    /mnt/wd1
/dev/ufsid/54469a8934f53c8b                   3.5T    1.5T    1.8T    46%    /mnt/wd2
/dev/md1                                       61M     23M     35M    40%    /var
/dev/da0s1a                                   117M    114M    2.2M    98%    /cf

but if you know a way to increase boot partition I will be grateful for your help.

[silicium]

Well, the boot size had to be increased for this latest release, so there's no guarantees that it won't happen again in the future..

I also have a problem with this bloating featuritis trend, implementing planned obsolescence of too much hardware less than 10 years old. I had purchased a lot of 256MB CF cards for several thin clients and laptops, and would have to hack too much of the latest embedded release, or at least backport the fixes only into last 9.2.
For the latest release, I have one 512MB CF card that is a few MB shorter than the image size
So the solution is... build from source and take only what you need, you will learn a lot

[Lee Sharp]

The problem is that newer hardware requires newer images of FreeBSD which is larger. But the older versions did not suddenly go away. I have a few systems that will not run the newer images, but still work to serve files.

[alexey123]

but if you know a way to increase boot partition I will be grateful for your help.

1. Backup config.xml on PC, not on nas pool
2. inspect your boot partition

Code: Select all

gpart show da0s1

result ~

Code: Select all

=>      0  1044162  da0s1  BSD  (509M)
        0   256032      1  freebsd-ufs  (125M)
   256032   788130         - free -  (384M)

3. copy /cf content to any place .n I make copy to dataset

Code: Select all

cd /mnt/dataset 
mkdir nasbackup && cd nasbackup
cp -r -p /cf/* .

4. Umount /cf

Code: Select all

umount /cf

5. Resize it

Code: Select all

gpart resize -i 1 -s 1040000 da0s1

6 Format it

Code: Select all

 newfs /dev/da0s1a

7 . Mount back

Code: Select all

mount /dev/da0s1a /cf

8. Restore files from backup

Code: Select all

cd /cf
cp -r -p /mnt/dataset/nasbackup/* .

9. check

Code: Select all

ls

and

Code: Select all

gpart show da0s1
=>      0  1044162  da0s1  BSD  (509M)
        0  1040000      1  freebsd-ufs  (507M)
  1040000     4162         - free -  (2.0M)

For me -work

[jamaroney]

That worked great - thanks!!