Re: Le système essaye de monter les partitions étendues

[Pascal Hambourg <pascal@plouf.fr.eu.org>]

Le 30/10/2018 à 14:56, Artur a écrit :
> /proc/mdstat
> Personalities : [raid1]
> md7 : active raid1 sda7[0] sdb7[1]
>        12187584 blocks [2/2] [UU]
> md6 : active raid1 sda6[0] sdb6[1]
>        935798720 blocks [2/2] [UU]
> md5 : active raid1 sda5[0] sdb5[1]
>        10238912 blocks [2/2] [UU]
> md3 : active raid1 sda3[0] sdb3[1]
>        10238912 blocks [2/2] [UU]
> md1 : active raid1 sda1[0] sdb1[1]
>        4094912 blocks [2/2] [UU]
> unused devices: <none>
>
> Et les swaps sont sur :
>
> /proc/swaps
> Filename                                Type            Size    Used
> Priority
> /dev/sdb2                               partition       4193276 0       -1
> /dev/sda2                               partition       4193276 0       -2
>
> Tout ça est très bien.

Je ne suis pas de cet avis.
1) 5 ensemble RAID distincts de même niveau sur la même grappe de 
disques, c'est inutilement lourd. En cas de remplacement d'un disque 
défaillant, il faut reconstruire tous les ensembles un par un. J'aurais 
plutôt créé un seul ensemble RAID partitionné ou utilisé comme volume 
physique LVM.

2) Le swap n'est pas en RAID, donc si un disque tombe, le swap tombe et 
le système risque de tomber avec. Rappelez-moi à quoi sert le RAID ? Il 
fournit de la disponibilité. Si le système tombe quand un disque tombe, 
tu parles d'une disponibilité.

> Il reste que je viens de jeter un oeil sur dmesg
> et je vois que le kernel essaye de monter ce qui correspond aux
> partitions étendues de chaque disque, soit sda4 et sdb4 :
>
> [   61.358348] EXT4-fs (sda4): unable to read superblock
> [   61.360061] EXT4-fs (sda4): unable to read superblock
> [   61.361725] EXT4-fs (sda4): unable to read superblock
> [   61.364113] XFS (sda4): Invalid superblock magic number
> [   61.368094] FAT-fs (sda4): utf8 is not a recommended IO charset for
> FAT filesystems, filesystem will be case sensitive!
> [   61.368337] FAT-fs (sda4): bogus number of reserved sectors
> [   61.368371] FAT-fs (sda4): Can't find a valid FAT filesystem
> [   61.369991] FAT-fs (sda4): utf8 is not a recommended IO charset for
> FAT filesystems, filesystem will be case sensitive!
> [   61.370216] FAT-fs (sda4): bogus number of reserved sectors
> [   61.370250] FAT-fs (sda4): Can't find a valid FAT filesystem
> [   61.376567] ntfs: (device sda4): read_ntfs_boot_sector(): Primary
> boot sector is invalid.
> [   61.376614] ntfs: (device sda4): read_ntfs_boot_sector(): Mount
> option errors=recover not used. Aborting without trying to recover.
> [   61.376671] ntfs: (device sda4): ntfs_fill_super(): Not an NTFS volume.
> [   61.378267] MINIX-fs: unable to read superblock
> [   61.379760] attempt to access beyond end of device
> [   61.379765] sda4: rw=16, want=3, limit=2
> [   61.379767] hfsplus: unable to find HFS+ superblock
> [   61.381526] qnx4: no qnx4 filesystem (no root dir).
> [   61.383130] 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
> [   61.386033] hfs: can't find a HFS filesystem on dev sda4
(...)
> Une idée pourquoi le système essaye de monter sda4/sdb4 ? Comment
> l’empêcher ?

Ça ressemble à ce qui se passe lorsque os-prober (généralement invoqué 
par grub-mkconfig lui même invoqué par update-grub) essaie de monter une 
partition de type inconnu à la recherche d'autres systèmes :
====
[ 2981.616457] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
[ 2981.655305] JFS: nTxBlock = 8050, nTxLock = 64404
[ 2981.745612] ntfs: driver 2.1.30 [Flags: R/W MODULE].
[ 2981.842744] QNX4 filesystem 0.2.3 registered.
[ 2982.948469] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 2982.950223] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 2982.951916] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 2983.006889] XFS (sda1): Invalid superblock magic number
[ 2983.019240] FAT-fs (sda1): utf8 is not a recommended IO charset for 
FAT filesystems, filesystem will be case sensitive!
[ 2983.019463] FAT-fs (sda1): invalid media value (0x7d)
[ 2983.019469] FAT-fs (sda1): Can't find a valid FAT filesystem
[ 2983.022505] FAT-fs (sda1): utf8 is not a recommended IO charset for 
FAT filesystems, filesystem will be case sensitive!
[ 2983.022741] FAT-fs (sda1): invalid media value (0x7d)
[ 2983.022747] FAT-fs (sda1): Can't find a valid FAT filesystem
[ 2983.031531] VFS: Can't find a Minix filesystem V1 | V2 | V3 on device 
sda1.
[ 2983.053425] hfsplus: unable to find HFS+ superblock
[ 2983.057595] qnx4: no qnx4 filesystem (no root dir).
[ 2983.061990] 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
[ 2983.062505] ufs_read_super: bad magic number
[ 2983.066970] hfs: can't find a HFS filesystem on dev sda1

Ici sda1 est une partition "BIOS boot" (GPT) ne contenant aucun système 
de fichiers.