Upgrade from 2.x to latest 4.x : Raid Ok but marked as 127

hubertes · 31. Juli 2018

Hi,

I did a fresh install on a thumb,

Then did my settings,

Raid is ok, but marked as md127 instead of md0, is this a problem ?

Code

Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
md127 : active raid6 sdb[8] sdf[6] sdc[2] sdd[0] sda[3] sde[7]
      5860548608 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU]

Code

/dev/sdb: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="b243c911-8058-51ff-0413-31fb1528c36c" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sdc: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="70983681-b5c2-9f70-1801-948b1b7c97d1" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sdd: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="b2460066-00b1-5070-cfe3-7ac67aae96c1" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sde: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="ce05af8c-7da1-c0a7-0a07-c10b0b154735" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sdf: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="440f9a88-1d42-020c-ba4d-d303afb76c7c" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/md127: LABEL="ZettaFiles" UUID="76c7546c-5ae6-4884-ac9f-3ecda0f473bc" TYPE="ext4"
/dev/sda: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="ee7eab8f-dc90-e3be-146d-a4e09d104418" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sdg1: UUID="e7e85422-36f4-425a-bf67-daeca4725765" TYPE="ext4" PARTUUID="d1d52e93-01"
/dev/sdg5: UUID="32f1f36a-e295-4904-b6e1-484eba83ff1a" TYPE="swap" PARTUUID="d1d52e93-05"

Code

Disk /dev/sdb: 1,8 TiB, 2000398934016 bytes, 3907029168 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 /dev/sdc: 1,4 TiB, 1500301910016 bytes, 2930277168 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/sdd: 1,4 TiB, 1500301910016 bytes, 2930277168 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 /dev/sde: 1,8 TiB, 2000398934016 bytes, 3907029168 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 /dev/sdf: 1,8 TiB, 2000398934016 bytes, 3907029168 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 /dev/sda: 1,4 TiB, 1500301910016 bytes, 2930277168 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 /dev/md127: 5,5 TiB, 6001201774592 bytes, 11721097216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 2097152 bytes




Disk /dev/sdg: 7,5 GiB, 8019509248 bytes, 15663104 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
Disklabel type: dos
Disk identifier: 0xd1d52e93


Device     Boot   Start      End Sectors  Size Id Type
/dev/sdg1  *       2048  7567359 7565312  3,6G 83 Linux
/dev/sdg2       7569406 15661055 8091650  3,9G  5 Extended
/dev/sdg5       7569408 15661055 8091648  3,9G 82 Linux swap / Solaris

Alles anzeigen

(I did update the fstab for the usb drive and flash plugin, why is it still showing the swap file ?)

Thanks

EDIT : tried to fix this too within grub and uuid, no luck

Code

mdadm : no array found in config file or automatically

ryecoaaron · 31. Juli 2018

Zitat von hubertes

Raid is ok, but marked as md127 instead of md0, is this a problem ?

Nope.

hubertes · 31. Juli 2018

Thanks !

And is this related too boot message :

mdadm : no array found in config file or automatically

ryecoaaron · 31. Juli 2018

What is the output of: cat /etc/mdadm/mdadm.conf

hubertes · 31. Juli 2018

Code

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#


# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions


# 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>


# definitions of existing MD arrays

Alles anzeigen

still have the old hdd where OMV 2.x was installed though

ryecoaaron · 31. Juli 2018

Zitat von hubertes

still have the old hdd where OMV 2.x was installed though

omv-mkconf mdadm should fix that file followed by update-grub. Then see if you see the message at boot.

hubertes · 31. Juli 2018

Thanks

Solved

Code

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#


# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions


# 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>


# definitions of existing MD arrays
ARRAY /dev/md/zetta:0 metadata=1.2 name=zetta:0 UUID=96b0e7b7:83aa203f:1545031b:43caaa85

Alles anzeigen

ryecoaaron · 31. Juli 2018

Zitat von hubertes

Solved

Just out of curiousity, did you create your array using OMV?

hubertes · 1. August 2018

Yes,

With an old OMV 2.X , I'd say 2 or 3 years ago ?

ryecoaaron · 1. August 2018

Zitat von hubertes

With an old OMV 2.X , I'd say 2 or 3 years ago ?

I'm surprised it didn't create the mdadm.conf entry. Oh well. It is there now.

hubertes · 1. August 2018

You mean when I reconnected my drives after clean installing omv 4.x ?

ryecoaaron · 1. August 2018

Zitat von hubertes

You mean when I reconnected my drives after clean installing omv 4.x ?

Ah. That is why there is no entry. I thought you upgraded from 2.x to 4.x. Mounting the filesystem will not create the entry.

hubertes · 1. August 2018

Ha ok. I followed the recommendation and installed a fresh new system and replugged my hard drive.

ryecoaaron · 2. August 2018

Zitat von hubertes

Ha ok. I followed the recommendation and installed a fresh new system and replugged my hard drive.

Normally this is ok. The mdadm.conf entry isn't required but it does make things less noisy. Not sure how to fix this other than telling people to run omv-mkconf mdadm when installing fresh with a mdadm raid array.

hubertes · 3. August 2018

didn't know that, maybe it'll help peole if you pin a short thread abour upgrading ?

Jetzt mitmachen!