LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-21-2019, 10:08 AM   #31
ricky_cardo
Member
 
Registered: Feb 2006
Location: Syracuse, NY
Distribution: Slackware64-Current
Posts: 124

Rep: Reputation: 28

I absolutely had same issue when adding drives to my B/U machine.
(this worked for me)

You may need to add uuid and initrd.gz to lilo or elilo respectively

- I believe the initrd.gz is needed when using uuid in the bootloader.
(so you'll likely need "/usr/share/mkinitrd/mkinitrd_command_generator.sh")

cat /boot/efi/EFI/Slackware/elilo.conf
chooser=simple
delay=1
timeout=1
#
image=vmlinuz
label=vmlinuz
initrd=/EFI/Slackware/initrd.gz
read-only
root=UUID=73b2ed4d-642e-47b2-446b-d40d4470c4d3
append="vga=normal ro"

Last edited by ricky_cardo; 12-21-2019 at 10:30 AM.
 
Old 12-21-2019, 11:28 AM   #32
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,476

Rep: Reputation: 4270Reputation: 4270Reputation: 4270Reputation: 4270Reputation: 4270Reputation: 4270Reputation: 4270Reputation: 4270Reputation: 4270Reputation: 4270Reputation: 4270
Your fstab looks fine, but you will want to look at your bootloader config (maybe lilo.conf, depending on the bootloader you use) and your initrd. If it is looking for /dev/sdc, then persistent naming wasn't used somewhere, and my guess is your initrd. I'm not sure if maybe you missed the partition in the error message, if it doesn't provide the partition number, or if it is just referring to the device itself, which is typically only when you write the bootloader itself using lilo.

My guess is still that it is probably trying to use the root device name rather than a UUID or label. If you use mkinitrd_command_generator.sh, it will automatically put your root device (/dev/sdc at the time) for the -r option. You would need to modify that to list your UUID for it to work. For example, if I run the generator, it will spit out the following line (I removed the last part just to keep it short):

Code:
mkinitrd -c -k 5.3.12 -f ext4 -r /dev/nvme0n1p3
I would need to change this to the following to have it use UUID instead of device naming:

Code:
mkinitrd -c -k 5.3.12 -f ext4 -r "UUID=76e5697b-96f0-4287-8c1a-2b6e6961765a"
You will also want to make sure your boot= line at the top of lilo.conf is using a persistent name so it is writing lilo to the correct drive:

Code:
boot=/dev/disk/by-id/ata-WDC_WD40EFRX-68WT0N0_WD-WCC4EJD5E4ZK
Finally, make sure that when you add a drive that it doesn't affect your boot order within your BIOS/UEFI firmware.
 
1 members found this post helpful.
Old 12-26-2019, 09:12 AM   #33
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware, Debian
Posts: 2,098

Original Poster
Blog Entries: 6

Rep: Reputation: 2309Reputation: 2309Reputation: 2309Reputation: 2309Reputation: 2309Reputation: 2309Reputation: 2309Reputation: 2309Reputation: 2309Reputation: 2309Reputation: 2309
I have made quite a bit of headway with this and it certainly didn't go the way I expected it to. The end result I am happy with, but the whole process took an unexpected turn.

bass - I have to say first of all, thank you very much indeed for your help. The steps you listed above, such as substituting the root partition name with the UUID in the mkinitrd command and entering the drive name into lilo.conf were both already done. However, and this is what confused me, I still got a kernel panic after rebooting, rerunning lilo, etc. Remember I've written quite an extensive blog entry on persistent naming [which needs to be updated now], and I was sure that I had the process down correctly, but I apparently I don't.

Following several kernel panics after I had plugged the other drives in, I thought I would just have to trust the Slackware installer and do a fresh install on my new drive but with all the other drives plugged in as well. This, during the process, gave me extra options to configure all drives in fstab. Great, so I thought, and rebooted after the installation had finished. Here is where things got worse.

On reboot, rather than seeing the familiar Slackware logo on the black and white lilo screen, I didn't actually get a lilo screen at all, but a black screen with the numbers "99 99 99 99 99" repeated over and over. I thought that maybe it was a bad boot or something, so did a couple of hard resets and again got the 99 Flake screen several times.

It was at this point that I decided, after many hours, that the amount of time I had invested in this was disproportionate to the payoff. I wanted a system that would boot successfully with all drives in and that could use for my ends - and I hadn't even got to the LUKS part yet.

I started to consider other operating systems. This was not a decision made out of annoyance but rationale, but also a slight sensation of dejection since I had exhausted my knowledge base. Add to this the fact that I am alone over the Xmas and New Year period, and it makes sense that I would want a working production desktop. After a few minutes of thought, I decided to change the OS on the machine to Debian - it wasn't a hard choice to make in spite of the fact that I am not a fan of systemd. I have quite a bit of historical experience with it and I know it's fit for my purposes. I considered Devuan, but I can't help thinking that the Debian devs are just 'tolerating' Devuan. Humouring them for now, almost.

After I had done the install of Debian on the main drive [which was done with the other three drives unplugged] I then powered off, plugged in the other three drives, rebooted and the system booted to desktop successfully and saw all the other drives. Debian [or systemd, I'm not sure] must automate the persistent naming process. Either way, getting it done was a breeze. I have also started the LUKS encryption of the other drives.

I'm not saying that Debian/GNOME doesn't have its niggles, it does, but these are snags which I'm happy to endure for now. I have a working machine with all drives functioning, two currently encrypted, and I can both work and play games. I really enjoy and love using Slackware, but when it comes to a somewhat complicated machine like this, I just want a stable system that works rather then spending more and more hours trying to get the thing to boot.

So for now I will keep things as they are. I still run 14.2/-current on my laptop[s].

Last edited by Lysander666; 12-26-2019 at 09:51 AM.
 
Old 12-26-2019, 09:39 AM   #34
_peter
Member
 
Registered: Sep 2014
Location: paris
Distribution: slackware
Posts: 70

Rep: Reputation: Disabled
Quote:
Originally Posted by Lysander666 View Post
and do a fresh install on my new drive but with all the other drives plugged in as well
On reboot, rather than seeing the familiar Slackware logo on the black and white lilo screen, I didn't actually get a lilo screen at all, but a black screen with the numbers "99 99 99 99 99" repeated over and over.
same here, installing on one drive while multiple drives are wired to the computer systematically gave me those 99 you observed upon boot.
i always re-install lilo in chroot from the drive's partition that has the fresh install, then the drive boots into slackware.
even after a simplistic dd cloning, i systematically re-install lilo.

https://docs.slackware.com/howtos:sl...olume_mounting

funny enough a work colleague last week had a complete nightmare cloning centos7 and re-installing grub2 on a single drive with 4 ext4 partitions and 1 efi one.
i couldn't help him and told him to experiment with one single ext4 partition then move-on more complex partition tables.
we also found that his fresh centos7 install didn't have the necessary packages to re-install or update grub2.
 
1 members found this post helpful.
Old 12-26-2019, 11:33 AM   #35
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 6,476

Rep: Reputation: 4270Reputation: 4270Reputation: 4270Reputation: 4270Reputation: 4270Reputation: 4270Reputation: 4270Reputation: 4270Reputation: 4270Reputation: 4270Reputation: 4270
The 99 error is sometimes due to referencing the partition in the "boot" line of lilo rather than the disk itself, but there does seem to be other unrelated issues that can cause that. If your motherboard is capable of using UEFI, it might be worth looking into the transition for that. elilo was much easier than I expected, and overall, I'd say it is less error prone than lilo itself.

But I'm glad you got it working, even if it did require a different OS. It can certainly be frustrating when you're stuck without your main machine and your mind is racing trying to figure out what you need to do to fix it.
 
2 members found this post helpful.
Old 12-26-2019, 12:46 PM   #36
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,623

Rep: Reputation: 2712Reputation: 2712Reputation: 2712Reputation: 2712Reputation: 2712Reputation: 2712Reputation: 2712Reputation: 2712Reputation: 2712Reputation: 2712Reputation: 2712
Hello Lysander666. I just wanted to mention that I'm sorry you felt alone during the holidays which can be a very stressful time. Additionally I hope you realize that despite only knowing you by your words, thoughts and music, and despite your now becoming a horrendous, despicable, turncoat TRAITOR! ( tongue firmly in cheek) you do have actual friends here. You're not really alone. People here know something of you and care about you. Don't be a stranger in the coming months and years over a distro choice. Happy New Year , Brother.
 
2 members found this post helpful.
Old 12-26-2019, 03:50 PM   #37
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware, Debian
Posts: 2,098

Original Poster
Blog Entries: 6

Rep: Reputation: 2309Reputation: 2309Reputation: 2309Reputation: 2309Reputation: 2309Reputation: 2309Reputation: 2309Reputation: 2309Reputation: 2309Reputation: 2309Reputation: 2309
Quote:
Originally Posted by bassmadrigal View Post
The 99 error is sometimes due to referencing the partition in the "boot" line of lilo rather than the disk itself, but there does seem to be other unrelated issues that can cause that.
I think I would file this under "other unrelated issues" since the boot line of lilo referenced the drive rather than the partition. The whole thing was most peculiar.

Quote:
Originally Posted by bassmadrigal View Post
But I'm glad you got it working, even if it did require a different OS. It can certainly be frustrating when you're stuck without your main machine and your mind is racing trying to figure out what you need to do to fix it.
Very true.

Quote:
Originally Posted by enorbet View Post
Hello Lysander666. I just wanted to mention that I'm sorry you felt alone during the holidays which can be a very stressful time. Additionally I hope you realize that despite only knowing you by your words, thoughts and music, and despite your now becoming a horrendous, despicable, turncoat TRAITOR! ( tongue firmly in cheek) you do have actual friends here. You're not really alone. People here know something of you and care about you. Don't be a stranger in the coming months and years over a distro choice. Happy New Year , Brother.
What a nice post, thank you very much, enorbet. I'm OK on my own and thank you for your kind words, but I do know that - particularly at this time of year - a working desktop is not something I feel comfortable without. I won't be going anywhere board-wise since my laptops still run Slackware, and I intend to keep it that way for the foreseeable future.

Last edited by Lysander666; 12-26-2019 at 06:25 PM.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Punching Out the Week on Boxing Day LXer Syndicated Linux News 0 12-26-2014 04:07 AM
LXer: Title Bout Championship Boxing 2013 Now Available LXer Syndicated Linux News 0 06-12-2013 02:41 AM
What is Linux Questions family going to buy on boxing day this year? puppymagic General 8 12-11-2012 06:57 AM
Boxing question: Rope-a-dope strategy hydraMax General 6 10-10-2012 05:04 AM
Anybody into boxing??? neo77777 General 1 12-08-2002 04:42 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:48 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration