Hi,

I'm trying to upgrade my pi4 via ssh. It hasn't been touche for a White.

What works :
- Sarpi updates ok
- Upgrade of glibc-solibs, pkgtools, bash and tmux ok
- Install-new ok

What I can't achieve :
- Upgrade-all from slackpkg or downloaded repo gives unfinished upgrade and everything segfaulting, even su or reboot.

When hard rebooted (plugged out/in), I have everything to start again (even installed packages have to be re-installed ). And I can't find logs.

Is it lack of space ? (Already moved packages to external disk)
Special arm upgrade order ?

Any hint would be apreciate !

What version of the distribution? 14.2 or -current?

I can't think of any reason that you'd get segfaults for, unless you did something like install packages from -current on 14.2 or vice versa, or your system's totally broken.

Look at the output of dmesg - perhaps it'll show you some file system or storage errors.

No.

Thanks for your reply !

I'm on current and will triple check my update configuration and dmesg.

If nothing arises I bet it could be sdcard failing or some black magic then go installing from fresh...

Not had any issues with couple my rpi sarpi installs or my bananapi pro install

good guess about failing sdcard, is there like some smartctrl, hdparm utility to identify issues for sdcards?

I've not had to worry about investigating questionable sdcard not sure how to investigate

let us know what if you find out what problem might be

I had an update/upgrade failure of -current with Xfce on a 16 GB SD card on RPi 4.

I hadn’t done sarpi updates yet. I was going to leave that until the end.

install-new went fine. There weren’t many packages in that.

The failure happened during upgrade-all. There were a lot of packages in that.

I hadn’t checked my available space before updating, and filled the card in the middle of the update/upgrade. I didn’t take a screenshot with my phone but saw several messages about packages not installed because disk full, despite not doing a full installation in order to save space (emacs, bsd-games, and Calligra and KDE l10ns.)

I am able to access files from my Sackware 14.2. (I opened a few from there after plugging the SD card into a card reader.)

This was (would have been) a big update and upgrade. I last updated early October, so today’s update would have included the upgrade to Xfce 4.14 and KDE 5. [Edit: drmozes notes in the next post that Xfce 4.14 and KDE5 upgrades are on their way.]

I expect I could have avoided the failure by doing the update/upgrade in smaller pieces rather than trying to swallow it whole, while keeping an eye on SD card capacity (or maybe by updating more often, or by using a bigger SD card, or maybe even by keeping /home on separate storage.)

That’s as far as I’ve taken it. I’m not sure yet if this installation is salvageable, or worth the time to try. It might be faster, or even only possible, to retrieve the few files I want and reinstall.

TKS

Not yet - I didn't build either of those but they are queued up.

You should to consume the updates by the 'batch' as any dependencies will (unless we missed any!) be included within that batch to maintain stability of the OS.
Just make sure there's enough space to house the downloaded files and some buffer on the OS to handle the package as it's being installed. The root filesystem should have at least (I reckon) a few hundred MB's free, even if your logs don't occupy space on the same filesystem.

It sounds like your OS is in bad state. It's going to be easier to reinstall it as you'd have to prop it up to some extent even to get pkgtools working.

1 members found this post helpful.

Stuart, thanks for the tip on installing in batches.

When I first installed, I had (if I remember right) a couple of GB free, but clearly haven’t been practicing good OS hygiene since.

No surprise that saving a few files, installing a few extra packages and some logs can add up to a couple of GB after a year, especially if, say, you never delete your old kernel txz files! I will certainly watch disk capacity more closely in future.

TKS

1 members found this post helpful.

I've 'killed' more than a few installs/builds/upgrades by not having enough working disk space available on the system.

Thanks for your inputs.

I finally had the time to dig in this but with no real succes : I should have enough space but 85% of the root partition is used, even after a good cleanup and I think this isn't enough for massive upgrade.

I moved slackpkg downloads on a side disk, as a lot of other stuff and will soon try to resize that or grab a new and slightly bigger sdcard.

All services are up and running, let's stick to that for the moment !

You can connect a USB stick to the RPi4, partition it, format it however you like, mount it, and use that as extra space.

I already have a 500G hard drive on this one and moved some things around. I believe it's not enough...

When I'm building/testing/playing with sarpi shizzle I generally use SD cards, which are usually 64GB capacity. I think only the RPi (1) uses a 32GB SD card now in my build setup.

I have a 480GB SSD with slackware arm installed on it which I use on the RPi4 and I won't fill that up in a hurry. I also have a 60GB SSD with ubuntu on it at the moment.

SlackwareARM -current installed to a new 64GB SD micro card and working well running Xfce.

Thanks again to Pat and team, drmozes and Exaga for Slackware, SlackwareARM and Sarpi.

I was going to reinstall to my original 16GB SD card after filling the card and corrupting Slackware during an update, but something else happened (no idea if due to my abuse or just worn out.) After wiping the card, it won't accept a new partition table via KDEParted or GParted.

In any case, 16GB is getting a bit tight for Slackware if you also store files on it, so I went to a bigger SD card and will look at getting an SSD for file storage. 32GB card would be plenty, only went with 64GB because on sale it was only $3 (CAD) more than the 32.

TKS

1 members found this post helpful.