Problems with raid5

[Jocko]

So currently, the standalone kernel version for 5big1 don't have by default raid support.

I don't know if fvdw included the modules in the kernel image and where.

So search if you see some ko files in a folder. Usually they are in /lib/modules/[kernel-version-number]

[samrise]

Cant seem to find it.

root@(none):/ # ls -l /sys/module/
total 0
drwxr-xr-x 3 root root 0 Jan 1 00:39 8250
drwxr-xr-x 4 root root 0 Jan 1 00:39 ahci
drwxr-xr-x 3 root root 0 Jan 1 00:39 aoe
drwxr-xr-x 3 root root 0 Jan 1 00:39 block
drwxr-xr-x 3 root root 0 Jan 1 00:39 ide_gd_mod
drwxr-xr-x 3 root root 0 Jan 1 00:39 kernel
drwxr-xr-x 3 root root 0 Jan 1 00:39 libahci
drwxr-xr-x 3 root root 0 Jan 1 00:39 libata
drwxr-xr-x 3 root root 0 Jan 1 00:39 netpoll
drwxr-xr-x 3 root root 0 Jan 1 00:39 printk
drwxr-xr-x 4 root root 0 Jan 1 00:39 sata_mv
drwxr-xr-x 3 root root 0 Jan 1 00:39 scsi_mod
drwxr-xr-x 3 root root 0 Jan 1 00:39 spurious
drwxr-xr-x 3 root root 0 Jan 1 00:39 tcp_cubic
drwxr-xr-x 2 root root 0 Jan 1 00:39 xz_dec
root@(none):/ # ls -l /lib/
total 0
root@(none):/ #

/lib is empty. Found that module dir inside /sys.

[Jocko]

Your last output confirms that currently no raid support is available

And I am sorry but without these additional modules we must await fvdw is back (~ next Thursday).

Currently, you can handle a raid device but not format it with a big partitions on the standard environment
and you can not handle a raid device but surely you may format on the standalone environment
:mrgreen:

[samrise]

Ok, waiting its not a problem. If it was a hdd problem it would be a lot worse.

[samrise]

Jocko, should i try this kernel? Is it newer than the one on downloads section?

[Jocko]

Hi samrise,

Yes I knew this topic but as you don't have an issue with the raid feature but with e2fs tools it is useless to try it.

What you can try is to use an old version for fvdw-sl console (version 5.3) and use this standalone version:
viewtopic.php?f=30&t=1557&start=30#p11644

But this version uses a basic way to set the NAS ip: only net : 192.168.1.xx or 192.168.0.xx can be used. So if you use it you need to change the settings of your LAN !!!

As version 5.3 package doesn't contain it you need also to download mdadm package and also udevstart : viewtopic.php?f=7&t=1271#p18801

For udevstart you need to set run permission and run it once to restore the block dev node settings:

Before trying to assemble the raid, you need to load these modules:

Code: Select all

xor
async_xor
async_raid6_recov
raid6_pq
async_memcpy
async_tx
raid456
md-mod

with the command insmod

So see if it is worth or wait for a few days (It is why I don't yet mentioned it)

[fvdw]

please post the output of

Code: Select all

fdisk -l

(it should list partition table and general info of all disks)

[samrise]

Disk /dev/sde: 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/sde4 201 121600 975145500 5 Extended
/dev/sde5 209 312 835380 83 Linux
/dev/sde6 321 328 64260 83 Linux
/dev/sde7 337 400 514080 83 Linux
/dev/sde8 409 121600 973474740 fd Linux raid autodetect

Disk /dev/sdd: 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/sdd4 201 121600 975145500 5 Extended
/dev/sdd5 209 312 835380 83 Linux
/dev/sdd6 321 328 64260 83 Linux
/dev/sdd7 337 400 514080 83 Linux
/dev/sdd8 409 121600 973474740 fd Linux raid autodetect

Disk /dev/sdc: 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/sdc4 201 121600 975145500 5 Extended
/dev/sdc5 209 312 835380 83 Linux
/dev/sdc6 321 328 64260 83 Linux
/dev/sdc7 337 400 514080 83 Linux
/dev/sdc8 409 121600 973474740 fd Linux raid autodetect

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

Disk /dev/sda: 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/sda1 9 72 514080 83 Linux
/dev/sda2 73 136 514080 83 Linux
/dev/sda3 137 200 514080 82 Linux swap
/dev/sda4 201 121601 975153532+ 5 Extended
/dev/sda5 209 312 835380 83 Linux
/dev/sda6 321 328 64260 83 Linux
/dev/sda7 337 400 514080 83 Linux
/dev/sda8 409 121601 973482772+ fd Linux raid autodetect
fdisk: device has more than 2^32 sectors, can't use all of them

Disk /dev/md0: 2199.0 GB, 2199023255040 bytes
2 heads, 4 sectors/track, 536870911 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md0 doesn't contain a valid partition table
root@nas:/ #

[fvdw]

the partition tables and block size of the 5 disks looks ok, need to think on possible options I can think of :scratch

[fvdw]

next what does

Code: Select all

gdisk -l /dev/md0

give as output

another thing I can think of is that the device node of the md0 device is wrong or pointing to the wrong block device
also give output of

Code: Select all

ls -al /dev/md0