Contenu | Rechercher | Menus

Annonce

Ubuntu-fr vend de superbes t-shirts et de belles clés USB 32Go
Rendez-vous sur la boutique En Vente Libre

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

#1 Le 03/09/2019, à 15:39

kookie68

Passer de 16.04 à 18.04 sur une machine en raid 5

Bonjour à tous,
j'envisage depuis un moment de passer de la 16.04 à la 18.04 mais comme je suis actuellement en raid 1, je me pose des questions sur les différentes possibilités de le faire :
- soit je fais un upgrade depuis la 16.04, mais je n'aime pas trop cette solution, car il reste toujours des restes de configuration de l'ancienne version.
- soit je réinstalle une nouvelle copie de la 18.04 pour repartir proprement pour quelques années.

Je penche très nettement pour la deuxième solution, mais que deviendra mon raid existant ? Faudra t-il le réinstaller avec mdadm ou sera t-il reconnu dès le début de l'installation ?

Merci pour vos éclaircissements éclairés smile

Dernière modification par kookie68 (Le 18/09/2019, à 14:53)

Hors ligne

#2 Le 09/09/2019, à 09:00

kookie68

Re : Passer de 16.04 à 18.04 sur une machine en raid 5

Personne n'a l'ombre du début d'une petite idée ?

Hors ligne

#3 Le 09/09/2019, à 13:00

geole

Re : Passer de 16.04 à 18.04 sur une machine en raid 5

Bonjour

Premier cas:   Ton RAIDS1 est utilisé pour y mettre le logiciel UBUNTU.
                               => une installation standard de la version ne propose pas d'installer sur le RAIDS, Je pens qu'il faut   préparer une installation contenant le logiciel MDADM

Second cas:    Ton RAIDS1 est utilisé pour gérer uniquement tes données personnelles.
                         => L'installation standard ne l'utilise pas.
Apres l'installation faite, il suffit  que tu lances le nouvel ubuntu , que tu installes le logiciel  MDADM, que tu fabriques un point de montage et que tu lances la commande

sudo mount   /dev/mdNNNN   /PointdeMontage

pour retrouver l'accès aux données.
          Mais cela, c'est  en théorie.   (vérifiée entre un passage 18.04  et 19.10) car je me souviens que le format EXT4    n'est pas  exactement le même entre la version 16.04 et la version 18.04.     Je ne sais pas si le format de l'enveloppe RAIDS a été impacté.   Cependant on peut penser  que l'ancien format reste compatible.

Le plus simple est que tu lances ton installation en technique DUAL-BOOT. Ce qui te permettra d'avoir la version 16.04 opérationnelle avec ton RAID1 et la version 18.04 dans laquelle tu  installeras MDADM et tu tenteras de monter le RAIDS.
Si le montage est refusé, tu ne bricoles rien avec MDADM et tu attends l'arrivée d'un spécialiste

Dernière modification par geole (Le 09/09/2019, à 13:05)

Hors ligne

#4 Le 12/09/2019, à 16:13

kookie68

Re : Passer de 16.04 à 18.04 sur une machine en raid 5

Merci pour ces premiers éléments. Je vais donc attendre l'arrivée d'un spécialiste.:)

Hors ligne

#5 Le 12/09/2019, à 17:37

geole

Re : Passer de 16.04 à 18.04 sur une machine en raid 5

Bonjour
Il faudrait quand même que tu fournisses un boot-info afin de montrer comment ton installation est faite. https://doc.ubuntu-fr.org/tutoriel/boot-info

Hors ligne

#6 Le 14/09/2019, à 07:47

kookie68

Re : Passer de 16.04 à 18.04 sur une machine en raid 5

Tu as raison, j'aurais pu commencer par là. Le voici, le voilà :

http://paste.ubuntu.com/p/GKmpQwmkCb/

Hors ligne

#7 Le 14/09/2019, à 08:28

xubu1957

Re : Passer de 16.04 à 18.04 sur une machine en raid 5

Bonjour,

Collage du Boot-Info :

Boot Info Script 8f991e4 + Boot-Repair extra info      [Boot-Info 25oct2017]


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

 => Grub2 (v2.00) 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 
    for (mduuid/3d03224e6fb008f32bd915d061b1c368)/boot/grub. It also embeds 
    following components:
    
    modules
    ---------------------------------------------------------------------------
    fshelp ext2 part_msdos diskfilter mdraid1x raid5rec biosdisk
    ---------------------------------------------------------------------------
 => Grub2 (v2.00) 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 (mduuid/3d03224e6fb008f32bd915d061b1c368)/boot/grub. It also embeds 
    following components:
    
    modules
    ---------------------------------------------------------------------------
    fshelp ext2 part_msdos diskfilter mdraid1x raid5rec biosdisk
    ---------------------------------------------------------------------------
 => Grub2 (v2.00) 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 
    for (mduuid/3d03224e6fb008f32bd915d061b1c368)/boot/grub. It also embeds 
    following components:
    
    modules
    ---------------------------------------------------------------------------
    fshelp ext2 part_msdos diskfilter mdraid1x raid5rec biosdisk
    ---------------------------------------------------------------------------

sda1: __________________________________________________________________________

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

sda2: __________________________________________________________________________

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

sda3: __________________________________________________________________________

    File system:       Extended Partition
    Boot sector type:  -
    Boot sector info: 

sda5: __________________________________________________________________________

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

sda4: __________________________________________________________________________

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

sdb1: __________________________________________________________________________

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

sdb2: __________________________________________________________________________

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

sdb3: __________________________________________________________________________

    File system:       Extended Partition
    Boot sector type:  -
    Boot sector info: 

sdb5: __________________________________________________________________________

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

sdb4: __________________________________________________________________________

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

sdc1: __________________________________________________________________________

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

sdc2: __________________________________________________________________________

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

sdc3: __________________________________________________________________________

    File system:       Extended Partition
    Boot sector type:  -
    Boot sector info: 

sdc5: __________________________________________________________________________

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

sdc4: __________________________________________________________________________

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

md/2: __________________________________________________________________________

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

md/0: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Mounting failed:   mount: /dev/md0 is already mounted or /mnt/BootInfo/MDRaid/md/0 busy
       /dev/md0 is already mounted on /

md/3: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  FAT32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Mounting failed:   mount: /dev/md0 is already mounted or /mnt/BootInfo/MDRaid/md/0 busy
       /dev/md0 is already mounted on /
mount: /dev/md3 is already mounted or /mnt/BootInfo/MDRaid/md/3 busy
       /dev/md3 is already mounted on /windows

md/1: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Mounting failed:   mount: /dev/md0 is already mounted or /mnt/BootInfo/MDRaid/md/0 busy
       /dev/md0 is already mounted on /
mount: /dev/md3 is already mounted or /mnt/BootInfo/MDRaid/md/3 busy
       /dev/md3 is already mounted on /windows
mount: /dev/md1 is already mounted or /mnt/BootInfo/MDRaid/md/1 busy
       /dev/md1 is already mounted on /home

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

Drive: sda _____________________________________________________________________
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sda1    *          2,048    68,360,191    68,358,144  fd Linux raid autodetect
/dev/sda2          68,360,192 1,904,297,983 1,835,937,792  fd Linux raid autodetect
/dev/sda3       1,904,300,030 1,935,548,415    31,248,386   5 Extended
/dev/sda5       1,904,300,032 1,935,548,415    31,248,384  fd Linux raid autodetect
/dev/sda4       1,935,548,416 1,953,523,711    17,975,296  fd Linux raid autodetect


Drive: sdb _____________________________________________________________________
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sdb1    *          2,048    68,360,191    68,358,144  fd Linux raid autodetect
/dev/sdb2          68,360,192 1,904,297,983 1,835,937,792  fd Linux raid autodetect
/dev/sdb3       1,904,300,030 1,935,548,415    31,248,386   5 Extended
/dev/sdb5       1,904,300,032 1,935,548,415    31,248,384  fd Linux raid autodetect
/dev/sdb4       1,935,548,416 1,953,523,711    17,975,296  fd Linux raid autodetect


Drive: sdc _____________________________________________________________________
Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sdc1    *          2,048    68,360,191    68,358,144  fd Linux raid autodetect
/dev/sdc2          68,360,192 1,904,297,983 1,835,937,792  fd Linux raid autodetect
/dev/sdc3       1,904,300,030 1,935,548,415    31,248,386   5 Extended
/dev/sdc5       1,904,300,032 1,935,548,415    31,248,384  fd Linux raid autodetect
/dev/sdc4       1,935,548,416 1,953,523,711    17,975,296  fd Linux raid autodetect


"blkid" output: ________________________________________________________________

Device           UUID                                   TYPE       LABEL

/dev/loop0                                              squashfs   
/dev/loop1                                              squashfs   
/dev/loop2                                              squashfs   
/dev/loop3                                              squashfs   
/dev/md/0        4e0631f7-d7d2-4435-88c8-e7254a9a2ba2   ext4       
/dev/md/1        b5b23e5c-d55c-4246-85b2-72bb1477cea7   ext4       
/dev/md/2        baeadf1d-9675-436d-99f8-adf133170401   swap       
/dev/md/3        AD82-EC2E                              vfat       
/dev/md0         4e0631f7-d7d2-4435-88c8-e7254a9a2ba2   ext4       
/dev/md1         b5b23e5c-d55c-4246-85b2-72bb1477cea7   ext4       
/dev/md2         baeadf1d-9675-436d-99f8-adf133170401   swap       
/dev/md3         AD82-EC2E                              vfat       
/dev/sda1        3d03224e-6fb0-08f3-2bd9-15d061b1c368   linux_raid_member kookie-PC:0
/dev/sda2        1b1866aa-e551-b458-e05d-c7cb6b840b66   linux_raid_member kookie-PC:1
/dev/sda4        9896c602-dc58-5c50-8206-6b4da3be179a   linux_raid_member kookie-PC:3
/dev/sda5        1963022c-7be5-e3f9-be84-6ce8d83cebaf   linux_raid_member kookie-PC:2
/dev/sdb1        3d03224e-6fb0-08f3-2bd9-15d061b1c368   linux_raid_member kookie-PC:0
/dev/sdb2        1b1866aa-e551-b458-e05d-c7cb6b840b66   linux_raid_member kookie-PC:1
/dev/sdb4        9896c602-dc58-5c50-8206-6b4da3be179a   linux_raid_member kookie-PC:3
/dev/sdb5        1963022c-7be5-e3f9-be84-6ce8d83cebaf   linux_raid_member kookie-PC:2
/dev/sdc1        3d03224e-6fb0-08f3-2bd9-15d061b1c368   linux_raid_member kookie-PC:0
/dev/sdc2        1b1866aa-e551-b458-e05d-c7cb6b840b66   linux_raid_member kookie-PC:1
/dev/sdc4        9896c602-dc58-5c50-8206-6b4da3be179a   linux_raid_member kookie-PC:3
/dev/sdc5        1963022c-7be5-e3f9-be84-6ce8d83cebaf   linux_raid_member kookie-PC:2

========================= "ls -l /dev/disk/by-id" output: ======================

total 0
lrwxrwxrwx 1 root root  9 Sep 12 08:28 ata-ATAPI_iHAS124_E_3524703_2C8445501338 -> ../../sr0
lrwxrwxrwx 1 root root  9 Sep 14 08:42 ata-WDC_WD10EZEX-00BN5A0_WD-WCC3FJ0Z7R9N -> ../../sdb
lrwxrwxrwx 1 root root 10 Sep 14 08:42 ata-WDC_WD10EZEX-00BN5A0_WD-WCC3FJ0Z7R9N-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Sep 14 08:42 ata-WDC_WD10EZEX-00BN5A0_WD-WCC3FJ0Z7R9N-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Sep 14 08:42 ata-WDC_WD10EZEX-00BN5A0_WD-WCC3FJ0Z7R9N-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 10 Sep 14 08:42 ata-WDC_WD10EZEX-00BN5A0_WD-WCC3FJ0Z7R9N-part4 -> ../../sdb4
lrwxrwxrwx 1 root root 10 Sep 14 08:42 ata-WDC_WD10EZEX-00BN5A0_WD-WCC3FJ0Z7R9N-part5 -> ../../sdb5
lrwxrwxrwx 1 root root  9 Sep 14 08:42 ata-WDC_WD10EZEX-00BN5A0_WD-WCC3FN3RJ832 -> ../../sda
lrwxrwxrwx 1 root root 10 Sep 14 08:42 ata-WDC_WD10EZEX-00BN5A0_WD-WCC3FN3RJ832-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Sep 14 08:42 ata-WDC_WD10EZEX-00BN5A0_WD-WCC3FN3RJ832-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Sep 14 08:42 ata-WDC_WD10EZEX-00BN5A0_WD-WCC3FN3RJ832-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Sep 14 08:42 ata-WDC_WD10EZEX-00BN5A0_WD-WCC3FN3RJ832-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Sep 14 08:42 ata-WDC_WD10EZEX-00BN5A0_WD-WCC3FN3RJ832-part5 -> ../../sda5
lrwxrwxrwx 1 root root  9 Sep 14 08:42 ata-WDC_WD10EZEX-08WN4A0_WD-WCC6Y5EVKYJZ -> ../../sdc
lrwxrwxrwx 1 root root 10 Sep 14 08:42 ata-WDC_WD10EZEX-08WN4A0_WD-WCC6Y5EVKYJZ-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Sep 14 08:42 ata-WDC_WD10EZEX-08WN4A0_WD-WCC6Y5EVKYJZ-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Sep 14 08:42 ata-WDC_WD10EZEX-08WN4A0_WD-WCC6Y5EVKYJZ-part3 -> ../../sdc3
lrwxrwxrwx 1 root root 10 Sep 14 08:42 ata-WDC_WD10EZEX-08WN4A0_WD-WCC6Y5EVKYJZ-part4 -> ../../sdc4
lrwxrwxrwx 1 root root 10 Sep 14 08:42 ata-WDC_WD10EZEX-08WN4A0_WD-WCC6Y5EVKYJZ-part5 -> ../../sdc5
lrwxrwxrwx 1 root root  9 Sep 14 08:42 md-name-kookie-PC:0 -> ../../md0
lrwxrwxrwx 1 root root  9 Sep 14 08:42 md-name-kookie-PC:1 -> ../../md1
lrwxrwxrwx 1 root root  9 Sep 14 08:42 md-name-kookie-PC:2 -> ../../md2
lrwxrwxrwx 1 root root  9 Sep 14 08:42 md-name-kookie-PC:3 -> ../../md3
lrwxrwxrwx 1 root root  9 Sep 14 08:42 md-uuid-1963022c:7be5e3f9:be846ce8:d83cebaf -> ../../md2
lrwxrwxrwx 1 root root  9 Sep 14 08:42 md-uuid-1b1866aa:e551b458:e05dc7cb:6b840b66 -> ../../md1
lrwxrwxrwx 1 root root  9 Sep 14 08:42 md-uuid-3d03224e:6fb008f3:2bd915d0:61b1c368 -> ../../md0
lrwxrwxrwx 1 root root  9 Sep 14 08:42 md-uuid-9896c602:dc585c50:82066b4d:a3be179a -> ../../md3
lrwxrwxrwx 1 root root  9 Sep 14 08:42 wwn-0x50014ee25fc9946c -> ../../sdb
lrwxrwxrwx 1 root root 10 Sep 14 08:42 wwn-0x50014ee25fc9946c-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Sep 14 08:42 wwn-0x50014ee25fc9946c-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Sep 14 08:42 wwn-0x50014ee25fc9946c-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 10 Sep 14 08:42 wwn-0x50014ee25fc9946c-part4 -> ../../sdb4
lrwxrwxrwx 1 root root 10 Sep 14 08:42 wwn-0x50014ee25fc9946c-part5 -> ../../sdb5
lrwxrwxrwx 1 root root  9 Sep 14 08:42 wwn-0x50014ee2b51f5916 -> ../../sda
lrwxrwxrwx 1 root root 10 Sep 14 08:42 wwn-0x50014ee2b51f5916-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Sep 14 08:42 wwn-0x50014ee2b51f5916-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Sep 14 08:42 wwn-0x50014ee2b51f5916-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Sep 14 08:42 wwn-0x50014ee2b51f5916-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Sep 14 08:42 wwn-0x50014ee2b51f5916-part5 -> ../../sda5
lrwxrwxrwx 1 root root  9 Sep 14 08:42 wwn-0x50014ee2b8ded60b -> ../../sdc
lrwxrwxrwx 1 root root 10 Sep 14 08:42 wwn-0x50014ee2b8ded60b-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Sep 14 08:42 wwn-0x50014ee2b8ded60b-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Sep 14 08:42 wwn-0x50014ee2b8ded60b-part3 -> ../../sdc3
lrwxrwxrwx 1 root root 10 Sep 14 08:42 wwn-0x50014ee2b8ded60b-part4 -> ../../sdc4
lrwxrwxrwx 1 root root 10 Sep 14 08:42 wwn-0x50014ee2b8ded60b-part5 -> ../../sdc5

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

Device           Mount_Point              Type       Options

/dev/md0         /                        ext4       (rw,relatime,errors=remount-ro,stripe=256,data=ordered)
/dev/md1         /home                    ext4       (rw,relatime,stripe=256,data=ordered)
/dev/md3         /windows                 vfat       (rw,relatime,gid=46,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)


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

File descriptor 9 (/proc/6935/mounts) leaked on lvs invocation. Parent PID 16850: bash
File descriptor 63 (pipe:[354553]) leaked on lvs invocation. Parent PID 16850: bash

ADDITIONAL INFORMATION :
=================== log of boot-info 20190914_0842 ===================
boot-info version : 4ppa66
boot-sav version : 4ppa66
boot-sav-extra version : 4ppa66
glade2script version : 3.2.3~ppa4

BLKID BEFORE RAID ACTIVATION:
/dev/sda1: UUID="3d03224e-6fb0-08f3-2bd9-15d061b1c368" UUID_SUB="d1fb8fef-a2be-1b19-ec1c-d20e961d4070" LABEL="kookie-PC:0" TYPE="linux_raid_member" PARTUUID="0002c526-01"
/dev/sda2: UUID="1b1866aa-e551-b458-e05d-c7cb6b840b66" UUID_SUB="e6685fc7-7da9-b9c8-7244-a451fa54350a" LABEL="kookie-PC:1" TYPE="linux_raid_member" PARTUUID="0002c526-02"
/dev/sda4: UUID="9896c602-dc58-5c50-8206-6b4da3be179a" UUID_SUB="88ae7f9b-4c3f-99e9-7173-081b077a8d1b" LABEL="kookie-PC:3" TYPE="linux_raid_member" PARTUUID="0002c526-04"
/dev/sda5: UUID="1963022c-7be5-e3f9-be84-6ce8d83cebaf" UUID_SUB="5ec18968-246e-5ffb-1730-754bdd6b4993" LABEL="kookie-PC:2" TYPE="linux_raid_member" PARTUUID="0002c526-05"
/dev/sdb1: UUID="3d03224e-6fb0-08f3-2bd9-15d061b1c368" UUID_SUB="2e2ab01d-465f-cc35-5a2f-79477e29a573" LABEL="kookie-PC:0" TYPE="linux_raid_member" PARTUUID="00011d77-01"
/dev/sdb2: UUID="1b1866aa-e551-b458-e05d-c7cb6b840b66" UUID_SUB="635b1c98-959c-39db-579e-8e9107d3df3d" LABEL="kookie-PC:1" TYPE="linux_raid_member" PARTUUID="00011d77-02"
/dev/sdb4: UUID="9896c602-dc58-5c50-8206-6b4da3be179a" UUID_SUB="d319b5b7-aea0-41ba-d7ee-8daf5972968b" LABEL="kookie-PC:3" TYPE="linux_raid_member" PARTUUID="00011d77-04"
/dev/sdb5: UUID="1963022c-7be5-e3f9-be84-6ce8d83cebaf" UUID_SUB="88386f29-e170-12dd-450b-66e30f096df0" LABEL="kookie-PC:2" TYPE="linux_raid_member" PARTUUID="00011d77-05"
/dev/sdc1: UUID="3d03224e-6fb0-08f3-2bd9-15d061b1c368" UUID_SUB="07ac7c14-f78f-c63d-9dd6-3a6188738286" LABEL="kookie-PC:0" TYPE="linux_raid_member" PARTUUID="c6048b91-01"
/dev/sdc2: UUID="1b1866aa-e551-b458-e05d-c7cb6b840b66" UUID_SUB="9b395899-accf-aae9-659d-9ccc3ed878f7" LABEL="kookie-PC:1" TYPE="linux_raid_member" PARTUUID="c6048b91-02"
/dev/sdc4: UUID="9896c602-dc58-5c50-8206-6b4da3be179a" UUID_SUB="7a554a64-9409-1982-b06f-cc1c4b26ec5e" LABEL="kookie-PC:3" TYPE="linux_raid_member" PARTUUID="c6048b91-04"
/dev/sdc5: UUID="1963022c-7be5-e3f9-be84-6ce8d83cebaf" UUID_SUB="e1c2bbdb-de6c-33ed-7f53-67488bf6109e" LABEL="kookie-PC:2" TYPE="linux_raid_member" PARTUUID="c6048b91-05"
/dev/md2: UUID="baeadf1d-9675-436d-99f8-adf133170401" TYPE="swap"
/dev/md0: UUID="4e0631f7-d7d2-4435-88c8-e7254a9a2ba2" TYPE="ext4"
/dev/md3: UUID="AD82-EC2E" TYPE="vfat"
/dev/md1: UUID="b5b23e5c-d55c-4246-85b2-72bb1477cea7" TYPE="ext4"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
dmraid -si -c: no raid disks
No DMRAID disk.
Scanning MDraid Partitions
mdadm --detail --scan: ARRAY /dev/md/2 metadata=1.2 name=kookie-PC:2 UUID=1963022c:7be5e3f9:be846ce8:d83cebaf
ARRAY /dev/md/0 metadata=1.2 name=kookie-PC:0 UUID=3d03224e:6fb008f3:2bd915d0:61b1c368
ARRAY /dev/md/3 metadata=1.2 name=kookie-PC:3 UUID=9896c602:dc585c50:82066b4d:a3be179a
ARRAY /dev/md/1 metadata=1.2 name=kookie-PC:1 UUID=1b1866aa:e551b458:e05dc7cb:6b840b66
File descriptor 9 (/proc/6935/mounts) leaked on lvs invocation. Parent PID 8752: /bin/sh
Partition 3 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
boot-info is executed in installed-session (Ubuntu 16.04.6 LTS, xenial, Ubuntu, x86_64)
CPU op-mode(s):        32-bit, 64-bit
BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=4e0631f7-d7d2-4435-88c8-e7254a9a2ba2 ro quiet splash intel_idle.max_cstate=1
Set sda as corresponding disk of md0
Set sda as corresponding disk of md3
Set sda as corresponding disk of md1
Set sda as corresponding disk of md0
Set sda as corresponding disk of md3
Set sda as corresponding disk of md1

=================== os-prober:
/dev/md0:L'OS actuellement utilisé - Ubuntu 16.04.6 LTS CurrentSession:linux

=================== blkid:
/dev/sda1: UUID="3d03224e-6fb0-08f3-2bd9-15d061b1c368" UUID_SUB="d1fb8fef-a2be-1b19-ec1c-d20e961d4070" LABEL="kookie-PC:0" TYPE="linux_raid_member" PARTUUID="0002c526-01"
/dev/sda2: UUID="1b1866aa-e551-b458-e05d-c7cb6b840b66" UUID_SUB="e6685fc7-7da9-b9c8-7244-a451fa54350a" LABEL="kookie-PC:1" TYPE="linux_raid_member" PARTUUID="0002c526-02"
/dev/sda4: UUID="9896c602-dc58-5c50-8206-6b4da3be179a" UUID_SUB="88ae7f9b-4c3f-99e9-7173-081b077a8d1b" LABEL="kookie-PC:3" TYPE="linux_raid_member" PARTUUID="0002c526-04"
/dev/sda5: UUID="1963022c-7be5-e3f9-be84-6ce8d83cebaf" UUID_SUB="5ec18968-246e-5ffb-1730-754bdd6b4993" LABEL="kookie-PC:2" TYPE="linux_raid_member" PARTUUID="0002c526-05"
/dev/sdb1: UUID="3d03224e-6fb0-08f3-2bd9-15d061b1c368" UUID_SUB="2e2ab01d-465f-cc35-5a2f-79477e29a573" LABEL="kookie-PC:0" TYPE="linux_raid_member" PARTUUID="00011d77-01"
/dev/sdb2: UUID="1b1866aa-e551-b458-e05d-c7cb6b840b66" UUID_SUB="635b1c98-959c-39db-579e-8e9107d3df3d" LABEL="kookie-PC:1" TYPE="linux_raid_member" PARTUUID="00011d77-02"
/dev/sdb4: UUID="9896c602-dc58-5c50-8206-6b4da3be179a" UUID_SUB="d319b5b7-aea0-41ba-d7ee-8daf5972968b" LABEL="kookie-PC:3" TYPE="linux_raid_member" PARTUUID="00011d77-04"
/dev/sdb5: UUID="1963022c-7be5-e3f9-be84-6ce8d83cebaf" UUID_SUB="88386f29-e170-12dd-450b-66e30f096df0" LABEL="kookie-PC:2" TYPE="linux_raid_member" PARTUUID="00011d77-05"
/dev/sdc1: UUID="3d03224e-6fb0-08f3-2bd9-15d061b1c368" UUID_SUB="07ac7c14-f78f-c63d-9dd6-3a6188738286" LABEL="kookie-PC:0" TYPE="linux_raid_member" PARTUUID="c6048b91-01"
/dev/sdc2: UUID="1b1866aa-e551-b458-e05d-c7cb6b840b66" UUID_SUB="9b395899-accf-aae9-659d-9ccc3ed878f7" LABEL="kookie-PC:1" TYPE="linux_raid_member" PARTUUID="c6048b91-02"
/dev/sdc4: UUID="9896c602-dc58-5c50-8206-6b4da3be179a" UUID_SUB="7a554a64-9409-1982-b06f-cc1c4b26ec5e" LABEL="kookie-PC:3" TYPE="linux_raid_member" PARTUUID="c6048b91-04"
/dev/sdc5: UUID="1963022c-7be5-e3f9-be84-6ce8d83cebaf" UUID_SUB="e1c2bbdb-de6c-33ed-7f53-67488bf6109e" LABEL="kookie-PC:2" TYPE="linux_raid_member" PARTUUID="c6048b91-05"
/dev/md2: UUID="baeadf1d-9675-436d-99f8-adf133170401" TYPE="swap"
/dev/md0: UUID="4e0631f7-d7d2-4435-88c8-e7254a9a2ba2" TYPE="ext4"
/dev/md3: UUID="AD82-EC2E" TYPE="vfat"
/dev/md1: UUID="b5b23e5c-d55c-4246-85b2-72bb1477cea7" TYPE="ext4"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"

Set sda as corresponding disk of md0

1 disks with OS, 1 OS : 1 Linux, 0 MacOS, 0 Windows, 0 unknown type OS.

Partition 3 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.

=================== /etc/grub.d/ :
drwxr-xr-x  2 root root      4096 mai    9 10:42 grub.d
total 80
-rwxr-xr-x 1 root root  9791 janv. 13  2017 00_header
-rwxr-xr-x 1 root root  6258 mars  15  2016 05_debian_theme
-rwxr-xr-x 1 root root 12512 mars   1  2017 10_linux
-rwxr-xr-x 1 root root 11082 janv. 13  2017 20_linux_xen
-rwxr-xr-x 1 root root  1992 janv. 28  2016 20_memtest86+
-rwxr-xr-x 1 root root 11692 janv. 13  2017 30_os-prober
-rwxr-xr-x 1 root root  1418 janv. 13  2017 30_uefi-firmware
-rwxr-xr-x 1 root root   214 janv. 13  2017 40_custom
-rwxr-xr-x 1 root root   216 janv. 13  2017 41_custom
-rw-r--r-- 1 root root   483 janv. 13  2017 README




=================== /etc/default/grub :

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
#GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=1"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"




/boot/grub/menu.lst detected

=================== md0/etc/mdadm/mdadm.conf :
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays
ARRAY /dev/md/0  metadata=1.2 UUID=3d03224e:6fb008f3:2bd915d0:61b1c368 name=kookie-PC:0
ARRAY /dev/md/1  metadata=1.2 UUID=1b1866aa:e551b458:e05dc7cb:6b840b66 name=kookie-PC:1
ARRAY /dev/md/3  metadata=1.2 UUID=9896c602:dc585c50:82066b4d:a3be179a name=kookie-PC:3
ARRAY /dev/md/2  metadata=1.2 UUID=1963022c:7be5e3f9:be846ce8:d83cebaf name=kookie-PC:2

# This file was auto-generated on Wed, 01 Feb 2017 11:45:26 +0100
# by mkconf $Id$




=================== md0/proc/mdstat :
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
md1 : active raid5 sdb2[0] sda2[1] sdc2[2]
1835675648 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]
bitmap: 5/7 pages [20KB], 65536KB chunk

md3 : active raid5 sdb4[0] sda4[1] sdc4[2]
17958912 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]

md0 : active raid5 sdb1[0] sda1[1] sdc1[2]
68292608 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]

md2 : active raid5 sdb5[0] sda5[1] sdc5[2]
31232000 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]

unused devices: <none>




=================== UEFI/Legacy mode:
This installed-session is not in EFI-mode.
SecureBoot disabled.


=================== PARTITIONS & DISKS:
md0	: sda,	not-sepboot,	grubenv-ok	grub2,	grub-pc grub1 ,	update-grub,	64,	with-boot,	is-os,	not--efi--part,	fstab-without-boot,	fstab-without-efi,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot,	apt-get,	grub-install,	with--usr,	fstab-without-usr,	not-sep-usr,	standard,	not-far,	notbiosboot, .
md3	: sda,	not-sepboot,	no-grubenv	nogrub,	no-docgrub,	no-update-grub,	32,	no-boot,	no-os,	not--efi--part,	part-has-no-fstab,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot,	nopakmgr,	nogrubinstall,	no---usr,	part-has-no-fstab,	not-sep-usr,	standard,	farbios,	notbiosboot, /windows.
md1	: sda,	maybesepboot,	no-grubenv	nogrub,	no-docgrub,	no-update-grub,	32,	no-boot,	no-os,	not--efi--part,	part-has-no-fstab,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot,	nopakmgr,	nogrubinstall,	no---usr,	part-has-no-fstab,	not-sep-usr,	standard,	not-far,	notbiosboot, /home.

sda	: not-GPT,	BIOSboot-not-needed,	has-no-EFIpart, 	not-usb,	not-mmc, has-os,	2048 sectors * 512 bytes
sdb	: not-GPT,	BIOSboot-not-needed,	has-no-EFIpart, 	not-usb,	not-mmc, no-os,	2048 sectors * 512 bytes
sdc	: not-GPT,	BIOSboot-not-needed,	has-no-EFIpart, 	not-usb,	not-mmc, no-os,	2048 sectors * 512 bytes


=================== parted -lm:

BYT;
/dev/sda:1000GB:scsi:512:4096:msdos:ATA WDC WD10EZEX-00B:;
1:1049kB:35.0GB:35.0GB:ext4::boot, raid;
2:35.0GB:975GB:940GB:::raid;
3:975GB:991GB:16.0GB:::;
5:975GB:991GB:16.0GB:::raid;
4:991GB:1000GB:9203MB:fat32::raid;

BYT;
/dev/sdb:1000GB:scsi:512:4096:msdos:ATA WDC WD10EZEX-00B:;
1:1049kB:35.0GB:35.0GB:ext4::boot, raid;
2:35.0GB:975GB:940GB:::raid;
3:975GB:991GB:16.0GB:::;
5:975GB:991GB:16.0GB:::raid;
4:991GB:1000GB:9203MB:fat32::raid;

BYT;
/dev/sdc:1000GB:scsi:512:4096:msdos:ATA WDC WD10EZEX-08W:;
1:1049kB:35.0GB:35.0GB:::boot, raid;
2:35.0GB:975GB:940GB:::raid;
3:975GB:991GB:16.0GB:::;
5:975GB:991GB:16.0GB:::raid;
4:991GB:1000GB:9203MB:::raid;

BYT;
/dev/md0:69.9GB:md:512:4096:loop:Linux Software RAID Array:;
1:0.00B:69.9GB:69.9GB:ext4::;

BYT;
/dev/md1:1880GB:md:512:4096:loop:Linux Software RAID Array:;
1:0.00B:1880GB:1880GB:ext4::;

BYT;
/dev/md2:32.0GB:md:512:4096:loop:Linux Software RAID Array:;
1:0.00B:32.0GB:32.0GB:linux-swap(v1)::;

BYT;
/dev/md3:18.4GB:md:512:4096:loop:Linux Software RAID Array:;
1:0.00B:18.4GB:18.4GB:fat32::;

=================== lsblk:
KNAME TYPE  FSTYPE              SIZE LABEL
sda   disk                    931,5G
sda1  part  linux_raid_member  32,6G kookie-PC:0
md0   raid5 ext4               65,1G
sda2  part  linux_raid_member 875,5G kookie-PC:1
md1   raid5 ext4                1,7T
sda3  part                        1K
sda4  part  linux_raid_member   8,6G kookie-PC:3
md3   raid5 vfat               17,1G
sda5  part  linux_raid_member  14,9G kookie-PC:2
md2   raid5 swap               29,8G
sdb   disk                    931,5G
sdb1  part  linux_raid_member  32,6G kookie-PC:0
md0   raid5 ext4               65,1G
sdb2  part  linux_raid_member 875,5G kookie-PC:1
md1   raid5 ext4                1,7T
sdb3  part                        1K
sdb4  part  linux_raid_member   8,6G kookie-PC:3
md3   raid5 vfat               17,1G
sdb5  part  linux_raid_member  14,9G kookie-PC:2
md2   raid5 swap               29,8G
sdc   disk                    931,5G
sdc1  part  linux_raid_member  32,6G kookie-PC:0
md0   raid5 ext4               65,1G
sdc2  part  linux_raid_member 875,5G kookie-PC:1
md1   raid5 ext4                1,7T
sdc3  part                        1K
sdc4  part  linux_raid_member   8,6G kookie-PC:3
md3   raid5 vfat               17,1G
sdc5  part  linux_raid_member  14,9G kookie-PC:2
md2   raid5 swap               29,8G
sr0   rom                      1024M
loop0 loop  squashfs            8,4M
loop1 loop  squashfs            8,4M
loop2 loop  squashfs           88,7M
loop3 loop  squashfs             89M

KNAME ROTA RO RM STATE   MOUNTPOINT
sda      1  0  0 running
sda1     1  0  0
md0      1  0  0         /
sda2     1  0  0
md1      1  0  0         /home
sda3     1  0  0
sda4     1  0  0
md3      1  0  0         /windows
sda5     1  0  0
md2      1  0  0         [SWAP]
sdb      1  0  0 running
sdb1     1  0  0
md0      1  0  0         /
sdb2     1  0  0
md1      1  0  0         /home
sdb3     1  0  0
sdb4     1  0  0
md3      1  0  0         /windows
sdb5     1  0  0
md2      1  0  0         [SWAP]
sdc      1  0  0 running
sdc1     1  0  0
md0      1  0  0         /
sdc2     1  0  0
md1      1  0  0         /home
sdc3     1  0  0
sdc4     1  0  0
md3      1  0  0         /windows
sdc5     1  0  0
md2      1  0  0         [SWAP]
sr0      1  0  1 running
loop0    1  1  0         /snap/canonical-livepatch/81
loop1    1  1  0         /snap/canonical-livepatch/77
loop2    1  1  0         /snap/core/7396
loop3    1  1  0         /snap/core/7713


=================== mount:
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=8155800k,nr_inodes=2038950,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1642168k,mode=755)
/dev/md0 on / type ext4 (rw,relatime,errors=remount-ro,stripe=256,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (rw,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb,release_agent=/run/cgmanager/agents/cgm-release-agent.hugetlb)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,clone_children)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids,release_agent=/run/cgmanager/agents/cgm-release-agent.pids)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event,release_agent=/run/cgmanager/agents/cgm-release-agent.perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=22,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/var/lib/snapd/snaps/canonical-livepatch_77.snap on /snap/canonical-livepatch/77 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/canonical-livepatch_81.snap on /snap/canonical-livepatch/81 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/core_7713.snap on /snap/core/7713 type squashfs (ro,nodev,relatime)
/var/lib/snapd/snaps/core_7396.snap on /snap/core/7396 type squashfs (ro,nodev,relatime)
/dev/md3 on /windows type vfat (rw,relatime,gid=46,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/md1 on /home type ext4 (rw,relatime,stripe=256,data=ordered)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
cgmfs on /run/cgmanager/fs type tmpfs (rw,relatime,size=100k,mode=755)
lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
tmpfs on /run/snapd/ns type tmpfs (rw,nosuid,noexec,relatime,size=1642168k,mode=755)
nsfs on /run/snapd/ns/canonical-livepatch.mnt type nsfs (rw)
tmpfs on /run/user/115 type tmpfs (rw,nosuid,nodev,relatime,size=1642168k,mode=700,uid=115,gid=124)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1642168k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)


=================== ls:
/sys/block/md0 (filtered):  alignment_offset bdi capability dev discard_alignment ext_range holders inflight integrity md power queue range removable ro size slaves stat subsystem trace uevent
/sys/block/md1 (filtered):  alignment_offset bdi capability dev discard_alignment ext_range holders inflight integrity md power queue range removable ro size slaves stat subsystem trace uevent
/sys/block/md2 (filtered):  alignment_offset bdi capability dev discard_alignment ext_range holders inflight integrity md power queue range removable ro size slaves stat subsystem trace uevent
/sys/block/md3 (filtered):  alignment_offset bdi capability dev discard_alignment ext_range holders inflight integrity md power queue range removable ro size slaves stat subsystem trace uevent
/sys/block/sda (filtered):  alignment_offset bdi capability dev device discard_alignment events events_async events_poll_msecs ext_range holders inflight integrity power queue range removable ro sda1 sda2 sda3 sda4 sda5 size slaves stat subsystem trace uevent
/sys/block/sdb (filtered):  alignment_offset bdi capability dev device discard_alignment events events_async events_poll_msecs ext_range holders inflight integrity power queue range removable ro sdb1 sdb2 sdb3 sdb4 sdb5 size slaves stat subsystem trace uevent
/sys/block/sdc (filtered):  alignment_offset bdi capability dev device discard_alignment events events_async events_poll_msecs ext_range holders inflight integrity power queue range removable ro sdc1 sdc2 sdc3 sdc4 sdc5 size slaves stat subsystem trace uevent
/sys/block/sr0 (filtered):  alignment_offset bdi capability dev device discard_alignment events events_async events_poll_msecs ext_range holders inflight integrity power queue range removable ro size slaves stat subsystem trace uevent
/dev (filtered):  autofs block bsg btrfs-control bus cdrom cdrw char console core cpu cpu_dma_latency cuse disk dri dvd dvdrw ecryptfs fd full fuse hidraw0 hidraw1 hidraw2 hidraw3 hidraw4 hidraw5 hidraw6 hidraw7 hidraw8 hidraw9 hpet hugepages hwrng i2c-0 i2c-1 i2c-2 i2c-3 initctl input kmsg kvm lightnvm log mapper mcelog md md0 md1 md2 md3 mem memory_bandwidth mqueue net network_latency network_throughput null nvidia0 nvidiactl nvidia-uvm port ppp psaux ptmx pts random rfkill rtc rtc0 sda sda1 sda2 sda3 sda4 sda5 sdb sdb1 sdb2 sdb3 sdb4 sdb5 sdc sdc1 sdc2 sdc3 sdc4 sdc5 sg0 sg1 sg2 sg3 shm snapshot snd sr0 stderr stdin stdout uhid uinput urandom usb userio vboxdrv vboxdrvu vboxnetctl vboxusb vfio vga_arbiter vhci vhost-net zero
ls /dev/md:  0 1 2 3
ls /dev/mapper:  control

=================== hexdump -n512 -C /dev/md3
00000000  eb 58 90 6d 6b 66 73 2e  66 61 74 00 02 20 20 00  |.X.mkfs.fat..  .|
00000010  02 00 00 00 00 f8 00 00  04 00 02 00 00 00 00 00  |................|
00000020  00 10 24 02 3d 22 00 00  00 00 00 00 02 00 00 00  |..$.="..........|
00000030  01 00 06 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000040  80 01 29 2e ec 82 ad 20  20 20 20 20 20 20 20 20  |..)....         |
00000050  20 20 46 41 54 33 32 20  20 20 0e 1f be 77 7c ac  |  FAT32   ...w|.|
00000060  22 c0 74 0b 56 b4 0e bb  07 00 cd 10 5e eb f0 32  |".t.V.......^..2|
00000070  e4 cd 16 cd 19 eb fe 54  68 69 73 20 69 73 20 6e  |.......This is n|
00000080  6f 74 20 61 20 62 6f 6f  74 61 62 6c 65 20 64 69  |ot a bootable di|
00000090  73 6b 2e 20 20 50 6c 65  61 73 65 20 69 6e 73 65  |sk.  Please inse|
000000a0  72 74 20 61 20 62 6f 6f  74 61 62 6c 65 20 66 6c  |rt a bootable fl|
000000b0  6f 70 70 79 20 61 6e 64  0d 0a 70 72 65 73 73 20  |oppy and..press |
000000c0  61 6e 79 20 6b 65 79 20  74 6f 20 74 72 79 20 61  |any key to try a|
000000d0  67 61 69 6e 20 2e 2e 2e  20 0d 0a 00 00 00 00 00  |gain ... .......|
000000e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200
Partition 3 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.

=================== df -Th:

Filesystem     Type      Size  Used Avail Use% Mounted on
udev           devtmpfs  7.8G     0  7.8G   0% /dev
tmpfs          tmpfs     1.6G   31M  1.6G   2% /run
/dev/md0       ext4       64G   23G   39G  37% /
tmpfs          tmpfs     7.9G   67M  7.8G   1% /dev/shm
tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
tmpfs          tmpfs     7.9G     0  7.9G   0% /sys/fs/cgroup
/dev/loop1     squashfs  8.5M  8.5M     0 100% /snap/canonical-livepatch/77
/dev/loop0     squashfs  8.5M  8.5M     0 100% /snap/canonical-livepatch/81
/dev/loop3     squashfs   90M   90M     0 100% /snap/core/7713
/dev/loop2     squashfs   89M   89M     0 100% /snap/core/7396
/dev/md3       vfat       18G   19M   18G   1% /windows
/dev/md1       ext4      1.7T  593G  1.1T  37% /home
cgmfs          tmpfs     100K     0  100K   0% /run/cgmanager/fs
tmpfs          tmpfs     1.6G   16K  1.6G   1% /run/user/115
tmpfs          tmpfs     1.6G   44K  1.6G   1% /run/user/1000

=================== fdisk -l:
Disk /dev/loop0: 8.4 MiB, 8839168 bytes, 17264 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


Disk /dev/loop1: 8.4 MiB, 8835072 bytes, 17256 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


Disk /dev/loop2: 88.7 MiB, 92983296 bytes, 181608 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


Disk /dev/loop3: 89 MiB, 93327360 bytes, 182280 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


Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x0002c526

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sda1  *          2048   68360191   68358144  32.6G fd Linux raid autodetect
/dev/sda2         68360192 1904297983 1835937792 875.5G fd Linux raid autodetect
/dev/sda3       1904300030 1935548415   31248386  14.9G  5 Extended
/dev/sda4       1935548416 1953523711   17975296   8.6G fd Linux raid autodetect
/dev/sda5       1904300032 1935548415   31248384  14.9G fd Linux raid autodetect

Partition table entries are not in disk order.


Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x00011d77

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sdb1  *          2048   68360191   68358144  32.6G fd Linux raid autodetect
/dev/sdb2         68360192 1904297983 1835937792 875.5G fd Linux raid autodetect
/dev/sdb3       1904300030 1935548415   31248386  14.9G  5 Extended
/dev/sdb4       1935548416 1953523711   17975296   8.6G fd Linux raid autodetect
/dev/sdb5       1904300032 1935548415   31248384  14.9G fd Linux raid autodetect

Partition table entries are not in disk order.




Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xc6048b91

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sdc1  *          2048   68360191   68358144  32.6G fd Linux raid autodetect
/dev/sdc2         68360192 1904297983 1835937792 875.5G fd Linux raid autodetect
/dev/sdc3       1904300030 1935548415   31248386  14.9G  5 Extended
/dev/sdc4       1935548416 1953523711   17975296   8.6G fd Linux raid autodetect
/dev/sdc5       1904300032 1935548415   31248384  14.9G fd Linux raid autodetect

Partition table entries are not in disk order.


Disk /dev/md2: 29.8 GiB, 31981568000 bytes, 62464000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes


Disk /dev/md0: 65.1 GiB, 69931630592 bytes, 136585216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes


Disk /dev/md3: 17.1 GiB, 18389925888 bytes, 35917824 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disklabel type: dos
Disk identifier: 0x00000000


Disk /dev/md1: 1.7 TiB, 1879731863552 bytes, 3671351296 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes




=================== Suggested repair
The default repair of the Boot-Repair utility would purge (in order to enable-raid) and reinstall the grub2 of md0 into the MBRs of all disks (except live-disks and removable disks without OS).
Additional repair would be performed: unhide-bootmenu-10s


=================== Final advice in case of suggested repair
N'oubliez pas de régler votre BIOS pour qu'il amorce sur le disque sda (ATA WDC WD10EZEX-00B) !


=================== User settings
The settings chosen by the user will not act on the boot.

Important : Pensez à passer vos sujets en [Résolu] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.

Xubuntu 18.04.1 LTS - Lenovo T410 -Toshiba Satellite A300  Membre de Linux-Azur

Hors ligne

#8 Le 14/09/2019, à 08:43

geole

Re : Passer de 16.04 à 18.04 sur une machine en raid 5

Bonjour.

Au vu du boot-info,  tu es en RAIDS-5.

=================== md0/proc/mdstat :
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
md1 : active raid5 sdb2[0] sda2[1] sdc2[2]
1835675648 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]
bitmap: 5/7 pages [20KB], 65536KB chunk

md3 : active raid5 sdb4[0] sda4[1] sdc4[2]
17958912 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]

md0 : active raid5 sdb1[0] sda1[1] sdc1[2]
68292608 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]

md2 : active raid5 sdb5[0] sda5[1] sdc5[2]
31232000 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]


Même la structure de boot est en RAIDS.     Ma proposition de dual-boot ne tient pas.
Il est probable que la solution UPGRADE  de la version 16.04  soit  aussi une solution  car une installation sur du RAIDS pur n'est pas très connue dans le forum

Pour mieux connaitre tes RAIDS,  Peux-tu donner le retour de ces commandes

sudo mdadm --detail /dev/md[0-3]  
sudo lsblk -o SIZE,NAME,FSTYPE,LABEL,MOUNTPOINT

Tu auras certainement un autre avis d'une personne connaissant très bien les RAIDS

Dernière modification par geole (Le 14/09/2019, à 08:48)

Hors ligne

#9 Le 14/09/2019, à 12:11

jamesbad000

Re : Passer de 16.04 à 18.04 sur une machine en raid 5

Bonjour,

kookie68 a écrit :

Je penche très nettement pour la deuxième solution, mais que deviendra mon raid existant ? Faudra t-il le réinstaller avec mdadm ou sera t-il reconnu dès le début de l'installation ?

Tes raid existant sont décrits par un superbloc raid présent dans chaque membre constitutif (ici des partitions), comme l'indique la mention "metadata=1.2" ci-dessous

ARRAY /dev/md/2 metadata=1.2 name=kookie-PC:2 UUID=1963022c:7be5e3f9:be846ce8:d83cebaf
ARRAY /dev/md/0 metadata=1.2 name=kookie-PC:0 UUID=3d03224e:6fb008f3:2bd915d0:61b1c368
ARRAY /dev/md/3 metadata=1.2 name=kookie-PC:3 UUID=9896c602:dc585c50:82066b4d:a3be179a
ARRAY /dev/md/1 metadata=1.2 name=kookie-PC:1 UUID=1b1866aa:e551b458:e05dc7cb:6b840b66

Ils seront donc reconnus par n'importe quelle installation contenant le paquet mdadm, y compris par un live cd d'install.

La seule chose qui n'est pas précisée dans le superbloc c'est le nom du device (mdX) qui en l'absence de fichier mdadm.conf sera attribué selon l'ordre de détection.
Mais de toute façon si tu utilise les UUID dans fstab le nom de device n'est pas très important. (Tiens. Je note que le fstab n'apparait pas dans le boot info. C'est nouveau ça ?)

Ce qu'il y a, c'est que pour faire une installation sur un raid existant, tu sera obligé de passer par le mode d'installation "avancé" pour choisir toi même tes partitions d'installation.

geole a écrit :

Même la structure de boot est en RAIDS.     Ma proposition de dual-boot ne tient pas.

Je ne vois pas bien en quoi cela s'oppose à un dual boot: Le core.img de grub embarque automatiquement le module raid si nécessaire (cf liste des modules au début du boot info), pour accéder à la partition boot.
La nouvelle installation peut soit avoir également un boot dans une autre partition séparée, soit directement dans sa partition racine...
(hum, je note aussi que boot-info a totalement échoué à décrire les informations de boot et d'os dans les mdX)


L'espace et le temps sont les modes par lesquels nous pensons, et non les conditions dans lesquelles nous vivons. (Signé Albert)

Hors ligne

#10 Le 17/09/2019, à 13:12

kookie68

Re : Passer de 16.04 à 18.04 sur une machine en raid 5

Un grand merci de vous pencher sur le "problème".
Le retour de mdadm --detail /dev/md[0-3] :

kookie@kookie-PC:~$ sudo mdadm --detail /dev/md[0-3]
[sudo] Mot de passe de kookie : 
/dev/md0:
        Version : 1.2
  Creation Time : Wed Feb  1 11:28:29 2017
     Raid Level : raid5
     Array Size : 68292608 (65.13 GiB 69.93 GB)
  Used Dev Size : 34146304 (32.56 GiB 34.97 GB)
   Raid Devices : 3
  Total Devices : 3
    Persistence : Superblock is persistent

    Update Time : Tue Sep 17 14:02:46 2019
          State : clean 
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 512K

           Name : kookie-PC:0  (local to host kookie-PC)
           UUID : 3d03224e:6fb008f3:2bd915d0:61b1c368
         Events : 509

    Number   Major   Minor   RaidDevice State
       0       8       17        0      active sync   /dev/sdb1
       1       8        1        1      active sync   /dev/sda1
       2       8       33        2      active sync   /dev/sdc1
/dev/md1:
        Version : 1.2
  Creation Time : Wed Feb  1 11:28:52 2017
     Raid Level : raid5
     Array Size : 1835675648 (1750.64 GiB 1879.73 GB)
  Used Dev Size : 917837824 (875.32 GiB 939.87 GB)
   Raid Devices : 3
  Total Devices : 3
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Tue Sep 17 14:02:48 2019
          State : clean 
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 512K

           Name : kookie-PC:1  (local to host kookie-PC)
           UUID : 1b1866aa:e551b458:e05dc7cb:6b840b66
         Events : 1403

    Number   Major   Minor   RaidDevice State
       0       8       18        0      active sync   /dev/sdb2
       1       8        2        1      active sync   /dev/sda2
       2       8       34        2      active sync   /dev/sdc2
/dev/md2:
        Version : 1.2
  Creation Time : Wed Feb  1 11:29:20 2017
     Raid Level : raid5
     Array Size : 31232000 (29.79 GiB 31.98 GB)
  Used Dev Size : 15616000 (14.89 GiB 15.99 GB)
   Raid Devices : 3
  Total Devices : 3
    Persistence : Superblock is persistent

    Update Time : Tue Sep 17 12:16:04 2019
          State : clean 
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 512K

           Name : kookie-PC:2  (local to host kookie-PC)
           UUID : 1963022c:7be5e3f9:be846ce8:d83cebaf
         Events : 37

    Number   Major   Minor   RaidDevice State
       0       8       21        0      active sync   /dev/sdb5
       1       8        5        1      active sync   /dev/sda5
       2       8       37        2      active sync   /dev/sdc5
/dev/md3:
        Version : 1.2
  Creation Time : Wed Feb  1 11:29:46 2017
     Raid Level : raid5
     Array Size : 17958912 (17.13 GiB 18.39 GB)
  Used Dev Size : 8979456 (8.56 GiB 9.19 GB)
   Raid Devices : 3
  Total Devices : 3
    Persistence : Superblock is persistent

    Update Time : Thu Sep 12 08:29:50 2019
          State : clean 
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 512K

           Name : kookie-PC:3  (local to host kookie-PC)
           UUID : 9896c602:dc585c50:82066b4d:a3be179a
         Events : 39

    Number   Major   Minor   RaidDevice State
       0       8       20        0      active sync   /dev/sdb4
       1       8        4        1      active sync   /dev/sda4
       2       8       36        2      active sync   /dev/sdc4
kookie@kookie-PC:~$ 

Et le retour de sudo lsblk -o SIZE,NAME,FSTYPE,LABEL,MOUNTPOINT :

kookie@kookie-PC:~$ sudo lsblk -o SIZE,NAME,FSTYPE,LABEL,MOUNTPOINT
  SIZE NAME    FSTYPE            LABEL       MOUNTPOINT
931,5G sda                                   
 32,6G ├─sda1  linux_raid_member kookie-PC:0 
 65,1G │ └─md0 ext4                          /
875,5G ├─sda2  linux_raid_member kookie-PC:1 
  1,7T │ └─md1 ext4                          /home
    1K ├─sda3                                
  8,6G ├─sda4  linux_raid_member kookie-PC:3 
 17,1G │ └─md3 vfat                          /windows
 14,9G └─sda5  linux_raid_member kookie-PC:2 
 29,8G   └─md2 swap                          [SWAP]
931,5G sdb                                   
 32,6G ├─sdb1  linux_raid_member kookie-PC:0 
 65,1G │ └─md0 ext4                          /
875,5G ├─sdb2  linux_raid_member kookie-PC:1 
  1,7T │ └─md1 ext4                          /home
    1K ├─sdb3                                
  8,6G ├─sdb4  linux_raid_member kookie-PC:3 
 17,1G │ └─md3 vfat                          /windows
 14,9G └─sdb5  linux_raid_member kookie-PC:2 
 29,8G   └─md2 swap                          [SWAP]
931,5G sdc                                   
 32,6G ├─sdc1  linux_raid_member kookie-PC:0 
 65,1G │ └─md0 ext4                          /
875,5G ├─sdc2  linux_raid_member kookie-PC:1 
  1,7T │ └─md1 ext4                          /home
    1K ├─sdc3                                
  8,6G ├─sdc4  linux_raid_member kookie-PC:3 
 17,1G │ └─md3 vfat                          /windows
 14,9G └─sdc5  linux_raid_member kookie-PC:2 
 29,8G   └─md2 swap                          [SWAP]
 1024M sr0                                   
  8,4M loop0   squashfs                      /snap/canonical-livepatch/81
  8,4M loop1   squashfs                      /snap/canonical-livepatch/77
 88,7M loop2   squashfs                      /snap/core/7396
   89M loop3   squashfs                      /snap/core/7713

Hors ligne

#11 Le 17/09/2019, à 15:35

kookie68

Re : Passer de 16.04 à 18.04 sur une machine en raid 5

Pour préciser la chose, je ne suis pas en dual boot. Uniquement Ubuntu. J'ai une partition qui contient une machine virtuelle Win..

Hors ligne

#12 Le 18/09/2019, à 19:48

jamesbad000

Re : Passer de 16.04 à 18.04 sur une machine en raid 5

Personne n'a suggéré non plus que tu étais en dual boot. Je disais juste, par rapport à la remarque de Geole qu'il n'y a pas d'impossibilité.
Au reste, comme je l'ai dis, tu peux parfaitement faire une installation fraîche de 18.04.

Il faudra pour cela passer par le mode avancé et assigner ton volume / à ton actuel md0 , /home à md1, /windows à md3 etc. en vérifiant bien que les dimensions  correspondent, car comme je le disais les lecteurs peuvent éventuellement se présenter avec des nom différent.
Et surtout éviter soigneusement de cocher la case formatage pour /home et /windows

Ton / actuel étant sur raid, j'imagine que tu as déjà du utiliser ce mode avancé pour faire ton installation précédemment...


L'espace et le temps sont les modes par lesquels nous pensons, et non les conditions dans lesquelles nous vivons. (Signé Albert)

Hors ligne

#13 Le 19/09/2019, à 17:20

kookie68

Re : Passer de 16.04 à 18.04 sur une machine en raid 5

jamesbad000 a écrit :

Personne n'a suggéré non plus que tu étais en dual boot. Je disais juste, par rapport à la remarque de Geole qu'il n'y a pas d'impossibilité.
Au reste, comme je l'ai dis, tu peux parfaitement faire une installation fraîche de 18.04.

Il faudra pour cela passer par le mode avancé et assigner ton volume / à ton actuel md0 , /home à md1, /windows à md3 etc. en vérifiant bien que les dimensions  correspondent, car comme je le disais les lecteurs peuvent éventuellement se présenter avec des nom différent.
Et surtout éviter soigneusement de cocher la case formatage pour /home et /windows

Ton / actuel étant sur raid, j'imagine que tu as déjà du utiliser ce mode avancé pour faire ton installation précédemment...

Tout à fait, mais c'était il y a plus de 3 ans wink ! C'était une version alternate ou server si je me rappelle bien. Et je me suis reposé sur mes lauriers pendant tout ce temps ! J'ai la mémoire qui flanche...

Je vais faire le test de lancer l'installation en Desktop en installant mdadm et voir ce que ça peut donner. Mais faudra que je sauvegarde mes données avant toute opération.

Hors ligne