Qnap ошибка fw00007

• FAQ

---

Last modified date: 2021-07-02

Answer

When firmware update failed with FW00007 via browser, follow the procedures below

1. Reboot the NAS
2. After the NAS reboots, upgrade the firmware by Qfinder.

If still meeting the same error, please create a ticket in QNAP service portal.

Was this article helpful?

Yes.
No.

80% of people think it helps.

Thank you for your feedback.

Please tell us how this article can be improved:

• The article is missing important information 

• The article’s solutions do not work

• The article is too complicated

• The article contains incorrect information

• The article is out-of-date

If you want to provide additional feedback, please include it below.

This site is protected by reCAPTCHA and the Google
Privacy Policy and
Terms of Service apply.

If you want to provide additional feedback, please include it below.

This site is protected by reCAPTCHA and the Google
Privacy Policy and
Terms of Service apply.

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 13 ratings

Have you received error FW003 when trying to update the firmware of your QNAP Network Attached Storage (NAS)?
You have found the right page!

 
If you encounter error FW003 when trying to update the firmware of your QNAP NAS, it means that the system disk partition (which is used by the NAS to actually work and is separated from the actual storage space) does not have enough free space to perform the update operations. For example, if the size of the new version of the firmware is 185 MB and the available space is only 180 MB, you will get this error.

 
The only way to solve is to free enough disk space to perform the update. To do this you will have to connect to the NAS via SSH (using PuTTY on Windows, or a terminal on Linux/MacOS), and start looking for files that can be sacrificed to make room for the update.

 
To achieve this, once connected to the NAS via SSH, you will have to perform the following operations:

1. Confirm you have not enough free space on the system disk by issuing this command:

   [~] # df

   You’ll get an output like the following:

   

   You have to check the column «Mounted on» and find «/mnt/HDA_ROOT». Check if available space is effectively smaller than the firmware update package. If so, go on. If not, contact QNAP support.

2. Confirm no /mnt/update file or folder and no /tmp/update_process file exist: if they exist, you need to delete them using:

   [~] # rm -rf /mnt/update
   [~] # rm -f /tmp/update_process

3. Repeat step 1. If available space on /mnt/HDA_ROOT is now larger than needed, proceed with the firmware update. If available space on /mnt/HDA_ROOT is still smaller than needed, proceed to Step 4.
4. Now you will have to look for the files that are occupying too much space on your /mnt/HDA_ROOT partition. This is different for every system, so there is not a unique solution. It’s basically trial-and-error. Start with:

   [~] # ls -als /mnt/HDA_ROOT/

   To get the list of directories on this partition. Now check every directory using the following command:

   [~] # ls -als /mnt/HDA_ROOT/directoryname

   where directoryname stands for each directory (and their subdirectories) on the partition. My suggestion: start with the .logs and lost+found directories. For example:

   [~] # ls -als /mnt/HDA_ROOT/.logs

   You might get something like this:

   -rw-r—r— 1 admin administ 184.7M Jan 21 2020 conn.log
   -rw-r—r— 1 admin administ 345.3M Jan 18 2020 event.log

   As you can see those files have become huge, so you can safely delete them (they are log files, so not needed by the system) using the command:

   [~] # rm -f /mnt/HDA_ROOT/.logs/conn.log
   [~] # rm -f /mnt/HDA_ROOT/.logs/event.log

   As specified above, this is just an example. You will have to find the files that actually occupy too much space ON YOUR SYSTEM.

5. Once deleted these files, and freed up enough space, proceed with the firmware update as usual.