Eliminar MDADM RAID1 sin perder datos -- raid campo con mdadm camp askubuntu Relacionados El problema

remove mdadm raid1 without loosing data


2
vote

problema

Español

Tengo 2 hdd's en raid1 usando mdadm .

Ahora quiero deshabilitar completamente la redada, pero quiero mantener los datos en el disco 1 y usar el disco 2 por separado

¿Hay alguna manera de hacer esto?

Sé honesto, sé lo que es RAID, pero no tengo idea de cómo se maneja por mdadm .

Estoy usando Ubuntu 14.04

Configuración:

  mdadm: /dev/md does not appear to be an md device /dev/md0:         Version : 1.2   Creation Time : Tue Jul  7 10:13:17 2015      Raid Level : raid1      Array Size : 16768896 (15.99 GiB 17.17 GB)   Used Dev Size : 16768896 (15.99 GiB 17.17 GB)    Raid Devices : 2   Total Devices : 2     Persistence : Superblock is persistent      Update Time : Sun Oct 11 15:50:16 2015           State : clean   Active Devices : 2 Working Devices : 2  Failed Devices : 0   Spare Devices : 0             Name : rescue:0            UUID : ec52104c:85983ebd:8a13b660:706bae89          Events : 32      Number   Major   Minor   RaidDevice State        0       8        1        0      active sync   /dev/sda1        1       8       17        1      active sync   /dev/sdb1 /dev/md1:         Version : 1.2   Creation Time : Tue Jul  7 10:13:20 2015      Raid Level : raid1      Array Size : 523968 (511.77 MiB 536.54 MB)   Used Dev Size : 523968 (511.77 MiB 536.54 MB)    Raid Devices : 2   Total Devices : 2     Persistence : Superblock is persistent      Update Time : Sat Sep 19 12:41:03 2015           State : clean   Active Devices : 2 Working Devices : 2  Failed Devices : 0   Spare Devices : 0             Name : rescue:1            UUID : decb590d:aac47b81:568a2afa:3dee7600          Events : 30      Number   Major   Minor   RaidDevice State        0       8        2        0      active sync   /dev/sda2        1       8       18        1      active sync   /dev/sdb2 /dev/md2:         Version : 1.2   Creation Time : Tue Jul  7 10:13:20 2015      Raid Level : raid1      Array Size : 1073610560 (1023.87 GiB 1099.38 GB)   Used Dev Size : 1073610560 (1023.87 GiB 1099.38 GB)    Raid Devices : 2   Total Devices : 2     Persistence : Superblock is persistent      Update Time : Mon Oct 12 09:25:14 2015           State : clean   Active Devices : 2 Working Devices : 2  Failed Devices : 0   Spare Devices : 0             Name : rescue:2            UUID : 1daa4480:ddf3f359:575a1f97:e232bbdd          Events : 195      Number   Major   Minor   RaidDevice State        0       8        3        0      active sync   /dev/sda3        1       8       19        1      active sync   /dev/sdb3 /dev/md3:         Version : 1.2   Creation Time : Tue Jul  7 10:13:20 2015      Raid Level : raid1      Array Size : 1839089920 (1753.89 GiB 1883.23 GB)   Used Dev Size : 1839089920 (1753.89 GiB 1883.23 GB)    Raid Devices : 2   Total Devices : 2     Persistence : Superblock is persistent      Update Time : Mon Oct 12 09:04:16 2015           State : clean   Active Devices : 2 Working Devices : 2  Failed Devices : 0   Spare Devices : 0             Name : rescue:3            UUID : 051aac4e:ecac8794:538fe663:c9212747          Events : 92      Number   Major   Minor   RaidDevice State        0       8        4        0      active sync   /dev/sda4        1       8       20        1      active sync   /dev/sdb4     

.

  WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.   Disk /dev/sda: 3000.6 GB, 3000592982016 bytes 256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 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 identifier: 0x00000000     Device Boot      Start         End      Blocks   Id  System /dev/sda1   *           1  4294967295  2147483647+  ee  GPT  WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.   Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes 256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 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 Disk identifier: 0x00000000     Device Boot      Start         End      Blocks   Id  System /dev/sdb1   *           1  4294967295  2147483647+  ee  GPT Partition 1 does not start on physical sector boundary.  Disk /dev/md0: 17.2 GB, 17171349504 bytes 2 heads, 4 sectors/track, 4192224 cylinders, total 33537792 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 Disk identifier: 0x00000000  Disk /dev/md0 doesn't contain a valid partition table  Disk /dev/md1: 536 MB, 536543232 bytes 2 heads, 4 sectors/track, 130992 cylinders, total 1047936 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 Disk identifier: 0x00000000  Disk /dev/md1 doesn't contain a valid partition table  Disk /dev/md3: 1883.2 GB, 1883228078080 bytes 2 heads, 4 sectors/track, 459772480 cylinders, total 3678179840 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 Disk identifier: 0x00000000  Disk /dev/md3 doesn't contain a valid partition table  Disk /dev/md2: 1099.4 GB, 1099377213440 bytes 2 heads, 4 sectors/track, 268402640 cylinders, total 2147221120 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 Disk identifier: 0x00000000  Disk /dev/md2 doesn't contain a valid partition table   
Original en ingles

I have 2 hdd's in raid1 using mdadm.

Now i want to completely disable raid but i want to keep data on disk 1, and use disk 2 separately

Is there a way to do this.

Ill be honest, i know what raid is, but i have no idea how it is handled by mdadm.

I'm using Ubuntu 14.04

Configuration:

mdadm: /dev/md does not appear to be an md device /dev/md0:         Version : 1.2   Creation Time : Tue Jul  7 10:13:17 2015      Raid Level : raid1      Array Size : 16768896 (15.99 GiB 17.17 GB)   Used Dev Size : 16768896 (15.99 GiB 17.17 GB)    Raid Devices : 2   Total Devices : 2     Persistence : Superblock is persistent      Update Time : Sun Oct 11 15:50:16 2015           State : clean   Active Devices : 2 Working Devices : 2  Failed Devices : 0   Spare Devices : 0             Name : rescue:0            UUID : ec52104c:85983ebd:8a13b660:706bae89          Events : 32      Number   Major   Minor   RaidDevice State        0       8        1        0      active sync   /dev/sda1        1       8       17        1      active sync   /dev/sdb1 /dev/md1:         Version : 1.2   Creation Time : Tue Jul  7 10:13:20 2015      Raid Level : raid1      Array Size : 523968 (511.77 MiB 536.54 MB)   Used Dev Size : 523968 (511.77 MiB 536.54 MB)    Raid Devices : 2   Total Devices : 2     Persistence : Superblock is persistent      Update Time : Sat Sep 19 12:41:03 2015           State : clean   Active Devices : 2 Working Devices : 2  Failed Devices : 0   Spare Devices : 0             Name : rescue:1            UUID : decb590d:aac47b81:568a2afa:3dee7600          Events : 30      Number   Major   Minor   RaidDevice State        0       8        2        0      active sync   /dev/sda2        1       8       18        1      active sync   /dev/sdb2 /dev/md2:         Version : 1.2   Creation Time : Tue Jul  7 10:13:20 2015      Raid Level : raid1      Array Size : 1073610560 (1023.87 GiB 1099.38 GB)   Used Dev Size : 1073610560 (1023.87 GiB 1099.38 GB)    Raid Devices : 2   Total Devices : 2     Persistence : Superblock is persistent      Update Time : Mon Oct 12 09:25:14 2015           State : clean   Active Devices : 2 Working Devices : 2  Failed Devices : 0   Spare Devices : 0             Name : rescue:2            UUID : 1daa4480:ddf3f359:575a1f97:e232bbdd          Events : 195      Number   Major   Minor   RaidDevice State        0       8        3        0      active sync   /dev/sda3        1       8       19        1      active sync   /dev/sdb3 /dev/md3:         Version : 1.2   Creation Time : Tue Jul  7 10:13:20 2015      Raid Level : raid1      Array Size : 1839089920 (1753.89 GiB 1883.23 GB)   Used Dev Size : 1839089920 (1753.89 GiB 1883.23 GB)    Raid Devices : 2   Total Devices : 2     Persistence : Superblock is persistent      Update Time : Mon Oct 12 09:04:16 2015           State : clean   Active Devices : 2 Working Devices : 2  Failed Devices : 0   Spare Devices : 0             Name : rescue:3            UUID : 051aac4e:ecac8794:538fe663:c9212747          Events : 92      Number   Major   Minor   RaidDevice State        0       8        4        0      active sync   /dev/sda4        1       8       20        1      active sync   /dev/sdb4   

.

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.   Disk /dev/sda: 3000.6 GB, 3000592982016 bytes 256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 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 identifier: 0x00000000     Device Boot      Start         End      Blocks   Id  System /dev/sda1   *           1  4294967295  2147483647+  ee  GPT  WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.   Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes 256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 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 Disk identifier: 0x00000000     Device Boot      Start         End      Blocks   Id  System /dev/sdb1   *           1  4294967295  2147483647+  ee  GPT Partition 1 does not start on physical sector boundary.  Disk /dev/md0: 17.2 GB, 17171349504 bytes 2 heads, 4 sectors/track, 4192224 cylinders, total 33537792 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 Disk identifier: 0x00000000  Disk /dev/md0 doesn't contain a valid partition table  Disk /dev/md1: 536 MB, 536543232 bytes 2 heads, 4 sectors/track, 130992 cylinders, total 1047936 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 Disk identifier: 0x00000000  Disk /dev/md1 doesn't contain a valid partition table  Disk /dev/md3: 1883.2 GB, 1883228078080 bytes 2 heads, 4 sectors/track, 459772480 cylinders, total 3678179840 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 Disk identifier: 0x00000000  Disk /dev/md3 doesn't contain a valid partition table  Disk /dev/md2: 1099.4 GB, 1099377213440 bytes 2 heads, 4 sectors/track, 268402640 cylinders, total 2147221120 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 Disk identifier: 0x00000000  Disk /dev/md2 doesn't contain a valid partition table 
     

Lista de respuestas

5
 
vote
vote
La mejor respuesta
 

No puede eliminar un disco directamente de la matriz, a menos que se haya fallado, por lo que primero tenemos que fallarlo (si la unidad, no se ha fallado, esto normalmente ya está en estado fallado y este paso no es necesario):

  mdadm --fail /dev/md0 /dev/sda1   

y ahora podemos eliminarlo:

  mdadm --remove /dev/md0 /dev/sda1   

Esto se puede hacer en un solo paso usando:

  mdadm /dev/md0 --fail /dev/sda1 --remove /dev/sda1   

Luego monte el disco como un disco normal:

  sudo mount -t auto /dev/sda1 /media/disk   
 

You cannot remove a disk directly from the array, unless it is failed, so we first have to fail it (if the drive it is failed this is normally already in failed state and this step is not needed):

mdadm --fail /dev/md0 /dev/sda1 

and now we can remove it:

mdadm --remove /dev/md0 /dev/sda1 

This can be done in a single step using:

mdadm /dev/md0 --fail /dev/sda1 --remove /dev/sda1 

Then mount the disk as a normal disk:

sudo mount -t auto /dev/sda1 /media/disk 
 
 
   
   

Relacionados problema

0  Luks2 en la parte superior de RAID5 no se monta correctamente  ( Luks2 on top of raid5 not mounting correctly ) 
Sistema: Ubuntu 18.04 64 bits. Tengo una matriz RAID-5 (MD0) que consta de 4 dispositivos (SDB1, SDC1, SDD1, SDE1). Me encripté / dev / md0 como un volumen ...

1  Reemplace el disco fallado en RAID 1  ( Replace failed disk in raid 1 ) 
Hace dos días, una de mis dos unidades en mi software RAID 1 (que se configuró el uso de los discos GNOME), falló la configuración. No pude acceder a los arch...

0  RAID1 no ensamblar  ( Raid1 not assemble ) 
Tengo RAID de software y no es ensamblar cuando intenté reunirlo. A continuación, estoy mostrando una salida de algunos comandos. mdadm -a -s / dev / md1 /...

0  ¿Alguien más tiene problemas para acceder a las particiones dinámicas de Windows de Ubuntu?  ( Anyone else having trouble accessing dynamic windows partitions from ubuntu ) 
He estado tratando de acceder a mi disco RAYS RAID RAID de Ubuntu durante al menos seis meses. Sé que hay guías por ahí, pero son un poco difíciles de seguir,...

0  Unidad reemplazada en la matriz RAID - ¡Ahora no se puede iniciar?  ( Replaced drive in raid array now cant boot ) 
Tengo un servidor de inicio que ejecuta 10.04 configurado con una matriz RAID basada en MDADM. Las particiones de arranque y / domiciliarias están tanto en ma...

0  ¿Cómo creo una redada de software en unidades no sistemas en Ubuntu 14.04?  ( How do i create a software raid on non system drives in ubuntu 14 04 ) 
El sistema operativo está instalado en un SSD independiente, pero tengo 3 veces unidades de 1TB. Quiero configurar en una RAID 5 para documentos, aplicaciones...

3  deshacerse de la redada de software  ( Get rid of software raid ) 
Estamos ejecutando software RAID1 usando MDADM en Ubuntu 11.04. ¿Cuál es la mejor manera de deshacerse de ella Mantener el sistema actual? Quiero usar RAID ...

0  Sin autoridad para RAID10 Array Linux Ubuntu  ( No authority to raid10 array linux ubuntu ) 
Acabo de crear una matriz RAID10 con MDADM de 3 x 1TB HHD, llamada MD0. Seguí estas instrucciones: https://www.digitalean.com/community/tutorials/how-to-crea...

1  ¿Reconstruye un RAID CAMBIAR DATOS?  ( Does rebuilding a raid change data ) 
acabo de reiniciar mi computadora, que estaba construyendo un RAID5 por primera vez. Esto, por supuesto, significaba que mi computadora tuvo que reconstruir...

3  ¿Es normal que MDADM tenga que comenzar desde cero cuando reinicie mi computadora mientras reconstruye el tercer disco?  ( Is it normal that mdadm has to start from scratch when i restart my computer whi ) 
He instalado un RAID5 usando ayer MDADM. Desde entonces se ha reconstruido. Acabo de reiniciar mi computadora y comenzó a reconstruir la redada desde cero. ...




© 2022 respuesta.top Reservados todos los derechos. Centro de preguntas y respuestas reservados todos los derechos