Код ошибки fw00007 qnap

Specs

See References for more details.

Internals

Problem

Received notification indicating that the fan 1 had failed.

When I checked on it, it appeared to be un-responsive.  Could not see it on the network after rebooting.

LEDs

Status — OFF

LAN — typical flashing for lan port

USB — blue

RED LEDs for HDs

Fan is running at full.

No POST beep  

Reason for the Failure

LPC clock degradation issue with the Intel Celeron J1900.

The Intel Celeron J1900 is part of the Bay Trail family of chips.

Intel revealed in its Q4 2016 quarterly report that there were quality issues in the C2000 product family, which had an effect on the financial performance of the company’s Data Center Group that quarter.^[12] An erratum named AVR54 published by Intel state there is a defect in the chip’s LPC clock, and affected systems «may experience inability to boot or may cease operation».^[13][14][15] A workaround is available requiring platform hardware changes. The SoC failures are thought to have led to failures in Cisco and Synology products,^[16] though discussion of the C2000 as the root cause of failure has been reported to be under a non-disclosure agreement for many vendors.^[17]

Intel released a new C0 stepping of the C2000 series in April 2017 which corrected the bug.^[18]

In July 2017 Intel published that a similar quality issue affects also Atom E3800 series embedded processors. The erratum named VLI89 published by Intel state, similar to issue with Atom C2000, that there is a defect in the chip’s LPC clock and affected systems «may experience inability to boot or may cease operation».^[19] Issues extend also to USB bus and SD card circuitry and should happen «under certain conditions where activity is high for several years». In April 2018 Intel announced it is releasing a new D1 stepping to fix the issue.^[20]

The LPC, USB and SD Card buses circuitry degradation issues also apply to other Bay Trail processors such as Intel Celeron J1900 and N2800/N2900 series;^[21] also to Pentium N3500, J2850, J2900 series; and Celeron J1800 and J1750 series — as those are based on the same affected silicon.

— https://en.wikipedia.org/wiki/Silvermont

Fix

Measure the voltage across pin1 (LPC CLK) and pin 8 or 10 (GROUND) on the LPC-CN1(10-pin connector, next to 4-pin COM1 connector)

If everything is normal, you should get a voltage around 1.7v.

If the voltage is ~2.4V, solder 100 Ohm between pin 1 (LPC CLK) and ground (pin 8 or 10).

Solder 100 ohm resister between CLK and GND on connector LPC-CN1.

Power on and now we get our POST BEEP and LEDs are showing boot up procedure.

How Long Will this Fix Last?

«… some reported it works for years after the rework and some reported the system died after 6 months, so don’t count this as a way to get a cheap NAS, as YMMV. I would recommend to turn it on only when you need to use it even if you don’t have the problem currently or it works again after the rework. If you plan to buy used systems, look up the CPU first and avoid all these models, including the Synology.»

References

I – Using md_checker Command To Get İnfo About RAID;

II – Fixing RAID With Usign AFR Command (Safe Way)

III – Fixing RAID With Using CFR Command (Warning, Dangerous)

.

I – Using md_checker Command To Get İnfo About RAID;

Type this command to get more info about your RAID;

md_checker

this commant may not be avaible, so type this commands to install it;

1 – Download the file to NAS:

# wget http://download.qnap.com/Storage/tsd/utility/md_checker

2 – Apply execute permission:

# chmod +x md_checker

3 – Run the script:
# ./md_checker

.

II – Fixing RAID With Usign AFR Command (Safe Way)

If your RAID structure seems “Not Active” and cannt access your files, you can fix this by this way;

Warning; if you’re not sure, don’t do it yourself, contact qnap support!

so we type this command line to fix our RAID;

mdadm -AfR /dev/md0 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3

.

What if we got “missing” or “Rebuildin” HDD? you must fallow right order & dont add “Missing” HDD’s to this command line

.

So in this case;

.

1 – Type This command to get RAID back online again;

mdadm -AfR /dev/md0 /dev/sdg3 /dev/sdh3 /dev/sda3 /dev/sdf3 /dev/sdc3 /dev/sdd3 /dev/sdb3

2 – And Now RAID Becomes Active Again!

3 – Type /etc/init.d/init_lvm.sh to mount RAID back again;

4 – Now RAID Comes back, and rebuilding start!

5 – İf you cant see your files under filestation;

6 – Just login with winscp, and check under /share/MD0_DATA folder;

.

III – Fixing RAID With Using CFR Command (Warning, Dangerous)

Type this command to fix your RAID;

This command shows that we have a RAID 5 with 4 HDD,

so we type this command line to fix our RAID;

mdadm -CfR –assume-clean /dev/md1 -n 4 -l 5 -c 64 -e 1.0 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3

.

2.1 – .. IF you have a RAID 6 with 10 HDD, type this command;

mdadm -CfR –assume-clean /dev/md1 -n 10 -l 6 -c 64 -e 1.0 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3 /dev/sde3 /dev/sdf3 /dev/sdg3 /dev/sdh3 /dev/sdi3 /dev/sdj3

.

-n 10 means you have 10 HDD!

-l 6 means you have a RAID 6 structure!

/dev/sda3 means your first HDD,

/dev/sdb3 means your 2.th HDD

.

2.2 – .. IF you have a RAID 5 with 8 HDD and 4.th HDD seems like broken, type this command;

mdadm -CfR –assume-clean /dev/md1 -n 8 -l 5 -c 64 -e 1.0 /dev/sda3 /dev/sdb3 /dev/sdc3 missing /dev/sde3 /dev/sdf3 /dev/sdg3 /dev/sdh3 /dev/sdi3 /dev/sdj3

Note; you must type missing for broken HDD’s to fix your RAID

.

2.3 – If your HDD order is not going just like “dev/sda3 /dev/sdb3 /dev/sdc3″ order, fix this mdadm command with right order;

mdadm -CfR –assume-clean /dev/md1 -n 15 -l 5 -c 64 -e 1.0 /dev/sdc3 /dev/sdd3 /dev/sdb3 /dev/sda3 /dev/sde3…

.

3 – Your RAID should be online again;

.

4 – Now, mount your RAID to access your files back again;

/etc/init.d/init_lvm.sh

…and your files should be back again!

.

.

How To Fix Not Active RAID After 4.1.0 FirmwareNot Active Görünen RAID Yapısını Nasıl Düzeltebilirsiniz (4.1.0 Firmware’i Sonrası), 9.6 out of 10 based on 12 ratings