41
edits
Changes
Jump to navigation
Jump to search
Line 12:
Line 12: − This can occur when a new disk has been added to the SME and that this disk is "a little bit" smaller than the disk what is already running. + − + Line 36:
Line 36: − ==== The RAID array: ====+ Line 120:
Line 120: − ==== The swap: ====+
Repairing RAID of the swap (view source)
Revision as of 16:52, 11 February 2016
, 16:52, 11 February 2016no edit summary
=== The starting point: the device for the swap can't get sync ===
=== The starting point: the device for the swap can't get sync ===
It can occur that the raid refuses to resync completely when a new disk has been added to the SME and that this disk is "a little bit" smaller than the disk what is already running.
The raid sync (e.g. started from the console) works of "/", for "/boot" but not for the swap because os missing some space on the added disk.
The raid sync (e.g. started from the console) works of "/", for "/boot" but not for the swap because of missing some space on the added disk.
==== look to the current state of the RAID: ====
==== look to the current state of the RAID: ====
mdadm: /dev/vdb2 not large enough to join array (the disk#2 has been added to the machine afterwards)
mdadm: /dev/vdb2 not large enough to join array (the disk#2 has been added to the machine afterwards)
=== The RAID array: ===
* stop the swap:
* stop the swap:
# swapoff -a
# swapoff -a
* Check that the UUID and the name are correct and wait the end of the sync.
* Check that the UUID and the name are correct and wait the end of the sync.
=== The swap: ===
Open /etc/fstab and remember the UUID set for the swap file system
Open /etc/fstab and remember the UUID set for the swap file system
nano /etc/fstab
nano /etc/fstab