NAS326 500 Internal Server Error

Davnel

I am receiving 500 Internal Server Error The server encountered an unexpected condition which prevented it from fulfilling the request when accessing drive (JBOD) from WEB interface - FileBrowser

Screenshot 2024-05-13 at 10.06.06 AM.png

When accessing network share the all vol show but all return the 500 error showing no content

Screenshot 2024-05-13 at 11.09.49 AM.png

When accessing device with Storage Manager no info returned only 'swirling clock"

Screenshot 2024-05-13 at 11.19.45 AM.png

Can anyone help??

Thanks,

Mijzelf

https://community.zyxel.com/en/discussion/6397/nas-542-500-internal-server-error

Davnel

I have not tried this answer - Telnet service has not be enabled on the NAS & I was not sure if the change to enable (because of the write to the disk) would cause an additional problem. If enabling Telnet would not cause any additional issues I will try.

Mijzelf

Most settings are stored on a flash partition, not on harddisk. Yet I'm not 100% sure the ssh server (telnet is not the best choice) indeed doesn't write on disk.

In case a symlink is the cause of the problem, it doesn't matter anyway, because it's not an error. Only the webinterface crashes on seemingly cyclic directory trees. In case there is actually a harddisk problem (hardware or filesystem) how are you going to diagnose that without ssh? The only option is to get the disk out and to connect it to another Linux box.

Davnel

Hi, I enabled telnet and did not find any unexpected s-link - I have never tried to manage the system by using telnet/ssh on used the web interface.

NAS still not showing any files on the device.

Davnel

I have some additional info:

The dir I-data  it had a link pointing to 
sysvol ->  /etc/zyxel/storage/sysvol
followed to /etc/zyxel/storage 
with sysvol pointing to sysvol -> /I-data/07660431 
followed to /I-data/07660431 
In /07660431
when ls -l   listed all the sub directories
when  cd  /photo 
then ls -l 
received listing  Input/output error for 8 sub-dir and along with listing for 16 directory 5 file/photos.
SEE png

DIR Roselind.png

Mijzelf

That input/output errors are either a filesystem error, or a disk error. A filesystem error might be cured by a filesystem repair, a disk error means almost certainly you'll have to replace the disk. The kernel log should tell which one it is. You can read it by executing 'dmesg'.

Davnel

Here is the output from dmesg:

Thanks,

DIR Roselind.png

Davnel

Sorry, Posted the wrong file: See below:

dmesg-Roselind.txt

Mijzelf

That doesn't look good. There are 'unhandled error code's from the harddisk, whatever that may be. If your data is valuable, you should create a bit-by-bit copy of the harddisk, and do a filesystem repair on the copy.

I suppose you have a disk slot free? In that case the copying can be done on the NAS itself. I can provide you the needed software. Get a new disk of at least the same size, and avoid writing to this disk.

Davnel

The NAS has a disk in the 2nd slot that I can replace with a new drive. I would like to save the date if possible.