[SOLVED] Major update today on Slack-Current - system now borked
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Major update today on Slack-Current - system now borked
Hello Everyone,
It has been quite a while since I have had an issue like this, but this one may not be recoverable.
As I am sure anyone running -current know, there was a major upgrade recetnly. I use Slackpackage to keep everything updated, and everything started normally (slackpackage-upgrade-all). About 3/4 through this large update, the network connection was lost for some reason not known. It was definitely a slack problem because all of the other machines in the house have no issue. I waited for quite a while for it to resume, but it never did, so I attempted to open another terminal investigate. Nothing would open. The system was not frozen, but no apps would open. Finally, I attempted a reboot (but I knew I was screwed when I did it). Sure enough, the system would not reboot with the error "There is a filesystem error. You will be given the chance to login as root to fix the issue". Well that was it. I could go no further.
If anyone has any thoughts I would appreciate any help. I can usually recover from this kind of disaster in other distros, but not all of the update packages had downloaded so when I rebooted I am sure the system was not even half updated. Can I fix this or am I screwed?
Thanks for the reply. That does look like the same problem. This is on a laptop that triple boots with Slack on /dev/sda7. Would I not be able to run e2fsck on this partition from the Fedora installation on another partition (since the slack partition would not be mounted)?
Oddly, I cannot seem to find the Slack installation DVD, so I would probably have to download another one.
310592 inodes used (42.38%)
8474 non-contiguous files (2.7%)
222 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 15207/127/0
1721354 blocks used (58.75%)
0 bad blocks
1 large file
OK, I have been able to chroot to the partition and all the files look OK and I have a network connection working, but the slackpackage command does not work from chroot. Does anyone know anything I could try from here?
Hello, mRgOBLIM, no, it seems to complain about libblkid.so.1 not being found. Starts to boot then stops with that error. As I mentioned above, I am currently at a bash prompt in a chroot to the Slack partition, and I have SBo installed, but can't seem to figure out how to install whatever I need to install. The network connection seems to be working as I have an IP address with ifconfig.
A post from dive mentions that this library is found in utils-linux-ng, but I do not seem to be able to find that anywhere and I do not have the slack install cd.
Thanks, that would have worked, but I guess I was wrong about having a connection. I seem to be connected to my home network (I can ping other machines) but wget gets me a name-resolve error, and I can ping anything on the net.
I suppose I can try to mount the partition in Fedora and move the downloaded file to my home directory on the mounted partition. Looks like that is the only thing I can and I do not have any idea if even that will fix this problem. I have seen that many other have had the same issue with this update yesterday and today. I understand their frustration. I have a lot of files on that partition which I suppose I can still get to, but I have had this installation for nearly two years with no major issues (upgrade upon upgrade) and it seems ashame to lose it all now.
at worst, you can simply get a new slackware dvd, chroot into your current install, and reinstall all the slackware packages off the dvd
that would preserve all your personal files and should fix whatever is wrong with the current installation without needing to do a full format and re-install
Well, if simply installing that package would fix this mess, I can "almost" do it as I downloaded it in Fedora and am able to mount my Slack partition in Fedora, but I cannot move the package there as there is a permissions problem. If I could get it to the Slack partition, I could install it inside the chroot mount. If anyone knows how I can get this package moved across partitions, I would appreciated it. If not, I will give up on this one and take a break from Slack for a while and reinstall another day. I have been using Slack since 10.1 and this is the first problem that looks like it is going to defeat me.
Thanks for all the kind help. The help I have always gotten here is what separate Slack from every other distro I have ever used.
My system was totally SCREWED yesterday (I'm using it now, it's pretty much fixed), and by the sounds of things, you need a Slack CD or DVD to boot from, at least to get it working again. For me, chroot didn't work because I had the system so totally mangled that everything I tried to do inside the chroot resulted in a Segmentation Fault (not happy I was, no.)
Can you get a DVD or CD and burn it? I'd be doing that anyways -- you'll want/need it for *something* *sometime*..
Or -- Work on that permissions issue. If you're logged into Fedora as root, and you mount the slack partition (rw) then you ought to be able to move the file over there easily as far as I know.
One way or the other, or another, I would really not lean towards re-installing the entire system at this early stage in the game (I ended up having to do pretty much exactly that, but didn't lose much, if anything, in the way of customizations, and my /home is separate anyways...)
You say you CAN get into the chroot, but have no internet, so what happens if you try starting the network and starting DHCP? Can you bring up the internet connection?
but I cannot move the package there as there is a permissions problem.
How are you mounting it? Do you have anything in fstab that might interfere with rw permissions? Usually a mount command with nothing in fstab should do the trick.
Another idea is get the file on a usb stick or cd.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.