Settings not applying and problems with RAID availability

[Shellm]

Hi there

Long time ago I once wrote an E-mail to Thecus Support but it seems like I never received an answer!!

The following problem description is sent to Thecus Support too:

First problem, which I reported once:
After booting the N5200 up (cold boot) the RAID is "N/A" (after a 1-second beep). I have to open the web interface and reboot the N5200 from there. After that reboot it beeps 1 second and like 15 seconds later the RAID is "healthy". This bug is very annoying because when I want to do a quick backup I don't want to boot 2 times.

Second problem (even more annoying):
I can't change ANY settings in the N5200 which require a reboot.
i.e.: WAN IP address, LAN IP address, LCD password (!!!!!), etc.
I could make changes to NFS shares (but I don't use NFS.. I just tried if it works).

System info:
- N5200B
- Firmware (current): 1.00.08
- Harddrives: 5 x ST3500841AS as RAID 5

Greetings from Switzerland
Miro Rutscho

P.S. Is there a possibility to disable the access of shares through IP / MAC adresses? The share IS password-protected but I'd like to "hide" the share for all other network users.

P.P.S.
Sorry for my bad english!

[Thecus - Yvon]

Dear Sir,

1.
Since first cold boot and the beep complete, please assit us to verify following 2 parts:
A. Waitng for few mintunes to cheking the RAID status information from web page.
B. The SMB or network disk still working?

If we waiting for few mintunes but still show NA & network disk doens't working, please keeping this environment and pprovide an IP address & account for us to access & check for you, here we would need port 21, 22, 80 & 443 open for connection, there are three ways to publish the NAS on the internet for your reference:

Public Fixed IP (most easy)

Just assign a public fixed IP on the NAS WAN/LAN1 port

DMZ (easy)
Enable Router DMZ function and fill in NAS WAN/LAN1 private IP in the Router DMZ column, and then tell me the Router WAN IP.

For Example:
Router WAN IP is 139.175.55.244
NAS WAN/LAN1 IP is 192.168.1.100

Enable Router DMZ function and fill in 192.168.1.100 for DMZ, thus the Router will forward all connection of 139.175.55.244 from internet to NAS WAN/LAN1 IP 192.168.1.100, than I could access to the NAS.

Virtual Server (port forward) (a little difficult)
Assign port 21/22/80 and 443 forward to NAS private IP, following case study about port 443 for your reference: http://www.thecus.com/storage_case03.php.


2.
If we chaneg the IP address & password from the web page, system would need reboot system to execute sthe setting work.

3.
We could change the folder attribution to unbrowseable, from Storage->Folder->Edit->Browseable->No


Yvon.

[Shellm]

Hi Yvon

Thanks for reading my problem report and for answering really fast

1.
Since first cold boot and the beep complete, please assit us to verify following 2 parts:
A. Waitng for few mintunes to cheking the RAID status information from web page.
B. The SMB or network disk still working?

I tried this several times (with current firmware). I took breakfast whilst waiting for the device to get ready. I was waiting about 30 minutes.. which should really be enough.

If we waiting for few mintunes but still show NA & network disk doens't working, please keeping this environment and pprovide an IP address & account for us to access & check for you, here we would need port 21, 22, 80 & 443 open for connection, there are three ways to publish the NAS on the internet for your reference:

Well I got private data on my NAS which I dont want to be accessible by anyone. Isnt there another way to provide you the information you need? Even though those are hexus-forum I cannot thrust you. Which privileges should the user have? What information do you want to obtain to solve the problem?

I think these are things which I could do for you too... if I'm told how to do it

2.
If we chaneg the IP address & password from the web page, system would need reboot system to execute sthe setting work.

Well I always followed the instructions and I tried severals times to apply those settings (IP-address WAN, LAN) with the reboot. So I tried to change to LCD password to change the settings on the LCD screen.. although I don't even know which settings can be changed by the LCD panel...

3.
We could change the folder attribution to unbrowseable, from Storage->Folder->Edit->Browseable->No

Whats the point of this change (I dont get it)?

[Thecus - Yvon]

Dear Sir,

1&2.
If possible please provide us 2 conf.bin file for us from web configuration page: System ->Config Mgmt->Downlaod
First conf.bin: Cold boot the N5200 and under RAID show NA status.
Second conf.bin: Reboot the N5200 and RAID heath.
for us to compare the difference

3.
If we set the fodler to unbrowseable, which means others user can't see this folder on the network.


Yvon.

[Shellm]

First conf.bin: Cold boot the N5200 and under RAID show NA status.
Second conf.bin: Reboot the N5200 and RAID heath.

I uploaded the files to h**p://mitglied.lycos.de/shellm/n5200/

First conf.bin: conf_after_cold_boot.bin
Second conf.bin: conf_after_sw_reboot.bin

The files are completely different (compared them with ultraedit).
I checked the RAID availability on the LCD screen and on the webinterface.
After the cold boot the disks didn't show up and the RAID was N/A.

After a reboot (through webinterface) the RAID was healthy (on LCD screen and on webinterface)

I can't even imagine where the problem is.

Btw: What data is stored in conf.bin? How can I decrypt this file?

3.
If we set the fodler to unbrowseable, which means others user can't see this folder on the network.

If Thecus can't solve the problem this would be my last chance, right? What would you expect to control on my N5200 via the web?

[Thecus - Yvon]

Dear Sir,

Thanks for your help about the conf.bin file, after compare the difference from the file, we found it is DOM damaged, thus please contact with your reseller for MRA service.

Following error message for your reference:

hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=90340, sector=90340
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 90340
Buffer I/O error on device hda5, logical block 34
lost page write due to I/O error on hda5
IO error syncing ext2 inode [hda5:000000ea]
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=90294, sector=90294
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 90294
Buffer I/O error on device hda5, logical block 11
lost page write due to I/O error on hda5
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=90296, sector=90296
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 90296
Buffer I/O error on device hda5, logical block 12
lost page write due to I/O error on hda5
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=90306, sector=90306
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 90306
Buffer I/O error on device hda5, logical block 17
lost page write due to I/O error on hda5
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=90314, sector=90314
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 90314
Buffer I/O error on device hda5, logical block 21
lost page write due to I/O error on hda5
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=90324, sector=90324
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 90324
Buffer I/O error on device hda5, logical block 26
lost page write due to I/O error on hda5
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=90332, sector=90332
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 90332
Buffer I/O error on device hda5, logical block 30
lost page write due to I/O error on hda5
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=90340, sector=90340
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 90340
Buffer I/O error on device hda5, logical block 34
lost page write due to I/O error on hda5
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=90284, sector=90284
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 90284
Buffer I/O error on device hda5, logical block 6
lost page write due to I/O error on hda5
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=90286, sector=90286
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 90286
Buffer I/O error on device hda5, logical block 7
lost page write due to I/O error on hda5
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=90288, sector=90288
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 90288
Buffer I/O error on device hda5, logical block 8
lost page write due to I/O error on hda5
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=90290, sector=90290
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 90290
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=90274, sector=90274
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 90274
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=90276, sector=90276
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 90276
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=90278, sector=90278
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 90278
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=90280, sector=90280
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 90280
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=92682, sector=92682
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 92682
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x80 { BadSector }, LBAsect=94370, sector=94370
ide: failed opcode was: unknown
criticalevent_user: disk_io_fail hda
end_request: I/O error, dev hda, sector 94370



Yvon.

[lproven]

P.S. Is there a possibility to disable the access of shares through IP / MAC adresses? The share IS password-protected but I'd like to "hide" the share for all other network users.

To hide Windows shares so that they don't show up when browsing the network, put a dollar sign on the end.

Visible:
\\server\share

Invisible:
\\server\share$

This should work on the Thecus' SAMBA server.

HTH.