Démarrage en RAID5

bertaudmarc · Février 21, 2016, 9:42pm

Quelques questions dans le but de m’instruire …

Lors du démarrage d’une machine, le BIOS recherche sur le disque le mbr afin de booter le système.

Comment le BIOS fait-il lorsqu’il y a plusieurs disques en RAID5 ?

Quand on fait grub-install sur un disque, qu’est-ce qui est stocké dans le mbr ?

Comment sait-on qu’un disque a un mbr équippé pour démarrer l’OS ?

Finalement qui lance grub.cfg situé dans /boot/grub ?

PascalHambourg · Février 21, 2016, 9:42pm

D’abord, il faut distinguer deux cas de RAID :
a) le RAID matériel véritable ou même géré par le BIOS (“fake RAID”)
b) le RAID logiciel géré par le pilote md du noyau Linux et mdadm.

Dans le cas a), le BIOS gère le RAID et peut donc “voir” l’ensemble RAID comme un volume unique. GRUB accède au volume RAID comme s’il s’agissait d’un disque classique.

Dans le cas b), le BIOS et GRUB ne voient que les disques individuels. Le BIOS va examiner chaque disque dans l’ordre d’amorçage défini. Pour pouvoir amorcer le système quel que soit le disque manquant, il faut installer GRUB sur chaque disque.

Il fait pareil que sans RAID. Dans le cas a) il cherche le MBR sur le volume RAID, dans le cas b) il cherche le MBR sur chaque disque dans l’ordre d’amorçage défini.

C’est la “boot image”. C’est un petit programme de quelques centaines d’octets qui peut contenir dans le MBR. Son rôle est de charger le morceau suivant, la “core image” dont la taille est de quelques dizaines de kilo-octets et qui est est aussi installée par grub-install mais pas dans le MBR. Il y a trois emplacements possibles pour la “core image” :

sur un disque partitionné au format traditionnel MBR/MSDOS, dans l’espace non partitionné entre le MBR et la première partition, si cet espace est suffisant (typiquement 32 Kio avec l’ancienne géométrie CHS et 1 Mio avec l’adressage LBA qui est la norme actuelle) ;
sur un disque partitionné au nouveau format GPT, dans une partition de type “BIOS boot” de taille suffisante dédiée à cet effet ;
à défaut, dans un fichier [mono]/boot/grub/core.img[/mono] pour les anciennes versions de GRUB 2 jusqu’à Wheezy ou [mono]/boot/grub/i386-pc/core.img[/mono] pour la version actuelle de GRUB 2 depuis Jessie. Cette solution n’étant pas recommandée, il est nécessaire d’ajouter l’option [mono]-f[/mono] pour forcer [mono]grub-install[/mono]. A noter que ce fichier est créé même dans les deux cas précédents, ce qui permet de faire un chaînage multiboot depuis un autre GRUB.

Dans le cas du RAID logiciel, si /boot se trouve sur un volume RAID alors la core image ne peut y être installée car la boot image ne sait pas lire le RAID logiciel. Il faut donc soit installer la core image dans un des deux autres emplacements, ce qui est préférable, soit créer des partitions de boot simple (non RAID) sur chaque disque et synchroniser leur contenu, ce qui est contraignant.

On peut utiliser le script [mono]bootinfoscript[/mono] du paquet boot-info-script.
Mais j’ai l’impression qu’il fonctionne moins bien avec la version actuelle de GRUB 2 incluse dans Jessie.

C’est la core image, elle-même lancée par la boot image. La core image peut intégrer des pilotes pour lire divers systèmes de fichiers (ext2/3/4, btrfs, reiserfs, xfs, FAT, NTFS…), les ensembles RAID logiciels, les volumes logiques LVM… /boot peut donc être sur un ensemble RAID à condition que la core image puisse être installée en dehors.

Et maintenant sur les PC récents il n’y a plus seulement le BIOS mais aussi les firmwares UEFI qui ont un système d’amorçage complètement différent, non basé sur le MBR mais sur une partition spéciale dite “partition système EFI”.

bertaudmarc · Février 21, 2016, 9:42pm

Merci pour toutes ces explications.
Finalement peut-on tester si tout ce mécanisme est bien en place ?
Personnellement je suis en RAID5 software.

PascalHambourg · Février 21, 2016, 9:42pm

Pour tester tu débranches (ou désactives dans le BIOS) chaque disque tour à tour et tu vérifies que le menu de GRUB s’affiche à chaque fois.

bertaudmarc · Février 21, 2016, 9:42pm

J’ai pas mal de message d’erreurs pour la commande [quote]bootinfoscript[/quote]: qu’en penses-tu ?

[code] Boot Info Script 0.61 [1 April 2012]

============================= Boot Info Summary: ===============================

=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 135 for .
=> Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
for (myRaid5LVM-boot)/grub on this drive.
=> Grub2 (v1.99) is installed in the MBR of /dev/sdc and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 135 for .
=> Grub2 (v1.99) is installed in the MBR of /dev/sdd and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 135 for .

sda1: __________________________________________________________________________

File system:       linux_raid_member
Boot sector type:  Unknown
Boot sector info:

sdb1: __________________________________________________________________________

File system:       linux_raid_member
Boot sector type:  Unknown
Boot sector info:

sdc1: __________________________________________________________________________

File system:       linux_raid_member
Boot sector type:  -
Boot sector info:

sdd1: __________________________________________________________________________

File system:       linux_raid_member
Boot sector type:  -
Boot sector info:

myRaid5LVM-root’: ______________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 
Mounting failed:   mount: unknown filesystem type ''

myRaid5LVM-home’: ______________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 
Mounting failed:   mount: unknown filesystem type ''

mount: unknown filesystem type ‘’

myRaid5LVM-var’: _______________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 
Mounting failed:   mount: unknown filesystem type ''

mount: unknown filesystem type ''
mount: unknown filesystem type ‘’

myRaid5LVM-swap’: ______________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 
Mounting failed:   mount: unknown filesystem type ''

mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ‘’

myRaid5LVM-boot’: ______________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 
Mounting failed:   mount: unknown filesystem type ''

mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ‘’

myRaid5LVM-usr’: _______________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 
Mounting failed:   mount: unknown filesystem type ''

mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ‘’

myRaid5LVM-tmp’: _______________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 
Mounting failed:   mount: unknown filesystem type ''

mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ‘’

md/0: __________________________________________________________________________

File system:       LVM2_member
Boot sector type:  -
Boot sector info:

============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________

Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 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

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 2,048 3,907,029,167 3,907,027,120 fd Linux raid autodetect

Drive: sdb _____________________________________________________________________

Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 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

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdb1 2,048 3,907,029,167 3,907,027,120 fd Linux raid autodetect

Drive: sdc _____________________________________________________________________

Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 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

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdc1 2,048 3,907,029,167 3,907,027,120 fd Linux raid autodetect

Drive: sdd _____________________________________________________________________

Disk /dev/sdd: 1.8 TiB, 2000398934016 bytes, 3907029168 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

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdd1 2,048 3,907,029,167 3,907,027,120 fd Linux raid autodetect

“blkid” output: ________________________________________________________________

Device UUID TYPE LABEL

/dev/mapper/myRaid5LVM-boot f281476a-f381-46f0-98f5-3c616cd28701 ext4
/dev/mapper/myRaid5LVM-home 86fa07d6-7199-4b9a-8b7b-4da793ce7749 ext4
/dev/mapper/myRaid5LVM-root b995b247-32f5-47a1-88f6-692b316e1ea2 ext4
/dev/mapper/myRaid5LVM-tmp 8044ff4f-cfcd-4701-bd60-6132efd34427 ext4
/dev/mapper/myRaid5LVM-usr 9ad2244e-cbc7-4aa5-a1d1-2647497144ce ext4
/dev/mapper/myRaid5LVM-var 2b2b0297-1380-4667-b77c-4212286ac41a ext4
/dev/md0 rKmg66-HWhf-epBB-c8OU-08cY-6FGY-USEHPk LVM2_member
/dev/md/0 rKmg66-HWhf-epBB-c8OU-08cY-6FGY-USEHPk LVM2_member
/dev/sda1 0e4fffc2-9795-8953-205e-ae06f0edce09 linux_raid_member debian:0
/dev/sdb1 0e4fffc2-9795-8953-205e-ae06f0edce09 linux_raid_member debian:0
/dev/sdc1 0e4fffc2-9795-8953-205e-ae06f0edce09 linux_raid_member debian:0
/dev/sdd1 0e4fffc2-9795-8953-205e-ae06f0edce09 linux_raid_member debian:0
/dev/sr0 2014-04-10-15-34-00-0 iso9660 V1210

========================= “ls -R /dev/mapper/” output: =========================

/dev/mapper:
control
myRaid5LVM-boot
myRaid5LVM-home
myRaid5LVM-root
myRaid5LVM-swap
myRaid5LVM-tmp
myRaid5LVM-usr
myRaid5LVM-var

================================ Mount points: =================================

Device Mount_Point Type Options

/dev/mapper/myRaid5LVM-boot /boot ext4 (rw,relatime,errors=remount-ro,stripe=1536,data=ordered)
/dev/mapper/myRaid5LVM-home /home ext4 (rw,relatime,errors=remount-ro,stripe=384,data=ordered)
/dev/mapper/myRaid5LVM-root / ext4 (rw,relatime,errors=remount-ro,stripe=384,data=ordered)
/dev/mapper/myRaid5LVM-tmp /tmp ext4 (rw,relatime,errors=remount-ro,stripe=384,data=ordered)
/dev/mapper/myRaid5LVM-usr /usr ext4 (rw,relatime,errors=remount-ro,stripe=384,data=ordered)
/dev/mapper/myRaid5LVM-var /var ext4 (rw,relatime,errors=remount-ro,stripe=384,data=ordered)

======================== Unknown MBRs/Boot Sectors/etc: ========================

Unknown BootLoader on sda1

00000000 a4 81 00 00 a7 05 00 00 2a 96 23 51 1a 96 23 51 |….#Q…#Q|
00000010 5a 04 e0 4b 00 00 00 00 00 00 01 00 04 00 00 00 |Z…K…|
00000020 00 00 08 00 01 00 00 00 0a f3 01 00 04 00 00 00 |…|
00000030 00 00 00 00 00 00 00 00 02 00 00 00 e4 a4 01 00 |…|
00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |…|
*
00000060 00 00 00 00 6c f7 b2 96 00 00 00 00 00 00 00 00 |…l…|
00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |…|
00000080 a4 81 00 00 0a 35 00 00 2b 96 23 51 1a 96 23 51 |…5…+.#Q…#Q|
00000090 5a 04 e0 4b 00 00 00 00 00 00 01 00 1c 00 00 00 |Z…K…|
000000a0 00 00 08 00 01 00 00 00 0a f3 01 00 04 00 00 00 |…|
000000b0 00 00 00 00 00 00 00 00 0e 00 00 00 e6 a4 01 00 |…|
000000c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |…|
*
000000e0 00 00 00 00 6d f7 b2 96 00 00 00 00 00 00 00 00 |…m…|
000000f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |…|
00000100 a4 81 00 00 e1 08 00 00 2b 96 23 51 1a 96 23 51 |…+.#Q…#Q|
00000110 5a 04 e0 4b 00 00 00 00 00 00 01 00 06 00 00 00 |Z…K…|
00000120 00 00 08 00 01 00 00 00 0a f3 01 00 04 00 00 00 |…|
00000130 00 00 00 00 00 00 00 00 03 00 00 00 f4 a4 01 00 |…|
00000140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |…|
*
00000160 00 00 00 00 6e f7 b2 96 00 00 00 00 00 00 00 00 |…n…|
00000170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |…|
00000180 a4 81 00 00 64 07 00 00 2a 96 23 51 1a 96 23 51 |…d….#Q…#Q|
00000190 5a 04 e0 4b 00 00 00 00 00 00 01 00 04 00 00 00 |Z…K…|
000001a0 00 00 08 00 01 00 00 00 0a f3 01 00 04 00 00 00 |…|
000001b0 00 00 00 00 00 00 00 00 02 00 00 00 f7 a4 01 00 |…|
000001c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |…|
*
000001e0 00 00 00 00 6f f7 b2 96 00 00 00 00 00 00 00 00 |…o…|
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |…|
00000200

Unknown BootLoader on sdb1

00000000 a4 81 00 00 a7 05 00 00 2a 96 23 51 1a 96 23 51 |….#Q…#Q|
00000010 5a 04 e0 4b 00 00 00 00 00 00 01 00 04 00 00 00 |Z…K…|
00000020 00 00 08 00 01 00 00 00 0a f3 01 00 04 00 00 00 |…|
00000030 00 00 00 00 00 00 00 00 02 00 00 00 e4 a4 01 00 |…|
00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |…|
*
00000060 00 00 00 00 6c f7 b2 96 00 00 00 00 00 00 00 00 |…l…|
00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |…|
00000080 a4 81 00 00 0a 35 00 00 2b 96 23 51 1a 96 23 51 |…5…+.#Q…#Q|
00000090 5a 04 e0 4b 00 00 00 00 00 00 01 00 1c 00 00 00 |Z…K…|
000000a0 00 00 08 00 01 00 00 00 0a f3 01 00 04 00 00 00 |…|
000000b0 00 00 00 00 00 00 00 00 0e 00 00 00 e6 a4 01 00 |…|
000000c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |…|
*
000000e0 00 00 00 00 6d f7 b2 96 00 00 00 00 00 00 00 00 |…m…|
000000f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |…|
00000100 a4 81 00 00 e1 08 00 00 2b 96 23 51 1a 96 23 51 |…+.#Q…#Q|
00000110 5a 04 e0 4b 00 00 00 00 00 00 01 00 06 00 00 00 |Z…K…|
00000120 00 00 08 00 01 00 00 00 0a f3 01 00 04 00 00 00 |…|
00000130 00 00 00 00 00 00 00 00 03 00 00 00 f4 a4 01 00 |…|
00000140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |…|
*
00000160 00 00 00 00 6e f7 b2 96 00 00 00 00 00 00 00 00 |…n…|
00000170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |…|
00000180 a4 81 00 00 64 07 00 00 2a 96 23 51 1a 96 23 51 |…d….#Q…#Q|
00000190 5a 04 e0 4b 00 00 00 00 00 00 01 00 04 00 00 00 |Z…K…|
000001a0 00 00 08 00 01 00 00 00 0a f3 01 00 04 00 00 00 |…|
000001b0 00 00 00 00 00 00 00 00 02 00 00 00 f7 a4 01 00 |…|
000001c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |…|
*
000001e0 00 00 00 00 6f f7 b2 96 00 00 00 00 00 00 00 00 |…o…|
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |…|
00000200

Unknown BootLoader on myRaid5LVM-root’

Unknown BootLoader on myRaid5LVM-home’

Unknown BootLoader on myRaid5LVM-var’

Unknown BootLoader on myRaid5LVM-swap’

Unknown BootLoader on myRaid5LVM-boot’

Unknown BootLoader on myRaid5LVM-usr’

Unknown BootLoader on myRaid5LVM-tmp’

=============================== StdErr Messages: ===============================

xz: (stdin): Compressed data is corrupt
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
hexdump: /dev/mapper/myRaid5LVM-root’: No such file or directory
hexdump: /dev/mapper/myRaid5LVM-root’: No such file or directory
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
hexdump: /dev/mapper/myRaid5LVM-home’: No such file or directory
hexdump: /dev/mapper/myRaid5LVM-home’: No such file or directory
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
hexdump: /dev/mapper/myRaid5LVM-var’: No such file or directory
hexdump: /dev/mapper/myRaid5LVM-var’: No such file or directory
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
hexdump: /dev/mapper/myRaid5LVM-swap’: No such file or directory
hexdump: /dev/mapper/myRaid5LVM-swap’: No such file or directory
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
hexdump: /dev/mapper/myRaid5LVM-boot’: No such file or directory
hexdump: /dev/mapper/myRaid5LVM-boot’: No such file or directory
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
hexdump: /dev/mapper/myRaid5LVM-usr’: No such file or directory
hexdump: /dev/mapper/myRaid5LVM-usr’: No such file or directory
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
One or more specified logical volume(s) not found.
hexdump: /dev/mapper/myRaid5LVM-tmp’: No such file or directory
hexdump: /dev/mapper/myRaid5LVM-tmp’: No such file or directory
[/code]

PascalHambourg · Février 21, 2016, 9:42pm

Les erreurs concernant les volumes logiques LVM proviennent d’un bug de bootinfoscript pour l’extraction des noms des volumes, qui laisse une apostophe [mono]’[/mono] à la fin du nom comme on peut le voir. Je l’ai corrigé à la va-vite sur une de mes machines, mais je ne l’ai pas sous la main. Ce n’est pas capital.

On voit qu’une boot image de GRUB est présente dans le MBR des 4 disques, ainsi qu’une core image installée dans l’espace après le MBR.

Le texte “[mono]looks in partition 135 for .[/mono]” pour 3 des 4 disques, qui est manifestement erroné mais que je retrouve systématiquement avec le GRUB de Jessie, est ce qui me faisait écrire plus haut que le bootinfoscript ne semble pas être capable d’extraire la localisation du répertoire /grub (/boot/grub) dans la core image de la version actuelle de GRUB.

Etonnamment, bootinfoscript a trouvé que la core image installée sur le disque /dev/sdb recherche le répertoire /grub sur le LV myRaid5LVM-boot. Mais le paragraphe précédent qui dit que cela ne devrait pas être le cas, combiné au fait que mono[/mono] est une ancienne syntaxe des versions précédentes de GRUB (jusqu’à Wheezy), l’actuelle étant mono[/mono] ou mono[/mono], me laisse penser que c’est un ancien GRUB qui se trouve sur /dev/sdb. Si j’ai raison, il se pourrait que cette ancien GRUB ne soit pas capable d’interpréter correctement le fichier de configuration grub.cfg créé pour une version plus récente de GRUB.

As-tu bien exécuté [mono]grub-install /dev/sd[/mono] sur chaque disque y compris /dev/sdb ?

bertaudmarc · Février 21, 2016, 9:43pm

Belle analyse.
Oui je pense avoir fait grub-install sur tous les disques. Rien n’empêche de le refaire ou bien ?

PascalHambourg · Février 21, 2016, 9:43pm

Dans le doute, rien n’empêche de le refaire.

bertaudmarc · Février 21, 2016, 9:43pm

C’est fait: je ne vois pas de différence …

[code] Boot Info Script 0.61 [1 April 2012]

============================= Boot Info Summary: ===============================

=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 135 for .
=> Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 135 for .
=> Grub2 (v1.99) is installed in the MBR of /dev/sdc and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 135 for .
=> Grub2 (v1.99) is installed in the MBR of /dev/sdd and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 135 for .

sda1: __________________________________________________________________________

File system:       linux_raid_member
Boot sector type:  Unknown
Boot sector info:

sdb1: __________________________________________________________________________

File system:       linux_raid_member
Boot sector type:  Unknown
Boot sector info:

sdc1: __________________________________________________________________________

File system:       linux_raid_member
Boot sector type:  -
Boot sector info:

sdd1: __________________________________________________________________________

File system:       linux_raid_member
Boot sector type:  -
Boot sector info:

myRaid5LVM-root’: ______________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 
Mounting failed:   mount: unknown filesystem type ''

myRaid5LVM-home’: ______________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 
Mounting failed:   mount: unknown filesystem type ''

mount: unknown filesystem type ‘’

myRaid5LVM-var’: _______________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 
Mounting failed:   mount: unknown filesystem type ''

mount: unknown filesystem type ''
mount: unknown filesystem type ‘’

myRaid5LVM-swap’: ______________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 
Mounting failed:   mount: unknown filesystem type ''

mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ‘’

myRaid5LVM-boot’: ______________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 
Mounting failed:   mount: unknown filesystem type ''

mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ‘’

myRaid5LVM-usr’: _______________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 
Mounting failed:   mount: unknown filesystem type ''

mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ‘’

myRaid5LVM-tmp’: _______________________________________________________________

File system:       
Boot sector type:  Unknown
Boot sector info: 
Mounting failed:   mount: unknown filesystem type ''

mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ''
mount: unknown filesystem type ‘’

md/0: __________________________________________________________________________

File system:       LVM2_member
Boot sector type:  -
Boot sector info: