Latest FW for NAS540 lost my Disk Group

lnxcwby

I updated to V5.21(AATB.13), and now the Disk Group is no longer showing up, and neither is Disk2 (shows a fault in the RAID, but will not allow a hot swap). I had a new spare and put it in the Disk2 slot, after verifying it, and still nothing showing in Disk2.

Tried to downgrade firmware to AATB.7, and it wouldn't allow the downgrade.

Suggestions? I'm quite frustrated, and don't want to have to buy a new NAS.

lnxcwby

UPDATE

I found how to force the ability to downgrade:

echo 1 >/firmware/mnt/info/revision

Unfortunately, the Disk Group is still missing. Am I completely screwed here?

Mijzelf

Can you post the outputs of

cat /proc/partitions
cat /proc/mdstat
cat /proc/mounts
su
vgdisplay

lnxcwby

Certainly!

login: can't chdir to home directory '/home/shares'

BusyBox v1.19.4 (2021-04-01 10:35:24 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/ $ cat /proc/partitions
major minor #blocks name

7 0 146432 loop0
31 0 256 mtdblock0
31 1 512 mtdblock1
31 2 256 mtdblock2
31 3 10240 mtdblock3
31 4 10240 mtdblock4
31 5 112640 mtdblock5
31 6 10240 mtdblock6
31 7 112640 mtdblock7
31 8 6144 mtdblock8
8 0 2930266584 sda
8 1 1998848 sda1
8 2 1999872 sda2
8 3 2926266368 sda3
8 16 2930266584 sdb
8 17 1998848 sdb1
8 18 1999872 sdb2
8 19 2926266368 sdb3
8 32 2930266584 sdc
8 33 1998848 sdc1
8 34 1999872 sdc2
8 35 2926266368 sdc3
31 9 102424 mtdblock9
9 0 1997760 md0
9 1 1998784 md1
31 10 4464 mtdblock10
9 2 8778405888 md2
/ $ cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md2 : active raid5 sda3[0] sdc3[4] sdb3[2]
8778405888 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/3] [U_UU]

md1 : active raid1 sda2[0] sdc2[4] sdb2[2]
1998784 blocks super 1.2 [4/3] [U_UU]

md0 : active raid1 sda1[0] sdc1[4] sdb1[2]
1997760 blocks super 1.2 [4/3] [U_UU]

unused devices: <none>
/ $ cat /proc/mounts
rootfs / rootfs rw 0 0
/proc /proc proc rw,relatime 0 0
/sys /sys sysfs rw,relatime 0 0
none /proc/bus/usb usbfs rw,relatime 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
ubi5:ubi_rootfs1 /firmware/mnt/nand ubifs ro,relatime 0 0
/dev/md0 /firmware/mnt/sysdisk ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/loop0 /ram_bin ext2 ro,relatime,user_xattr,barrier=1 0 0
/dev/loop0 /usr ext2 ro,relatime,user_xattr,barrier=1 0 0
/dev/loop0 /lib/security ext2 ro,relatime,user_xattr,barrier=1 0 0
/dev/loop0 /lib/modules ext2 ro,relatime,user_xattr,barrier=1 0 0
/dev/loop0 /lib/locale ext2 ro,relatime,user_xattr,barrier=1 0 0
/dev/ram0 /tmp/tmpfs tmpfs rw,relatime,size=5120k 0 0
/dev/ram0 /usr/local/etc tmpfs rw,relatime,size=5120k 0 0
ubi3:ubi_config /etc/zyxel ubifs rw,relatime 0 0
/dev/md2 /i-data/46e46fc8 ext4 rw,noatime,user_xattr,barrier=1,stripe=48,data=ordered,usrquota 0 0
/dev/md2 /usr/local/apache/htdocs/desktop,/pkg ext4 rw,noatime,user_xattr,barrier=1,stripe=48,data=ordered,usrquota 0 0
nfsd /proc/fs/nfsd nfsd rw,relatime 0 0
configfs /sys/kernel/config configfs rw,relatime 0 0
/ $ su
Password:

BusyBox v1.19.4 (2021-04-01 10:35:24 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ # vgdisplay
File descriptor 19 (/dev/urandom) leaked on vgdisplay invocation. Parent PID 20877: sh

~ #
~ # vgdisplay
File descriptor 19 (/dev/urandom) leaked on vgdisplay invocation. Parent PID 20877: sh
~ #

Mijzelf

There is a disk in slot 2 at the moment? And you also had another disk in that slot? The disk is not seen at all. It's device name (/dev/sdb) is in use by the disk in slot 3.

I'm afraid either the SATA port or the power supply in slot 2 died.

lnxcwby

That's what I was afraid of, that the hardware was at fault.

I guess it's time for a new NAS.

Thanks for another set of eyes!