Crashed my slackware current during slackpkg upgrade.
Can I access intalled root system from Slackware Live which I am able to boot.
Why is install Slackware option locked on the Live version?

you can. you might want to try and hunt down if something failed to upgrade properly and reinstall that. you could theoretically use the ROOT= with slackpkg to help do all that. you might need to manually run fsck.ext4 or fsck for whatever file system you are using.

1 members found this post helpful.

Thank you khronosschoty

error updating slackware crashed before running #slackpkg clean-system and #lilo -v
Now cant boot into linux:
Loading Linux EBDA is big; Kernel setup stack overlaps Lilo second stage.

So do I sign into Slackware Live as root and mount my four partition slackware system?
From Slackware Live GUI Desktop I can see the partitions but to access them it asked for authentication. Do I use my Slackware System's root password? or Should I go into terminal mode?
fyi i'm having a back few days. Appreciate all your time

well if it were me, I would boot Slackware live; open a terminal, su -l root. Then if I had a luks and or lvm root system I would handle that. Then I would run the proper fsck.$filesystem on the partitions; afterwards I would mount the root file system to something like /mnt. I would then mount the other partitions to wherever they go.(for example /mnt/boot for my boot partition if I have one) then I would would do something like:

mount -o bind /dev /mnt/dev
mount -o bind /sys /mnt/sys
mount -o bind /proc /mnt/proc
mount -o bind /dev/pts /mnt/dev/pts

I might copy over my /etc/resolv.conf to /mnt/etc/resolv.conf
then I would chroot /mnt /bin/sh -l

then I would make sure everything that needs upgraded is upgraded, check for broken packages and reinstall those finally check my /etc/lilo and run /sbin/lilo (making sure of course everything in lilo is right and the kernel and the initrd is present)

This is all assuming whatever damage took place didn't leave me without a functional system to chroot into... if not (that is if I can't chroot into a working system) then I would try and fix that system (outside of the chroot) by reinstalling the broken packages using slackpkg or upgradepkg using the ROOT=/mnt , since ROOT=/mnt is where I would mount everything like in the example above -- before finally doing the steps I covered in brief above.

EDIT: this is all assuming I felt like things were worth saving -- in the case where I thought a reinstall might be wiser / easier, I would just backup my /home and reinstall. However, I'm assuming that its probably just a simple issue and lilo needs re-run. Perhaps you ended up with a busted kernel or something.

1 members found this post helpful.

Wow! Thanks. Can't I just run #slackpkg clean-system & #lilo -v lol
I have no luks or lvm that's too advanced for me. I'll try follow you instructions. Thank you bunches

Maybe reinstall lilo and all the kernel stuff and go from there, inside of the chroot. I'm not sure of your abilities here, as in how good you are at checking for broken packages. The the thing to do is to check what packages you have installed against the package tree -- see https://ftp.osuosl.org/pub/slackware...re64/FILE_LIST

Compare those packages to whats inside of /var/log/packages/ and lastly check the contents of each package entry found in that list to whats present.

1 members found this post helpful.

What are the commands to compare /var/log/packages ?

fyi I'm running xfce no kde no lvm, no luks, no raid. Should have backedup my Docs and Book Marks, crash was unexpected. Runlevel went to GUI on its own, I don't like GUI login. Think my video card failed, I replaced it.

you could still back those up, just follow the mounting procedure above, locate the files you want to cp and cp them over to an external. alternatively, you could run slackpkg and just reinstall everything and then just install anything missing, if finding broken packages is too much work. slackpkg reinstall all for example.

ROOT=/mnt slackpkg update
ROOT=/mnt slackpkg reinstall-all
ROOT=/mnt slackpkg upgrade-all

or just cp over what you want and start with a fresh install. The point is there is many ways to go about this. I'm not sure what the best solution for you is.

1 members found this post helpful.

Think I will go ahead and copy the files I want over to my separate HDD and then go through the steps you proposed. But if I recall correctly there are a few commands to compare lists?
If so what are they?