Error creating Raid 5

[b1gnas]

ok

all done... now rebooting

[fvdw]

And don't forget to load the raid modules after reboot

[b1gnas]

And don't forget to load the raid modules after reboot

running this command?

Code: Select all

sed -rie "s/exit 0/modprobe raid0 2>> boot.log\nmodprobe raid1 2>> boot.log\nmodprobe raid456 2>> boot.log\nmodprobe raid10 2>> boot.log\nexit 0/g" /etc/init.d/insert-modules

[Jocko]

Yes you can use this line to keep the changes but you need to reboot the nas after running it.

[Jocko]

Note: I confirm that you need to create a raid5 with 4 devices first...

It seems that with raid5 when you create a degraded raid device (with a missing disk), mdadm doesn't start to synchronize the raid. It is why you can not format it.

Only raid1 can be built in that way

[b1gnas]

so i have to create a raid 5 with the standard way described in the guide? and using which disks?

[Jocko]

Yes with this line

Code: Select all

mdadm --create /dev/md0 --level=5 --assume-clean --raid-devices=4 /dev/sdb8 /dev/sdc8 /dev/sdd8 /dev/sde8

before you need to clean the disk by removing the superblock for these 4 disks

[b1gnas]

Code: Select all

root@fvdwsl-base:/ # fdisk /dev/sdb

The number of cylinders for this disk is set to 121601.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb4             201      121600   975145500   5 Extended
/dev/sdb5             209         312      835380  83 Linux
/dev/sdb6             321         328       64260  83 Linux
/dev/sdb7             337         400      514080  83 Linux
/dev/sdb8             409      121600   973474740  83 Linux

Command (m for help): t
Partition number (1-8): 8
Hex code (type L to list codes): fd
Changed system type of partition 8 to fd (Linux raid autodetect)

Command (m for help): p

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb4             201      121600   975145500   5 Extended
/dev/sdb5             209         312      835380  83 Linux
/dev/sdb6             321         328       64260  83 Linux
/dev/sdb7             337         400      514080  83 Linux
/dev/sdb8             409      121600   973474740  fd Linux raid autodetect

Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
root@fvdwsl-base:/ # fdisk /dev/sdb

The number of cylinders for this disk is set to 121601.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb4             201      121600   975145500   5 Extended
/dev/sdb5             209         312      835380  83 Linux
/dev/sdb6             321         328       64260  83 Linux
/dev/sdb7             337         400      514080  83 Linux
/dev/sdb8             409      121600   973474740  fd Linux raid autodetect



is that warning ok?

[Jocko]

You got this warning because sdb8 is mounted, you need to follow the standard way described in the guide but use the mdadm line posted previously.

So unmount the 4 sd[bcde]8 partitions, and ...

Note: can you post also the dmesg output (we have only an output without the additional modules)

[b1gnas]

ok formatting :please