Laptop: Fails to mount the root partition.

Alexander88207 · 07-03-2019, 07:43 AM

Hello dear slackers,

today i have installed current on my laptop and if i want to restart now, i will be forwarded directly to the rescue shell.. The installation itself was executed with no errors.

Unfortunately, I can't find out much from the logs, maybe you?

Picture: https://cdn.discordapp.com/attachmen...703_141106.jpg

As always, i am very grateful for any help i can get.

More information about the laptop:

Model: HKC NT11H: 29 cm (11 Zoll)
Boot: UEFI (Only)
CPU: Intel Atom x5-Z8350 1.44 GHz
RAM: 2 GB RAM
Storage: 32 GB eMMC
GPU: Intel HD Graphics 400

My partitions:

/dev/mmcblk0p1 512M EFI
/dev/mmcblk0p2 500M Swap
/dev/mmcblk0p3 27GB Root

lazydog · 07-03-2019, 09:31 AM

Can you boot up this laptop with the install CD and then get a command prompt. Once on the CLI run:

Code:

fdisk -l

This will give a listing of what partitions you have on the disk.

To be honest while you might not have seen any errors when installing from the looks of the attached picture something didn't go right.

Alexander88207 · 07-03-2019, 10:00 AM

Quote:

Originally Posted by lazydog

Can you boot up this laptop with the install CD and then get a command prompt. Once on the CLI run:

Code:

fdisk -l

This will give a listing of what partitions you have on the disk.

To be honest while you might not have seen any errors when installing from the looks of the attached picture something didn't go right.

Thanks for your response

fdisk-l

Device Start End Sectors Size Type
/dev/mmcblk0p1 2048 1050623 1048576 512M EFI Systems
/dev/mmcblk0p2 1050624 2074623 1024000 500M Linux swap
/dev/mmcblk0p3 2074624 61071326 58996703 28.1G Linux filesystem

colorpurple21859 · 07-03-2019, 10:03 AM

what bootloader are you using and are you booting the huge or generic kernel?

Alexander88207 · 07-03-2019, 10:13 AM

Quote:

Originally Posted by colorpurple21859

what bootloader are you using and are you booting the huge or generic kernel?

elilo & 4.19.56

colorpurple21859 · 07-03-2019, 11:22 AM

are you using an initrd.gz when booting?

Alexander88207 · 07-03-2019, 11:43 AM

Quote:

Originally Posted by colorpurple21859

are you using an initrd.gz when booting?

I didn't change the boot process after installation, should this be something optional.

colorpurple21859 · 07-03-2019, 12:20 PM

post your /etc/fstab, elilo.config and the output of

Code:

 blkid
parted -l

jostber · 07-03-2019, 12:33 PM

You have a relevant recent post for this in the Slackware installation forum:

https://www.linuxquestions.org/quest...ns-4175644615/

Seems like due to the special disk configuration you will need to do some steps after installation.

Didier Spaier · 07-03-2019, 12:41 PM

This line in your boot log puzzles me:

Code:

mount: mounting /dev/mmcblk0p3 on /mnt failed: No such file or directory

Please start the installer, then once logged in as root type this command and post its output:

Code:

lsblk -l -o name,size,fstype|grep mmcblk0p3

Then type:

Code:

mount /dev/mmcblk0p3 /mnt

Then post the output of:

Code:

cat /mnt/etc/fstab|grep "/ "

Still, I don't understand why the root partition would be mounted on /mnt while booting.

Alien Bob · 07-03-2019, 01:01 PM

Quote:

Originally Posted by Alexander88207

I didn't change the boot process after installation, should this be something optional.

The "exports duplicate symbol", the wad of "insmod" lines and the final error about mounting the root partition on /mnt are all proof of an initrd that is loaded together with a huge kernel.
Now, the Slackware installer does not create an initrd for you. Either you did that yourself, or you did not install Slackware.

Can you tell us more about how you installed -current? Where did you obtain the boot image? How did you boot that image? From a CD, a USB stick, the network?
What did you do after the installer reported that it was done and suggested Ctrl-Alt-Del, and before you actually performed the reboot?

Alexander88207 · 07-03-2019, 01:51 PM

Quote:

Originally Posted by Alien Bob

The "exports duplicate symbol", the wad of "insmod" lines and the final error about mounting the root partition on /mnt are all proof of an initrd that is loaded together with a huge kernel.
Now, the Slackware installer does not create an initrd for you. Either you did that yourself, or you did not install Slackware.

Can you tell us more about how you installed -current? Where did you obtain the boot image? How did you boot that image? From a CD, a USB stick, the network?
What did you do after the installer reported that it was done and suggested Ctrl-Alt-Del, and before you actually performed the reboot?

1. Downloaded the ISO from here http://bear.alienbase.nl/mirrors/sla...4-current-iso/
2. Flash the ISO to 2 USB Hard Drives (The ISO on HHD and the sources on SSD)
3. Boot into the ISO and create with cfdisk the following partitions:
/dev/mmcblk0p1 512M EFI
/dev/mmcblk0p2 500M Swap
/dev/mmcblk0p3 27GB Linux Filesystem

4. Selected the Swap, Root and EFI partition

5. Selected to install from a Hard Drive partition (SSD)

6. Installing...

After Installing a ramdisk for the generic kernel was created!

7. Skip making a USB boot stick

8. Skip Installing LILO and proceed to ELILO Installation

9. Install ELILO on the EFI System Partition

10. Install a boot menu entry

11. Deny the GPM Configuration

12. Configured the network, time etc...

13. Select reboot now

14. Reboot wont work and i had to press the power button for 5 seconds

15. Press power again and start

This is how i have installed it on my gaming rig and it works.

Alexander88207 · 07-03-2019, 02:58 PM

Quote:

Originally Posted by Didier Spaier

This line in your boot log puzzles me:

Code:

mount: mounting /dev/mmcblk0p3 on /mnt failed: No such file or directory

Please start the installer, then once logged in as root type this command and post its output:

Code:

lsblk -l -o name,size,fstype|grep mmcblk0p3

Then type:

Code:

mount /dev/mmcblk0p3 /mnt

Then post the output of:

Code:

cat /mnt/etc/fstab|grep "/ "

Still, I don't understand why the root partition would be mounted on /mnt while booting.

lsblk -l -o name,size,fstype|grep mmcblk0p3 = mmcblk0p3 28.1G ext4

cat /mnt/etc/fstab|grep "/ " = /dev/mmcblk0p3 / ext4 defaults 1 1

bassmadrigal · 07-03-2019, 06:01 PM

Quote:

Originally Posted by Alien Bob

The "exports duplicate symbol", the wad of "insmod" lines and the final error about mounting the root partition on /mnt are all proof of an initrd that is loaded together with a huge kernel.
Now, the Slackware installer does not create an initrd for you. Either you did that yourself, or you did not install Slackware.

I thought -current now creates initrds for you automatically during the install.

Code:

+--------------------------+
Wed Jan 23 22:02:34 UTC 2019
--snip--
a/mkinitrd-1.4.11-x86_64-9.txz: Rebuilt.
       Automatically generate an initial ramdisk from the installer.
       Added 'geninitrd' script to generate an initial ramdisk for the kernel that
       /boot/vmlinuz-generic (and/or /boot/vmlinuz-generic-smp) points to.
--snip--

In fact, I checked on my HTPC which I installed using a -current ISO from 23ish May and it had created an initrd and boots the huge kernel by default on UEFI hardware and using elilo. I didn't do anything manually on that system during the install. The installer prompted to use elilo. I agreed, and at some point it built the initrd, and eliloconfig moved the initrd and the huge kernel (named as simply vmlinuz -- I compared filesizes to what was stored in /boot) to the EFI partition and setup the elilo.conf.

Alien Bob · 07-04-2019, 12:56 AM

Quote:

Originally Posted by bassmadrigal

I thought -current now creates initrds for you automatically during the install

Thanks for reminding me ;-) I had forgotten, and have not done a fresh -current install in 2019.