NAS doesn't boot after setup Raid

[Jocko]

:scratch

So if there is no new boot.log that would mean now the bootloader fails to handle the sda disk when the NAS boots...

and explains this:

your outputs are as if the last step (add sda8 in md0) was not performed :scratch

Code: Select all

   - Mounting volume Vol-A:  [ OK ]
   - Mounting volume RD1-0:  [ OK ]

(should try to mount only md0)

Do you change the position of the switch (big/safe100) on the back ?

[jungfichte]

Do you change the position of the switch (big/safe100) on the back ?

No, should I try to change it?

[Jocko]

Ok,

We are not sure but it should be on "Big" position.

Before installing 16.1, do you have some issues with this disk ?

Now it is time to :z)

[jungfichte]

I tried both positions - same behavior.
Now its on "Big" position.

I bought the NAS on ebay.
The HDDs are original SEAGATE baracuda

At my first try to build the raid after installing the fvdw firmware i got the same error NAS does not Boot after Step II / 3 End to build the RAID

Then i erased both HDDs with:

Code: Select all

dd if=/dev/zero of=/dev/sdX

The second try fails at the same step... and now i'm looking for help from you ;)

[Jocko]

Hi jungfichte,

for next steps, you need to wait up to Monday as I am not at home this WE.

But can you explain how did you format the disk sdb ?
and if you wrote some partition images on it (for example on sdb6)

what happens if you do

Code: Select all

dd if=/dev/zero of=/dev/sdb6

[jungfichte]

But can you explain how did you format the disk sdb ?
and if you wrote some partition images on it (for example on sdb6)

I used this howto: http://plugout.net/download/file.php?id=4122
and choose 3.1 Making ms-dos partition table (for disks smaller then 2TB) using fdisk.
I don't wrote a partition image to sdb6.

I dismantled der HDD and connect in on my ubuntu notebook
gdisk puts out:

Code: Select all

jungfichte@jungfichte-ubuntu:~$ sudo gdisk /dev/sdb
[sudo] password for jungfichte:
GPT fdisk (gdisk) version 0.8.8

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): p
Disk /dev/sdb: 976773168 sectors, 465.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): F910D1B9-54D2-4EA4-AA5D-B1765BC47475
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 976773134
Partitions will be aligned on 8-sector boundaries
Total free space is 3748181 sectors (1.8 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   5         3341520         5012279   815.8 MiB   8300  Linux filesystem
   6         5140800         5269319   62.8 MiB    8300  Linux filesystem
   7         5397840         6425999   502.0 MiB   8300  Linux filesystem
   8         6554520       976751999   462.6 GiB   FD00  Linux RAID

Command (? for help): q
jungfichte@jungfichte-ubuntu:~$


what happens if you do

Code: Select all

dd if=/dev/zero of=/dev/sdb6

After saving an image of /dev/sdb6, the erasing was sucessful:

Code: Select all

jungfichte@jungfichte-ubuntu:~$ sudo dd if=/dev/zero of=/dev/sdb6
dd: Schreiben in »/dev/sdb6“: Auf dem Gerät ist kein Speicherplatz mehr verfügbar
128521+0 Datensätze ein
128520+0 Datensätze aus
65802240 Bytes (66 MB) kopiert, 11,5008 s, 5,7 MB/s
jungfichte@jungfichte-ubuntu:~$

[Jocko]

Hi jungfichte,

We go to remove your raid1 and see if you have again access on the NAS;

- Get again a telnet access
- reset mdadm.conf on sda5

Code: Select all

mkdir /sda5
mount /dev/sda5 /sda5
cp -f /sda5/etc/mdadm.0 /sda5/etc/mdadm.conf

-reset superblocks on sda8 and sdb8

Code: Select all

mdadm --zero-superblock /dev/sda8
mdadm --zero-superblock /dev/sdb8

check if you did not set some superblocks on another level

Code: Select all

 mdadm --examine --scan

output should be empty. If not, post the output and wait what you should do

-reset partition type on partition sda8/sdb8
set the code 8300 as you did with fd (gdisk /dev/sda ->t->8->8300->w->y)

reboot the NAS and see what happens.

Then if you have an ssh access, post the output

Code: Select all

cat /boot.log

grep '<disk>' /etc/nas_conf_db.xml -A 20
grep '<vol>' /etc/nas_conf_db.xml -A 12
grep '<addonsvolume>' /etc/nas_conf_db.xml

 ls -l /direct-usb
 ls -l /usr/local


[jungfichte]

Hi jocko,
i hope you had a nice weekend.

Code: Select all

Code:
mkdir /sda5
mount /dev/sda5 /sda5
cp -f /sda5/etc/mdadm.0 /sda5/etc/mdadm.conf

Code: Select all

root@(none):/ # mkdir /sda5
root@(none):/ # mount /dev/sda5 /sda5
root@(none):/ # cp -f /sda5/etc/mdadm.0 /sda5/etc/mdadm.conf
cp: can't stat '/sda5/etc/mdadm.0': No such file or directory
root@(none):/ # cd sda5/etc/
root@(none):/sda5/etc # ls
dropbear                 nas_conf_db.xml.bak      nas_ext_hdd_db.xml
mdadm.conf               nas_conf_db.xml.tmp-org  ntp.conf
nas_conf_db.xml          nas_conf_db.xmle         ssl
root@(none):/sda5/etc #

[Jocko]

indeed mdadm.0 is not stored on sda5 but sda7.

So do

Code: Select all

mkdir /sda5
mount /dev/sda5 /sda5
mkdir /sda7
mount /dev/sda7 /sda7
cp -f /sda7/etc/mdadm.0 /sda5/etc/mdadm.conf

[jungfichte]

Ok, that worked:

Code: Select all

Code:
mkdir /sda5
mount /dev/sda5 /sda5
mkdir /sda7
mount /dev/sda7 /sda7
cp -f /sda7/etc/mdadm.0 /sda5/etc/mdadm.conf


mdadm.conf is reseted
also the reset of the superblocks on sda8 and sdb8 works fine
The ouput of

Code: Select all

mdadm --examine --scan

is empty.
gdisk is not available:

Code: Select all

root@(none):/ # gdisk /dev/sda
-sh: gdisk: not found
root@(none):/ #

what can we do?