Thanks Wols, but, I was so impatient to solve this issue that I end up
messing things up. :(
In short, I was able to get it clean, but I'm not able to mount it,
this is how it looks now:
/dev/md/RAID:
Version : 1.2
Creation Time : Fri Jan 18 19:10:11 2019
Raid Level : raid5
Array Size : 9767557120 (9315.07 GiB 10001.98 GB)
Used Dev Size : 1953511424 (1863.01 GiB 2000.40 GB)
Raid Devices : 6
Total Devices : 6
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Jan 18 19:10:11 2019
State : clean
Active Devices : 6
Working Devices : 6
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Name : andromedahive:RAID (local to host andromedahive)
UUID : b6223486:cf8e0986:25f0a536:bf37d0dd
Events : 0
Number Major Minor RaidDevice State
0 8 81 0 active sync /dev/sdf1
1 8 65 1 active sync /dev/sde1
2 8 1 2 active sync /dev/sda1
3 8 17 3 active sync /dev/sdb1
4 8 49 4 active sync /dev/sdd1
5 8 97 5 active sync /dev/sdg1
----------------------------------------------------------------------------------
array disks details:
/dev/sda1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : b6223486:cf8e0986:25f0a536:bf37d0dd
Name : andromedahive:RAID (local to host andromedahive)
Creation Time : Fri Jan 18 19:10:11 2019
Raid Level : raid5
Raid Devices : 6
Avail Dev Size : 3907022991 (1863.01 GiB 2000.40 GB)
Array Size : 9767557120 (9315.07 GiB 10001.98 GB)
Used Dev Size : 3907022848 (1863.01 GiB 2000.40 GB)
Data Offset : 4096 sectors
Super Offset : 8 sectors
Unused Space : before=4008 sectors, after=143 sectors
State : clean
Device UUID : 97785afb:f2bf46cf:03c16b45:838dc0f9
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Jan 18 19:10:11 2019
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : ec893da0 - correct
Events : 0
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 2
Array State : AAAAAA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdb1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : b6223486:cf8e0986:25f0a536:bf37d0dd
Name : andromedahive:RAID (local to host andromedahive)
Creation Time : Fri Jan 18 19:10:11 2019
Raid Level : raid5
Raid Devices : 6
Avail Dev Size : 3907022991 (1863.01 GiB 2000.40 GB)
Array Size : 9767557120 (9315.07 GiB 10001.98 GB)
Used Dev Size : 3907022848 (1863.01 GiB 2000.40 GB)
Data Offset : 4096 sectors
Super Offset : 8 sectors
Unused Space : before=4008 sectors, after=143 sectors
State : clean
Device UUID : 396c91ab:7e10b3f3:6c1e8c87:9ad629de
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Jan 18 19:10:11 2019
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : e7b6284f - correct
Events : 0
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 3
Array State : AAAAAA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdd1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : b6223486:cf8e0986:25f0a536:bf37d0dd
Name : andromedahive:RAID (local to host andromedahive)
Creation Time : Fri Jan 18 19:10:11 2019
Raid Level : raid5
Raid Devices : 6
Avail Dev Size : 3907022991 (1863.01 GiB 2000.40 GB)
Array Size : 9767557120 (9315.07 GiB 10001.98 GB)
Used Dev Size : 3907022848 (1863.01 GiB 2000.40 GB)
Data Offset : 4096 sectors
Super Offset : 8 sectors
Unused Space : before=4008 sectors, after=143 sectors
State : clean
Device UUID : f6ab5e71:fbb5e07c:5d6ef29c:ef06ea23
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Jan 18 19:10:11 2019
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : 91d78dcf - correct
Events : 0
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 4
Array State : AAAAAA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sde1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : b6223486:cf8e0986:25f0a536:bf37d0dd
Name : andromedahive:RAID (local to host andromedahive)
Creation Time : Fri Jan 18 19:10:11 2019
Raid Level : raid5
Raid Devices : 6
Avail Dev Size : 3907022991 (1863.01 GiB 2000.40 GB)
Array Size : 9767557120 (9315.07 GiB 10001.98 GB)
Used Dev Size : 3907022848 (1863.01 GiB 2000.40 GB)
Data Offset : 4096 sectors
Super Offset : 8 sectors
Unused Space : before=4008 sectors, after=143 sectors
State : clean
Device UUID : 2bf3b0f5:d7cf7ca8:59921d8f:a8684cd4
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Jan 18 19:10:11 2019
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : e4537493 - correct
Events : 0
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 1
Array State : AAAAAA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdf1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : b6223486:cf8e0986:25f0a536:bf37d0dd
Name : andromedahive:RAID (local to host andromedahive)
Creation Time : Fri Jan 18 19:10:11 2019
Raid Level : raid5
Raid Devices : 6
Avail Dev Size : 3907022991 (1863.01 GiB 2000.40 GB)
Array Size : 9767557120 (9315.07 GiB 10001.98 GB)
Used Dev Size : 3907022848 (1863.01 GiB 2000.40 GB)
Data Offset : 4096 sectors
Super Offset : 8 sectors
Unused Space : before=4008 sectors, after=143 sectors
State : clean
Device UUID : 1c85f63f:5dc0b045:aa717699:4cc15b17
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Jan 18 19:10:11 2019
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : 19352efd - correct
Events : 0
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 0
Array State : AAAAAA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdg1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : b6223486:cf8e0986:25f0a536:bf37d0dd
Name : andromedahive:RAID (local to host andromedahive)
Creation Time : Fri Jan 18 19:10:11 2019
Raid Level : raid5
Raid Devices : 6
Avail Dev Size : 3907022991 (1863.01 GiB 2000.40 GB)
Array Size : 9767557120 (9315.07 GiB 10001.98 GB)
Used Dev Size : 3907022848 (1863.01 GiB 2000.40 GB)
Data Offset : 4096 sectors
Super Offset : 8 sectors
Unused Space : before=4008 sectors, after=143 sectors
State : clean
Device UUID : e7d50c95:94157168:65aa90f8:675723cb
Internal Bitmap : 8 sectors from superblock
Update Time : Fri Jan 18 19:10:11 2019
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : a3eda3db - correct
Events : 0
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 5
Array State : AAAAAA ('A' == active, '.' == missing, 'R' == replacing)
----------------------------------------------------------------------------------
/proc/mdstat:
Personalities : [raid6] [raid5] [raid4]
md127 : active (auto-read-only) raid5 sdf1[0] sdg1[5] sdd1[4] sdb1[3]
sda1[2] sde1[1]
9767557120 blocks super 1.2 level 5, 512k chunk, algorithm 2
[6/6] [UUUUUU]
bitmap: 0/15 pages [0KB], 65536KB chunk
unused devices: <none>
----------------------------------------------------------------------------------
# mount -t ext4 /dev/md/RAID /mnt/RAIDVol
mount: wrong fs type, bad option, bad superblock on /dev/md127,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
----------------------------------------------------------------------------------
so, checked it with fsck.ext4 -f:
fsck.ext4 -f /dev/md127
e2fsck 1.42.12 (29-Aug-2014)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks...
fsck.ext4: Bad magic number in super-block while trying to open /dev/md127
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
At this time, I'm still using mdadm v3.3.2.
Do I have any chance to mount it?
Thanks,
Romulo
On Fri, Jan 18, 2019 at 6:18 AM Wols Lists <antlists@xxxxxxxxxxxxxxx> wrote:
>
> On 16/01/19 22:36, Romulo Albuquerque wrote:
> > Hi Wols,
> >
> > Nice to hear that it's all looking good...
> >
> > Running mdadm
> > # mdadm --version
> > mdadm - v3.3.2 - 21st August 2014
> >
> > Running on kernel version:
> > # uname -a
> > Linux andromedah 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u6
> > (2015-11-09) x86_64 GNU/Linux
> >
> > Please, let me know what is the best approach to revert-reshape in my case.
> >
> > Thanks for looking into this!
> >
> Hi,
>
> Sorry for the slow reply ...
>
> I'd install the latest mdadm - v4.1 iirc - and see if that can revert
> the reshape. If that succeeds, it'll probably also successfully fire off
> a new reshape, but I'd backup first ...
>
> Otherwise, boot from a rescue CD and stop the reshape, then reshape
> using the rescue CD before bringing the system back into production.
>
> Cheers,
> Wol
>
