Trouble in Paradise.
 

Started slackpkg upgrade-up and went to bed. Woke up to find the power had gone out during the night. The computer booted up, but displayed a message that said something to the effect of, "Error occurred during root file system check. You will be given the option of doing maintenance......"
I can get to a command prompt, but regardless of what I do a message pops saying it can't find libblkid.so.1
So, now what?
What needs to be done to get it running again?
Thank you very much.
:hattip:

As I recall, you can use the slackware install CD/DVD as a boot disk if needed. However can you tell us more about the problem? Like what is it saying exactly? The closer to the message you can tell us, the easier it is to fix.

Maybe this will help: http://www.linuxquestions.org/questi...issing-792833/
Seems like another user got that too

What version of slackpkg you used ?
You run slackpkg install-new before run slackpkg upgrade-all ?

this lib is from util-linux package...

see you
gar0t0

First thing I would do is fix the file system. Boot up with slack cd/dvd and run the appropriate fsck on the disk. You don't mention file system but e2fsck -f -y -v /dev/hdx ought to work.

Strangely enough the library libblkid.so.1 comes from a/e2fsprogs (in 13.0 anyway). If you can mount the partition, copy the package there and chroot into it you may be able to installpkg it. If not, try untarring it in / and sourcing /install/doinst.sh and try installpkg on it again.

If all goes well that ought to have things working and you can boot up and run slackpkg upgrade-all again.

I'm missing file from e2fsprogs also, mentioned in another thread, perhaps it needs to be updated up-stream.

samac

In -current it is in util-linux-ng:

/var/log/packages/util-linux-ng-2.17.1-i486-1:lib/libblkid.so.1.1.0

and moved out of e2fsprogs.

Would You Like Jam Or Jelly With Your Toast?
 

Thanks to everyone for their help, but it is toast.
I've tried twice and it just isn't going to work. I'll put Slackware64-13 back on so I can get to my data, but will wait for the next release before trying again.
I've burned out on upgrading everytime I turn around just to get a usable version of KDE and KDE 4.2.4 isn't worth the time it takes to install it.
Thanks, again.
:hattip:

Back to Slackware64-13 and Xfce.
After trying to upgrade twice, a good many things are screwed up. Guess I'm going to have to remove a few packages and re-install them to get them to run correctly.
A clean install is in order, but I'm just not in the mood after the nonsense of the last couple of days.

Have you tried creating an install DVD using alienBOB's -current install script. It works like a charm for me. That is another option if you want to try -current.

Will someone please post when Slack fixes it?
I was gonna upgrade too till I saw this....

@cwizardone

If you'd like to make a fresh install of current, I can suggest the DVD iso files available at:

ftp://ftp.slackware.no/linux/slackwa...e-current-iso/

Of course, these are unofficial iso files but I've used them a couple of times (the last time being in January 2010). If you are interested, I would recommend that you wait until the next update of iso files (they are updated every Tuesday) because the ones dated 2nd March may not contain the latest updates of current (which happened on the same day).

@linus72

I don't think cwizardone's troubles are linked to any instability in Slackware current. It looks to me like an upgrade that was stopped due to power outage and I can understand it's a messy thing afterward because of the huge amount of packages to be upgraded (and new ones to be installed).

Mine borked too. I tried to reinstall the packages from my local copy of current but couldn't connect to anything.
Judging by some other posts I think I'll just reinstall with the latest iso that gegechris99 mentioned.

edit:
Thanks gegechris99

I had this exact same problem during the recent big upgrade. As people mention above, it's not due to the instability of Slackware and has more to do with the power outage during the upgrade. If you use some file systems, like ext4, some files may have also zero bytes and be damaged.

I booted from a rescue CD, checked the disk and updated my packages manually (as in running upgradepkg without any additional tool). Once I could at least boot my system, I checked the contents of /var/log/packages. I detected files with zero size in there and other damaged files, and reinstalled those packages. I searched for regular files in my system with size zero in /bin, /sbin, /usr/bin, /usr/sbin, /lib, /usr/lib, /usr/share, /etc and whatever other directory I considered interesting. Then I reinstalled every package that had any file with zero sized. I used slackroll to automate finding and reinstalling those packages.

Finally, I have to mention special trouble with the gzip package. Their programs were damaged and had zero size, and I needed gzip to reinstall the gzip package (it's a .tgz), so I had to manually extract and install that package from the rescue CD to restore it.

Next time I'll leave the laptop battery plugged in during the upgrade. God, what a mess.

There is at least one other thread about systems getting borked during recent upgrade to -current, so I doubt this has anything to do with power outages. A number of people in that thread reported the same problem with the file system. It's unlikely so many people are having power outages in the midst of their -current upgrade.

http://www.linuxquestions.org/questi...borked-793473/