ntfsfix found no error, ntfsinfo is less helpful; while it prints info at the end it persists of failing to open the device it just printed info about.
Code: Select all
root@porteus:/1/Boot# ntfsfix --version|head -n 1
ntfsfix v2021.8.22
root@porteus:~# ntfsfix /dev/sda1
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... FIXED
NTFS volume version is 3.1.
NTFS partition /dev/sda1 was processed successfully.
root@porteus:~# ntfsinfo -m /dev/sda1
Volume is scheduled for check.
Please boot into Windows TWICE, or use the 'force' option.
NOTE: If you had not scheduled check and last time accessed this volume
using ntfsmount and shutdown system properly, then init scripts in your
distribution are broken. Please report to your distribution developers
(NOT to us!) that init scripts kill ntfsmount or mount.ntfs-fuse during
shutdown instead of proper umount.
Failed to open '/dev/sda1'.
Here all my vmlinuz of my internal first partition and their md5sum
Code: Select all
root@porteus:/1/Boot# ls -o vmlinuz*
-rwxrwxrwx 1 root 4322688 2020-04-04 20:23 vmlinuz
-rwxrwxrwx 1 root 3576672 2015-05-30 13:30 vmlinuz64
-rwxrwxrwx 1 root 0 2017-11-12 04:36 vmlinuz64_is_TinyCorePure64-6.3
-rwxrwxrwx 1 root 3855120 2018-04-22 20:25 vmlinuz_Porteus_4.0_x86_64
-rwxrwxrwx 1 root 4384128 2019-05-26 00:00 vmlinuz_Porteus_5.0rc1_x86_64
-rwxrwxrwx 1 root 3978112 2019-02-24 00:00 vmlinuz_Porteus_5.0rc1d_x86_64
-rwxrwxrwx 1 root 4330880 2020-08-09 00:00 vmlinuz_Porteus_5.0rc2_x86_64
-rwxrwxrwx 1 root 4318592 2020-02-12 02:24 vmlinuz_Porteus_5.4.19_x86_64
-rwxrwxrwx 1 root 4322688 2020-04-04 20:23 vmlinuz_Porteus_5.4.30_x86_64
-rwxrwxrwx 1 root 2248032 2010-07-14 14:43 vmlinuz_quirkyNOP120
root@porteus:/1/Boot# md5sum vmlinuz*
f5df3c96f73367689085585bd438b6e7 vmlinuz
c4f46b5cd826d7a765a3e85439309cfc vmlinuz64
d41d8cd98f00b204e9800998ecf8427e vmlinuz64_is_TinyCorePure64-6.3
1c642ff455d89ba59ebbd93222712bfc vmlinuz_Porteus_4.0_x86_64
bceeb13f2e102d59af577d3e40f54bfa vmlinuz_Porteus_5.0rc1_x86_64
fff901330ceb38ef836137ee8cd50a6d vmlinuz_Porteus_5.0rc1d_x86_64
4309801d9bc0e7d575812ed23a92bf9d vmlinuz_Porteus_5.0rc2_x86_64
e2197abb9d338d66690068ad5e3c1503 vmlinuz_Porteus_5.4.19_x86_64
f5df3c96f73367689085585bd438b6e7 vmlinuz_Porteus_5.4.30_x86_64
a32329edbcfb9c0717a7c5e98ea6a032 vmlinuz_quirkyNOP120
same for initrd
Code: Select all
root@porteus:/1/Boot# ls -o initrd*
-rwxrwxrwx 1 root 821660 2020-04-11 00:00 initrd.xz
-rwxrwxrwx 1 root 824160 2018-04-22 20:25 initrd.xz_Porteus_4.0_x86_64
-rwxrwxrwx 1 root 822732 2019-02-24 00:00 initrd.xz_Porteus_5.0rc1d_x86_64
-rwxrwxrwx 1 root 821660 2020-04-11 00:00 initrd.xz_Porteus_5.0rc2_x86_64
-rwxrwxrwx 1 root 1808240 2010-07-14 14:43 initrd_quirkyNOP120.gz
root@porteus:/1/Boot# md5sum initrd*
ee8fd5662737b8385d51592982075645 initrd.xz
2934a6c4b46bc2ab99cddcb4647e6e5c initrd.xz_Porteus_4.0_x86_64
19bd879c9e3b502f67cbcb9baf4422f4 initrd.xz_Porteus_5.0rc1d_x86_64
ee8fd5662737b8385d51592982075645 initrd.xz_Porteus_5.0rc2_x86_64
9a5623b6dbe806ed6d757ef5210af483 initrd_quirkyNOP120.gz
Now the probably strangest part. As you can see above, vmlinuz and vmlinuz_Porteus_5.4.30_x86_64 have the same size and same md5sum.
Still when configuring vmlinuz_Porteus_5.4.30_x86_64 in porteus.cfg I get the error from the screenshot from the initial post.
BUT when I configure vmlinuz instead...
strangely is loads this kernel
Code: Select all
root@porteus:~# uname -a
Linux porteus.example.net 5.4.57-porteus #1 SMP Sun Aug 9 09:03:28 UTC 2020 x86_
64 Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz GenuineIntel GNU/Linux
which is vmlinuz_Porteus_5.0rc2_x86_64. Of course I cannot start X since this kernel not works with my 010-nvidia-340.108-k.5.4.30-porteus-v5.0-x86_64_rava.xzm .
Code: Select all
root@porteus:/1/Boot# file vmlinuz_Porteus_5.0rc2_x86_64
vmlinuz_Porteus_5.0rc2_x86_64: Linux kernel x86 boot executable bzImage, version 5.4.57-porteus (root@porteus) #1 SMP Sun Aug 9 09:03:28 UTC 2020, RO-rootFS, swap_dev 0x4, Normal VGA
root@porteus:/1/Boot# file vmlinuz
vmlinuz: Linux kernel x86 boot executable bzImage, version 5.4.30-porteus (root@porteus) #1 SMP Sat Apr 4 20:11:00 UTC 2020, RO-rootFS, swap_dev 0x4, Normal VGA
I honestly do not get what is going on.
How can loading vmlinuz - which is 5.4.30_x86_64 kernel - load vmlinuz_Porteus_5.0rc2_x86_64 instead?
How can it be that my porteus.cfg seems to do other stuff than what it is configured and told to do?
To make it all complete, here the relevant entry of the internal partition porteus.cfg:
Code: Select all
LABEL xfceRava5.0rc3f
MENU LABEL 5.0rc3f baseV2021-??-?? INTERN XFCE fsck Text mode, RavaStyle
KERNEL vmlinuz
APPEND initrd=initrd.xz from=UUID:Bla-BluBB/Porteus_5.0rc3f ramsize=10% zram=20% timezone=Europe/Berlin volume=75% kmap=de lang=de fsck 3
TEXT HELP
Run Porteus the Rava way:
always fresh - telinit 3 (or
"without starting X")
ENDTEXT
the f in Porteus_5.0rc3
f is my personal numbering and has no reflection on how the 5.0rc3 version is officially named.