Fails to update TOS 5.1.x, the TOS webpage keeps showing blank after reboot?

[splaquet]

I have a T5-420 w/ 3 12TB drives and a 500GB SSD for cache.

So… at some point during the media caching, i checked in and it worked (but it wasn’t completed).

I checked back in a day later and… well, now I’m experiencing the ”Loading..., please wait!” message… and can no longer log in.

I’m able to SSH into the system and look through everything, but don’t seem to have any other access.

…FYI, i realized that i forgot to mention that i had rebuilt the system with the HDs. After the system was up and running, that’s when i added the SSD… and followed that up with the media indexing.

##

I actually just discovered something totally off the wall.

I’m really not sure what to do… but, I would really like to have steady access to my content again

When i look at:

Code: Select all

cat /etc/network

I’m seeing:

Code: Select all

[eth2]
DNS1      = 10.0.1.1
SLAVE     = 0
DNS2      = 
IPADDRESS = 192.168.1.99
NETMASK   = 255.255.255.0
GATEWAY   = 192.168.1.1
MTU       = 1500
DHCP      = YES

[eth3]
SLAVE     = 0
DNS1      = 192.168.1.1
DNS2      = 
IPADDRESS = 192.168.1.99
NETMASK   = 255.255.255.0
GATEWAY   = 192.168.1.1
MTU       = 1500
DHCP      = YES

[eth0]
SLAVE     = 0
DNS1      = 10.0.1.1
DNS2      = 
IPADDRESS = 192.168.1.99
NETMASK   = 255.255.255.0
GATEWAY   = 192.168.1.1
MTU       = 1500
DHCP      = YES

[eth1]
SLAVE     = 0
DNS1      = 10.0.1.1
DNS2      = 
IPADDRESS = 192.168.1.99
NETMASK   = 255.255.255.0
GATEWAY   = 192.168.1.1
MTU       = 1500
DHCP      = YES

Here’s the big question…
1) my gateway is 10.0.1.1
2) my static IP is 10.0.1.70
3) the ”Loading..., please wait!” message appears on https://10.0.1.70:5443/
4) nothing shows up on 192.168.1.99

This page sums up my issue… AND my frustrations!!
viewtopic.php?f=9&t=4345&p=25093&hilit= ... .99#p25093

[TMzethar]

{L_BUTTON_AT}splaquet

Regarding "Loading, Please wait Question, have you understood the explanation at the beginning of this topic post? If you can access the system through SSH, you can try the following two methods: 1. Check and fix possible file system issues viewtopic.php?f=79&t=2575 2. If you are a BTRFS file system, please disable 'quota':

Code: Select all

btrfs quota disable /Volume1

As for the other issue you mentioned that is unrelated to this topic, we are trying to reproduce and investigate it.

[topo01]

TM:
You're allowed to feel a sense of frustration in the following lines:

It's more than 6 weeks now since TM has discovered the issue with the too small system partition. I don't see the slightest indication that you are working on a solution. All I read is "don't upgrade to 5.1" or "delete your disks and re-initialize". Is that really all I can expect from a consumer device that's advertised as a safe place for my data???

I suppose this issue affects the majority of users.

So what's your plan TM?

[splaquet]

{L_BUTTON_AT}splaquet

Regarding "Loading, Please wait Question, have you understood the explanation at the beginning of this topic post?

I thought that I understood, but maybe not entirely? I might have missed the part that read, “When you have a fully function TOS GUI interface, that does not mean that everything is okay. Adding an additional SSD drive into the system and activating media caching WILL HAVE THE POTENTIAL to corrupt your TOS system, preventing you from logging into the GUI again. But, as long as you still have SSH access, you’ll most likely be able to restore the working state of your TOS system.” I’ll have to double check on the BTRFS when I’m back home.

[TMzethar]

{L_BUTTON_AT}splaquet

What do you mean by 'media caching' by something similar?
This is not a POTENTIAL to corruption for the TOS system.
You can give it a try.

[splaquet]

I'm saying that everything was 100% working as expected for me... until I added in the SSD drive back in and activated media caching.

After the media had been indexed, that's when I started seeing this message. Maybe it was coincidence, but other than changing a few ports (2222 for SSH), it was literally the only other change that I made... and I haven't been able to log back in since.

##

I referenced that link that you shared, to pull info with DMESG command. does any of this indicate anything?

Code: Select all

# dmesg|grep fail
[    0.374121] pci 0000:00:1c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.374297] pci 0000:00:1c.1: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.374459] pci 0000:00:1c.2: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.374620] pci 0000:00:1c.3: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.374785] pci 0000:00:1c.3: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.374946] pci 0000:00:1c.2: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.375108] pci 0000:00:1c.1: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    0.375277] pci 0000:00:1c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[    1.194114] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    1.194214] cfg80211: failed to load regulatory.db
[   13.457751] r8169 0000:01:00.0: Direct firmware load for rtl_nic/rtl8168e-3.fw failed with error -2
[   15.533175] r8169 0000:02:00.0: Direct firmware load for rtl_nic/rtl8168e-3.fw failed with error -2

# dmesg|grep error
[    1.194114] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   13.457751] r8169 0000:01:00.0: Direct firmware load for rtl_nic/rtl8168e-3.fw failed with error -2
[   15.533175] r8169 0000:02:00.0: Direct firmware load for rtl_nic/rtl8168e-3.fw failed with error -2
[   55.457525] postgres[2009]: segfault at 0 ip 00007f1035deffaa sp 00007ffe209fe678 error 4 in libc-2.26.so[7f1035d64000+1a7000]
[   85.352500] postgres[2315]: segfault at 0 ip 00007f1035deffaa sp 00007ffe209fe678 error 4 in libc-2.26.so[7f1035d64000+1a7000]
[  106.390770] postgres[2883]: segfault at 0 ip 00007f1035deffaa sp 00007ffe209fe678 error 4 in libc-2.26.so[7f1035d64000+1a7000]
[  135.460482] postgres[3775]: segfault at 0 ip 00007f1035deffaa sp 00007ffe209fe678 error 4 in libc-2.26.so[7f1035d64000+1a7000]

# dmesg|grep segfault
[   55.457525] postgres[2009]: segfault at 0 ip 00007f1035deffaa sp 00007ffe209fe678 error 4 in libc-2.26.so[7f1035d64000+1a7000]
[   85.352500] postgres[2315]: segfault at 0 ip 00007f1035deffaa sp 00007ffe209fe678 error 4 in libc-2.26.so[7f1035d64000+1a7000]
[  106.390770] postgres[2883]: segfault at 0 ip 00007f1035deffaa sp 00007ffe209fe678 error 4 in libc-2.26.so[7f1035d64000+1a7000]
[  135.460482] postgres[3775]: segfault at 0 ip 00007f1035deffaa sp 00007ffe209fe678 error 4 in libc-2.26.so[7f1035d64000+1a7000]

# dmesg|grep ext4

# dmesg|grep btrfs

# dmesg|grep Volume

# dmesg|grep ':md'
[    2.500016] md/raid1:md9: active with 1 out of 72 mirrors
[   46.082255] md/raid1:md1: active with 1 out of 1 mirrors
[   55.518144] md/raid1:md8: active with 1 out of 72 mirrors
[   55.968925] md/raid:md0: device sdc4 operational as raid disk 0
[   55.969007] md/raid:md0: device sdb4 operational as raid disk 2
[   55.969078] md/raid:md0: device sdd4 operational as raid disk 1
[   55.970324] md/raid:md0: raid level 5 active with 3 out of 3 devices, algorithm 2

# btrfs check /dev/mapper/vg0-lv0
Opening filesystem to check...
ERROR: mount check: cannot open /dev/mapper/vg0-lv0: No such file or directory
ERROR: could not check mount status: No such file or directory

[splaquet]

{L_BUTTON_AT}splaquet

2. If you are a BTRFS file system, please disable 'quota':

Code: Select all

btrfs quota disable /Volume1

One item that I've only now realized... I don't have a /Volume1, but I do have a /Volume2

Code: Select all

drwxr-xr-x   	22 	splaquet splaquet 4.0K Jun 21  2023 .
drwxr-xr-x   	22 	splaquet splaquet 4.0K Jun 21  2023 ..
drwxr-xr-x    	2 	splaquet splaquet 4.0K Apr 27 18:59 bin
drwxr-xr-x    	2 	splaquet splaquet 4.0K Apr 27 20:44 boot
drwxr-xr-x   	11 	splaquet splaquet 3.6K Jun 21 14:03 dev
drwxr-xr-x   	84 	splaquet splaquet 4.0K Jun 21 14:04 etc
drwxr-xr-x   	75 	splaquet splaquet 4.0K Apr 27 18:59 etc.default
drwxr-xr-x+   	1 	splaquet splaquet  296 Nov 23  2022 home
-rwxr-xr-x    	1 	splaquet splaquet  702 Apr 27 18:59 init
drwxr-xr-x   	13 	splaquet splaquet 4.0K Apr 27 18:59 lib
lrwxrwxrwx    	1	 splaquet splaquet    3 Apr 27 18:59 lib64 -> lib
drwxr-xr-x    	2 	splaquet splaquet 4.0K Apr 27 18:59 media
drwxr-xr-x    	3 	splaquet splaquet 4.0K May 27 02:22 mnt
drwxr-xr-x    	3 	splaquet splaquet 4.0K May 27 10:04 opt
dr-xr-xr-x  	251 	splaquet splaquet    0 Jun 21  2023 proc
drwxr-xr-x    	2 	splaquet splaquet 4.0K Jun 21  2023 root
drwxr-xr-x    	9 	splaquet splaquet  440 Jun 21 14:04 run
drwxr-xr-x    	2 	splaquet splaquet 4.0K Apr 27 20:49 sbin
drwxr-xr-x    	3 	splaquet splaquet 4.0K Apr 27 18:59 share
dr-xr-xr-x   	12 	splaquet splaquet    0 Jun 21  2023 sys
drwxrwxrwt   	13 	splaquet splaquet  460 Jun 21 14:02 tmp
drwxr-xr-x   	12 	splaquet splaquet 4.0K May 27 02:06 usr
lrwxrwxrwx    	1 	splaquet splaquet    8 Jun 21  2023 var -> /opt/var
drwxr-xr-x    	1 	splaquet splaquet  778 Jun 21 14:03 Volume2
drwxr-xr-x   	19 	splaquet splaquet 4.0K Apr 27 19:00 xvar

[TMroy]

For specific issues, you need to create a new post.

[Reva]

The system partition storage capacity of TNAS has been used up, which leads to incomplete system updates and system failure to boot, as we discovered by examining a few situations. These devices all share the trait of using TOS 4.x or even TOS 3.x as their basic operating system.

[freman]

Just need someone to lend me 50tb of drives so I can migrate... I actually have a USB/SAS external bay from an earlier nas project... just need drives to fill it up with temporarily lol