Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

[solved] edit update grub modif

Help for Current Versions of MX
Message
Author
tradonal
Forum Novice
Forum  Novice
Posts: 80
Joined: Mon Sep 25, 2017 11:43 am

[solved] edit update grub modif

#1 Post by tradonal » Sun Mar 04, 2018 4:45 pm

hello,
update GRUB on 4.15.5 has completely modify directory /etc/grub.d/
https://www.antixforum.com/spectre-and- ... -upgrades/
before I had this

Code: Select all

# ls
00_header        10_linux      20_memtest86+  30_uefi-firmware  41_custom
05_debian_theme  20_linux_xen  30_os-prober   40_custom        README 
Now I have this

Code: Select all

# ls
00_header        20_linux_xen        40_custom_proxy     43_custom_proxy  backup            README
05_debian_theme  21_memtest86+       41_os-prober_proxy  44_custom        bin
10_linux         30_os-prober_proxy  42_uefi-firmware    45_grml          proxifiedScripts

Code: Select all

root@mx1:/
# ls -la /etc/grub.d/*
-rwxr-xr-x 1 root root  9424 déc 14  2015 /etc/grub.d/00_header
-rwxr-xr-x 1 root root  6058 déc 14  2015 /etc/grub.d/05_debian_theme
-rwxr-xr-x 1 root root 12261 déc 14  2015 /etc/grub.d/10_linux
-rwxr-xr-x 1 root root 11082 déc 14  2015 /etc/grub.d/20_linux_xen
-rwxr-xr-x 1 root root  1570 avr 15  2017 /etc/grub.d/21_memtest86+
-rwxr-xr-x 1 root root   442 fév 24 21:48 /etc/grub.d/30_os-prober_proxy
-rwxr-xr-x 1 root root   410 fév 24 21:48 /etc/grub.d/40_custom_proxy
-rwxr-xr-x 1 root root   841 fév 24 21:48 /etc/grub.d/41_os-prober_proxy
-rwxr-xr-x 1 root root  1416 déc 14  2015 /etc/grub.d/42_uefi-firmware
-rwxr-xr-x 1 root root   410 fév 24 21:48 /etc/grub.d/43_custom_proxy
-rwxr-xr-x 1 root root   216 déc 14  2015 /etc/grub.d/44_custom
-rwxr-xr-x 1 root root  3276 jan 24  2014 /etc/grub.d/45_grml
-rw-r--r-- 1 root root   483 déc 14  2015 /etc/grub.d/README

/etc/grub.d/backup:
total 24
drwxr-xr-x 4 root root 4096 oct 31 21:35 .
drwxr-xr-x 5 root root 4096 mar  4 13:35 ..
drwxr-xr-x 5 root root 4096 oct 31 21:35 boot_grub
-rw-r--r-- 1 root root 1295 oct 31 21:35 default_grub
drwxr-xr-x 2 root root 4096 oct 31 21:35 etc_grub_d
-rw-r--r-- 1 root root  519 oct 31 21:35 RESTORE_INSTRUCTIONS

/etc/grub.d/bin:
total 456
drwxr-xr-x 2 root root   4096 fév 24 21:48 .
drwxr-xr-x 5 root root   4096 mar  4 13:35 ..
-rwxr-xr-x 1 root root 458256 fév 24 21:48 grubcfg_proxy

/etc/grub.d/proxifiedScripts:
total 24
drwxr-xr-x 2 root root  4096 mar  3 19:39 .
drwxr-xr-x 5 root root  4096 mar  4 13:35 ..
-rwxr-xr-x 1 root root   518 mar  3 19:39 custom
-rwxr-xr-x 1 root root 11692 déc 14  2015 os-prober
root@mx1:/
# 
?

thx

EDIT1 the 30/03/2018
for
hello,
update GRUB on 4.15.5 has completely modify directory /etc/grub.d/
https://www.antixforum.com/spectre-and- ... -upgrades/
before I had this
This is not fair, the cause is grub-customizer
it's here viewtopic.php?p=440473#p440473
Last edited by tradonal on Fri Mar 30, 2018 11:31 am, edited 3 times in total.

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 10089
Joined: Sun Dec 16, 2007 1:17 pm

Re: Meltdown and Spectre

#2 Post by dolphin_oracle » Sun Mar 04, 2018 4:48 pm

I believe your changes are due to usage of grub-customizer, not due to the kernel change. the give away is the presence of the backup directory.

also, your forum topic title has nothing to do with your post.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

tradonal
Forum Novice
Forum  Novice
Posts: 80
Joined: Mon Sep 25, 2017 11:43 am

Re: Meltdown and Spectre

#3 Post by tradonal » Sun Mar 04, 2018 5:53 pm

re
latest Meltdown patched kernels available
https://antixlinux.com/category/news/
here is how it happened
-) grub is in the mbr
-) sda1 primary partition with my main system MX-16
-) sda6 logical partition to try various distributions
-) I installed antix-17- 4.10.5 on sda6 option grub do not install
-) reboot on sda1
-) update-grub, ok nothing changes

reboot on antiX-17
-) run antix-packageinstaller
-) kernel proposes 4.15.5
-) run instal

Code: Select all

Preparing the unpacking of ... / 0-linux-headers-4.15.5-antix.1-686-smp-pae_4.15.5-antix.1-686-smp-pae-2_i386.deb ...
Unpacking of linux-headers-4.15.5-antix.1-686-smp-pae (4.15.5-antix.1-686-smp-pae-2) ...
Selection of the linux-image-4.15.5-antix.1-686-smp-pae package previously deselected.
Preparing the unpacking of ... / 1-linux-image-4.15.5-antix.1-686-smp-pae_4.15.5-antix.1-686-smp-pae-2_i386.deb ...
Unpacking of linux-image-4.15.5-antix.1-686-smp-pae (4.15.5-antix.1-686-smp-pae-2) ...
-) install is ok

reboot on sda1 for update grub and that's where everything was changed

I believe your changes are due to usage of grub-customizer, not due to the kernel change.
i always do like that since tjs and i never had that ....
I have never used grub-customizer to edit grub

thank you

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 10089
Joined: Sun Dec 16, 2007 1:17 pm

Re: edit update grub modif

#4 Post by dolphin_oracle » Sun Mar 04, 2018 6:39 pm

I have never used grub-customizer to edit grub
my mistake. :happy:
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

tradonal
Forum Novice
Forum  Novice
Posts: 80
Joined: Mon Sep 25, 2017 11:43 am

Re: edit update grub modif

#5 Post by tradonal » Thu Mar 08, 2018 5:00 pm

re,
I am french, more precisely belgique francophone .... :happy:
https://fr.wikipedia.org/wiki/Communaut ... e_Belgique

I'm sorry, but I can not translate the meaning of your answer ?
dolphin_oracle wrote:
I have never used grub-customizer to edit grub
my mistake. :happy:
-) my mistake = mon erreur
En FR:
Dois-je comprendre par votre réponse que c'est une erreur de ma part de ne pas utiliser grub-customizer et que vous me conseillez d'utiliser celui ci ?
Traduction:
Should I understand from your answer that it is an error on my part not to use grub-customizer and that you advise me to use this one?

just to test and for me see, I did:
-) I no longer have antiX on sda6, I format the partition
-) I installed SliTaz GNU / Linux - 5.0-RC4 20180305 on sda6
-) reboot sur sda1 and update-grub

1) my grub.cfg file is good over menuentry antix-17 on sda6

Code: Select all

root@mx1:~
# grep -i sda6 /boot/grub/grub.cfg 
menuentry "unknown Linux distribution (sur /dev/sda6)" --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-d6aad3a1-1ef7-490f-ae42-9e65ca7c6445' {
	linux /boot/vmlinuz-3.2.98-slitaz root=/dev/sda6
submenu "Options avancées pour unknown Linux distribution (sur /dev/sda6)"{
menuentry "unknown Linux distribution (sur /dev/sda6)" --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.2.98-slitaz--d6aad3a1-1ef7-490f-ae42-9e65ca7c6445' {
		linux /boot/vmlinuz-3.2.98-slitaz root=/dev/sda6
root@mx1:~
# 
2) I run grub-customizer just to see

Code: Select all

carl@mx1:~
$ gksudo grub-customizer 
 *** initializing (w/o specified bootloader type)…
   * reading partition info…
   * Loading Framebuffer resolutions (background process)
   * Finding out if this is a live CD
 *** initializing (w/ specified bootloader type)…
   * Checking if the config directory is clean
 *** loading configuration
 *** loading - preserveConfig: no
   * unsetting saved config
 *** loading settings
 *** loading grub list
   * loading scripts…
   * loading proxies…
   * cleaning up proxy configuration…
   * creating proxifiedScript links & chmodding other files…
   * running grub-mkconfig
   * restoring grub configuration
   * removing invalid proxies from list
   * loading completed
 *** grub list completely loaded
 *** loading saved grub list
and is not fair, it gives me tjs entries for antix on sda6
Image

what do you recommend ?
thank you

User avatar
cyrilus31
Forum Regular
Forum Regular
Posts: 556
Joined: Thu Nov 03, 2016 3:24 pm

Re: edit update grub modif

#6 Post by cyrilus31 » Fri Mar 09, 2018 6:16 am

Non, my mistake c'est "mes excuses" car d_o pensait que tu avais utilisé grub-customizer.
Anyway I'll let d_o answer your question.

User avatar
male
Forum Regular
Forum Regular
Posts: 323
Joined: Thu Jan 23, 2014 8:38 am

Re: edit update grub modif

#7 Post by male » Fri Mar 09, 2018 6:40 am

Félicitations pour la destruction de votre système Dual/Multiboot par l'utilisation simultanée de update-grub (CLI) et du customizer (GUI) en même temps!

Mon avis appartient à grub-customizer interdit! :lipsrsealed:
Male is the capital of the Maldives and its wonderful people.

tradonal
Forum Novice
Forum  Novice
Posts: 80
Joined: Mon Sep 25, 2017 11:43 am

Re: edit update grub modif

#8 Post by tradonal » Fri Mar 09, 2018 2:26 pm

re
cyrilus31 wrote:Non, my mistake c'est "mes excuses" car d_o pensait que tu avais utilisé grub-customizer.
Anyway I'll let d_o answer your question.
Thank you for the feedback :wink:
male wrote:Félicitations pour la destruction de votre système Dual/Multiboot par l'utilisation simultanée de update-grub (CLI) et du customizer (GUI) en même temps!

Mon avis appartient à grub-customizer interdit! :lipsrsealed:
-) J'ai tjs utilisé cette méthode pour mettre a jour grub
-) I always use this method to update grub

Code: Select all

$ sudo update-grub
[sudo] password for carl: 
Création du fichier de configuration GRUB…
Image Linux trouvée : /boot/vmlinuz-4.10.1-antix.1-486-smp
Image mémoire initiale trouvée : /boot/initrd.img-4.10.1-antix.1-486-smp
Image Linux trouvée : /boot/vmlinuz-3.16.0-4-686-pae
Image mémoire initiale trouvée : /boot/initrd.img-3.16.0-4-686-pae
Image Linux trouvée : /boot/vmlinuz-3.16.0-4-586
Image mémoire initiale trouvée : /boot/initrd.img-3.16.0-4-586
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
  No volume groups found
unknown Linux distribution trouvé sur /dev/sda6
  No volume groups found
unknown Linux distribution trouvé sur /dev/sda6
fait
-) Avec grub-customizer, je n'ai jamais rien enregistré, je ferme toujours l'application sans sauvegarder
With grub-customizer, I have never registered anything, I always close the application without saving
.....
...

1) for my personal information I would like to understand how and why this modification of files in grub.d ?
thx

User avatar
male
Forum Regular
Forum Regular
Posts: 323
Joined: Thu Jan 23, 2014 8:38 am

Re: edit update grub modif

#9 Post by male » Fri Mar 09, 2018 5:17 pm

tradonal wrote: for my personal information I would like to understand how and why this modification of files in grub.d ?
I think you just installed the wrong kernel with 4.15.5 (see above).

Anti writes clearly and unequivocally that this one is for the 17.
antiX-16/16.1/16.2 users have these options.


1. Use the 4.9.83.antix.1 kernel now in jessie repo (RECOMMENDED)
2. Use the 4.4.109 kernel. This was built from Ubuntu 4.4.109 source
3. Use a patched Debian kernel (3.16.0-5)
4. Do nothing (not advised)
You've got to have

Code: Select all

Distro: MX-16-RC1_386 Metamorphosis 24 November 2016

... and, SliTaz is probably very weak over his chest at the moment. :bagoverhead:
http://www.slitaz.org/fr/get/
Male is the capital of the Maldives and its wonderful people.

tradonal
Forum Novice
Forum  Novice
Posts: 80
Joined: Mon Sep 25, 2017 11:43 am

Re: edit update grub modif

#10 Post by tradonal » Sat Mar 10, 2018 4:08 pm

re,
thank you for your reply,
it is with antix-17 on sda6 that I install the kernel 4.15.5

little summary of my config:
viewtopic.php?f=104&t=44313#p437947
-) grub is in the mbr
-) sda1 primary partition with my main system MX-16
-) sda6 logical partition to try various distributions
-) I installed antix-17- 4.10.5 on sda6 option grub do not install
reboot on sda1
-) update-grub, ok nothing changes
reboot on antiX-17 on sda6
-) run antix-packageinstaller
-) kernel proposes 4.15.5
-) run instal
....
...
Without being sure, I think that the modification of the directory /grub.d on sda1 has nothing to do with the update-grub for antix-17 4.15.5 on sda6 ....
because for
for my personal information I would like to understand how and why this modification of files in grub.d ?
I just came across this: https://answers.launchpad.net/grub-customizer/+faq/1355

on the other hand, I just noticed that after running the update-grub command

Code: Select all

root@mx1:/
# update-grub
Création du fichier de configuration GRUB…
Image Linux trouvée : /boot/vmlinuz-4.10.1-antix.1-486-smp
Image mémoire initiale trouvée : /boot/initrd.img-4.10.1-antix.1-486-smp
Image Linux trouvée : /boot/vmlinuz-3.16.0-4-686-pae
Image mémoire initiale trouvée : /boot/initrd.img-3.16.0-4-686-pae
Image Linux trouvée : /boot/vmlinuz-3.16.0-4-586
Image mémoire initiale trouvée : /boot/initrd.img-3.16.0-4-586
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
  No volume groups found
unknown Linux distribution trouvé sur /dev/sda6
  No volume groups found
unknown Linux distribution trouvé sur /dev/sda6
fait
root@mx1:/
# 
A dmesg just after running update-grub shows errors

Code: Select all

[sam mar 10 20:28:07 2018] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[sam mar 10 20:28:07 2018] JFS: nTxBlock = 8192, nTxLock = 65536
[sam mar 10 20:28:07 2018] QNX4 filesystem 0.2.3 registered.
[sam mar 10 20:28:08 2018] REISERFS warning (device sda2): sh-2006 read_super_block: bread failed (dev sda2, block 8, size 1024)
[sam mar 10 20:28:08 2018] REISERFS warning (device sda2): sh-2006 read_super_block: bread failed (dev sda2, block 64, size 1024)
[sam mar 10 20:28:08 2018] REISERFS warning (device sda2): sh-2021 reiserfs_fill_super: can not find reiserfs on sda2
[sam mar 10 20:28:08 2018] EXT4-fs (sda2): unable to read superblock
[sam mar 10 20:28:08 2018] EXT4-fs (sda2): unable to read superblock
[sam mar 10 20:28:08 2018] EXT2-fs (sda2): error: unable to read superblock
[sam mar 10 20:28:08 2018] SQUASHFS error: squashfs_read_data failed to read block 0x0
[sam mar 10 20:28:08 2018] squashfs: SQUASHFS error: unable to read squashfs_super_block
[sam mar 10 20:28:08 2018] FAT-fs (sda2): bogus number of reserved sectors
[sam mar 10 20:28:08 2018] FAT-fs (sda2): Can't find a valid FAT filesystem
[sam mar 10 20:28:08 2018] FAT-fs (sda2): bogus number of reserved sectors
[sam mar 10 20:28:08 2018] FAT-fs (sda2): Can't find a valid FAT filesystem
[sam mar 10 20:28:08 2018] isofs_fill_super: bread failed, dev=sda2, iso_blknum=16, block=32
[sam mar 10 20:28:08 2018] UDF-fs: error (device sda2): udf_read_tagged: read failed, block=256, location=256
[sam mar 10 20:28:08 2018] UDF-fs: error (device sda2): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0
[sam mar 10 20:28:08 2018] UDF-fs: error (device sda2): udf_read_tagged: read failed, block=512, location=512
[sam mar 10 20:28:08 2018] UDF-fs: error (device sda2): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0
[sam mar 10 20:28:08 2018] UDF-fs: error (device sda2): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0
[sam mar 10 20:28:08 2018] UDF-fs: warning (device sda2): udf_load_vrs: No anchor found
[sam mar 10 20:28:08 2018] UDF-fs: Rescanning with blocksize 2048
[sam mar 10 20:28:08 2018] UDF-fs: error (device sda2): udf_read_tagged: read failed, block=256, location=256
[sam mar 10 20:28:08 2018] UDF-fs: error (device sda2): udf_read_tagged: read failed, block=512, location=512
[sam mar 10 20:28:08 2018] UDF-fs: warning (device sda2): udf_load_vrs: No anchor found
[sam mar 10 20:28:08 2018] UDF-fs: warning (device sda2): udf_fill_super: No partition found (1)
[sam mar 10 20:28:08 2018] XFS (sda2): Invalid superblock magic number
[sam mar 10 20:28:08 2018] MINIX-fs: unable to read superblock
[sam mar 10 20:28:08 2018] attempt to access beyond end of device
[sam mar 10 20:28:08 2018] sda2: rw=2048, want=3, limit=2
[sam mar 10 20:28:08 2018] hfsplus: unable to find HFS+ superblock
[sam mar 10 20:28:08 2018] qnx4: no qnx4 filesystem (no root dir).
[sam mar 10 20:28:08 2018] ufs: You didn't specify the type of your ufs filesystem

mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...

>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[sam mar 10 20:28:08 2018] hfs: can't find a HFS filesystem on dev sda2
[sam mar 10 20:28:13 2018] REISERFS warning (device sda2): sh-2006 read_super_block: bread failed (dev sda2, block 8, size 1024)
[sam mar 10 20:28:13 2018] REISERFS warning (device sda2): sh-2006 read_super_block: bread failed (dev sda2, block 64, size 1024)
[sam mar 10 20:28:13 2018] REISERFS warning (device sda2): sh-2021 reiserfs_fill_super: can not find reiserfs on sda2
[sam mar 10 20:28:13 2018] EXT4-fs (sda2): unable to read superblock
[sam mar 10 20:28:13 2018] EXT4-fs (sda2): unable to read superblock
[sam mar 10 20:28:13 2018] EXT2-fs (sda2): error: unable to read superblock
[sam mar 10 20:28:13 2018] SQUASHFS error: squashfs_read_data failed to read block 0x0
[sam mar 10 20:28:13 2018] squashfs: SQUASHFS error: unable to read squashfs_super_block
[sam mar 10 20:28:13 2018] FAT-fs (sda2): bogus number of reserved sectors
[sam mar 10 20:28:13 2018] FAT-fs (sda2): Can't find a valid FAT filesystem
[sam mar 10 20:28:13 2018] FAT-fs (sda2): bogus number of reserved sectors
[sam mar 10 20:28:13 2018] FAT-fs (sda2): Can't find a valid FAT filesystem
[sam mar 10 20:28:13 2018] isofs_fill_super: bread failed, dev=sda2, iso_blknum=16, block=32
[sam mar 10 20:28:13 2018] UDF-fs: error (device sda2): udf_read_tagged: read failed, block=256, location=256
[sam mar 10 20:28:13 2018] UDF-fs: error (device sda2): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0
[sam mar 10 20:28:13 2018] UDF-fs: error (device sda2): udf_read_tagged: read failed, block=512, location=512
[sam mar 10 20:28:13 2018] UDF-fs: error (device sda2): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0
[sam mar 10 20:28:13 2018] UDF-fs: error (device sda2): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0
[sam mar 10 20:28:13 2018] UDF-fs: warning (device sda2): udf_load_vrs: No anchor found
[sam mar 10 20:28:13 2018] UDF-fs: Rescanning with blocksize 2048
[sam mar 10 20:28:13 2018] UDF-fs: error (device sda2): udf_read_tagged: read failed, block=256, location=256
[sam mar 10 20:28:13 2018] UDF-fs: error (device sda2): udf_read_tagged: read failed, block=512, location=512
[sam mar 10 20:28:13 2018] UDF-fs: warning (device sda2): udf_load_vrs: No anchor found
[sam mar 10 20:28:13 2018] UDF-fs: warning (device sda2): udf_fill_super: No partition found (1)
[sam mar 10 20:28:13 2018] XFS (sda2): Invalid superblock magic number
[sam mar 10 20:28:13 2018] MINIX-fs: unable to read superblock
[sam mar 10 20:28:13 2018] attempt to access beyond end of device
[sam mar 10 20:28:13 2018] sda2: rw=2048, want=3, limit=2
[sam mar 10 20:28:13 2018] hfsplus: unable to find HFS+ superblock
[sam mar 10 20:28:13 2018] qnx4: no qnx4 filesystem (no root dir).
[sam mar 10 20:28:13 2018] ufs: You didn't specify the type of your ufs filesystem

mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...

>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[sam mar 10 20:28:13 2018] hfs: can't find a HFS filesystem on dev sda2
root@mx1:/
# 
thx

Post Reply

Return to “MX Help”