Having Issues with my NAS. Shares missing, WebUI broken.

[Woodani]

Hi,

I'm back again needing help with my NAS.

I noticed yesterday that my NAS had a red light on drive bay 1. I hadn't used the NAS in a few days so I figured I better log into the WebUI and look and see if that disk had failed or what was going on. When I logged on I noticed right away the webui was looking kind of... broken. I'll try to attach some screen shots of what it looks like, but basically things that should say "Setup" instead say "MnuSetup" or instead of "System Info" I've got "SysInfo".

$matches[2]

Also some sub-menu items seem to be missing. I had an issue similar to this once before and a simple reboot took care of it. So that was the first thing I tried this time. Unfortunately no luck. After the reboot the webui still looks the same however the red LED on disk 1 went back to blue which is good I guess.

At this point I decided I had better look in my share folder and see if my files were still intact. Nope. My shares seam to be complete missing at this point. Browsing in windows to \\(IP of NAS) gives me an empty directory with none of my shares to be found. I also have Plex running on a Linux box with the NAS acting as its library and that library seams to be missing from there as well. If I look in "MnuFileShare" in the webui it only has the option to CreateNewShare.

2020-12-08 20_52_27-Settings.png

I'm pretty sure if everything was working properly this is where my shares would be listed.

I've put a ton of data on this NAS after you helped me get it working a few months ago. I really don't want to loose all that if at all possible.

Thanks in advance for your help.

[fvdw]

Sorry to hear this.
Probably there is some issue with the system partition. Most likely your data will be ok as it is on other partitions, no panic yet ;)

Do you still have ssh access to your 5big2 ?

If yes log in then we can investigate what is wrong. To start with that post output of

Code: Select all

mount
cat boot.log
ls -al /lacie-boot

[Jocko]

Hi

According with your screen capture, I think you have a faulty disk on sda which may explain why the dictionary is not loaded and some other menus.

To have a red LED on a slot disk, if you do not use a raid means the fw detects a corrupted fs on its data partition (and then the partition should not be mounted : you can not see your data)

[Woodani]

Hey,

Thanks for the replies. I was able to ssh into the nas, here are the results of the commands you wanted to see.

Code: Select all

root@fvdwsl-base:/ # mount
/dev/sda1 on / type ext3 (rw,relatime,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
/dev/sda5 on /rw_fs type ext3 (rw,noatime,data=ordered)
tmpfs on /rw_fs/tmp/usr/var type tmpfs (rw,relatime,size=5000k)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/dev/md0 on /share/1100 type ext4 (rw,noatime,nodelalloc,stripe=512,data=ordered)
/dev/sda7 on /lacie-boot type ext3 (rw,relatime,data=ordered)
root@fvdwsl-base:/ # cat boot.log
start boot log
is a physical machine
detect and set platform
5big2
kirkwood
UIMAGE-414133-KIRKWOOD-1
Current kernel: 4.14.133 #1 PREEMPT Wed Jul 17 14:46:56 CEST 2019
5big2
kirkwood
 mount dev/pts
update dev nodes
booting using sda1 root file system...
enable IP forwarding...
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'iscsi_trgt' not found
start buttons control daemon
device = 5big2
source = buttons-nwsp2
buttons-nwsp2 daemon started
Mon Apr 23 09:04:48 EDT 2018
create temporary passwd file
create temporary group file
set samba environment for version 4.x
configure loopback network interface
setting reboot and standby
5big2
rebootd-nwsp2
5big2
standbyd-nwsp2
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:  [ OK ]
 * Finishing restore RAID devices...     [ OK ]
 * Found database configuration file...  [ OK ]
 * Updating Disks database...                    [ OK ]
 * Starting mount of volumes...
   - Mounting volume 5-Disk-Raid-5:  [ OK ]
 * Finishing mount of volumes...                 [ OK ]
 * Generating Hosts File...                      [ OK ]
 * Configuring System Hostname...                [ OK ]
 * Configuring Bonding interface...      [ 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 NTP client...                                [ OK ]
 * Starting vnstat daemon...                     [ OK ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
    This is fvdw-sl version: fvdw-sl 18.2
    built on: October 18 2019

    LAN IP address: 192.168.1.185 (static)

    Port configuration:

    LAN   -> bond0
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
LED settings
else loop1 finished
rcS finished
root@fvdwsl-base:/ # ls -al /lacie-boot
total 8
drwxrwxr-x   2 root root 4096 2018-01-06 03:05 .
drwxr-xr-x  23 root root 4096 2018-04-23 09:05 ..
-rw-r--r--   1 root root    0 2018-01-06 03:05 sda1boot

I was worried it could possibly be a faulty disk. Although I have not seen the red LED anymore after the first reboot and from what little I can understand from that boot.log file the raid seems to start with an OK and the disks mount with an OK. I'm sure you will be able to tell better if there are any problems in there. Wile I wait for your replies I will see if I can come up with a spare HDD in case this one needs to be replaced.

Thanks.

[Jocko]

Hi

For me all is ok.
About raid, around 20 min is required so that a temporary bad status (eg. resyncing) is updated with the led behaviour (maybe it was your case)
canyou post this output

Code: Select all

mdadm --detail /dev/md0
cat /proc/mdstat

other point can you confirm, you have access on your data

[Woodani]

Hi,

Certainly. Here is that info:

Code: Select all

root@fvdwsl-base:/ # mdadm --detail /dev/md0
/dev/md0:
        Version : 1.0
  Creation Time : Mon Jan  1 07:03:58 2018
     Raid Level : raid5
     Array Size : 15616464896 (14893.02 GiB 15991.26 GB)
  Used Dev Size : 3904116224 (3723.26 GiB 3997.82 GB)
   Raid Devices : 5
  Total Devices : 5
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Tue Apr 24 01:06:24 2018
          State : clean
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 512K

           Name : fvdwsl-base.local:0  (local to host fvdwsl-base.local)
           UUID : 35290b17:a118a68b:8ca0e64f:f1a01f89
         Events : 2

    Number   Major   Minor   RaidDevice State
       0       8       40        0      active sync   /dev/sda8
       1       8       24        1      active sync   /dev/sdb8
       2       8        8        2      active sync   /dev/sdc8
       3       8       72        3      active sync   /dev/sdd8
       4       8       56        4      active sync   /dev/sde8
root@fvdwsl-base:/ # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md0 : active raid5 sda8[0] sde8[4] sdd8[3] sdc8[2] sdb8[1]
      15616464896 blocks super 1.0 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]
      bitmap: 0/30 pages [0KB], 65536KB chunk

unused devices: <none>

Also, No I currently do NOT have access to any of my data.

Thanks.

[fvdw]

To check if your data is present in the raid array you can give this command

Code: Select all

ls -al /share/1100

If the shares are listed I think we must search te problem in the apache webserver

[Jocko]

in addition with fvdw's post
About your data, do you use windows 10 and currently you set only public shares on your nas ?
(with windows 10, you have to enable the guess login)

need to find the related topic on our board


--edit---
the related topic: https://plugout.net/viewtopic.php?f=9&t=3169

[fvdw]

...... I will see if I can come up with a spare HDD in case this one needs to be replaced.

You cannot replace the disk sda in slot 1 (most lefhand side slot seen from back of the 5big2) just like that as it contains the firmware and is needed for booting and runing the firmware. The disk contains several partitions only one of them (sda8) is containing your data and is part of the raid array The story is different for the other 4 disks. Those contain only a data partition

[Woodani]

Code: Select all

root@fvdwsl-base:/ # ls -al /share/1100
total 40
drwxrwxr-x   7 root sys   4096 2018-01-12 08:49 .
drwxrwxr-x   4 root sys   4096 2018-04-23 09:05 ..
drwxrwxrwx   2 root root  4096 2018-01-01 07:54 Backups
drwxr-xr-x   3 root root  4096 2018-01-12 08:49 fvdw
drwx------   2 root root 16384 2018-01-01 07:04 lost+found
drwxrwxrwx  11 root root  4096 2018-03-25 09:30 NAS_Storage
drwxrwxrwx   8 root root  4096 2018-01-12 08:58 Plex_Media

Good news. Looks like all my shares are there.

As far as the shares being public only, I believe they are password protected. I use both Windows 10 and Fedora Linux to access this NAS and they both are unable to see the shares. I know I had to enable samba1 support in windows 10 and do some configuring that I don't remember in Fedora before I figured out how to get the addons working for samba3. Everything was working fine before the red HDD light.

You cannot replace the disk sda in slot 1 (most lefhand side slot seen from back of the 5big2) just like that as it contains the firmware and is needed for booting and runing the firmware.

Of course that is the disk I'm having issues with... :pissed just my luck. But I also kind of knew that from the installation process. I just meant that I would try to have a HDD on hand if this one was totally dead and I had to reinstall the firmware again.

Thanks.