NAS326 500 Internal Server Error
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
When accessing network share the all vol show but all return the 500 error showing no content
When accessing device with Storage Manager no info returned only 'swirling clock"
Can anyone help??
Thanks,
All Replies
-
0
-
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.
0 -
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.
0 -
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.
0 -
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 png0 -
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'.
0 -
Here is the output from dmesg:
Thanks,
0 -
Sorry, Posted the wrong file: See below:
0 -
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.
0 -
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.
0
Categories
- All Categories
- 415 Beta Program
- 2.5K Nebula
- 152 Nebula Ideas
- 101 Nebula Status and Incidents
- 5.8K Security
- 296 USG FLEX H Series
- 281 Security Ideas
- 1.5K Switch
- 77 Switch Ideas
- 1.1K Wireless
- 42 Wireless Ideas
- 6.5K Consumer Product
- 254 Service & License
- 396 News and Release
- 85 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.6K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 87 About Community
- 76 Security Highlight