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
User avatar
male
Forum Regular
Forum Regular
Posts: 230
Joined: Thu Jan 23, 2014 8:38 am

Re: edit update grub modif

#11 Post by male » Sat Mar 10, 2018 6:20 pm

Thank you for your patience! ;)
But I still don't understand your problem.

The output of dmesg affects your Partition sda2 and is irrelevant here.

So it's antiX17 (and not SliTaz) on sda6. Right?

If you can start antiX17 from the Grub menu of MX-16....
then what's your problem?
I understood that you left out the bootloader of antiX during the installation.


... and, I repeat, do not use the grub-customitzer. :exclamation:
Then I'm out of here!

Your turn
Male is the capital of the Maldives and its wonderful people.

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

Re: edit update grub modif

#12 Post by tradonal » Sun Mar 11, 2018 2:01 pm

;)
So it is antiX17 (and not SliTaz) on sda6.
sda6 is just a partition logic that I use to install a linux distribution to try it
I just formatted sda6 and install another distri to see if there would be any changes ...
it is devuan_jessie_1.0.0_i386 on sda6 now....
But I still do not understand your problem.
the modification of the directory /etc/grub.d/*
-) before I had

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 /etc/grub.d/
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
I thought it was because of this:
source of problem viewtopic.php?f=13&t=44301

but I found that it concerns grub-customizer:
https://answers.launchpad.net/grub-customizer/+faq/1355
The output of dmesg affects your Partition sda2 and is irrelevant here.
with this change to the grub.d directory, after using the update-grub or os-prober command, the dmesg output shows errors on dev sda2
-) sda2 is an extended partition

Code: Select all

root@mx1:/# parted /dev/sda p
Model: ATA IC25N060ATMR04-0 (scsi)
Disk /dev/sda: 60,0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type      File system     Flags
 1      1049kB  32,9GB  32,9GB  primary   ext4            boot
 2      32,9GB  60,0GB  27,1GB  extended
 5      32,9GB  35,0GB  2097MB  logical   linux-swap(v1)
 6      35,0GB  60,0GB  25,0GB  logical   ext4

root@mx1:/# 

Exemple:

launch my system at [dim mar 11 16:50:21 2018]
end [dim mar 11 16:51:55 2018]

Code: Select all

root@mx1:/
# dmesg -T
[dim mar 11 16:50:21 2018] Initializing cgroup subsys cpuset
[dim mar 11 16:50:21 2018] Initializing cgroup subsys cpu
[dim mar 11 16:50:21 2018] Initializing cgroup subsys cpuacct
[dim mar 11 16:50:21 2018] Linux version 3.16.0-4-586 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 Debian 3.16.51-3 (2017-12-13)
[dim mar 11 16:50:21 2018] e820: BIOS-provided physical RAM map:
***
**
*
[dim mar 11 16:51:55 2018] wlan0: associated
[dim mar 11 16:51:55 2018] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
launch os-prober at [dim mar 11 18:28:46 2018]

Code: Select all

root@mx1:/
# os-prober 
  No volume groups found
/dev/sda6:unknown Linux distribution:Linux:linux
root@mx1:/
launch dmesg just after

Code: Select all

root@mx1:/
# dmesg -T
[dim mar 11 18:28:46 2018] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[dim mar 11 18:28:46 2018] JFS: nTxBlock = 8192, nTxLock = 65536
[dim mar 11 18:28:46 2018] ntfs: driver 2.1.30 [Flags: R/W MODULE].
[dim mar 11 18:28:46 2018] QNX4 filesystem 0.2.3 registered.[dim mar 11 16:51:55 2018] wlan0: associated
[dim mar 11 18:28:47 2018] EXT4-fs (sda2): unable to read superblock
[dim mar 11 18:28:47 2018] EXT4-fs (sda2): unable to read superblock
[dim mar 11 18:28:47 2018] EXT4-fs (sda2): unable to read superblock
[dim mar 11 18:28:47 2018] XFS (sda2): Invalid superblock magic number
[dim mar 11 18:28:47 2018] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[dim mar 11 18:28:47 2018] FAT-fs (sda2): bogus number of reserved sectors
[dim mar 11 18:28:47 2018] FAT-fs (sda2): Can't find a valid FAT filesystem
[dim mar 11 18:28:47 2018] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[dim mar 11 18:28:47 2018] FAT-fs (sda2): bogus number of reserved sectors
[dim mar 11 18:28:47 2018] FAT-fs (sda2): Can't find a valid FAT filesystem
[dim mar 11 18:28:47 2018] MINIX-fs: unable to read superblock
[dim mar 11 18:28:47 2018] attempt to access beyond end of device
[dim mar 11 18:28:47 2018] sda2: rw=16, want=3, limit=2
[dim mar 11 18:28:47 2018] hfsplus: unable to find HFS+ superblock
[dim mar 11 18:28:47 2018] qnx4: no qnx4 filesystem (no root dir).
[dim mar 11 18:28:47 2018] 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
[dim mar 11 18:28:47 2018] hfs: can't find a HFS filesystem on dev sda2
root@mx1:/
# 

I think 50mounted-tests is involved

Code: Select all

root@mx1:/
# cat /var/log/syslog* |grep os-prober
Mar 11 18:28:46 mx1 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda2
Mar 11 18:28:47 mx1 os-prober: debug: /dev/sda5: is active swap
Mar 11 18:28:47 mx1 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda6
Mar 11 18:28:49 mx1 os-prober: debug: os detected by /usr/lib/os-probes/50mounted-tests
thx


EDIT 1:
disabling os-prober update-grub no longer generates an error
/etc/default/grub

Code: Select all

GRUB_DISABLE_OS_PROBER="true"

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

Re: edit update grub modif

#13 Post by male » Sun Mar 11, 2018 3:45 pm

Please don't be mad at me, but you're actually riding a dead horse! :p

sda2 is an extended partition. This does not have a file system! dmesg shows you the check of all file systems it knows.
Every Linuxer in the world who uses an extended part has this "error checking" of dmsg.
tradonal wrote:I just formatted sda6 and install another distri to see if there would be any changes ...
:lion:
It's nice for you to have already installed the third distribution on your "test partition" sda6. Certainly without bootloader. You have also shut down the os-prober of MX to get rid of your "error message".... Then how do they boot sda6?
tradonal wrote:but I found that it concerns grub-customizer:
This has already been answered by d_o in the 2nd post. But they claim to have never used the customitzer.
... and I thought you wanted to know how to get antiX17 displayed correctly in the Grub menu of MX-16....
Male is the capital of the Maldives and its wonderful people.

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

Re: edit update grub modif

#14 Post by tradonal » Thu Mar 15, 2018 4:27 pm

;)
I am French and use google translation.... :happy:
I'm not mad at you .....
I just tried to summarize to help you better understand my problem. ...:
While re-reading, it is true that the form of my message can appear as direct
:confused:
all that will follow is just for info
[align=center]beginning of the information[/align][/color]
sda2 is an extended partition. This does not have a file system! dmesg shows you the check of all file systems it knows.
Every Linuxer in the world who uses an extended part has this "error checking" of dmsg.
;) as you say for sda2 is without file system ... ok for me
I am not an expert, if I try to deduce like this .....
for the command update-grub
1)

Code: Select all

 When I boot my system, various scripts are run ....
so
-) dmesg does not show error files checking this is ok
2)

Code: Select all

execute the command update-grub reads the file  / etc / default / grub  and execute the shell-Scripts 30_os-prober of /etc/grub.d/
IF
GRUB_DISABLE_OS_PROBER = "false"
so
-) dmesg shows an error files checking on sda2
3)

Code: Select all

execute the command update-grub reads  the file / etc / default / grub  and [b]NOT[/b] execute the shell-Scripts 30_os-prober of /etc/grub.d/
IF
GRUB_DISABLE_OS_PROBER = "true"
so
-) dmesg does not show an error files checking on sda2
on the other hand, the os-prober command is bad
1)

Code: Select all

 execute the command os-prober 
-) dmesg shows an error files checking on sda2
exit of dmesg after the os-prober command

Code: Select all

[jeu mar 15 19:08:41 2018] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[jeu mar 15 19:08:41 2018] JFS: nTxBlock = 8192, nTxLock = 65536
[jeu mar 15 19:08:41 2018] ntfs: driver 2.1.30 [Flags: R/W MODULE].
[jeu mar 15 19:08:41 2018] QNX4 filesystem 0.2.3 registered.
[jeu mar 15 19:08:42 2018] EXT4-fs (sda2): unable to read superblock
[jeu mar 15 19:08:42 2018] EXT4-fs (sda2): unable to read superblock
[jeu mar 15 19:08:42 2018] EXT4-fs (sda2): unable to read superblock
[jeu mar 15 19:08:42 2018] XFS (sda2): Invalid superblock magic number
[jeu mar 15 19:08:42 2018] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[jeu mar 15 19:08:42 2018] FAT-fs (sda2): bogus number of reserved sectors
[jeu mar 15 19:08:42 2018] FAT-fs (sda2): Can't find a valid FAT filesystem
[jeu mar 15 19:08:42 2018] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[jeu mar 15 19:08:42 2018] FAT-fs (sda2): bogus number of reserved sectors
[jeu mar 15 19:08:42 2018] FAT-fs (sda2): Can't find a valid FAT filesystem
[jeu mar 15 19:08:42 2018] MINIX-fs: unable to read superblock
[jeu mar 15 19:08:42 2018] attempt to access beyond end of device
[jeu mar 15 19:08:42 2018] sda2: rw=16, want=3, limit=2
[jeu mar 15 19:08:42 2018] hfsplus: unable to find HFS+ superblock
[jeu mar 15 19:08:42 2018] qnx4: no qnx4 filesystem (no root dir).
[jeu mar 15 19:08:42 2018] 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
[jeu mar 15 19:08:42 2018] hfs: can't find a HFS filesystem on dev sda2
https://anonscm.debian.org/cgit/d-i/os- ... ree/README
It's nice for you to have already installed the third distribution on your "test partition" sda6. Certainly without bootloader. You have also shut down the os-prober of MX to get rid of your "error message".... Then how do they boot sda6?
I never install the boot manager proposed by the distrib when I install on sda6,
not on root partition and not on mbr and i use my personal config for ..... and normally my os-prober is disabled...
I had modified this entry myself and so normally the entry GRUB_DISABLE_OS_PROBER should have been "true" because I prefer to manage it with

-) entry in script 40_custom

Code: Select all

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
menuentry "Distribs lancées depuis leur fichier 'iso'" {
set root='hd0,msdos1'
configfile /isos/00_isoboot.cfg
}
-) on sda1 i have a directory for iso with a file 00_isoboot.cfg

Code: Select all

root@mx1:/
# ls  /isos/
00_isoboot.cfg                         CentOS-6.9-i386-minimal.iso
antiX-13.2_386-full.iso                CorePlus-current.iso
antiX-15-V_386-full.iso                devuan_jessie_1.0.0_i386_desktop-live.iso
antiX-17_386-base.iso                  lubuntu-17.10-desktop-i386.iso
bl-Deuterium-i386+NonPAE_20170429.iso  slitaz-rolling-core.iso
CentOS-6.9-i386-LiveDVD.iso            super_grub2_disk_hybrid_2.02s9.iso
root@mx1:/
Exemple:
-) first config of the file /isos/00_isoboot.cfg for boot on iso

Code: Select all

menuentry "devuan-live (i386)" {
set isofile="/isos/devuan_jessie_1.0.0_i386_desktop-live.iso"
loopback loop $isofile
linux (loop)/live/vmlinuz boot=live findiso=${isofile} username=devuan hooks=file:///lib/live/mount/medium/live/hooks/fix-lang.sh locales=fr_BE.UTF-8
initrd (loop)/live/initrd.img 
}
then reboot on menuentry for run iso
if
-) I install on sda6, then reboot on sda1 and modify the file 00_isoboot.cfg
with this:
-) perso config of the file /isos/00_isoboot.cfg

Code: Select all

menuentry "devuan (sur /dev/sda6)" {
insmod part_msdos
insmod ext2
set root='hd0,msdos6'
linux /vmlinuz root=/dev/sda6
initrd /initrd.img
}
menuentry "devuan vmlinuz (sur /dev/sda6)" {
insmod part_msdos
insmod ext2
set root='hd0,msdos6'
linux /boot/vmlinuz-3.16.0-4-686-pae root=/dev/sda6
initrd /boot/initrd.img-3.16.0-4-686-pae
}
with the update-grub command after re passing the entry
GRUB_DISABLE_OS_PROBER on true
there no more sda6 in the file grub.cfg, it's a good thing for me

Code: Select all

root@mx1:/
# grep msdos6 /boot/grub/grub.cfg 
root@mx1:/
my personal conclusion
with the modify directory of /etc/grub.d/ and surely other directory with file
viewtopic.php?p=437922#p437922
?? for update-grub: corruption an error in the shell scripts 30_os-prober from /etc/grub.d/*** ??
?? for os-prober: ????? :frown:
[align=center]end of the information[/align][/color]
? main questions ?
-) I do not want any more GRUB-customizer on my system, uninstall customizer
-) reinstall or repair grub or other in order to eliminate os-prober and update-grub errors
what do you recommend
thank you all for the time you give to help others

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

Re: edit update grub modif

#15 Post by male » Fri Mar 16, 2018 3:57 pm

tradonal wrote:I am French and use google translation....
Take this, it's definitely better than this google junk. ;)

I refer to the second part of your information about starting ISO's by Grub (because I stumbled across it myself and didn't understand why at first).

Unfortunately I can only serve this purpose with German explanations (please don't be angry, I have never used ubuntu in my Linux life, but they have an excellent wiki)
http://lab.ks.uni-freiburg.de/projects/ ... _von_GRUB2
https://wiki.ubuntuusers.de/GRUB_2/Skri ... ack-booten

That was my 40_custom, where I didn't get the ISO at the start.

Code: Select all

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
menuentry 'Chainload Mageia 7 (auf /dev/sda8)' {
	set root='hd0,msdos8'
	configfile /boot/grub2/grub.cfg
}
menuentry 'Kernel(4.9.35)MGA7 (auf /dev/sda8)' {
	set root='hd0,msdos8'
	linux /boot/vmlinuz-4.9.35-desktop-1.mga6 BOOT_IMAGE=linux root=UUID=aeac8153-a888-4389-b866-b1c72247c28a splash quiet noiswmd resume=UUID=045398f2-dfbc-4cc5-99c5-dca098051969 vga=788
	initrd /boot/initrd-4.9.35-desktop-1.mga6.img
}
menuentry 'Chainload Paint It Black - lxde (2016.1) (auf /dev/sda10)' {
	set root='hd0,msdos10'
	configfile /boot/grub/grub.cfg
}
menuentry 'Chainload 2017.1.0 patience (kde) (auf /dev/sda11)' {
	set root='hd0,msdos11'
	configfile /boot/grub/grub.cfg
}	
menuentry 'Chainload ROSA (lxqt) (auf /dev/sda7)' {
	set root='hd0,msdos7'
	configfile /boot/grub2/grub.cfg
}
menuentry 'Chainload antiX17 (auf /dev/sdb1)' {
	set root='hd1,msdos1'
	configfile /boot/grub/grub.cfg
}
menuentry 'loopback ISO-suduction-patience (auf /dev/sdb6)' {
	insmod loopback
	insmod iso9660
	insmod part_msdos
	insmod vfat
	insmod ext2
	search -n -f --set=root ${GRUB_LOOPBACK_ISO_FILE}
	loopback loop ${GRUB_LOOPBACK_ISO_FILE}
	linux (loop)/boot/vmlinuz0.amd boot=fll lang=de_DE tz=Europe/Berlin iso-scan/filename=${GRUB_LOOPBACK_ISO_FILE} ${GRUB_CMDLINE_LINUX_DEFAULT} quiet splash
	initrd (loop)/boot/initrd0.amd
}
the reason is
3. the script must not contain partitions that already exist with /etc/grub.d/10_linux or with the other scripts (see above).
In the computer I have two HDD. The ISO's are all located in a partition of sdb.
But since os-prober(a script! ;) ) already writes arch-linux on sdb5 to the
/boot/grub/grub.cfg
of the main bootloader on sda generated, the start of ISO by 40_custom could not work.

After creating the ISO entry from the 40_custom into a separate 42_myISO and adding /etc/default/grub to the entry

Code: Select all

export GRUB_LOOPBACK_ISO_FILE="/maui/maui-1703-64bit.iso"
42_meineISO

Code: Select all

#! /bin/sh -e
echo "Adding Live CD entry" >&2

 cat << EOF
menuentry 'loopback ISO-maui-plasma (auf /dev/sdb6)' {
	insmod loopback
	insmod iso9660
	insmod part_msdos
	insmod fat
	insmod ext2
	search -n -f --set=root ${GRUB_LOOPBACK_ISO_FILE}
	loopback loop ${GRUB_LOOPBACK_ISO_FILE}
	linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=${GRUB_LOOPBACK_ISO_FILE} quiet splash
	initrd (loop)/casper/initrd.lz
}
EOF

and running update-grub, I was able to start the ISO after the reboot.

Long story short...
you should see your

Code: Select all

menuentry "Distribs lancées depuis leur fichier 'iso'" {
set root='hd0,msdos1'
configfile /isos/00_isoboot.cfg
}
to /etc/grub.d/42_xxx laying

Then you can also install test distribution(s) with the Grub, the scripts
30_os-prober
memtest etc.
the right to execute (to avoid generating a large number of entries in the grub.cfg of your main bootloader)

Code: Select all

chmod -x 30_os-prober

In the meantime, however, I have abandoned it, because testing ISO's in QEMU is much easier, you don't have to edit configuration files of Grub all the time. :happy:
Last edited by male on Tue Mar 27, 2018 4:11 pm, edited 1 time in total.
Male is the capital of the Maldives and its wonderful people.

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

Re: edit update grub modif

#16 Post by tradonal » Mon Mar 19, 2018 3:47 pm

Unfortunately I can only serve this purpose with German explanations
You are german ;)
Danke für deine Antwort was mir beim Lernen von GRUB nützlich sein wird :happy:
https://debian-facile.org/viewtopic.php?id=18874
Das grundlegende Problem, das war Bearbeiten des Verzeichnisses /etc/grub.d/ ist gelöst ;)
Verantwortlich für diese Änderung war der GRUB Customizer
Das Verzeichnis /etc/grub.d/ ist jetzt gut

Code: Select all

root@mx1:/
# ls -la /etc/grub.d/
total 96
drwxr-xr-x   2 root root  4096 mar 18 22:36 .
drwxr-xr-x 154 root root 12288 mar 19 20:40 ..
-rwxr-xr-x   1 root root  9424 déc 14  2015 00_header
-rwxr-xr-x   1 root root  6058 déc 14  2015 05_debian_theme
-rwxr-xr-x   1 root root 12261 déc 14  2015 10_linux
-rwxr-xr-x   1 root root 11082 déc 14  2015 20_linux_xen
-rwxr-xr-x   1 root root  1570 avr 15  2017 20_memtest86+
-rwxr-xr-x   1 root root 11692 déc 14  2015 30_os-prober
-rwxr-xr-x   1 root root  1416 déc 14  2015 30_uefi-firmware
-rwxr-xr-x   1 root root   464 mar 18 22:36 40_custom
-rwxr-xr-x   1 root root   216 déc 14  2015 41_custom
-rwxr-xr-x   1 root root  3276 jan 24  2014 42_grml
-rw-r--r--   1 root root   483 déc 14  2015 README
root@mx1:/
# 
Ich gebe die Methode, die ich für die Reparatur verwendet habe, nachdem .....

Danke euch allen

En francais pour
You are german ;)
Danke für deine Antwort was mir beim Lernen von GRUB nützlich sein wird :happy:
https://debian-facile.org/viewtopic.php?id=18874
Das grundlegende Problem, das war Bearbeiten des Verzeichnisses /etc/grub.d/ ist gelöst ;)
Verantwortlich für diese Änderung war der GRUB Customizer
Das Verzeichnis /etc/grub.d/ ist jetzt gut

Ich gebe die Methode, die ich für die Reparatur verwendet habe, nachdem .....
-) Traduction:
Vous êtes allemand
Merci pour votre réponse qui me sera utile lors de l'apprentissage de GRUB: [URL] https://debian-facile.org/viewtopic.php?id=18874 [/ url]
Le problème de base qui était modification du répertoire /etc/grub.d/ est résolu
Le responsable de ce changement était Customizer GRUB
Le répertoire /etc/grub.d/ est maintenant bon

EDIT = strikeout][/strikeout
Je donnerai la méthode utilisée pour la réparation après .....

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

Re: [solved] edit update grub modif

#17 Post by tradonal » Fri Mar 30, 2018 12:29 pm

;)
I will give the method used for the repair after .....

before going further.
Without referring to the general topic, what about this ??
What can cause it's error ??

Code: Select all

# grep sda2 /var/log/*
/var/log/messages:Mar 30 17:49:54 mx1 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda2
$ dmesg -TxH
kern  :info  : [mar30 17:49] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
kern  :info  : [  +0,033567] JFS: nTxBlock = 8192, nTxLock = 65536
kern  :info  : [  +0,091604] ntfs: driver 2.1.30 [Flags: R/W MODULE].
kern  :info  : [  +0,094469] QNX4 filesystem 0.2.3 registered.
kern  :err   : [  +0,752623] EXT4-fs (sda2): unable to read superblock
kern  :err   : [  +0,003782] EXT4-fs (sda2): unable to read superblock
kern  :err   : [  +0,003846] EXT4-fs (sda2): unable to read superblock
kern  :warn  : [  +0,121701] XFS (sda2): Invalid superblock magic number
kern  :warn  : [  +0,015687] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
kern  :err   : [  +0,000244] FAT-fs (sda2): bogus number of reserved sectors
kern  :info  : [  +0,000007] FAT-fs (sda2): Can't find a valid FAT filesystem
kern  :warn  : [  +0,004688] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
kern  :err   : [  +0,000262] FAT-fs (sda2): bogus number of reserved sectors
kern  :info  : [  +0,000006] FAT-fs (sda2): Can't find a valid FAT filesystem
kern  :warn  : [  +0,011390] MINIX-fs: unable to read superblock
kern  :info  : [  +0,043969] attempt to access beyond end of device
kern  :info  : [  +0,000012] sda2: rw=16, want=3, limit=2
kern  :warn  : [  +0,000006] hfsplus: unable to find HFS+ superblock
kern  :err   : [  +0,004404] qnx4: no qnx4 filesystem (no root dir).
kern  :warn  : [  +0,003718] 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
kern  :warn  : [  +0,011335] hfs: can't find a HFS filesystem on dev sda2
with colors it's more beautiful

Code: Select all

$ dmesg -TxH
Image

thx ;)

EDIT
/var/log/messages:Mar 30 17:49:54 mx1 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda2

Post Reply

Return to “MX Help”