Replaced and initialised HDD. RAID no longer intact

[boerie]

root@LacieNAS:/ # cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid5 sdd8[4] sdb8[0] sde8[3] sdc8[1]
11712345600 blocks super 1.0 level 5, 512k chunk, algorithm 2 [4/3] [UU_U]
[===>.................] recovery = 18.8% (735943000/3904115200) finish=4075.6min speed=12955K/sec

unused devices: <none>
root@LacieNAS:/ #

4075 mins to go!! Will update again in 3 days

Thank you

[boerie]

Hello

All done

Do I reboot?

Thank you

root@LacieNAS:/ # cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid5 sdd8[4] sdb8[0] sde8[3] sdc8[1]
11712345600 blocks super 1.0 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]

unused devices: <none>
root@LacieNAS:/ #

[Jocko]

Hi
:thumbup

So your raid is now clean ! before rebooting I would want to test if the fs is not corrupted on md0. So do

Code: Select all

mkdir /tmp/md0
mount /dev/md0 /tmp/md0
ls -l /tmp/md0

You should see your shares

If it is the case reboot the nas and look at what status is reported in disk setup menu

[boerie]

Oh dear


root@LacieNAS:/ # mkdir /tmp/md0
root@LacieNAS:/ # mount /dev/md0 /tmp/md0
mount: /rw_fs/tmp/md0: wrong fs type, bad option, bad superblock on /dev/md0, missing codepage or helper program, or other error.
root@LacieNAS:/ #

[boerie]

Oh dear


root@LacieNAS:/ # mkdir /tmp/md0
root@LacieNAS:/ # mount /dev/md0 /tmp/md0
mount: /rw_fs/tmp/md0: wrong fs type, bad option, bad superblock on /dev/md0, missing codepage or helper program, or other error.
root@LacieNAS:/ #

[Jocko]

:pissed
So reboot the nas and load to the disk setup menu. Open the edit volume of your raid. It should be named Raid5.
Here run the fs check. And see what errors are detected and repaired... :-?

[boerie]

Is it the “make a raid volume” button?

[Jocko]

Hi
:dry

You do not have the link to edit the raid volume settings because the firmware failed to assemble the raid on nas booting :?:
So post

Code: Select all

cat /boot.log

check what error is reported when you did it manually.

Code: Select all

ls -l /etc/mdadm.conf
cat /etc/mdadm.conf   (remove personal data like email address)
mdadm --assemble /dev/md0 --run
cat /proc/mdstat

if you get your raid, you can try to repair its fs

Code: Select all

e2fsck -fy /dev/md0

(be careful this may run for a long time : do not close the shell window)

[boerie]

Hello

Here is the output

Thank you

Code: Select all

root@LacieNAS:/ # cat /boot.log
start boot log
is a physical machine
detect and set platform
5big1
5big1
UIMAGE-3142-5BIG1-33
Current kernel: 3.14.2 #33 Sun Nov 15 23:37:25 CET 2020
device 5big1
family 5big1
Arm: found valid system disk sda
system disk = sda
 mount dev/pts
update dev nodes
booting using sda2 root file system...
enable IP forwarding...
run udevstart to update dev nodes when necessary
inserting kernel modules:
start buttons control daemon
device = 5big1
source = buttons-5big1
buttons-5big1 version 1 daemon started
 parent proces pid = 688 parent proces stop
Tue Oct 21 19:04:51 UTC 2025
configuration partition is rightly mounted
create temporary passwd file
create temporary group file
set samba environment for version 3.0.37
configure loopback network interface
setting reboot and standby
5big1
rebootd-isp1
5big1
standbyd-isp1
start fan
starting php based setup routines step 1
 * Initialize the volatile db file...    [ OK ]
 * Starting udevd...                              [ OK ]
 * Starting RAID monitor:                         [ OK ]
 * Starting restore RAID devices...
   - Assembling device /dev/md0:  [ Fail ]
 * Finishing restore RAID devices...     [ Fail ]
 * Found database configuration file...  [ OK ]
 * Updating Disks database...                    [ OK ]
 * Starting mount of volumes...
   - Mounting volume Vol-A:  [ OK ]
 * Finishing mount of volumes...                 [ OK ]
 * Generating Hosts File...                      [ OK ]
 * Configuring System Hostname...                [ OK ] 
 * Configuring LAN interface...                  [ OK ]
 * Initializing Timezone...                      [ OK ]
 * Starting web server...
        Configure WebDav service :                [ OK ]
        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 ]
 * Starting ZeroConf Service...                  [ 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 VPN-pptpd Server...                  [ OK ]
 * Starting daemon update Hosts File...  [ OK ]
 * Starting NTP Server ...                        [ OK ]
 * Starting mount of remote shares...
 * Finishing mount shares...                     [ OK ]
 * Starting AFP Service...                        [ OK ]
 * Starting NTP client...                         [ OK ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
    This is fvdw-sl version: fvdw-sl 18.3
    built on: February 20 2024

    LAN IP address: 192.168.0.193 (DHCP)

    Port configuration:

    LAN   -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
move smbd en nmbd db files away from ram disk to prevent hanging samba server

------------------------
Monitor if file system check is required on next booting
LED settings

Send a boot mail notification xxx
else loop1 finished
rcS finished

Code: Select all

root@LacieNAS:/ #
[                        locale
ab                       localedef
ad                       logger
addgroup                 login
adduser                  logname
adjtimex                 logread
afp_client               logresolve
afpcmd                   logsave
afpd                     losetup
afpfs                    lowntfs-3g
afpfsd                   ls
afpgetstatus             lsattr
afpldaptest              lsmod
afppasswd                lsof
afpstats                 lsscsi
annotate                 lsusb
apachectl                lsusb.py
apple_dump               lzcat
apr-1-config             lzcmp
apr-config               lzdiff
apu-1-config             lzegrep
apu-config               lzfgrep
apxs                     lzgrep
ar                       lzless
....
libvorbisenc.so.2        xzless
libvorbisenc.so.2.0.6    xzmore
libvorbisfile.so         yes
libvorbisfile.so.3       zcat
libvorbisfile.so.3.3.2   zdump
link                     zfs
ln                       zic
loadfont                 zip
loadkmap

Code: Select all

root@LacieNAS:/ # ls -l /etc/mdadm.conf
lrwxrwxrwx  1 root root 21 2017-05-27 17:41 /etc/mdadm.conf -> /rw_fs/etc/mdadm.conf
root@LacieNAS:/ # cat /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*

MAILADDR xxx

ARRAY /dev/md0 metadata=1.0 level=raid5 num-devices=4 UUID=1a941ae0:d0e32eb5:6d41a0f6:99054107
root@LacieNAS:/ # cat /etc/mdadm.conf

root@LacieNAS:/ # mdadm --assemble /dev/md0 --run
root@LacieNAS:/ # cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
unused devices: <none>
root@LacieNAS:/ #

[Jocko]

Hi

You do not have the right UUID of your raid in madadm.conf !!! I do not know how you did it :whistle

So do

Code: Select all

sed -rie 's/UUID=.*/UUID=a6a81cbf:e6e4dd12:4e969bc3:4d662a7d/g' /rw_fs/etc/mdadm.conf
cat /etc/mdadm.conf

check if you have now 'a6a81cbf:e6e4dd12:4e969bc3:4d662a7d' instead of '1a941ae0:d0e32eb5:6d41a0f6:99054107' as UUID in mdadm.conf file

if yes do

Code: Select all

mdadm --assemble /dev/md0 --run
cat /proc/mdstat

if the firmware succeeded to assemble your raid you can reboot the nas. Check if you have this time your raid volume from disk setup menu. Click on its name (which opens the edit menu and here you will find the button to run a fs check)

Note: how did you get this output ?

Code: Select all

root@LacieNAS:/ #
[                        locale
ab                       localedef
ad                       logger
addgroup                 login
adduser                  logname
adjtimex                 logread
afp_client               logresolve
afpcmd                   logsave
afpd                     losetup
afpfs                    lowntfs-3g
afpfsd                   ls
afpgetstatus             lsattr
afpldaptest              lsmod
afppasswd                lsof
afpstats                 lsscsi
annotate                 lsusb
apachectl                lsusb.py
apple_dump               lzcat
apr-1-config             lzcmp
apr-config               lzdiff
apu-1-config             lzegrep
apu-config               lzfgrep
apxs                     lzgrep
ar                       lzless
....
libvorbisenc.so.2        xzless
libvorbisenc.so.2.0.6    xzmore
libvorbisfile.so         yes
libvorbisfile.so.3       zcat
libvorbisfile.so.3.3.2   zdump
link                     zfs
ln                       zic
loadfont                 zip
loadkmap

Note2: please to use the BBcode [ code][/ code] see: faq.php?mode=bbcode#f2r1 which allows to get a more readable a message when you post an output. Upto now I edited all your posts!