[Help] F4-210 NAS Fails to Boot with Multiple Independent Disks

[TMbuddy]

This is the update notes for TOS 4.2.44. Please review them, and we hope this resolves your issue!
viewtopic.php?t=6002

[AlAleksiev]

Below the log of "/etc/tos/scripts/mntdata" It started ok with disk 1 and 2 inserted then I added 3 and 4 and execute the commad

Code: Select all

Welcome to TNAS
root@TNAS-01573E:~# /etc/tos/scripts/mntdata
script mntdata get lock
dev.raid.speed_limit_max = 200000
dev.raid.speed_limit_min = 100000
mdadm: sdd2 does not appear to be a component of /dev/md9
mdadm: added /dev/sdd2
mdadm: sde2 does not appear to be a component of /dev/md9
mdadm: added /dev/sde2
mdadm: /dev/md9: no change requested
mdadm: sdd3 does not appear to be a component of /dev/md8
mdadm: added /dev/sdd3
mdadm: sde3 does not appear to be a component of /dev/md8
mdadm: added /dev/sde3
mdadm: /dev/md8: no change requested
mdadm: Fail create md1 when using /sys/module/md_mod/parameters/new_array
mdadm: /dev/md1 has been started with 1 drive.
mdadm: Fail create md3 when using /sys/module/md_mod/parameters/new_array
mdadm: /dev/md3 has been started with 1 drive.
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd (created here) takes precedence over ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  Volume group "vg2" successfully renamed to "gr3"
  Volume group "gr3" successfully renamed to "vg3"
check filesystem on /dev/vg1/lv1
  Reading all physical volumes.  This may take a while...
  Found volume group "vg3" using metadata type lvm2
  Found volume group "vg2" using metadata type lvm2
  Found volume group "vg1" using metadata type lvm2
  Found volume group "vg0" using metadata type lvm2
Starting Flashcache...
Waiting for udev to settle...
/sbin/flashcache_scan: line 16: /sbin/udevadm: not found
check filesystem on /dev/vg3/lv3
  Reading all physical volumes.  This may take a while...
  Found volume group "vg3" using metadata type lvm2
  Found volume group "vg2" using metadata type lvm2
  Found volume group "vg1" using metadata type lvm2
  Found volume group "vg0" using metadata type lvm2
Starting Flashcache...
Waiting for udev to settle...
/sbin/flashcache_scan: line 16: /sbin/udevadm: not found
public 1
appdata 1
F1Storica 1
Film-HD 1
Film-con-DVD 1
Film-senza-dvd-corto 1
Film_Famiglia 1
Formula1 1
Foto_Famiglia 1
Musica-Definitiva 1
SerieTV 1
Film-No-DVD 1
Archivio-Buckup-new 1
Video-Doppioni-Duplicati 1
Archivio 1
coresize=3072
swapsize=2048
fireware=https://download3.terra-master.com/TOS%20packages/TOS%20installation%20packages/4.2/arm%20realtek1296/TOS_A1.0_Install_ARM4.2_4.2.44_LTS23061206_2403260950.ins
md5=8821252485b99b357d145b972289a073
version=4.2.44

script mntdata put lock
root@TNAS-01573E:~#

Hey guys, just trying to add some value here - in the above log it seems like the Volume Groups (VGs), on the different disks, are with the same name.

The conflict is hapening when "/dev/md3 has been started with 1 drive" and this is a visible problem that could be resolved to not contribute to (or cause) the issue.
The easiest way is to start the NAS with only one disk - the one that's using 'vg2' as a VG name and to rename the volume. For example:

Code: Select all

$ sudo vgrename vg2 vg2dup

After that you can try to test again with all the disks and /etc/tos/scripts/mntdata

Good luck

[antocara]

[/quote]

Hey guys, just trying to add some value here - in the above log it seems like the Volume Groups (VGs), on the different disks, are with the same name.

The conflict is hapening when "/dev/md3 has been started with 1 drive" and this is a visible problem that could be resolved to not contribute to (or cause) the issue.
The easiest way is to start the NAS with only one disk - the one that's using 'vg2' as a VG name and to rename the volume. For example:

Code: Select all

$ sudo vgrename vg2 vg2dup

After that you can try to test again with all the disks and /etc/tos/scripts/mntdata

Good luck
[/quote]
AlAleksiev,
Thankyou very much for your suggestion.

I'll try it al let you know.

Regards

[TMzethar]

Here you can get the TOS 4.2.44 packages.
https://support.terra-master.com/downlo ... uct=F4-210

Update:
viewtopic.php?t=6002
https://download3.terra-master.com/TOS% ... 260950.bz2

or

Reinstall:
viewtopic.php?t=423
https://download3.terra-master.com/TOS% ... 260950.ins