Upgrade failure - I think

[apostolakisl]

I installed the 14.1 polisy image and it formatted my drive with only a 3GB partition and left the rest of the drive unformatted. 

If you do an image restore, I would definitely run the df command to confirm you haven't trapped yourself in a barely big enough partition.  I posted a link to a youtube video that shows you how to pretty quickly expand the partition if indeed you need to.  

The 14.1 image is 5.9.1 and the older bsd version.  But after installing that image, fixing the partition size, I was able to update to 6.0.0 and the newer BSD just fine.

[xlurkr]

Looks like I got a small partition.  This is a 32GB SSD.

Everything is working, but not a lot of free space.  I'm going to check out the video.

-Tom

[xlurkr]

8 hours ago, apostolakisl said:

I posted a link to a youtube video that shows you how to pretty quickly expand the partition if indeed you need to.  

I saw this, but I can't find it.  can you repost?  Thanks.

@Michel Kohanim your image did get me going again, but I'm concerned about the disk image size.  Should I be?  Is there a reason that the total disk space is so much smaller than before, and the used amount (capacity) is so much higher?

-Tom

[Guy Lavoie]

So this small filesystem size thing is popping up again. That's three of us now.

[paulbates]

Sounds like the thing to do is SSH in and check that prior to proceeding with the upgrade

[apostolakisl]

10 hours ago, xlurkr said:

I saw this, but I can't find it.  can you repost?  Thanks.

@Michel Kohanim your image did get me going again, but I'm concerned about the disk image size.  Should I be?  Is there a reason that the total disk space is so much smaller than before, and the used amount (capacity) is so much higher?

-Tom

This worked for me exactly as posted in the video except for subbing in "zudi" for "zroot" starting at 1:06 in the video.  The screen shot for the video here is where the creator is typing zroot, you should be using zudi here and on the next line as well.

Edited Saturday at 03:37 PM by apostolakisl

[apostolakisl]

1 hour ago, Guy Lavoie said:

So this small filesystem size thing is popping up again. That's three of us now.

Yeah, looks like his drive was only partitioned with less than 6GB of space.  After the update, I was using a bit over 6GB, so that would definitely not work out.

[xlurkr]

1 hour ago, apostolakisl said:

This worked for me exactly as posted in the video except for subbing in "zudi" for "zroot" starting at 1:06 in the video.

Thanks.  I found your older post and just did this on my Polisy.  In addition to the zudi substitution, I had to "sudo" the autoexpand command.  It looks like it worked.

Two additional comments: I'm not sure the update packages that I ran after reimaging did much, if anything.  And it probably all fit in the 6G original partition because this is an empty Polisy.

Now, I'd love to hear from anyone who has run upgrade packages on a Polisy and had it work correctly.  I still have not upgraded my working Polisy, and I don't want to without more confidence that it will work correctly.

-Tom

 

[Guy Lavoie]

5 minutes ago, xlurkr said:

Now, I'd love to hear from anyone who has run upgrade packages on a Polisy and had it work correctly.  I still have not upgraded my working Polisy, and I don't want to without more confidence that it will work correctly.

 

 One of my two Polisys did upgrade correctly, and I made an image of that one to reimage the other that didn't upgrade properly. The one that failed (the first one I tried) had one of those smaller filesystems, and it's one I had previously reimaged from a file provided by UDI. Hence the discussion about these incidents of smaller filesystems.

[apostolakisl]

4 hours ago, xlurkr said:

Thanks.  I found your older post and just did this on my Polisy.  In addition to the zudi substitution, I had to "sudo" the autoexpand command.  It looks like it worked.

Two additional comments: I'm not sure the update packages that I ran after reimaging did much, if anything.  And it probably all fit in the 6G original partition because this is an empty Polisy.

Now, I'd love to hear from anyone who has run upgrade packages on a Polisy and had it work correctly.  I still have not upgraded my working Polisy, and I don't want to without more confidence that it will work correctly.

-Tom

 

After I flashed polisy to 5.9.1 I only had 3GB on my drive.  I didn't know it at the time because I never checked, did think I needed to.  I then tried upgrade packages and it bricked it.  Then when I put the drive back onto my windows PC I discovered that the partition was only 3GB.  I flashed it again, and once again, 3GB.  At this point I did the above youtube instruction and it expanded my partition to 120GB.  Then I did the "update packages" command, it worked correctly.  So my polisy is now on 6.0.0.

EDIT:  Of note, after it updated to 6.0.0, polisy was using roughly 6GB of drive space, so I suspect your previous update packages would not have had enough room.  Surprised it didn't brick like mine.

Edited Saturday at 09:09 PM by apostolakisl

[xlurkr]

I think - not sure - that the image I flashed was already 6.0.  It was definitely FreeBSD 14.3 based on the name (though it was misspelled "poilsy" as @larryllix correctly documented.) That's why I said it didn't seem like the upgrade packages that I did after the reimage actually did anything.  Also, I think I had a 6GB partition from the start.

Perhaps Michel is creating these on the fly as each request comes in, and basing each new one on lessons learned from the last one.  I know that the link to my image was time-limited, because it timed out and I had to ask for another.  Meant to prevent sharing of images, potentially "bad" early ones?  Or maybe it's tied to my UUID somehow, for the purpose of tracking portal subscriptions?

-Tom

[GSORS400]

I all, not intending to hijack this thread.... but perhaps this may help others...

My Polisy update failed. I Putty'ed into to the unit and went though the recovery options and then the update was successful:

sudo rm /var/udx/.udx_install_cleanup
sudo rm /var/udx/.upgrade_status
sudo pkg install -f isy
sudo service udx restart

• Wait for two minutes

sudo service isy status

• Your eisy should now be available in your IoX Launcher. If it is, launch the Admin Console, go to the Configuration tab and click on Upgrade Packages button again. Wait till completion or reboot. 

Edited yesterday at 02:07 PM by GSORS400

[apostolakisl]

3 hours ago, xlurkr said:

I think - not sure - that the image I flashed was already 6.0.  It was definitely FreeBSD 14.3 based on the name (though it was misspelled "poilsy" as @larryllix correctly documented.) That's why I said it didn't seem like the upgrade packages that I did after the reimage actually did anything.  Also, I think I had a 6GB partition from the start.

Perhaps Michel is creating these on the fly as each request comes in, and basing each new one on lessons learned from the last one.  I know that the link to my image was time-limited, because it timed out and I had to ask for another.  Meant to prevent sharing of images, potentially "bad" early ones?  Or maybe it's tied to my UUID somehow, for the purpose of tracking portal subscriptions?

-Tom

I'm not positive on this, but I think those images could probably be loaded on "generic" hardware and UD is trying to keep them under wraps.

Whatever the partitioning is before you flash the drive is lost when you flash it using rufus and the images UD supplied.  The ssd I flashed to I had already formatted to the full 128GB and after flashing it was only ~3GB of usable space and rest inaccessible.  While I am sure all imaging software has its own details, the windows imaging software I use on a very regular basis creates an image with a partition size the same as the source.  If you try to restore to a smaller drive, it just won't, and if you restore it to a larger drive, you need to do some partition expansion or it goes unused.

[xlurkr]

Makes sense.  But what is the smallest drive ever shipped with a Polisy?  Both of mine are 32G, so why not have that be the default partition size?

-Tom

[apostolakisl]

16 hours ago, xlurkr said:

Makes sense.  But what is the smallest drive ever shipped with a Polisy?  Both of mine are 32G, so why not have that be the default partition size?

-Tom

???

[Guy Lavoie]

The two Polisys I have also have 32 GB SSDs. I doubt they ever came with something smaller.

[larryllix]

3 hours ago, Guy Lavoie said:

The two Polisys I have also have 32 GB SSDs. I doubt they ever came with something smaller.

Both my Polisae came with 32GB SSDs. Now they both have 64GB. One went bad and one has survived but totally spare now. For $26 I wasn't going to return it.

I think the partitioning had to be based on an old SD card format , saving some small hidden partition  for recovery images etc... Expanding that to 32GB made the remainder seem huge.

@Michel Kohanim is reading this and laughing!

Edited 20 hours ago by larryllix