Qnap ошибка обновления

  • FAQ
  • QTS
  • QuTS hero
  • QuTScloud
  • System Management
  • Productivity

Last modified date: 2022-06-24

Applied Products:

  • All NAS Series
  • All QTS Firmware Versions

While trying to update firmware, it may fail with error FW004. In that case, it is recommended to download the firmware image directly from QNAP website, so later you can upload it manually through Qfinder Pro > Tools > Update Firmware, then upgrading the firmware this way.

If above still fails, another reason may be the NAS DOM is defective, and will need to contact QNAP Support to verify, as the NAS will possibly need to be repaired.

Was this article helpful?

63% of people think it helps.

Thank you for your feedback.

Please tell us how this article can be improved:

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

Источник

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.
Источник

Tue Mar 22 09:20:16 2022 -> *Current working dir is /var/lib/clamav/

Tue Mar 22 09:20:16 2022 -> *Loaded freshclam.dat:

Tue Mar 22 09:20:16 2022 -> *  version:    1

Tue Mar 22 09:20:16 2022 -> *  uuid:       dd0512fc—399b—46af—8bd3—3ef86b3a37d6

Tue Mar 22 09:20:16 2022 -> ClamAV update process started at Tue Mar 22 09:20:16 2022

Tue Mar 22 09:20:16 2022 -> *Current working dir is /var/lib/clamav/

Tue Mar 22 09:20:16 2022 -> ^DNS Update Info disabled. Falling back to HTTP mode.

Tue Mar 22 09:20:16 2022 -> *Current working dir is /var/lib/clamav/

Tue Mar 22 09:20:16 2022 -> *check_for_new_database_version: Local copy of daily found: daily.cvd.

Tue Mar 22 09:20:16 2022 -> Trying to retrieve CVD header from http://clmvupd.deltamoby.ru/daily.cld

*   Trying 88.84.222.213:80…

* Connected to clmvupd.deltamoby.ru (88.84.222.213) port 80 (#0)

> GET /daily.cld HTTP/1.1

Host: clmvupd.deltamoby.ru

Range: bytes=0—511

User—Agent: ClamAV/0.104.1 (OS: Linux, ARCH: x86_64, CPU: x86_64, UUID: dd0512fc—399b—46af—8bd3—3ef86b3a37d6)

Accept: */*

If—Modified—Since: Mon, 21 Mar 2022 08:28:19 GMT

Connection: close

* Mark bundle as not supporting multiuse

< HTTP/1.1 301 Moved Permanently

< Date: Tue, 22 Mar 2022 06:20:16 GMT

< Server: Apache

< Location: https://clmvupd.deltamoby.ru/daily.cld

< Content—Length: 246

< Connection: close

< Content—Type: text/html; charset=iso-8859-1

<

* Closing connection 0

* Issue another request to this URL: ‘https://clmvupd.deltamoby.ru/daily.cld’

*   Trying 88.84.222.213:443…

* Connected to clmvupd.deltamoby.ru (88.84.222.213) port 443 (#1)

* ALPN, offering h2

* ALPN, offering http/1.1

* successfully set certificate verify locations:

*  CAfile: /etc/ssl/certs/ca—certificates.crt

*  CApath: /etc/ssl/certs

* SSL connection using TLSv1.2 / ECDHE—RSA—AES256—GCM—SHA384

* ALPN, server accepted to use http/1.1

* Server certificate:

*  subject: CN=clmvupd.deltamoby.ru

*  start date: Mar 22 05:06:49 2022 GMT

*  expire date: Jun 20 05:06:48 2022 GMT

*  subjectAltName: host «clmvupd.deltamoby.ru» matched cert‘s «clmvupd.deltamoby.ru»

*  issuer: C=US; O=Let’s Encrypt; CN=R3

*  SSL certificate verify ok.

> GET /daily.cld HTTP/1.1

Host: clmvupd.deltamoby.ru

Range: bytes=0—511

User—Agent: ClamAV/0.104.1 (OS: Linux, ARCH: x86_64, CPU: x86_64, UUID: dd0512fc—399b—46af—8bd3—3ef86b3a37d6)

Accept: */*

If—Modified—Since: Mon, 21 Mar 2022 08:28:19 GMT

Connection: close

* Mark bundle as not supporting multiuse

< HTTP/1.1 404 Not Found

< Date: Tue, 22 Mar 2022 06:20:16 GMT

< Server: Apache

< Content—Length: 196

< Connection: close

< Content—Type: text/html; charset=iso-8859-1

<

* Closing connection 1

Tue Mar 22 09:20:16 2022 -> ^remote_cvdhead: file not found: http://clmvupd.deltamoby.ru/daily.cld

Tue Mar 22 09:20:16 2022 -> Trying to retrieve CVD header from http://clmvupd.deltamoby.ru/daily.cvd

*   Trying 88.84.222.213:80…

* Connected to clmvupd.deltamoby.ru (88.84.222.213) port 80 (#0)

> GET /daily.cvd HTTP/1.1

Host: clmvupd.deltamoby.ru

Range: bytes=0—511

User—Agent: ClamAV/0.104.1 (OS: Linux, ARCH: x86_64, CPU: x86_64, UUID: dd0512fc—399b—46af—8bd3—3ef86b3a37d6)

Accept: */*

If—Modified—Since: Mon, 21 Mar 2022 08:28:19 GMT

Connection: close

* Mark bundle as not supporting multiuse

< HTTP/1.1 301 Moved Permanently

< Date: Tue, 22 Mar 2022 06:20:16 GMT

< Server: Apache

< Location: https://clmvupd.deltamoby.ru/daily.cvd

< Content—Length: 246

< Connection: close

< Content—Type: text/html; charset=iso-8859-1

<

* Closing connection 0

* Issue another request to this URL: ‘https://clmvupd.deltamoby.ru/daily.cvd’

*   Trying 88.84.222.213:443…

* Connected to clmvupd.deltamoby.ru (88.84.222.213) port 443 (#1)

* ALPN, offering h2

* ALPN, offering http/1.1

* successfully set certificate verify locations:

*  CAfile: /etc/ssl/certs/ca—certificates.crt

*  CApath: /etc/ssl/certs

* SSL connection using TLSv1.2 / ECDHE—RSA—AES256—GCM—SHA384

* ALPN, server accepted to use http/1.1

* Server certificate:

*  subject: CN=clmvupd.deltamoby.ru

*  start date: Mar 22 05:06:49 2022 GMT

*  expire date: Jun 20 05:06:48 2022 GMT

*  subjectAltName: host «clmvupd.deltamoby.ru» matched cert‘s «clmvupd.deltamoby.ru»

*  issuer: C=US; O=Let’s Encrypt; CN=R3

*  SSL certificate verify ok.

> GET /daily.cvd HTTP/1.1

Host: clmvupd.deltamoby.ru

Range: bytes=0—511

User—Agent: ClamAV/0.104.1 (OS: Linux, ARCH: x86_64, CPU: x86_64, UUID: dd0512fc—399b—46af—8bd3—3ef86b3a37d6)

Accept: */*

If—Modified—Since: Mon, 21 Mar 2022 08:28:19 GMT

Connection: close

* Mark bundle as not supporting multiuse

< HTTP/1.1 206 Partial Content

< Date: Tue, 22 Mar 2022 06:20:16 GMT

< Server: Apache

< Last—Modified: Tue, 22 Mar 2022 05:51:55 GMT

< ETag: «3765084-5dac835e045da»

< Accept—Ranges: bytes

< Content—Length: 512

< Content—Range: bytes 0—511/58085508

< Connection: close

<

* Closing connection 1

Tue Mar 22 09:20:16 2022 -> OK

Tue Mar 22 09:20:16 2022 -> *daily database version obtained using HTTP GET: 26488

Tue Mar 22 09:20:16 2022 -> daily.cvd database is up—to—date (version: 26488, sigs: 1976522, f—level: 90, builder: raynman)

Tue Mar 22 09:20:16 2022 -> *fc_update_database: daily.cvd already up—to—date.

Tue Mar 22 09:20:16 2022 -> *Current working dir is /var/lib/clamav/

Tue Mar 22 09:20:16 2022 -> *check_for_new_database_version: Local copy of main found: main.cvd.

Tue Mar 22 09:20:16 2022 -> Trying to retrieve CVD header from http://clmvupd.deltamoby.ru/main.cld

*   Trying 88.84.222.213:80…

* Connected to clmvupd.deltamoby.ru (88.84.222.213) port 80 (#0)

> GET /main.cld HTTP/1.1

Host: clmvupd.deltamoby.ru

Range: bytes=0—511

User—Agent: ClamAV/0.104.1 (OS: Linux, ARCH: x86_64, CPU: x86_64, UUID: dd0512fc—399b—46af—8bd3—3ef86b3a37d6)

Accept: */*

If—Modified—Since: Thu, 16 Sep 2021 12:32:42 GMT

Connection: close

* Mark bundle as not supporting multiuse

< HTTP/1.1 301 Moved Permanently

< Date: Tue, 22 Mar 2022 06:20:16 GMT

< Server: Apache

< Location: https://clmvupd.deltamoby.ru/main.cld

< Content—Length: 245

< Connection: close

< Content—Type: text/html; charset=iso-8859-1

<

* Closing connection 0

* Issue another request to this URL: ‘https://clmvupd.deltamoby.ru/main.cld’

*   Trying 88.84.222.213:443…

* Connected to clmvupd.deltamoby.ru (88.84.222.213) port 443 (#1)

* ALPN, offering h2

* ALPN, offering http/1.1

* successfully set certificate verify locations:

*  CAfile: /etc/ssl/certs/ca—certificates.crt

*  CApath: /etc/ssl/certs

* SSL connection using TLSv1.2 / ECDHE—RSA—AES256—GCM—SHA384

* ALPN, server accepted to use http/1.1

* Server certificate:

*  subject: CN=clmvupd.deltamoby.ru

*  start date: Mar 22 05:06:49 2022 GMT

*  expire date: Jun 20 05:06:48 2022 GMT

*  subjectAltName: host «clmvupd.deltamoby.ru» matched cert‘s «clmvupd.deltamoby.ru»

*  issuer: C=US; O=Let’s Encrypt; CN=R3

*  SSL certificate verify ok.

> GET /main.cld HTTP/1.1

Host: clmvupd.deltamoby.ru

Range: bytes=0—511

User—Agent: ClamAV/0.104.1 (OS: Linux, ARCH: x86_64, CPU: x86_64, UUID: dd0512fc—399b—46af—8bd3—3ef86b3a37d6)

Accept: */*

If—Modified—Since: Thu, 16 Sep 2021 12:32:42 GMT

Connection: close

* Mark bundle as not supporting multiuse

< HTTP/1.1 404 Not Found

< Date: Tue, 22 Mar 2022 06:20:16 GMT

< Server: Apache

< Content—Length: 196

< Connection: close

< Content—Type: text/html; charset=iso-8859-1

<

* Closing connection 1

Tue Mar 22 09:20:16 2022 -> ^remote_cvdhead: file not found: http://clmvupd.deltamoby.ru/main.cld

Tue Mar 22 09:20:16 2022 -> Trying to retrieve CVD header from http://clmvupd.deltamoby.ru/main.cvd

*   Trying 88.84.222.213:80…

* Connected to clmvupd.deltamoby.ru (88.84.222.213) port 80 (#0)

> GET /main.cvd HTTP/1.1

Host: clmvupd.deltamoby.ru

Range: bytes=0—511

User—Agent: ClamAV/0.104.1 (OS: Linux, ARCH: x86_64, CPU: x86_64, UUID: dd0512fc—399b—46af—8bd3—3ef86b3a37d6)

Accept: */*

If—Modified—Since: Thu, 16 Sep 2021 12:32:42 GMT

Connection: close

* Mark bundle as not supporting multiuse

< HTTP/1.1 301 Moved Permanently

< Date: Tue, 22 Mar 2022 06:20:16 GMT

< Server: Apache

< Location: https://clmvupd.deltamoby.ru/main.cvd

< Content—Length: 245

< Connection: close

< Content—Type: text/html; charset=iso-8859-1

<

* Closing connection 0

* Issue another request to this URL: ‘https://clmvupd.deltamoby.ru/main.cvd’

*   Trying 88.84.222.213:443…

* Connected to clmvupd.deltamoby.ru (88.84.222.213) port 443 (#1)

* ALPN, offering h2

* ALPN, offering http/1.1

* successfully set certificate verify locations:

*  CAfile: /etc/ssl/certs/ca—certificates.crt

*  CApath: /etc/ssl/certs

* SSL connection using TLSv1.2 / ECDHE—RSA—AES256—GCM—SHA384

* ALPN, server accepted to use http/1.1

* Server certificate:

*  subject: CN=clmvupd.deltamoby.ru

*  start date: Mar 22 05:06:49 2022 GMT

*  expire date: Jun 20 05:06:48 2022 GMT

*  subjectAltName: host «clmvupd.deltamoby.ru» matched cert‘s «clmvupd.deltamoby.ru»

*  issuer: C=US; O=Let’s Encrypt; CN=R3

*  SSL certificate verify ok.

> GET /main.cvd HTTP/1.1

Host: clmvupd.deltamoby.ru

Range: bytes=0—511

User—Agent: ClamAV/0.104.1 (OS: Linux, ARCH: x86_64, CPU: x86_64, UUID: dd0512fc—399b—46af—8bd3—3ef86b3a37d6)

Accept: */*

If—Modified—Since: Thu, 16 Sep 2021 12:32:42 GMT

Connection: close

* Mark bundle as not supporting multiuse

< HTTP/1.1 206 Partial Content

< Date: Tue, 22 Mar 2022 06:20:16 GMT

< Server: Apache

< Last—Modified: Tue, 22 Mar 2022 05:51:56 GMT

< ETag: «a2950ad-5dac835e5859b»

< Accept—Ranges: bytes

< Content—Length: 512

< Content—Range: bytes 0—511/170479789

< Connection: close

<

* Closing connection 1

Tue Mar 22 09:20:16 2022 -> OK

Tue Mar 22 09:20:16 2022 -> *main database version obtained using HTTP GET: 62

Tue Mar 22 09:20:16 2022 -> main.cvd database is up—to—date (version: 62, sigs: 6647427, f—level: 90, builder: sigmgr)

Tue Mar 22 09:20:16 2022 -> *fc_update_database: main.cvd already up—to—date.

Tue Mar 22 09:20:16 2022 -> *Current working dir is /var/lib/clamav/

Tue Mar 22 09:20:16 2022 -> *check_for_new_database_version: Local copy of bytecode found: bytecode.cld.

Tue Mar 22 09:20:16 2022 -> Trying to retrieve CVD header from http://clmvupd.deltamoby.ru/bytecode.cld

*   Trying 88.84.222.213:80…

* Connected to clmvupd.deltamoby.ru (88.84.222.213) port 80 (#0)

> GET /bytecode.cld HTTP/1.1

Host: clmvupd.deltamoby.ru

Range: bytes=0—511

User—Agent: ClamAV/0.104.1 (OS: Linux, ARCH: x86_64, CPU: x86_64, UUID: dd0512fc—399b—46af—8bd3—3ef86b3a37d6)

Accept: */*

If—Modified—Since: Mon, 08 Mar 2021 15:21:51 GMT

Connection: close

* Mark bundle as not supporting multiuse

< HTTP/1.1 301 Moved Permanently

< Date: Tue, 22 Mar 2022 06:20:16 GMT

< Server: Apache

< Location: https://clmvupd.deltamoby.ru/bytecode.cld

< Content—Length: 249

< Connection: close

< Content—Type: text/html; charset=iso-8859-1

<

* Closing connection 0

* Issue another request to this URL: ‘https://clmvupd.deltamoby.ru/bytecode.cld’

*   Trying 88.84.222.213:443…

* Connected to clmvupd.deltamoby.ru (88.84.222.213) port 443 (#1)

* ALPN, offering h2

* ALPN, offering http/1.1

* successfully set certificate verify locations:

*  CAfile: /etc/ssl/certs/ca—certificates.crt

*  CApath: /etc/ssl/certs

* SSL connection using TLSv1.2 / ECDHE—RSA—AES256—GCM—SHA384

* ALPN, server accepted to use http/1.1

* Server certificate:

*  subject: CN=clmvupd.deltamoby.ru

*  start date: Mar 22 05:06:49 2022 GMT

*  expire date: Jun 20 05:06:48 2022 GMT

*  subjectAltName: host «clmvupd.deltamoby.ru» matched cert‘s «clmvupd.deltamoby.ru»

*  issuer: C=US; O=Let’s Encrypt; CN=R3

*  SSL certificate verify ok.

> GET /bytecode.cld HTTP/1.1

Host: clmvupd.deltamoby.ru

Range: bytes=0—511

User—Agent: ClamAV/0.104.1 (OS: Linux, ARCH: x86_64, CPU: x86_64, UUID: dd0512fc—399b—46af—8bd3—3ef86b3a37d6)

Accept: */*

If—Modified—Since: Mon, 08 Mar 2021 15:21:51 GMT

Connection: close

* Mark bundle as not supporting multiuse

< HTTP/1.1 404 Not Found

< Date: Tue, 22 Mar 2022 06:20:16 GMT

< Server: Apache

< Content—Length: 196

< Connection: close

< Content—Type: text/html; charset=iso-8859-1

<

* Closing connection 1

Tue Mar 22 09:20:16 2022 -> ^remote_cvdhead: file not found: http://clmvupd.deltamoby.ru/bytecode.cld

Tue Mar 22 09:20:16 2022 -> Trying to retrieve CVD header from http://clmvupd.deltamoby.ru/bytecode.cvd

*   Trying 88.84.222.213:80…

* Connected to clmvupd.deltamoby.ru (88.84.222.213) port 80 (#0)

> GET /bytecode.cvd HTTP/1.1

Host: clmvupd.deltamoby.ru

Range: bytes=0—511

User—Agent: ClamAV/0.104.1 (OS: Linux, ARCH: x86_64, CPU: x86_64, UUID: dd0512fc—399b—46af—8bd3—3ef86b3a37d6)

Accept: */*

If—Modified—Since: Mon, 08 Mar 2021 15:21:51 GMT

Connection: close

* Mark bundle as not supporting multiuse

< HTTP/1.1 301 Moved Permanently

< Date: Tue, 22 Mar 2022 06:20:16 GMT

< Server: Apache

< Location: https://clmvupd.deltamoby.ru/bytecode.cvd

< Content—Length: 249

< Connection: close

< Content—Type: text/html; charset=iso-8859-1

<

* Closing connection 0

* Issue another request to this URL: ‘https://clmvupd.deltamoby.ru/bytecode.cvd’

*   Trying 88.84.222.213:443…

* Connected to clmvupd.deltamoby.ru (88.84.222.213) port 443 (#1)

* ALPN, offering h2

* ALPN, offering http/1.1

* successfully set certificate verify locations:

*  CAfile: /etc/ssl/certs/ca—certificates.crt

*  CApath: /etc/ssl/certs

* SSL connection using TLSv1.2 / ECDHE—RSA—AES256—GCM—SHA384

* ALPN, server accepted to use http/1.1

* Server certificate:

*  subject: CN=clmvupd.deltamoby.ru

*  start date: Mar 22 05:06:49 2022 GMT

*  expire date: Jun 20 05:06:48 2022 GMT

*  subjectAltName: host «clmvupd.deltamoby.ru» matched cert‘s «clmvupd.deltamoby.ru»

*  issuer: C=US; O=Let’s Encrypt; CN=R3

*  SSL certificate verify ok.

> GET /bytecode.cvd HTTP/1.1

Host: clmvupd.deltamoby.ru

Range: bytes=0—511

User—Agent: ClamAV/0.104.1 (OS: Linux, ARCH: x86_64, CPU: x86_64, UUID: dd0512fc—399b—46af—8bd3—3ef86b3a37d6)

Accept: */*

If—Modified—Since: Mon, 08 Mar 2021 15:21:51 GMT

Connection: close

* Mark bundle as not supporting multiuse

< HTTP/1.1 206 Partial Content

< Date: Tue, 22 Mar 2022 06:20:16 GMT

< Server: Apache

< Last—Modified: Tue, 22 Mar 2022 05:59:45 GMT

< ETag: «47b26-5dac851d8ffa7»

< Accept—Ranges: bytes

< Content—Length: 512

< Content—Range: bytes 0—511/293670

< Connection: close

<

* Closing connection 1

Tue Mar 22 09:20:16 2022 -> OK

Tue Mar 22 09:20:16 2022 -> *bytecode database version obtained using HTTP GET: 333

Tue Mar 22 09:20:16 2022 -> bytecode.cld database is up—to—date (version: 333, sigs: 92, f—level: 63, builder: awillia2)

Tue Mar 22 09:20:16 2022 -> *fc_update_database: bytecode.cld already up—to—date.

Источник

Понравилась статья? Поделить с друзьями:
  • Qnap не удалось обновить систему код ошибки 4
  • R studio ошибка 433
  • Qnap архив доступа к диску i o ошибка
  • Qnap connect ошибка 807
  • R studio ошибка 1001