The officially official Devuan Forum!

You are not logged in.

#1 2018-01-20 09:39:15

devuan_dk_fan
Member
Registered: 2018-01-10
Posts: 90  

Vanilla KDE Jessie Devuan system prompts for USB pen drives.

Hi. I am new to Devuan (never used Debian) and have come across an irritating issue. I have a vanilla KDE Jessie Devuan system running on a laptop. Unlike other Devuan DEs, I get prompted for root (sudo) password each time that I want to mount a USB pen drive. As mentioned, this doesn't happen with the Devuan MATE or XFCE4 DEs and I am wondering - why?

$ ls -l /media | grep $USER
drwxr-x---+ 2 root root 4096 Jan 19 16:24 username
$ getfacl /media/usernamegetfacl: Removing leading '/' from absolute path names# file: media/username# owner: root# group: rootuser::rwxuser:username:r-xgroup::---mask::r-xother::---

Is this related with a KDE specific issue? How do I change this so I don't get prompted for a password all the time?

Last edited by devuan_dk_fan (2018-01-21 17:25:13)


Military justice is to justice what military music is to music. - Groucho Marx
I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

#2 2018-01-23 00:01:20

golinux
Administrator
Registered: 2016-11-25
Posts: 3,137  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

KDE is a bit broken in Jessie. We're hoping to have it working in Ascii.  Please see this mail thread for discussion.  You might want to join the ML for the most up-to-date progress reports.  You might also consider upgrading to ascii to help with the testing.

Offline

#3 2018-01-23 08:08:45

devuan_dk_fan
Member
Registered: 2018-01-10
Posts: 90  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

Many thanks for the info. As I understand it, the only way to install KDE on Devuan at this time, is to do as I did? So the correct order would be: net install, edit the sources.list file for ascii, upgrade, and then do an apt-get install kde-standard?


Military justice is to justice what military music is to music. - Groucho Marx
I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

#4 2018-01-23 23:19:44

devuan_dk_fan
Member
Registered: 2018-01-10
Posts: 90  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

Hmm. Running into some odd behavior on a reinstall. I get the following errors:
target file system doesn't have requested /sbin/init
mounting on /dev on /root/dev failed: no such file or directory
no init found. try passing init=bootarg
/bin/sh: can't access tty: job control turned off.
switched to clocksource tsc

I have tried running fsck /dev/sdd1 to no avail.

I have a multiboot system with Linux Mint KDE Sylvia (18.3), Windows 10 and now Devuan Jessie minimal (no DE or WM).

Here is my configuration:

$ sudo fdisk -l

Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xd409f079

Device     Boot    Start        End    Sectors  Size Id Type
/dev/sda1  *        2048   33867282   33865235 16.2G 83 Linux
/dev/sda2       33873918 3907028991 3873155074  1.8T  5 Extended
/dev/sda5       33873920   33939455      65536   32M 82 Linux swap / Solaris
/dev/sda6       33941504 3907028991 3873087488  1.8T 83 Linux

Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B0241C9D-3B5D-4BB7-A133-5B6FEDC6C1D0

Device     Start        End    Sectors  Size Type
/dev/sdb1   2048 7814035455 7814033408  3.7T Microsoft basic data

Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00034d54

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sdc1  *          2048 1951774217 1951772170 930.7G  7 HPFS/NTFS/exFAT
/dev/sdc2       1951774720 1953519615    1744896   852M 27 Hidden NTFS WinRE

Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5d0c65f5

Device     Boot    Start        End    Sectors   Size Id Type
/dev/sdd1  *        2048   34818047   34816000  16.6G 83 Linux
/dev/sdd2       34828286 1953523711 1918695426 914.9G  5 Extended
/dev/sdd5       34828288   34893823      65536    32M 82 Linux swap / Solaris
/dev/sdd6       34895872 1953523711 1918627840 914.9G 83 Linux

Disk /dev/sde: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x0007fb19

Device     Boot Start        End    Sectors  Size Id Type
/dev/sde1        2048 3907028991 3907026944  1.8T  7 HPFS/NTFS/exFAT
$ sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.10.0-42-generic
Found initrd image: /boot/initrd.img-4.10.0-42-generic
Found linux image: /boot/vmlinuz-4.10.0-38-generic
Found initrd image: /boot/initrd.img-4.10.0-38-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 10 (loader) on /dev/sdc1
Found unknown Linux distribution on /dev/sdd1
done

The idea is of course to upgrade to ASCII, once I can boot into the system.

Last edited by devuan_dk_fan (2018-01-23 23:21:25)


Military justice is to justice what military music is to music. - Groucho Marx
I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

#5 2018-01-24 03:42:28

fsmithred
Administrator
Registered: 2016-11-25
Posts: 2,409  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

Looks like you're booting the wrong system. There's no 4.10 kernel in jessie or in any devuan or debian repo right now. Run blkid and compare the uuids to what is in grub.cfg to make sure they are correct. It's also possible that grub and the kernel don't agree on the disk order.

Offline

#6 2018-01-24 06:36:51

devuan_dk_fan
Member
Registered: 2018-01-10
Posts: 90  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

4.10 is the Linux Mint kernel. The Devuan kernel is the "unknown Linux distribution" on /dev/sdd1.

Last edited by devuan_dk_fan (2018-01-24 06:37:48)


Military justice is to justice what military music is to music. - Groucho Marx
I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

#7 2018-01-24 07:07:15

devuan_dk_fan
Member
Registered: 2018-01-10
Posts: 90  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

The two uuid entries are the same:

$ blkid
/dev/sdd1: UUID="fd47cef5-ce5e-4090-8bfa-aef277a49e3e"

and the /boot/grub/grub.cfg reads:

menuentry "unknown Linux distribution (on /dev/sdd1)" --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-fd47cef5-ce5e-4090-8bfa-aef277a49e3e' {
        insmod part_msdos
        insmod ext2
        set root='hd3,msdos1'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos1 --hint-efi=hd3,msdos1 --hint-baremetal=ahci3,msdos1  fd47cef5-ce5e-4090-8bfa-aef277a49e3e
        else
          search --no-floppy --fs-uuid --set=root fd47cef5-ce5e-4090-8bfa-aef277a49e3e
        fi
        linux /vmlinuz root=/dev/sdd1
        initrd /initrd.img

Military justice is to justice what military music is to music. - Groucho Marx
I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

#8 2018-01-24 10:39:50

devuan_dk_fan
Member
Registered: 2018-01-10
Posts: 90  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

OK, I reinstalled the system again (no de or wm) from the Jessie CD .iso. I tried installing the linux-image-3.16.0-4-amd64 rather than linux-image-amd64, but there was no change. I still get the same messages. Interestingly, I booted into Linux Mint and mounted the /dev/sdd1 partition where the Devuan install resides, cd into sbin and ran # ls -l The information from /sbin/init shows that it is pointing to /lib/systemd/systemd. I have a Devuan system on a laptop, with a similar system, where I later added "kde-standard", where the /sbin/init file does not point anywhere. I assume that this has something to do with the install procedure wonking out because I didn't install a boot loader, as I am using my Linux Mint GRUB on /dev/sda1. Weirdly, I didn't run into this issue when I installed this system the first time on my tower computer. The only thing that I can think of that I have done differently, from the first time around, is that I make sure that the Devuan installer doesn't format and include the swap partition for my Linux Mint install on /dev/sda5.

Last edited by devuan_dk_fan (2018-01-24 10:41:16)


Military justice is to justice what military music is to music. - Groucho Marx
I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

#9 2018-01-24 16:27:13

fsmithred
Administrator
Registered: 2016-11-25
Posts: 2,409  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

Now that IS weird. I don't know how you could install systemd (or even get a broken symlink to systemd) in devuan. Is there a /lib/systemd/systemd on /dev/sdd1? You're sure you were looking at the mounted sdd1? (have to ask that) Leaving swap unformatted shouldn't affect that. If you know how to boot from grub command line, that might be useful for diagnosing the problem, in case the problem is related to the disk order changing.

linux-image-amd64 is a metapackage that will always give you the newest kernel for the release. Until recently, that would have been linux-image-3.16.0-4-amd64. The kernel with the patch for meltdown is linux-image-3.16.0-5-amd64. You probably want that one, but don't expect it to fix the current problem.

FWIW, I installed kde5 in ascii last week, and it seemed to be working fine. I haven't played with it much.

Offline

#10 2018-01-24 17:08:16

devuan_dk_fan
Member
Registered: 2018-01-10
Posts: 90  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

Weird indeed:

$ sudo mkdir /mnt/devuan
$ sudo mount /dev/sdd1 /mnt/devuan  
$ cd /mnt/devuan
$ cd /sbin
$ ls -l
total 18968
lrwxrwxrwx 1 root root        20 Dec 21 13:16 init -> /lib/systemd/systemd
$ cd /lib/systemd/     
$ ls -l
total 8404
drwxr-xr-x  2 root root    4096 Nov 27 10:57 network
drwxr-xr-x 28 root root   20480 Jan 11 07:49 system
-rwxr-xr-x  1 root root 1577232 Oct 27 12:12 systemd
-rwxr-xr-x  1 root root   14600 Oct 27 12:12 systemd-ac-power
-rwxr-xr-x  1 root root   55744 Oct 27 12:12 systemd-activate
-rwxr-xr-x  1 root root   92752 Oct 27 12:12 systemd-backlight
-rwxr-xr-x  1 root root   47680 Oct 27 12:12 systemd-binfmt
-rwxr-xr-x  1 root root  105088 Oct 27 12:12 systemd-bootchart
-rwxr-xr-x  1 root root  359632 Oct 27 12:12 systemd-bus-proxyd
-rwxr-xr-x  1 root root  273616 Oct 27 12:12 systemd-cgroups-agent
-rwxr-xr-x  1 root root   92752 Oct 27 12:12 systemd-cryptsetup
-rwxr-xr-x  1 root root  307224 Oct 27 12:12 systemd-fsck
-rwxr-xr-x  1 root root   76376 Oct 27 12:12 systemd-fsckd
-rwxr-xr-x  1 root root   31152 Oct 27 12:12 systemd-hibernate-resume
-rwxr-xr-x  1 root root  339152 Oct 27 12:12 systemd-hostnamed
-rwxr-xr-x  1 root root  281808 Oct 27 12:12 systemd-initctl
-rwxr-xr-x  1 root root  326224 Oct 27 12:12 systemd-journald
-rwxr-xr-x  1 root root  347344 Oct 27 12:12 systemd-localed
-rwxr-xr-x  1 root root  618520 Oct 27 12:12 systemd-logind
-rwxr-xr-x  1 root root   51792 Oct 27 12:12 systemd-modules-load
-rwxr-xr-x  1 root root  847104 Oct 27 12:12 systemd-networkd
-rwxr-xr-x  1 root root  125520 Oct 27 12:12 systemd-networkd-wait-online
-rwxr-xr-x  1 root root   35320 Oct 27 12:12 systemd-quotacheck
-rwxr-xr-x  1 root root   35256 Oct 27 12:12 systemd-random-seed
-rwxr-xr-x  1 root root   51800 Oct 27 12:12 systemd-remount-fs
-rwxr-xr-x  1 root root   31152 Oct 27 12:12 systemd-reply-password
-rwxr-xr-x  1 root root  667664 Oct 27 12:12 systemd-resolved
-rwxr-xr-x  1 root root   92752 Oct 27 12:12 systemd-rfkill
-rwxr-xr-x  1 root root  146032 Oct 27 12:12 systemd-shutdown
-rwxr-xr-x  1 root root   72272 Oct 27 12:12 systemd-sleep
-rwxr-xr-x  1 root root   92752 Oct 27 12:12 systemd-socket-proxyd
-rwxr-xr-x  1 root root   51800 Oct 27 12:12 systemd-sysctl
-rwxr-xr-x  1 root root    1324 Oct 27 04:22 systemd-sysv-install
-rwxr-xr-x  1 root root  340016 Oct 27 12:12 systemd-timedated
-rwxr-xr-x  1 root root  141904 Oct 27 12:12 systemd-timesyncd
-rwxr-xr-x  1 root root  453240 Oct 27 12:12 systemd-udevd
-rwxr-xr-x  1 root root  281808 Oct 27 12:12 systemd-update-utmp
-rwxr-xr-x  1 root root   35256 Oct 27 12:12 systemd-user-sessions
drwxr-xr-x  2 root root    4096 Nov 27 11:22 system-generators
drwxr-xr-x  2 root root    4096 Nov 27 10:57 system-preset
drwxr-xr-x  2 root root    4096 Apr 12  2016 system-shutdown
drwxr-xr-x  2 root root    4096 Nov 27 11:22 system-sleep

Military justice is to justice what military music is to music. - Groucho Marx
I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

#11 2018-01-25 04:50:34

devuan_dk_fan
Member
Registered: 2018-01-10
Posts: 90  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

If any of the developers at Devuan want me to mirror and upload a copy of the USB pen drive that I am using or the actual hard drive install, please let me know now (with instructions), because otherwise, I will just burn another copy of the Jessie installer and try a reinstall. I am also seriously considering wiping my Linux Mint install, to rule out the possibility of systemd infiltration.


Military justice is to justice what military music is to music. - Groucho Marx
I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

#12 2018-01-25 08:49:27

devuan_dk_fan
Member
Registered: 2018-01-10
Posts: 90  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

OK, something is definitely wrong here. I pre-formatted the partitions on the target hard drive and re-burned the devuan_jessie_1.0.0_amd64_CD.iso onto the USB pen drive. I again ran into the same errors and the same problems as above - systemd all over the place. I don't dare erase Linux Mint Sylvia KDE as I could still end up not being able to get a working Devuan system to install.

Please keep me up to date on any progress as I would like to get a working Devuan system installed.


Military justice is to justice what military music is to music. - Groucho Marx
I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

#13 2018-01-25 09:35:25

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 1,106  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

You seem to have put yourself in a muddle as you first mount /dev/sdd1 onto /mnt/devuan, and then cd into /sbin rather than /mnt/devuan/sbin.

So the rest shows that your root file system (presumably your Mint) has systemd.

Perhaps you should try # chroot /mnt/devuan instead, in order to investigate the /dev/sdd1 partition as if it was the root file system.

Offline

#14 2018-01-25 14:58:49

devuan_dk_fan
Member
Registered: 2018-01-10
Posts: 90  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

Hi Ralph. Thanks for the reply. Ahh. Understood. The main issue is however, that I am unable to get a Devuan system up and running, as no matter what I do, I consistently get the same errors:

target file system doesn't have requested /sbin/init
mounting on /root/dev failed. no such file or directory
no init found. try passing init=bootarg.
/bin/sh: cant' access tty: job control turned off.
switched to clocksource tsc

If these are unlikely to be caused by an errant systemd, what is causing them? I have tried searching and solving each error, but I don't seem to have any luck.

I am experimenting with a Miyo system running Trinity right now, but can try reinstall a minimal cli Devuan system, if I have an idea how to solve the above errors.

Last edited by devuan_dk_fan (2018-01-25 14:59:55)


Military justice is to justice what military music is to music. - Groucho Marx
I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

#15 2018-01-25 15:55:55

fsmithred
Administrator
Registered: 2016-11-25
Posts: 2,409  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

Those look like the kinds of errors I've seen when trying to boot the wrong partition. Try poking around in grub, and maybe you can boot it manually and figure out what's going on.

https://www.linux.com/learn/how-rescue- … ub-2-Linux

Offline

#16 2018-01-25 16:42:46

devuan_dk_fan
Member
Registered: 2018-01-10
Posts: 90  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

The weird thing, as you can see from above, the UUIDs for the partition and the GRUB entry are the same.


Military justice is to justice what military music is to music. - Groucho Marx
I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

#17 2018-01-25 18:01:41

devuan_dk_fan
Member
Registered: 2018-01-10
Posts: 90  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

OK, I have rechecked the sha256sum for the devuan_jessie_1.0.0_amd64_CD.iso and I have burned the .iso to another USB pen drive. I have then succeeded installing a minimal cli system without a DE on the laptop and have then added the Trinity DE repos and installed without a problem.

On the other hand, I have tried the same install on my tower computer. I erased my MiyoLinux install and then installed the same minimal cli system as installed on my laptop, but still get the same errors at boot. I have confirmed that the UUID entry in GRUB matches the actual UUID for /dev/sdd1. I have also followed Ralph's advice and used # chroot:

# mount /dev/sdd1 /mnt/devuan
leviathan brian # chroot /mnt/devuan          
# cd /sbin
root@leviathan:/sbin# ls -l
total 7004

-rwxr-xr-x 1 root root     37064 May 29  2015 init

As Ralph pointed out, the chroot made the difference as to which system install that I am in smile

Nothing has as of yet suggested a solution to the above errors, so while we know it isn't systemd that is at play, I have no idea what is actually going on here.


Military justice is to justice what military music is to music. - Groucho Marx
I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

#18 2018-01-25 21:25:11

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 1,106  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

target file system doesn't have requested /sbin/init
mounting on /root/dev failed. no such file or directory
no init found. try passing init=bootarg.
/bin/sh: cant' access tty: job control turned off.
switched to clocksource tsc

That output would be issued by the initrd init script(s), being unhappy with /dev/sdd1 as the root file system. It thus would seem the right kernel, (hd3,msdos1)/vmlinuz, is loaded with its initrd, (hd3,msdos1)/initrd.img, but there is then a problem with the mounting of /dev/sdd1 as root file system.

Perhaps there is an /etc/fstab that disagrees? (In the Devuan partition)

This kind of pivot issues are challenging to debug, but the initrd init scripts (of Devuan) might include the ability to break the initialization procedure, and enter an interactive at a certain point. For example, you could add

break=mount

to the "linux" line in the grub stanza, to gain a command shell at the "mount" point, which is just before the target root file system is mounted.

It will let you investigate things while in the pre-pivot stage. At that stage, the initrd is root file system, so don't confuse yourself about that smile. The goal would be to find out why, at that point, /dev/sdd1 is not the right file system to pivot to.

Offline

#19 2018-01-25 23:39:04

devuan_dk_fan
Member
Registered: 2018-01-10
Posts: 90  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

Hmm. This is really outside my frame of reference, so please bear with me. As I understand it, I was supposed to make the GRUB "linux" boot line for my Devuan install to look like this when I start the computer up and temporarily edit the boot settings:

linux /vmlinuz root=/dev/sdd1 break=mount

I was expecting a cli of sorts from your description, but I just got the following:

spawning shell within the initramfs
modeprobe: module ehci-pci not found in modules.dep
modeprobe: module ehci-orio not found in modules.dep
modeprobe: module uhci-hcd not found in modules.dep

The fundamental problem is that even if I had gotten a command line, what should I have done?
A vi /etc/fstab? Not sure where I would be residing in the initrd file system, nor how I would gain access to /etc/fstab


Military justice is to justice what military music is to music. - Groucho Marx
I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

#20 2018-01-26 05:43:55

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 1,106  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

Yes, I also expected it to go into a shell prompt; a busybox shell prompt. And it should have a number of useful commands available, plus some more in /bin and /sbin.

But maybe you should park that line of study for the moment, and first address those module complaints. They all concern USB, and perhaps it's important to get them into your initrd.

1. Thus, first restore the grub line to be

linux root=/dev/sdd1

2. Then, boot up your Mint, and mount the partition like before, chroot into it, and set up the kernel's virtual file systems:

# mount /dev/sdd1 /mnt/devuan
# chroot /mnt/devuan
# mount -t proc none /proc
# mount -t sysfs none /sys
# mount -t devpts none /dev/pts

In passing, note that the chroot command starts a /bin/bash from within the Devuan file system, and all commands are from within the Devuan file system. The running kernel however is the Mint kernel.

3. Now, edit the file /etc/initramfs-tools/modules, to add the modules you saw mentioned:

ehci-pci
ehci-orion
uhci-hcd

(note I assume it said ehci-orion with a final n, and not ehci-orio. In any case, the actual module has that final n)

4. Then rebuild the initrd with the following

# update-initramfs -u -k all

That command will look for all kernels in /boot of the chroot-ed file system (Devuan), and prepare an initrd for each, into /boot. It does not change the links /vmlinuz and /initrd.img, which thus remain pointing out the kernel to use and its associated, and now updated, initrd.

5. Then, have a peek at /etc/fstab in the chroot-ed file system, and make sure it's fully agreeable.

6. Exit the chroot, and reboot into Devuan ... without problems ... (as if:))

If it doesn't work, you might want to try the UUID variation for the grub line, i.e.

linux root=UUID=fd47cef5-ce5e-4090-8bfa-aef277a49e3e

Doing so would avoid any possible problems with USB device enumeration during boot. As fsmithred noted, it's possible that the Devuan boot-up sees a different device enumeration than the Mint boot-up (for reasons too complicated to worry about), and, say, that the Devuan partition gets enumrated as the first disk (/dev/sda1) or something. By referring to the UUID, it ignores the enumeration, and it picks the matching partition with that UUID.
It's again important that /etc/fstab of the Devuan partition agrees.

Offline

#21 2018-01-26 07:35:45

devuan_dk_fan
Member
Registered: 2018-01-10
Posts: 90  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

Hi again Ralph. I get the following error right off the bat:

# mount -t procfs none /proc
mount: unknown filesystem type 'procfs'

Probably not necessary, but I thought that I would check to see if things are in place:

# ls -l
total 92
drwxr-xr-x  2 root root  4096 Jan 25 18:20 bin
drwxr-xr-x  2 root root  4096 Jan 25 18:38 boot
drwxr-xr-x  4 root root  4096 Jan 25 18:08 dev
drwxr-xr-x 94 root root  4096 Jan 25 18:38 etc
drwxr-xr-x  2 root root  4096 Jan 25 18:07 home
lrwxrwxrwx  1 root root    31 Jan 25 18:11 initrd.img -> /boot/initrd.img-3.16.0-4-amd64
drwxr-xr-x 16 root root  4096 Jan 25 18:14 lib
drwxr-xr-x  2 root root  4096 Jan 25 18:13 lib64
drwx------  2 root root 16384 Jan 25 18:07 lost+found
drwxr-xr-x  3 root root  4096 Jan 25 18:07 media
drwxr-xr-x  2 root root  4096 Jan 25 18:08 mnt
drwxr-xr-x  2 root root  4096 Jan 25 18:08 opt
drwxr-xr-x  2 root root  4096 May  9  2016 proc
drwx------  2 root root  4096 Jan 25 19:03 root
drwxr-xr-x  3 root root  4096 Jan 26 08:33 run
drwxr-xr-x  2 root root  4096 Jan 25 18:38 sbin
drwxr-xr-x  2 root root  4096 Jan 25 18:08 srv
drwxr-xr-x  2 root root  4096 May 29  2015 sys
drwxrwxrwt  2 root root  4096 Jan 25 18:22 tmp                                                                                                                                                                    
drwxr-xr-x 10 root root  4096 Jan 25 18:08 usr                                                                                                                                                                    
drwxr-xr-x 11 root root  4096 Jan 25 18:08 var                                                                                                                                                                    
lrwxrwxrwx  1 root root    27 Jan 25 18:11 vmlinuz -> boot/vmlinuz-3.16.0-4-amd64
/boot# ls -l
total 9604
-rw-r--r-- 1 root root  157756 Dec 14 22:27 config-3.16.0-4-amd64
-rw-r--r-- 1 root root 3845607 Jan 25 18:38 initrd.img-3.16.0-4-amd64
-rw-r--r-- 1 root root 2684316 Dec 14 22:27 System.map-3.16.0-4-amd64
-rw-r--r-- 1 root root 3137712 Dec 14 22:25 vmlinuz-3.16.0-4-amd64

So at least on the surface, things look like they are where they are supposed to be. I have been searching to find a reason for the "unknown file system" error up top, but I haven't found anything relevant to this situation yet.

# mount -t sysfs none /sys
# mount -t devpts  /dev/pts
mount: can't find /dev/pts in /etc/fstab

As you can see, mounting the sys file system went fine, but the next command also kicked up an error. Am I correct in my assumption that this error means that there are no "/dev/" or UUID mount points in /etc/fstab?

Last edited by devuan_dk_fan (2018-01-26 08:22:43)


Military justice is to justice what military music is to music. - Groucho Marx
I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

#22 2018-01-26 08:23:06

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 1,106  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

Ah, my fault. It should be

# mount -t proc none /proc

sorry about that.

(I've corrected the post above)

Offline

#23 2018-01-26 10:15:55

devuan_dk_fan
Member
Registered: 2018-01-10
Posts: 90  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

I am still getting an error with the following:

# mount -t devpts  /dev/pts
mount: can't find /dev/pts in /etc/fstab

Not sure if I can go ahead with the rest that you posted. Things are screwy enough as is smile

Last edited by devuan_dk_fan (2018-01-26 10:22:37)


Military justice is to justice what military music is to music. - Groucho Marx
I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

#24 2018-01-26 10:17:23

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 1,106  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

Sorry again; I'm too sloppy. It should have been

# mount -t devpts  none /dev/pts

('ve editied the original as well)

Offline

#25 2018-01-26 10:26:31

devuan_dk_fan
Member
Registered: 2018-01-10
Posts: 90  

Re: Vanilla KDE Jessie Devuan system prompts for USB pen drives.

OK, I got part of the way:

# update-initramfs -k all
You must specify at least one of -c, -u, or -d.

Usage: /usr/sbin/update-initramfs [OPTION]...

Options:
 -k version     Specify kernel version or 'all'
 -c             Create a new initramfs
 -u             Update an existing initramfs
 -d             Remove an existing initramfs
 -t             Take over a custom initramfs with this one
 -b directory   Set alternate boot directory
 -v             Be verbose
 -h             This message

It looks like "-k" and "all" are the same thing. OK to just run:

# update-initramfs -k

???

Nope that doesn't work.

# update-initramfs -k vmlinuz-3.16.0-4-amd64

???

Nope. I also tried this:

# /usr/sbin/update-initramfs -k all
You must specify at least one of -c, -u, or -d.

Usage: /usr/sbin/update-initramfs [OPTION]...

Options:
 -k version     Specify kernel version or 'all'
 -c             Create a new initramfs
 -u             Update an existing initramfs
 -d             Remove an existing initramfs
 -t             Take over a custom initramfs with this one
 -b directory   Set alternate boot directory
 -v             Be verbose
 -h             This message

Last edited by devuan_dk_fan (2018-01-26 10:40:34)


Military justice is to justice what military music is to music. - Groucho Marx
I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

Board footer