plugout.net

Hi, i'm very bad lucky, i know.
I'm trying to make a raid5 inside my first nas, 5bigN2, all the disks inside are 2tb, the same as before, i never change them since 4 years to now.
But since now them were 5 disks with individual volume. So i had 5 volumes, like 5 different storages.
Now i would like to do a raid volume with them.

What i have done?

1) inizialize Hard disk and volumes
2) select all disks, chose GPT and EXT4, then run task
3) after reboot, i chose New Volume called "5big2" and chose raid5 and ext4.
4) then after many scrips i get the error sda8 can not change to fd00
here some screen:




So, i did reboot the nas. But after the reboot, inside the disk manager i see this:



So... is the raid5 real? or not? that error (fail can not change sda8 to fd00) is a bad error that i need to worry? or i can forget it and starting to trasfer all my files inside the nas?

Hi

It is a minor error and your raid5 is building. You can see that by

Code: Select all

cat /proc/mdstat

Now I think you get this issue because you selected gpt table for the other disks whereas sda is a msdos table which can not be changed (system disk)

Please to post

Code: Select all

gdisk -l /dev/sda
gdisk -l /dev/sdb

And also

Code: Select all

cat /etc/.setup.fs/makeraid.sh

hi jocko, thanks for reply! mmm... i'm stuck in command "gdisk -l /dev/sda" that get this:



What i have to choose?

I reread the setup task, and no this can not be the explanation about ms-dos table.

So please to post the asked output

So we know now why it fails.

What is the disk size on sda (>2TB ?)

really... this is it...I swear :hail

Code: Select all

login as: root
root@192.168.1.189's password:
root@Norman_Nas:/ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5

Caution: invalid main GPT header, but valid backup; regenerating main header
from backup!

Caution! After loading partitions, the CRC doesn't check out!
Warning! Main partition table CRC mismatch! Loaded backup partition table
instead of main partition table!

Warning! One or more CRCs don't match. You should repair the disk!

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: damaged

Found valid MBR and corrupt GPT. Which do you want to use? (Using the
GPT MAY permit recovery of GPT data.)
 1 - MBR
 2 - GPT
 3 - Create blank GPT

Your answer:


Please to answer to my previous post

Jocko wrote:So we know now why it fails.

What is the disk size on sda (>2TB ?)

and post

Code: Select all

fdisk -l /dev/sda

Jocko wrote:So we know now why it fails.
What is the disk size on sda (>2TB ?)

Yes it is a 2TB but not exactly like the other 4 disks.

Disk-a is 1859.88 GB
all other disks are 1860.24 GB

and this output

Code: Select all

fdisk -l /dev/sda

Jocko wrote:Please to answer to my previous post So we know now why it fails.
What is the disk size on sda (>2TB ?)

Disk-a = 1859.88 GB
Others = 1860.24 GB

Jocko wrote:and post

Code: Select all

fdisk -l /dev/sda

Code: Select all

login as: root
root@192.168.1.189's password:
root@Norman_Nas:/ # fdisk -l /dev/sda

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 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      243201  1951905532+  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      243201  1950234772+ 83 Linux
root@Norman_Nas:/ #