TS-EC879u-RP with FW 3.5.1.1002 Unstable

[StarrCompany]

Yes iSCSI enabled its pretty much all thats running now as config stripped right back - interesting re NIC ill check - had email from qnap:


Currently we have confirmed that current BIOS on the x79 series may cause the reboot problem and we will release a new BIOS before next week.
I will send you the upgrade guide and the BIOS once available.

[ProTeck]

StarrCompany,

Please keep us posted on the "new" firmware and if that solves the problem.

Thanks,

[gm85]

Just wanted to provide an update.

As per QNAP's instructions (on 3.5.2), i disabled trunking on Jan 26. Since that date, the system had been stable.

On Feb 16, I shut the system down, applied 3.6.0, and re-enabled trunking.

System crashed tonight. Checked and sent the logs to QNAP. Good news is those previous iscsi issues (that used to flood the logs) are no longer there.... bad news is there is no indication in the logs of the crash.

It's probably just coincidence (or luck), but I disabled trunking again as it hasn't yet crashed while trunking is off.

Good to hear that QNAP believes it's a BIOS issue as that definitely seems to be what the issue is (not software or OS... otherwise SOMETHING would be logged somewhere).

[crm0922]

Any update on this? We want to buy one of these units but if it is unstable that's a major dealbreaker.

[RedShift]

We also have a TS-1279 that has been rebooting. It's equipped with 6 x 3 TB Seagate Constellation ES.2 drives in RAID 10. It only has one NIC active and 1 iSCSI target, nothing else. It serves as a backup location for another storage server, so most of the time it's doing nothing.

We were getting the "The system was not shut down properly last time." messages in the logs and via email, the device was rebooting almost every day, it would never achieve an uptime greater than one day. We updated it last thursday with the 3.6.0 firmware and it hasn't rebooted since.

Not declaring it fixed yet though, as some people here have had an unexpected reboot after a week or two. Haven't contacted QNAP about this.

[crm0922]

Thanks for the update. I still think this is a potential nightmare scenario until I can get a 100% confirmation that the issue is resolved.

We are assuming this is some kind of kernel panic, not a hardware failure/design issue?

[ProTeck]

How did this pass QNAPs Quality Assurance process. QNAP, was this unit tested with iSCSI features enabled and used prior to releasing said product?

[RedShift]

How did this pass QNAPs Quality Assurance process. QNAP, was this unit tested with iSCSI features enabled and used prior to releasing said product?

Yeah, seems at bit strange as this is their top-of-the-line product. There's nothing more, it's the best they have to offer at this time...

[gm85]

We just had another crash. This time, however it happened during the day and Port Trunking was turned off.

Looks like I'll have to begin moving some of my virtual servers to a standby storage server while this issue is resolved

[ProTeck]

Question for everyone on this thread. Does everyone have iSCSI enabled and using it? What happens if you create a drive via a NFS share if using VMWare? Luckily for us, since we disabled the iSCSI service/stopped using it, we haven't experienced a crash in a while. Granted, we took a lot of load off it too. If some of you are will to disable iSCSI, see how long it will take to crash if it does.

[StarrCompany]

We have had instructions for downloading and updating to the new BIOS version - fingers crossed!!!

[gm85]

Hey Everyone,
Just ran the BIOS update on the system. The update was successful, but I ran into a small issue. I'll admit that the problem was probably my own fault (by previously changing certain BIOS / ME settings), but I just wanted to give you a heads up on how to fix the issue if it happens to you.

After applying the bios update and unplugging/restarting the system, I noticed that the primary network interface was not accessible. If this happens to you, here are the steps to fix it:

Log into the Console of your NAS (with a monitor and USB keyboard) with your Admin account.
Type

Code: Select all

ifconfig | more

You should see 3 interfaces: eth0, eth1 and l0.

If you only see 2 (eth1 and l0), follow the steps below:
Restart your system and press F2 when the system prompts you to enter BIOS settings.
Select the Chipset Menu (I think that's what it's called), and then select ME Subsystem.
You shoud see an option to allow you to reset the ME Subsystem. Change that option to Enabled.

Save changes and restart. During the startup, you will be prompted if you want to reset the ME Subsystem. Select Yes

Your primary network interface sould be working again once the system boots.

[RedShift]

There's a new firmware update available for these NAS'es, 3.6.1, containing another BIOS update.

[volido]

Im running into the same problem for some dais. the firmware is up to date 3.61. and after disable port trunking the situation has slightly improved but still rebooting unexpectedly several times a day....
...each time we have to unplug network wire form the qnap box, wait a couple of minutes, cross fingers and restart....once the drivers are on, we can connect the rj45 back. if we try to restart with the rj45 connected...the box just reboot and reboot and reboot without reaching the drives.....pathetic.
we have been very happy with the box for a long time...but this is completely unacceptable in a professional environment and make the box useless ...

log

2012-04-20 10:29:44 System 127.0.0.1 localhost [Mirror Disk Volume: Drive 1 2] The file system is not clean. It is suggested that you run "check disk".
2012-04-20 10:29:30 System 127.0.0.1 localhost System started.
2012-04-20 10:29:29 System 127.0.0.1 localhost The system was not shut down properly last time.
2012-04-20 06:02:24 System 127.0.0.1 localhost Lan 1 link is Up.
2012-04-20 05:54:26 System 127.0.0.1 localhost Lan 1 link is Down.
2012-04-20 05:41:30 max 192.168.1.30 --- [DDNS] DDNS stopped successfully.
2012-04-20 05:30:03 System 127.0.0.1 localhost external ip is change ,update ddns.
2012-04-20 05:28:40 System 127.0.0.1 localhost [Mirror Disk Volume: Drive 1 2] The file system is not clean. It is suggested that you run "check disk".
2012-04-20 05:28:26 System 127.0.0.1 localhost System started.
2012-04-20 05:28:25 System 127.0.0.1 localhost The system was not shut down properly last time.

if we perform "check disk" at 20% of the process the machine fall in the rebooting loop explained above.
what is the situation with this issue at this moment?...please help

[QNAPDavid]

Dear Users:
We have released a BIOS update utility to fix the reboot issue on the TS-X79 series. With the QNAP BIOS update utility users can update the BIOS/ME ROM and 82574 EEPROM image from a bootable USB flash drive. It is suggested to update the BIOS ONLY if the users encounter the reboot issue.


===============================================================================================
QNAP BIOS update instructions (READ FIRST BEFORE UPDATING):http://eu1.qnap.com/Storage/BIOS/X79/20120302/X79-BIOS-Update-SOP_20120302.pdf
QNAP BIOS update utility: http://eu1.qnap.com/Storage/BIOS/X79/20120302/X79_BIOS_20120302.zip
===============================================================================================