Reallocating the drive to use the full 64 MB is more work, because another partition has to be moved (partitions have to be contiguous). I also have a 64 GB SSD in one of my Polisys, but I left it configured as a 32 GB. The whole UDI software only requires about 6 GB.

6 minutes ago, Guy Lavoie said:

Reallocating the drive to use the full 64 MB is more work, because another partition has to be moved (partitions have to be contiguous). I also have a 64 GB SSD in one of my Polisys, but I left it configured as a 32 GB. The whole UDI software only requires about 6 GB.

Geeesh. I am totally about 250K x 1K blocked used but my df total shows about 5,500K x 1K blocks on the drive.

Somebody has been stealing my sectors!!!!

There must be a sector compaction command on freeBSD..maybe somewhat dangerous for a running system though.

I suspect the hardware in polisy may not handle more sectors than 32 GB of space.....eeeew, dread the thought.

Maybe I ordered too many pizzas on my polisy?

Edited Saturday at 09:53 PM2 days by larryllix

No, the hardware can handle both 32 and 64 GB SSDs. If you do have a spare SSD as you seem to saying try this: make a backup of your current system, then take out the SSD. Flash the new SSD the way you did it to recover and put that in your Polisy, then restore your backup. Now you're running a clone of your system, and do the filesystem expansion process as shown in the video. No risk for your original SSD.

40 minutes ago, Guy Lavoie said:

No, the hardware can handle both 32 and 64 GB SSDs. If you do have a spare SSD as you seem to saying try this: make a backup of your current system, then take out the SSD. Flash the new SSD the way you did it to recover and put that in your Polisy, then restore your backup. Now you're running a clone of your system, and do the filesystem expansion process as shown in the video. No risk for your original SSD.

I just realised that imagers require an image, not a file backup. Can the imagers produce an image from and existing HDD?

I gave up on Rufus last time. It didn't appear to be able to handle and image larger than 2 or 16 GB. I d/l another program (diskimager) and it worked just fine.

There still must be something wrong with 32 GB used up on this system. There has to be tonnes of spare space left, somewhere. Even the df counts don't add up to the totals. Three main folders show about 55MB each and a few others show 1-2MB each. I can't account for more than about 250 MB (0.25 GB). ?????

Did you get your eisy-ui into your 32GB partition?

Edited Saturday at 10:51 PM2 days by larryllix

12 minutes ago, larryllix said:

I just realised that imagers require an image, not a file backup. Can the imagers produce an image from and existing HDD?


Did you get your eisy-ui into your 32GB partition?

Yes, I've done that: make a new image file. 32 GB is plenty of space for everything, including eisy-ui, plugins etc. The screenshot of my df command above is my test Polisy with all the latest versions.

Since you say you have 2 Polisys, why not make a new image file from the not reimaged one instead of the recovery image you got from UDI. It's that recovery image (I think it was 5.9.1) that had the problematic small image.

But post your df screenshot. I'd like to see it.

Edited Saturday at 11:12 PM2 days by Guy Lavoie

36 minutes ago, Guy Lavoie said:

Yes, I've done that: make a new image file. 32 GB is plenty of space for everything, including eisy-ui, plugins etc. The screenshot of my df command above is my test Polisy with all the latest versions.

Since you say you have 2 Polisys, why not make a new image file from the not reimaged one instead of the recovery image you got from UDI. It's that recovery image (I think it was 5.9.1) that had the problematic small image.

But post your df screenshot. I'd like to see it.

I found info on expanding your freeBSD SSD drive partitions and so far...it seems totally successful.

It took some nerves and some guessing at system naming but I got through it.

https://kb.royalehosting.net/en/article/how-to-resize-a-freebsd-partition-eu4wlu/#2-3-resize-the-partition

The last line needs to use "zudi" instead of the "zpool" as listed. The line number 5 referred to was line 3 in my system.

I think I had to reboot my polisy when done as eisy-ui seemed a bit of a mess. Took a while to come back without insanity.

Things are much better. Lines are still little too fat vertically but much, much better. From what I can remember now, those boxes can never be filled out to the edges in HTML code. Nice going @Javi (pat on the back)

@larryllix ,

There's a command in the instructions for reflash (wish you had submitted a ticket):
In Case of Errors (no beep):

1. On Windows, use Command app

2. On Mac, use Terminal app

3. Type ssh admin@1.2.3.4 where 1.2.3.4 is replaced by the actual IP address for your Polisy

4. When prompted for password, type:
   admin

5. Issue the following commands:

6. curl -s https://pkg.isy.io/script/resize32.sh | sudo bash

7. sudo pkg install -f eisyui isy pg3x sqlite3

8. sudo reboot

4 minutes ago, Michel Kohanim said:

@larryllix ,

There's a command in the instructions for reflash (wish you had submitted a ticket):
In Case of Errors (no beep):

1. On Windows, use Command app

2. On Mac, use Terminal app

3. Type ssh admin@1.2.3.4 where 1.2.3.4 is replaced by the actual IP address for your Polisy

4. When prompted for password, type:
   admin

5. Issue the following commands:

6. curl -s https://pkg.isy.io/script/resize32.sh | sudo bash

7. sudo pkg install -f eisyui isy pg3x sqlite3

8. sudo reboot

Thanks but ll seems to be working now with the method I used.

It doesn't seem to make sense I am using 32GB of SSD with this system though. Others didn't need the extra room, apparently.

4 hours ago, Michel Kohanim said:

@larryllix ,

There's a command in the instructions for reflash (wish you had submitted a ticket):
In Case of Errors (no beep):

1. On Windows, use Command app

2. On Mac, use Terminal app

3. Type ssh admin@1.2.3.4 where 1.2.3.4 is replaced by the actual IP address for your Polisy

4. When prompted for password, type:
   admin

5. Issue the following commands:

6. curl -s https://pkg.isy.io/script/resize32.sh | sudo bash

7. sudo pkg install -f eisyui isy pg3x sqlite3

8. sudo reboot

The reflash instructions that several of us got last year didn't mention the resize32 script! Better late than never 🙂

23 minutes ago, Guy Lavoie said:

The reflash instructions that several of us got last year didn't mention the resize32 script! Better late than never 🙂

I'm obviously not understanding this sector usage chart on my polisy but some things just don't seem to add up to 32GB being full.

----------------------------------------------------------------------------------------
[admin@polisy ~]$ df
Filesystem 1K-blocks Used Avail Capacity Mounted on
zudi/ROOT/default 60295013 4666919 55628093 8% /
devfs 1 0 1 0% /dev
procfs 8 0 8 0% /proc
zudi/tmp 55628128 35 55628093 0% /tmp
zudi/usr/home 55628183 90 55628093 0% /usr/home
zudi/var/polyglot 10485760 55429 10430330 1% /var/polyglot
zudi/var/isy 10485760 56322 10429437 1% /var/isy
zudi/var/log 55628710 616 55628093 0% /var/log
zudi 55628117 24 55628093 0% /zudi
zudi/var/tmp 55628117 24 55628093 0% /var/tmp
zudi/var/empty 55628117 24 55628093 0% /var/empty
zudi/var/db 55629372 1279 55628093 0% /var/db
zudi/var/run 55628142 48 55628093 0% /var/run
zudi/var/crash 55628117 24 55628093 0% /var/crash
zudi/var/db/pkg 55663864 35770 55628093 0% /var/db/pkg

Edited Sunday at 07:27 PM1 day by larryllix

11 minutes ago, larryllix said:

I'm obviously not understanding this sector usage chart on my polisy but some things just don't seem to add up to 32GB being full.

----------------------------------------------------------------------------------------

Filesystem 1K-blocks Used Avail Capacity Mounted on
zudi/ROOT/default 60295013 4666919 55628093 8% /

That looks more like a 64 GB SSD getting full available capacity.

1 hour ago, Guy Lavoie said:

That looks more like a 64 GB SSD getting full available capacity.

That is the 64 GB, fully captured by the polisy system.