plugout.net

by **jungfichte** » Fri Nov 18, 2016 9:12 pm

Hi,

I installed the fvdw 16.1 on my 2big on the first (left hand) drive succesfully
Adding the additional (right hand) disk was succesfull too,
but building a raid fails :scratch

I used this tutorial: http://plugout.net/download/file.php?id=3552
Everything workes fine till Step II / 3 End to build the RAID
After initating the reboot the LacieNas doesn't comes back again

Code: Select all: root@LaCiePussy:/ # gdisk /dev/sdb GPT fdisk (gdisk) version 0.8.5 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: not present *************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by typing 'q' i f you don't want to convert your MBR partitions to GPT format! *************************************************************** 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 8300 Linux filesystem 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 filesyste m 6 5140800 5269319 62.8 MiB 8300 Linux filesyste m 7 5397840 6425999 502.0 MiB 8300 Linux filesyste m 8 6554520 976751999 462.6 GiB 8300 Linux filesyste m 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 8300 Linux filesystem Command (? for help): t Partition number (5-8): 8 Current type is 'Linux filesystem' Hex code or GUID (L to show codes, Enter = 8300): fd00 Changed type of partition to 'Linux RAID' 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): w Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!! Do you want to proceed? (Y/N): Y OK; writing new GUID partition table (GPT) to /dev/sdb. The operation has completed successfully. root@LaCiePussy:/ # gdisk /dev/sdb GPT fdisk (gdisk) version 0.8.5 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 root@LaCiePussy:/ # umount /dev/sdb8 umount: /dev/sdb8: not mounted root@LaCiePussy:/ # mdadm --create /dev/md0 --level=1 --assume-clean --ra id-devices=2 missing /dev/sdb8 mdadm: /dev/sdb8 appears to contain an ext2fs file system size=485097472K mtime=Thu Jan 1 00:00:00 1970 Continue creating array? y mdadm: array /dev/md0 started. root@LaCiePussy:/ # cat /proc/mdstat Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : active raid1 sdb8[1] 485098604 blocks super 1.0 [2/1] [_U] unused devices: <none> root@LaCiePussy:/ # cat /etc/mdadm.0 > /etc/mdadm.conf root@LaCiePussy:/ # mdadm --detail --scan >> /etc/mdadm.conf root@LaCiePussy:/ # mke2fs -t ext3 -j -m 1 /dev/md0 mke2fs 1.42.11 (09-Jul-2014) /dev/md0 contains a ext3 file system created on Fri Nov 18 21:08:14 2016 Proceed anyway? (y,n) y Creating filesystem with 121274368 4k blocks and 30377808 inodes Filesystem UUID: b0dcb3d3-a0e7-4eb0-97ee-72b5708b40b9 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000 Allocating group tables: done Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done root@LaCiePussy:/ # reboot root@LaCiePussy:/ # login as: root root@192.168.18.201's password: root@LaCiePussy:/ # umount /dev/sda8 root@LaCiePussy:/ # gdisk /dev/sda GPT fdisk (gdisk) version 0.8.5 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: not present *************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by typing 'q' if you don't want to convert your MBR partitions to GPT format! *************************************************************** Command (? for help): p Disk /dev/sda: 976773168 sectors, 465.8 GiB Logical sector size: 512 bytes Disk identifier (GUID): 7E18297E-FF7C-406B-AC8F-F036FBA89800 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 663701 sectors (324.1 MiB) Number Start (sector) End (sector) Size Code Name 1 128520 1156679 502.0 MiB 8300 Linux filesystem 2 1156680 2184839 502.0 MiB 8300 Linux filesystem 3 2184840 3212999 502.0 MiB 8200 Linux swap 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 8300 Linux filesystem Command (? for help): t Partition number (1-8): 8 Current type is 'Linux filesystem' Hex code or GUID (L to show codes, Enter = 8300): fd00 Changed type of partition to 'Linux RAID' Command (? for help): p Disk /dev/sda: 976773168 sectors, 465.8 GiB Logical sector size: 512 bytes Disk identifier (GUID): 7E18297E-FF7C-406B-AC8F-F036FBA89800 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 663701 sectors (324.1 MiB) Number Start (sector) End (sector) Size Code Name 1 128520 1156679 502.0 MiB 8300 Linux filesystem 2 1156680 2184839 502.0 MiB 8300 Linux filesystem 3 2184840 3212999 502.0 MiB 8200 Linux swap 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): w Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!! Do you want to proceed? (Y/N): Y OK; writing new GUID partition table (GPT) to /dev/sda. Warning: The kernel is still using the old partition table. The new table will be used at the next reboot. The operation has completed successfully. root@LaCiePussy:/ # mdadm --add /dev/md0 /dev/sda8 mdadm: added /dev/sda8 root@LaCiePussy:/ # cat /etc/mdadm.0 > /etc/mdadm.conf root@LaCiePussy:/ # mdadm --detail --scan >> /etc/mdadm.conf root@LaCiePussy:/ # reboot root@LaCiePussy:/ #

What went wrong?
Any Ideas? :please

Best regards
Thomas

by **Jocko** » Sat Nov 19, 2016 9:49 am

Hi jungfichte,

Indeed it is not the expected behaviour...

Need more information:
- At the first reboot, did you load the disk setup menu (to check if the firmware detected the new raid1)

jungfichte wrote:I installed the fvdw 16.1 on my 2big

Did you install also the patches ? at least one fixes an issue on fs symlink.

jungfichte wrote:After initating the reboot the LacieNas doesn't comes back again

did you use fvdw-sl assistant to check if it detected or not your big1?

To understand what happens. you need to use now fvdw-sl console.

After getting a telnet access (load a standalone kernel), post these outputs

Code: Select all: mkdir /sda7 mount /dev/sda7 /sda7 check what fs partition is used on booting ls /sda7/lacie-boot => you should see a file sda1boot or sda2boot. Then mount the related partition mkdir /sdax (where x=1 or 2) mount /dev/sdax /sdax read the boot.log content cat /sdax/boot.log Read mdadm.conf content mkdir /sda5 mount /dev/sda5 /sda5 cat /sda5/etc/mdadm.conf check the nas database grep '<disk>' /sda5/etc/nas_conf_db.xml -A 20 grep '<vol>' /sda5/etc/nas_conf_db.xml -A 12

by **jungfichte** » Sat Nov 19, 2016 10:56 am

Hi Jocko,
thanks for your quick response.

At the first reboot, did you load the disk setup menu (to check if the firmware detected the new raid1)

Yes, i checked this.
I also copied the technical shares to RD1-0
I found a screenshot in the old open browser session from yesterday

screenshot.png

You can see everything worked fine here.

Did you install also the patches ? at least one fixes an issue on fs symlink.

No, i didn't install any patches.

did you use fvdw-sl assistant to check if it detected or not your big1?

When powering on, i can see the hdd leds blinking on the backside and hearing the nas working.
After 10-15 sek. the nas powers off, the hdds spinning down and no hdd-led are lighting.
Only the yellow nic leds are blinking...

mkdir /sda7
mount /dev/sda7 /sda7

check what fs partition is used on booting
ls /sda7/lacie-boot
=> you should see a file sda1boot or sda2boot.

Then mount the related partition
mkdir /sdax (where x=1 or 2)
mount /dev/sdax /sdax

read the boot.log content
cat /sdax/boot.log

ls /sda7/lacie-boot shows no file
i post the /sda7/boot.log:

Code: Select all: root@(none):/ # ls /sda7/lacie-boot root@(none):/ # ls /sda7 bin clunc lacie-boot mail postupgrade.log sbin usr bin_cab dev lib mnt proc share var boot direct-usb linuxrc nowhere root sys boot.log etc lost+found opt rw_fs tmp root@(none):/ # cat /sda7/boot.log start boot log detect and set platform 2big1 UIMAGE-3142-2BIG1-6 Current kernel: 3.14.2 #6 Sat Nov 29 22:15:32 CET 2014 2big1 mount dev/pts update dev nodes booting using root file system... make dev node for buttons... make dev node for tun device... enable IP forwarding... start buttons control daemon device = 2big1 source = buttons-nwsp2 buttons-nwsp2 daemon started Fri Nov 18 21:26:33 UTC 2016 create temporary passwd file run udevstart to update dev nodes when necessary inserting kernel modules: modprobe: module 'xor.ko' not found create temporary group file configure loopback network interface setting reboot and standby 2big1 rebootd-isp1 2big1 standbyd-isp1 starting php based setup routines step 1 * Starting udevd... [ OK ] * Found XML database configuration file... [ OK ] * Starting RAID monitor: [ OK ] * Starting restore RAID devices... - Assembling device /dev/md0: [ OK ] * Finishing restore RAID devices... [ OK ] * Updating Disks database... Warning: Illegal string offset 'lvname' in /etc/finc/dm_set_usb_raid.finc on line 19 Warning: Illegal string offset 'volid' in /etc/finc/dm_set_usb_raid.finc on line 102 Warning: Illegal string offset 'volid' in /etc/finc/dm_set_usb_raid.finc on line 106 Warning: Illegal string offset 'lvname' in /etc/finc/dm_set_usb_raid.finc on line 116 Warning: Illegal string offset 'lvname' in /etc/finc/dm_set_usb_raid.finc on line 116 Warning: Illegal string offset 'lvname' in /etc/finc/dm_set_usb_raid.finc on line 128 Warning: Illegal string offset 'size' in /etc/finc/dm_set_usb_raid.finc on line 136 [ OK ] * Starting mount of volumes... - Mounting volume Vol-A: [ OK ] - Mounting volume RD1-0: [ OK ] * Finishing mount of volumes... [ OK ] * Generating Hosts File... [ OK ] * Configuring System Hostname... [ OK ] * Configuring LAN interface... [ OK ] * Initializing Timezone... [ OK ] * Starting web server... [ OK ] * Starting mount of internal USB ... * Finishing mount internal USB ... [ OK ] * Configuring Disks... [ OK ] * Configuring Samba... [ OK ] * Configuring System Users... Root password: use default password Set users, linux and samba accounts [ OK ] * Starting Fvdw-sl Discovery Daemon... [ OK ] start rpcbind service starting php based setup routines step 2 * Starting dropbear... [ OK ] * Kill temporary dropbear... [ OK ] starting php based setup routines step 3 * Starting daemon update Hosts File... [ OK ] * Starting mount of remote shares... * Finishing mount shares... [ OK ] starting php based setup routines step banner *** fvdw-sl NAS firmware This is fvdw-sl version: fvdw-sl 16.1 built on: Oct 01 2015 LAN IP address: 192.168.18.201 (static) Port configuration: LAN -> eth0 php based setup routines finished web permission on resolv.conf set device tuning for dms performance LED settings else loop1 finished rcS finished root@(none):/ #

Read mdadm.conf content
mkdir /sda5
mount /dev/sda5 /sda5
cat /sda5/etc/mdadm.conf

Code: Select all: root@(none):/ # mkdir /sda5 root@(none):/ # mount /dev/sda5 /sda5 root@(none):/ # cat /sda5/etc/mdadm.conf CREATE owner=root group=root mode=0666 auto=yes metadata=1.0 PROGRAM /usr/bin/mdadm-events DEVICE /dev/sd* /dev/se* ARRAY /dev/md0 level=raid1 num-devices=2 spares=1 name=0 UUID=1902932f:dd39c09d:c9d35e37:d2eab7ba root@(none):/ #

check the nas database
grep '<disk>' /sda5/etc/nas_conf_db.xml -A 20
grep '<vol>' /sda5/etc/nas_conf_db.xml -A 12

Code: Select all: root@(none):/ # grep '<disk>' /sda5/etc/nas_conf_db.xml -A 20 <disk> <device>/dev/sda</device> <inactivityperiod>15</inactivityperiod> <lastselftest>0</lastselftest> </disk> </hdparams> <notify> <eventbmp>3</eventbmp> <email> <enable>false</enable> <address/> <smtpip/> </email> <icq> <enable>false</enable> <idnum/> <passwd/> <dest_idnum/> </icq> <sms> <enable>false</enable> -- <disk> <size>462.626209259</size> <internal>true</internal> <name>Disk-A</name> <system>true</system> <blockdev>/dev/sda</blockdev> <diskid>9QM659QK</diskid> <model> ST3500620AS</model> <usb>false</usb> <freesize>0</freesize> <init>true</init> <partitions> <partition> <lvname>/dev/sda8</lvname> <color>#6f851e</color> <volid>1000</volid> <index>0</index> <size>462.626209259</size> </partition> </partitions> </disk> <disk> <size>462.626209259</size> <internal>true</internal> <name>Disk-B</name> <system>false</system> <blockdev>/dev/sdb</blockdev> <diskid>9QG7HFPZ</diskid> <model> ST3500630AS</model> <usb>false</usb> <freesize>0</freesize> <init>true</init> <partitions> <partition> <lvname>/dev/sdb8</lvname> <color>#757bc1</color> <volid>1100</volid> <index>0</index> <size>462.626209259</size> </partition> </partitions> </disk> root@(none):/ # root@(none):/ # grep '<vol>' /sda5/etc/nas_conf_db.xml -A 12 <vol> <volid>1000</volid> <md>/dev/sda8</md> <fs>1000</fs> <lastindex>1</lastindex> <name>Vol-A</name> <devices/> <raidtype>single</raidtype> <color>#6f851e</color> <formatting>0</formatting> <size>462.626209259</size> </vol> <vol> <volid>1100</volid> <md>/dev/md0</md> <fs>1100</fs> <lastindex>1</lastindex> <name>RD1-0</name> <devices>missing /dev/sdb8 </devices> <raidtype>raid1</raidtype> <color>#c339ff</color> <formatting>0</formatting> <size>462.626079559</size> </vol> </vols> root@(none):/ #

Thank you for the support
Thomas

by **Jocko** » Sat Nov 19, 2016 11:17 am

Well

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)

Code: Select all: Fri Nov 18 21:26:33 UTC 2016

This date is right with your last restart time :?: (note the date uses UTC)

Still from fvdw-sl console post

Code: Select all: mdadm --examine /dev/sda8

(to get mdadm binary you need to load it : viewtopic.php?f=26&t=2317&p=23193&hilit=mdadm+tftp#p23193)

---edit---
and also this commandline (which it is used by the boot script)

Code: Select all: /sbin/mdadm --examine --brief /dev/sda8 /sbin/mdadm --examine --brief /dev/sdb8

by **jungfichte** » Sat Nov 19, 2016 11:28 am

the restart time should be right.

Still from fvdw-sl console post
Code:
mdadm --examine /dev/sda8

Code: Select all: root@(none):/ # mdadm --examine /dev/sda8 /dev/sda8: Magic : a92b4efc Version : 1.0 Feature Map : 0x2 Array UUID : 1902932f:dd39c09d:c9d35e37:d2eab7ba Name : 0 Creation Time : Fri Nov 18 21:20:27 2016 Raid Level : raid1 Raid Devices : 2 Avail Dev Size : 970197336 (462.63 GiB 496.74 GB) Array Size : 485098604 (462.63 GiB 496.74 GB) Used Dev Size : 970197208 (462.63 GiB 496.74 GB) Super Offset : 970197464 sectors Recovery Offset : 5019136 sectors State : clean Device UUID : dab59262:f6d1a8da:fdc1485f:a1b34c4d Update Time : Fri Nov 18 21:33:51 2016 Checksum : afcfde68 - correct Events : 13 Device Role : Active device 0 Array State : AA ('A' == active, '.' == missing)

---edit---
and also this commandline (which it is used by the boot script)
Code:
/sbin/mdadm --examine --brief /dev/sda8
/sbin/mdadm --examine --brief /dev/sdb8

Code: Select all: root@(none):/ # /sbin/mdadm --examine --brief /dev/sda8 ARRAY /dev/md/0 metadata=1.0 UUID=1902932f:dd39c09d:c9d35e37:d2eab7ba name=0 root@(none):/ # /sbin/mdadm --examine --brief /dev/sdb8 ARRAY /dev/md/0 metadata=1.0 UUID=1902932f:dd39c09d:c9d35e37:d2eab7ba name=0 root@(none):/ #

by **Jocko** » Sat Nov 19, 2016 11:42 am

ok,

we go to try to assemble manually md1:

Code: Select all: mdadm --assemble /dev/sda8 /dev/sdb8

and see its status

mdadm --detail /dev/md0
mdadm --detail --scan

by **jungfichte** » Sat Nov 19, 2016 11:45 am

Code: Select all: root@(none):/ # mdadm --assemble /dev/sda8 /dev/sdb8 mdadm: device /dev/sda8 exists but is not an md array. root@(none):/ # mdadm --detail /dev/md0 mdadm: cannot open /dev/md0: No such device or address root@(none):/ # mdadm --detail --scan root@(none):/ #

by **Jocko** » Sat Nov 19, 2016 11:55 am

Sorry I gave a bad mdadm commandline.

So repeat with

mdadm --asemble /dev/md0

:doh

by **jungfichte** » Sat Nov 19, 2016 12:21 pm

no problem ;)

root@(none):/ # mdadm --asemble /dev/md0
mdadm: unrecognized option `--asemble'
Usage: mdadm --help
for help
root@(none):/ # mdadm --assemble /dev/md0
mdadm: /dev/md0 not identified in config file.
root@(none):/ #

by **Jocko** » Sat Nov 19, 2016 12:25 pm

indeed as you are on fvdw-sl console environnement, it fails to read mdadm.conf :cry:

So this time the right command is

Code: Select all: mdadm --assemble /dev/md0 /dev/sda8 /dev/sdb8

plugout.net

NAS doesn't boot after setup Raid

NAS doesn't boot after setup Raid

Re: NAS doesn't boot after setup Raid

Re: NAS doesn't boot after setup Raid

Re: NAS doesn't boot after setup Raid

Re: NAS doesn't boot after setup Raid

Re: NAS doesn't boot after setup Raid

Re: NAS doesn't boot after setup Raid

Re: NAS doesn't boot after setup Raid

Re: NAS doesn't boot after setup Raid

Re: NAS doesn't boot after setup Raid

Who is online