[SOLVED] Upgraded to current using slackpkg. root is no longer recognized as valid login and the OS won't load on startup

burning · 06-01-2020, 07:04 PM

Quote:

Originally Posted by bassmadrigal

I've never tried to get network running from within a chroot. If you just want to update your config files with the new .new files, you don't need network. You can simply run:

Code:

slackpkg new-config

If you do want to get network running, I'd try running dhcpcd eth0 and see if you get an IP address.

Thanks. I managed to update the config files. But running dhcpcd eth0 got me the following:

Code:

DUID 00:04:73:9d:10:01:48:d8:11:cb:cb:a2:84:d2:4c:95:7f:4f:25
eth0: IAID 41:e2:06:ba
eth0: adding address fe80::d0de:179:8e59:7cd6
ipv6_addaddr1: Operation not supported
eth0: soliciting an IPv6 router
eth0: soliciting a DHCP lease
eth0: offered 192.168.0.39 from 192.168.0.1
eth0: probing address 192.168.0.39/24
eth0: Router Advertisement from fe80::26a7:dcff:fedb:699
eth0: adding address fde9:a858:61b8:0:f95:cb6:b8a1:5df6/64
eth0: adding route to 2a02:c7f:683:f300:c788:e693:9296:1b29/64
eth0: adding route to fde9:a858:61b1::/64
eth0: adding route to 2a02:c7f:683:f300::/64
eth0: requesting DHCPv6 information
eth0: pid -1090408939 deleted route to fde9:a858:61b8::/64
eth0: pid -91793523 deleted route to 2a02:c7f:683:f300::/64
eth0: adding route to fde9:a858:61b8::/64
eth0: adding route to 2a02:c7f:683:f300::/64
eth0: adding default route via fe80::26a7:dcff:fedb:699
eth0: pid -133700453 deleted default route via fe80::26a7:dcff:fedb:699
forked to background, child pid 610
dhcp6_openudp: Address already in use

And on reboot, the system still wouldn't get past "Loading Linux............" on the bootup screen

colorpurple21859 · 06-01-2020, 07:52 PM

what are you using for a bootloader, eilo or grub?

bassmadrigal · 06-01-2020, 07:58 PM

That output looks normal for dhcpcd and seems to show you got connected with the standard IPv4 address.

As for the Loading Linux issue, that could be due to something in your bootloader's conf file or your initrd.

Simplicity wise, it would probably be much easier to just reinstall using an ISO for -current that is automatically generated by Alien Bob. This will allow you to skip upgrading a 14.2 install to -current and any pitfalls that can occur with that.

If you do want to try and recover this system, it is most likely possible, but it might take a bit as we diagnose over the forum and may take a lot of effort on your part.

burning · 06-03-2020, 09:29 AM

Quote:

Originally Posted by bassmadrigal

That output looks normal for dhcpcd and seems to show you got connected with the standard IPv4 address.

As for the Loading Linux issue, that could be due to something in your bootloader's conf file or your initrd.

Simplicity wise, it would probably be much easier to just reinstall using an ISO for -current that is automatically generated by Alien Bob. This will allow you to skip upgrading a 14.2 install to -current and any pitfalls that can occur with that.

If you do want to try and recover this system, it is most likely possible, but it might take a bit as we diagnose over the forum and may take a lot of effort on your part.

Thank you. I was considering reinstalling but I think I'd find the process of trying to recover it more educational. I don't mind putting in more effort if it means I get to figure out exactly why what I did did what it did.

burning · 06-03-2020, 09:29 AM

Quote:

Originally Posted by colorpurple21859

what are you using for a bootloader, eilo or grub?

Lilo. I was planning on installing Grub when I installed a 2nd OS on it.

colorpurple21859 · 06-03-2020, 09:39 AM

post your /etc/lilo.conf and /etc/fstab and "ls /boot"

burning · 06-14-2020, 08:41 AM

Quote:

Originally Posted by colorpurple21859

post your /etc/lilo.conf and /etc/fstab and "ls /boot"

Contents of /etc/lilo.conf:

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel paramters:
append=" vt.default_utf8=0"
boot = /dev/sda

#compact        # faster, but won't work on all systems.

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
 bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
 bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to 
# be used. We don't specify it here as there's just one column.
 bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
 bmp-timer = 65,27,0,255

#Standard menu
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

#Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in the tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
 reset
# Ask for video mode at boot (time out to normal in 30s)
vga = ask
# Normal VGA console
#vga = normal
# VESA framebuffer console @ 1024x768x64k
#vga=791
# VESA framebuffer console @ 1024x768x32k
#vga=790
# VESA framebuffer console @ 1024x768x256
#vga=773
# VESA framebuffer console @ 800x600x64k
#vga=788
# VESA framebuffer console @ 800x600x32k
#vga=787
# VESA framebuffer console @ 800x600x256
#vga=771
# VESA framebuffer console @ 640x480x64k
#vga=785
# VESA framebuffer console @ 640x480x32k
#vga=784
# VESA framebuffer console @ 640x480x256
#vga = 769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = dev/sda5
  label = Linux
_ read-only
# Linux bootable partition config ends

Contents of /etc/fstab:

Code:

/dev/sda5           /                   ext4            defaults                            1  1
/dev/sda1           /usr/local          ext4            defaults                            1  2
/dev/sda6           /usr/local          ext4            defaults                            1  2
/dev/cdrom          /mnt/cdrom          auto            noauto,owner,ro,comment=x-gvfs-show 0  0
/dev/fd0            /mnt/floppy         auto            noauto,owner                        0  0
devpts              /dev/pts            devpts          gid=5,moder=620                     0  0
proc                /proc               proc            defaults                            0  0
tmpfs               /dev/shm            tmpfs           defaults                            0  0

Contents of ls /boot:

Code:

home  lost+found

BrunoLafleur · 06-14-2020, 09:41 AM

Why is there an underscore _ in front of _read-only in the lilo.conf file ?

Why do you have twice /usr/local in the fstab file ?

Why home and lost+found inside /boot : it is totally anormal.

colorpurple21859 · 06-14-2020, 10:12 PM

first what does

Code:

ls /boot/home

display and then

Code:

mount /dev/sda1 /boot

then post the output of

Code:

ls /boot

burning · 06-16-2020, 08:00 AM

Quote:

Originally Posted by BrunoLafleur

Why is there an underscore _ in front of _read-only in the lilo.conf file ?

Why do you have twice /usr/local in the fstab file ?

Why home and lost+found inside /boot : it is totally anormal.

Unfortunately I have no idea. I never touched those directories or files.

burning · 06-16-2020, 08:07 AM

Quote:

Originally Posted by colorpurple21859

first what does

Code:

ls /boot/home

display and then

Code:

mount /dev/sda1 /boot

then post the output of

Code:

ls /boot

Turning on my computer and using a USB live bootable, without doing:

Code:

mount /dev/sda5 /mnt
mount /dev/sda1 /mnt/boot
mount /dev/sda6 /mnt/home
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount -o bind /run /mnt/run
chroot /mnt

Entering ls /boot/home gives me:
/bin/ls: Cannot access '/boot/home': No such file or directory

doing mount /dev/sda1 /boot gives me:
mount: mount point /boot is a symbolic link to nowhere

and doing ls /boot gives nothing but:
/boot@

After performing:

Code:

mount /dev/sda5 /mnt
mount /dev/sda1 /mnt/boot
mount /dev/sda6 /mnt/home
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount -o bind /run /mnt/run
chroot /mnt

trying ls /boot returns nothing

trying mount /dev/sda1 /boot gives:
mount: /boot: /dev/sda1 already mounted or mount point busy.

entering ls /boot gives:
home lost+found

colorpurple21859 · 06-16-2020, 08:55 AM

from the live usb

Code:

mkdir /mnt/sda1
mkdir /mnt/sda5
mkdir /mnt/sda6
mount /dev/sda1 /mnt/sda1
mount /dev/sda5 /mnt/sda5
mount /dev/sda6 /mnt/sda6

post the output of

Code:

ls /mnt/sda1
ls /mnt/sda5 
ls /mnt/sda6
cat /mnt/sda5/etc/fstab
cat /mnt/sda5/etc/lilo.conf

burning · 06-16-2020, 01:55 PM

Quote:

Originally Posted by colorpurple21859

from the live usb

Code:

mkdir /mnt/sda1
mkdir /mnt/sda5
mkdir /mnt/sda6
mount /dev/sda1 /mnt/sda1
mount /dev/sda5 /mnt/sda5
mount /dev/sda6 /mnt/sda6

post the output of

Code:

ls /mnt/sda1
ls /mnt/sda5 
ls /mnt/sda6
cat /mnt/sda5/etc/fstab
cat /mnt/sda5/etc/lilo.conf

output of ls /mnt/sda1:

Code:

home/  lost+found/

output of ls /mnt/sda5:

Code:

bin/  dev/  home/  lost+found/ mnt/ proc/ run/   srv/  tmp/ var/
boot/ etc/  lib/   media/      opt/ root/ sbin/  sys/  usr/

output of ls /mnt/sda6:

Code:

bin/  games/    info/   lost+found/  sbin/  src/
etc/  include/  lib/    man/         share/

output of cat /mnt/sda5/etc/fstab:

Code:

/dev/sda5           /                   ext4            defaults                            1  1
/dev/sda1           /usr/local          ext4            defaults                            1  2
/dev/sda6           /usr/local          ext4            defaults                            1  2
#/dev/cdrom         /mnt/cdrom          auto            noauto,owner,ro,comment=x-gvfs-show 0  0
/dev/fd0            /mnt/floppy         auto            noauto,owner                        0  0
devpts              /dev/pts            devpts          gid=5,moder=620                     0  0
proc                /proc               proc            defaults                            0  0
tmpfs               /dev/shm            tmpfs           defaults                            0  0

output of cat /mnt/sda5/etc/lilo.conf:

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel paramters:
append=" vt.default_utf8=0"
boot = /dev/sda

#compact        # faster, but won't work on all systems.

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
 bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
 bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to 
# be used. We don't specify it here as there's just one column.
 bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
 bmp-timer = 65,27,0,255

#Standard menu
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

#Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in the tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
 reset
# Ask for video mode at boot (time out to normal in 30s)
vga = ask
# Normal VGA console
#vga = normal
# VESA framebuffer console @ 1024x768x64k
#vga=791
# VESA framebuffer console @ 1024x768x32k
#vga=790
# VESA framebuffer console @ 1024x768x256
#vga=773
# VESA framebuffer console @ 800x600x64k
#vga=788
# VESA framebuffer console @ 800x600x32k
#vga=787
# VESA framebuffer console @ 800x600x256
#vga=771
# VESA framebuffer console @ 640x480x64k
#vga=785
# VESA framebuffer console @ 640x480x32k
#vga=784
# VESA framebuffer console @ 640x480x256
#vga = 769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = dev/sda5
  label = Linux
  read-only
# Linux bootable partition config ends

bassmadrigal · 06-16-2020, 03:00 PM

It looks like your fstab got things mucked up.

Try swapping the mount point for /dev/sda1 to /home. If /dev/sda6 is intended for /usr/local, that and /dev/sda5 can remain unchanged.

Hopefully /mnt/sda5/boot has your normal boot items. If so, you should be able to do the following after a fresh boot off your installation media:

Code:

mount /dev/sda5 /mnt
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
chroot /mnt
lilo
exit
reboot

If your boot directory is empty, we'll need to address that.

colorpurple21859 · 06-16-2020, 03:37 PM

post the output of

Code:

ls /mnt/sda5/boot
ls /mnt/sda5/home
ls /mnt/sda1/home