red/green led flashing - 2 days+
-
- Getting the hang of things
- Posts: 71
- Joined: Wed Nov 14, 2012 11:04 pm
red/green led flashing - 2 days+
Similar to thread: http://forum.qnap.com/viewtopic.php?f=25&t=60283: After upgrading to Firmware 4.1.2 build 0126 for my TS-410 the machine got stuck on the red/green flashing light upon reboot. The status lights of my four drives (2x2TB, 1x3TB and 1x4TB) were all green.
QFinder could still not find the NAS, and my network tools (including my router) also did not detect the NAS; there was no response when I pinged at the designated fixed IP address.
The LAN status light on the NAS did flash (both the one on the front as one the rear end). Rebooting my router also did not work, the rest of my network seems to work fine.
Following instruction from the other topic I shut down the NAS, unplugged all the drives, shut down the system (by pressing the power button for approx 10 second) and rebooted.
During the reboot the status lights were flashing red/green from the beginning. After about 10 seconds into the reboot, the system produced a beep for about 1 second.
After this QFinder could still not find the NAS.
Another instruction in the mentioned thread also indicated that I should hot-plugin my drives one, by one, until the status lights of the system would turn green again.
I did this, but no luck. I'm beginning to fear for my NAS a little, any suggestions?
Does anyone have any luck with this rescue method? http://wiki.qnap.com/wiki/Firmware_Recovery
QFinder could still not find the NAS, and my network tools (including my router) also did not detect the NAS; there was no response when I pinged at the designated fixed IP address.
The LAN status light on the NAS did flash (both the one on the front as one the rear end). Rebooting my router also did not work, the rest of my network seems to work fine.
Following instruction from the other topic I shut down the NAS, unplugged all the drives, shut down the system (by pressing the power button for approx 10 second) and rebooted.
During the reboot the status lights were flashing red/green from the beginning. After about 10 seconds into the reboot, the system produced a beep for about 1 second.
After this QFinder could still not find the NAS.
Another instruction in the mentioned thread also indicated that I should hot-plugin my drives one, by one, until the status lights of the system would turn green again.
I did this, but no luck. I'm beginning to fear for my NAS a little, any suggestions?
Does anyone have any luck with this rescue method? http://wiki.qnap.com/wiki/Firmware_Recovery
- pwilson
- Guru
- Posts: 22533
- Joined: Fri Mar 06, 2009 11:20 am
- Location: Victoria, BC, Canada (UTC-08:00)
Re: red/green led flashing - 2 days+
Impossible to help without some more information provided. Please review: When you're asking a question, please include the following. Specifically we need to know the Make/Model/HDD-slot for every drive in your NAS, and the Volume type setup on the NAS. RAID5 perhaps?Atrejoe wrote:Similar to thread: http://forum.qnap.com/viewtopic.php?f=25&t=60283: After upgrading to Firmware 4.1.2 build 0126 for my TS-410 the machine got stuck on the red/green flashing light upon reboot. The status lights of my four drives (2x2TB, 1x3TB and 1x4TB) were all green.
QFinder could still not find the NAS, and my network tools (including my router) also did not detect the NAS; there was no response when I pinged at the designated fixed IP address.
The LAN status light on the NAS did flash (both the one on the front as one the rear end). Rebooting my router also did not work, the rest of my network seems to work fine.
Following instruction from the other topic I shut down the NAS, unplugged all the drives, shut down the system (by pressing the power button for approx 10 second) and rebooted.
During the reboot the status lights were flashing red/green from the beginning. After about 10 seconds into the reboot, the system produced a beep for about 1 second.
After this QFinder could still not find the NAS.
Another instruction in the mentioned thread also indicated that I should hot-plugin my drives one, by one, until the status lights of the system would turn green again.
I did this, but no luck. I'm beginning to fear for my NAS a little, any suggestions?
Does anyone have any luck with this rescue method? http://wiki.qnap.com/wiki/Firmware_Recovery
We also need to know if your NAS will boot without HDD's installed. whether or not you should be even attempting to follow the QNAPl: Firmware Recovery Guide for ARM based NAS depends on your answer to this question.
Can you access your NAS via SSH, so that we can do some actual "troubleshooting"?
Patrick M. Wilson
Victoria, BC Canada
QNAP TS-470 Pro w/ 4 * Western Digital WD30EFRX WD Reds (RAID5) - - Single 8.1TB Storage Pool FW: QTS 4.2.0 Build 20151023 - Kali Linux v1.06 (64bit)
Forums: View My Profile - Search My Posts - View My Photo - View My Location - Top Community Posters
QNAP: Turbo NAS User Manual - QNAP Wiki - QNAP Tutorials - QNAP FAQs
Please review: When you're asking a question, please include the following.
-
- Getting the hang of things
- Posts: 71
- Joined: Wed Nov 14, 2012 11:04 pm
Re: red/green led flashing - 2 days+
Good day Patrick, thank you for your response.
The NAS is a TS-410 crashed during upgrade from 4.1.2 build 1229 to 4.1.2 build 0126 (the build number show only the month and day of the build, is december 2014 build to january 2015 build)
The following disks are running in a RAID5 setup:
(Over the years I've had to replace a few drives, that's why they're all different.)
As I said, I cannot find the NAS by ip, with or without the disks inserted. I cannot ping it, my router doesn't see it, Qfinder doesn't see it. Therefore I cannot access it via SSH over the normal network.
I'm using Windows 8.1
I'm not using port trunking and have tried Ethernet port 1 and 2.
The network status lights (font and back) do blink though.
Upon booting with or without the drives inserted, I hear only one short beep. The long beep that should follow after about two minutes doesn't happen.
The NAS is a TS-410 crashed during upgrade from 4.1.2 build 1229 to 4.1.2 build 0126 (the build number show only the month and day of the build, is december 2014 build to january 2015 build)
The following disks are running in a RAID5 setup:
Code: Select all
#1 Seagate Barracude LP 2TB ST32000542AS
#2 Seagate 4TB ST4000DM000
#3 Western Digital Green 3TB WD30EZRX
#4 Seagate Barracude 2TB ST2000DM001
As I said, I cannot find the NAS by ip, with or without the disks inserted. I cannot ping it, my router doesn't see it, Qfinder doesn't see it. Therefore I cannot access it via SSH over the normal network.
I'm using Windows 8.1
I'm not using port trunking and have tried Ethernet port 1 and 2.
The network status lights (font and back) do blink though.
Upon booting with or without the drives inserted, I hear only one short beep. The long beep that should follow after about two minutes doesn't happen.
-
- Getting the hang of things
- Posts: 71
- Joined: Wed Nov 14, 2012 11:04 pm
Re: red/green led flashing - 2 days+
So I decided to attempt the firmware recovery as described at:
http://wiki.qnap.com/w/index.php?title= ... _based_NAS
All went well until step 22. (Power off the NAS, plug the HDD(s) back by original order, then power it on.)
With the disks inserted the NAS keeps blinking red/green again and doesn't register on the network again.
Without the disk inserted QFinder finds my NAS, which now has a new name and older firmware, see screenshot: The firmware recovery instructions do not describe whether I should initialize the NAS (again, without the disks inserted), QFinder does prompt me to initialize it, which I answered with 'No' I can access the web-interface, which only shows a warning about the missing disk too. Any ideas on how I should proceed? When the disk are not inserted, I can access the NAS via using SSH.
http://wiki.qnap.com/w/index.php?title= ... _based_NAS
All went well until step 22. (Power off the NAS, plug the HDD(s) back by original order, then power it on.)
With the disks inserted the NAS keeps blinking red/green again and doesn't register on the network again.
Without the disk inserted QFinder finds my NAS, which now has a new name and older firmware, see screenshot: The firmware recovery instructions do not describe whether I should initialize the NAS (again, without the disks inserted), QFinder does prompt me to initialize it, which I answered with 'No' I can access the web-interface, which only shows a warning about the missing disk too. Any ideas on how I should proceed? When the disk are not inserted, I can access the NAS via using SSH.
You do not have the required permissions to view the files attached to this post.
-
- Getting the hang of things
- Posts: 71
- Joined: Wed Nov 14, 2012 11:04 pm
Re: red/green led flashing - 2 days+
Some more info, after I ran config_util 1, it seems to confirm the 4 drives, yet it mentions them
I'm a bit worried that it states that it finds a two-disk raid1 array.
Code: Select all
[~] # config_util 1
Start to mirror ROOT part...
config_util: HD1 config Match serial_no of HD1.
config_util: HD2 config Match serial_no of HD2.
config_util: HD3 config Match serial_no of HD3.
config_util: HD4 config Match serial_no of HD4.
mdadm: /dev/md9 has been started with 4 drives.
Mirror of ROOT succeeded.
[~] # storage_boot_init 1
storage_boot_init 1 ...
[~] # mdadm: /dev/sda2 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sun Feb 1 14:00:39 2015
mdadm: array /dev/md4 started.
Code: Select all
[/] # df -h
Filesystem Size Used Available Use% Mounted on
/dev/ram0 32.9M 28.9M 4.0M 88% /
tmpfs 32.0M 128.0k 31.9M 0% /tmp
tmpfs 32.0M 0 32.0M 0% /.eaccelerator.tmp
/dev/md9 509.5M 148.4M 361.0M 29% /mnt/HDA_ROOT
Code: Select all
[~] # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md4 : active raid1 sdd2[2](S) sdc2[3](S) sdb2[1] sda2[0]
530048 blocks [2/2] [UU]
md9 : active raid1 sda1[0] sdd1[3] sdc1[2] sdb1[1]
530048 blocks [4/4] [UUUU]
bitmap: 1/65 pages [4KB], 4KB chunk
unused devices: <none>
- pwilson
- Guru
- Posts: 22533
- Joined: Fri Mar 06, 2009 11:20 am
- Location: Victoria, BC, Canada (UTC-08:00)
Re: red/green led flashing - 2 days+
Atrejoe wrote:The NAS is a TS-410 crashed during upgrade from 4.1.2 build 1229 to 4.1.2 build 0126 (the build number show only the month and day of the build, is december 2014 build to january 2015 build)
The following disks are running in a RAID5 setup:(Over the years I've had to replace a few drives, that's why they're all different.)Code: Select all
#1 Seagate Barracude LP 2TB ST32000542AS #2 Seagate 4TB ST4000DM000 #3 Western Digital Green 3TB WD30EZRX #4 Seagate Barracude 2TB ST2000DM001
Your taste in drives is suspect. 4 different drives in your NAS, and not even 1 of them is suitable for use in RAID. Seagate and WD Greens are not suitable for RAID use. Seagate DM's are problematic drives. Check out these messages.
As you can boot it without drives, Firmware recovery is not required. Do not attempt it.Atrejoe wrote:As I said, I cannot find the NAS by ip, with or without the disks inserted. I cannot ping it, my router doesn't see it, Qfinder doesn't see it. Therefore I cannot access it via SSH over the normal network.
I'm using Windows 8.1
If you boot without drives, we should be able to access it via SSH. Lets try that next:Atrejoe wrote:Upon booting with or without the drives inserted, I hear only one short beep. The long beep that should follow after about two minutes doesn't happen.
Proceed as follows:
- Power off your NAS
- Eject all drives. (Do not remove them, just eject them by 1" (3cm) so they are no longer connected to the SATA Bus).
- Turn on the NAS. (You'll hear a short "beep")
- After 2-3 minutes, a long beep will be heard, and the NAS can be "found" via QNAP QFinder
- Hot-plug all HDDs into the NAS (Do not power off the NAS. Do not follow the Quick Setup prompts)
- Access your NAS via SSH (using PuTTY) (Note: it's IP address may have changed, use QNAP QFinder if necessary to determine it's IP address)
- Execute the following commands on the NAS:
Code: Select all
config_util 1 storage_boot_init 1 sleep 30 storage_boot_init 2 config_util 4 sleep 2 mount /dev/sda4 /mnt/ext mv /mnt/HDA_ROOT/.config/uLinux.conf /mnt/HDA_ROOT/.config/uLinux.conf.OLD cp /etc/default_config/uLinux.conf /mnt/HDA_ROOT/.config/ setcfg -f /etc/config/uLinux.conf Misc configured TRUE df -h cat /proc/mdstat #done
Please cut&paste the output of this entire SSH session back to this message thread. [/list]
Patrick M. Wilson
Victoria, BC Canada
QNAP TS-470 Pro w/ 4 * Western Digital WD30EFRX WD Reds (RAID5) - - Single 8.1TB Storage Pool FW: QTS 4.2.0 Build 20151023 - Kali Linux v1.06 (64bit)
Forums: View My Profile - Search My Posts - View My Photo - View My Location - Top Community Posters
QNAP: Turbo NAS User Manual - QNAP Wiki - QNAP Tutorials - QNAP FAQs
Please review: When you're asking a question, please include the following.
-
- Getting the hang of things
- Posts: 71
- Joined: Wed Nov 14, 2012 11:04 pm
Re: red/green led flashing - 2 days+
I think 'suspect' may be an understatement.
As indicated, I already did the firmware restore, as the NAS was not responding with nor without drives.
Now (after firmware restore) it is only booting properly without drives.
I did as you instructed, here's my entire SSH session (i did not know whether you wanted it to be executed all at once or command-by-command, so I did command-by command):
Yes, there I can now 'see' the 5.4 TB RAID5 array, mounted on /share/MD0_DATA which contains my shares!
So the data seems to be there and accessible, how to I persist this? Can I issue a reboot command?
I'm holding my horses until you give the go-ahead.
As indicated, I already did the firmware restore, as the NAS was not responding with nor without drives.
Now (after firmware restore) it is only booting properly without drives.
I did as you instructed, here's my entire SSH session (i did not know whether you wanted it to be executed all at once or command-by-command, so I did command-by command):
Code: Select all
[~] # config_util 1
Start to mirror ROOT part...
config_util: HD1 config Match serial_no of HD1.
config_util: HD2 config Match serial_no of HD2.
config_util: HD3 config Match serial_no of HD3.
config_util: HD4 config Match serial_no of HD4.
mdadm: /dev/md9 has been started with 4 drives.
Mirror of ROOT succeeded.
[~] # storage_boot_init 1
storage_boot_init 1 ...
[~] # mdadm: /dev/sda2 appears to be part of a raid array:
level=raid1 devices=2 ctime=Sun Feb 1 17:33:10 2015
mdadm: array /dev/md4 started.
[~] # sleep 30
[~] # storage_boot_init 2
storage_boot_init 2 ...
mdadm: /dev/md0 has been started with 4 drives.
storage_boot_init.c: Start raid device /dev/md0 successfully
md0 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1]
md0 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1]
md0 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1]
md0 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1]
storage_boot_init.c: /dev/md0 is active.
storage_boot_init.c: Check filesystem on /dev/md0.
md5sum: /etc/config/proftpd.conf: No such file or directory
Restore default shares on vol[1]
storage_boot_init.c: check_last_degrade_error...
[~] # config_util 4
Start to mirror RFS_EXT part...
config_util: HD1 is TS-NASARM.
config_util: HD2 is TS-NASARM.
config_util: HD3 is TS-NASARM.
config_util: HD4 is TS-NASARM.
mdadm: /dev/sda4 has been started with 4 drives.
config_util: (0) /dev/sda4 size = 458880
Mirror of RFS_EXT succeeded.
[~] # sleep 2
[~] # mount /dev/sda4 /mnt/ext
<fig/uLinux.conf /mnt/HDA_ROOT/.config/uLinux.conf.OLD
[~] # cp /etc/default_config/uLinux.conf /mnt/HDA_ROOT/.config/
[~] # setcfg -f /etc/config/uLinux.conf Misc configured TRUE
[~] # df -h
Filesystem Size Used Available Use% Mounted on
/dev/ram0 32.9M 29.1M 3.8M 88% /
tmpfs 32.0M 84.0k 31.9M 0% /tmp
tmpfs 32.0M 0 32.0M 0% /.eaccelerator.tmp
/dev/md9 509.5M 148.4M 361.0M 29% /mnt/HDA_ROOT
/dev/md0 5.4T 5.0T 375.7G 93% /share/MD0_DATA
/dev/sda4 371.0M 238.0M 133.0M 64% /mnt/ext
[~] # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md13 : active raid1 sda4[0] sdd4[3] sdc4[2] sdb4[1]
458880 blocks [4/4] [UUUU]
bitmap: 0/57 pages [0KB], 4KB chunk
md4 : active raid1 sdd2[2](S) sdc2[3](S) sdb2[1] sda2[0]
530048 blocks [2/2] [UU]
md9 : active raid1 sda1[0] sdd1[3] sdc1[2] sdb1[1]
530048 blocks [4/4] [UUUU]
bitmap: 0/65 pages [0KB], 4KB chunk
md0 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1]
5855836800 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
unused devices: <none>
So the data seems to be there and accessible, how to I persist this? Can I issue a reboot command?
I'm holding my horses until you give the go-ahead.
- pwilson
- Guru
- Posts: 22533
- Joined: Fri Mar 06, 2009 11:20 am
- Location: Victoria, BC, Canada (UTC-08:00)
Re: red/green led flashing - 2 days+
Yes. Try rebooting. Let me know if your data is still accessible after the reboot.Atrejoe wrote:I think 'suspect' may be an understatement.
As indicated, I already did the firmware restore, as the NAS was not responding with nor without drives.
Now (after firmware restore) it is only booting properly without drives.
I did as you instructed, here's my entire SSH session (i did not know whether you wanted it to be executed all at once or command-by-command, so I did command-by command):
Yes, there I can now 'see' the 5.4 TB RAID5 array, mounted on /share/MD0_DATA which contains my shares!Code: Select all
[~] # config_util 1 Start to mirror ROOT part... config_util: HD1 config Match serial_no of HD1. config_util: HD2 config Match serial_no of HD2. config_util: HD3 config Match serial_no of HD3. config_util: HD4 config Match serial_no of HD4. mdadm: /dev/md9 has been started with 4 drives. Mirror of ROOT succeeded. [~] # storage_boot_init 1 storage_boot_init 1 ... [~] # mdadm: /dev/sda2 appears to be part of a raid array: level=raid1 devices=2 ctime=Sun Feb 1 17:33:10 2015 mdadm: array /dev/md4 started. [~] # sleep 30 [~] # storage_boot_init 2 storage_boot_init 2 ... mdadm: /dev/md0 has been started with 4 drives. storage_boot_init.c: Start raid device /dev/md0 successfully md0 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1] md0 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1] md0 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1] md0 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1] storage_boot_init.c: /dev/md0 is active. storage_boot_init.c: Check filesystem on /dev/md0. md5sum: /etc/config/proftpd.conf: No such file or directory Restore default shares on vol[1] storage_boot_init.c: check_last_degrade_error... [~] # config_util 4 Start to mirror RFS_EXT part... config_util: HD1 is TS-NASARM. config_util: HD2 is TS-NASARM. config_util: HD3 is TS-NASARM. config_util: HD4 is TS-NASARM. mdadm: /dev/sda4 has been started with 4 drives. config_util: (0) /dev/sda4 size = 458880 Mirror of RFS_EXT succeeded. [~] # sleep 2 [~] # mount /dev/sda4 /mnt/ext <fig/uLinux.conf /mnt/HDA_ROOT/.config/uLinux.conf.OLD [~] # cp /etc/default_config/uLinux.conf /mnt/HDA_ROOT/.config/ [~] # setcfg -f /etc/config/uLinux.conf Misc configured TRUE [~] # df -h Filesystem Size Used Available Use% Mounted on /dev/ram0 32.9M 29.1M 3.8M 88% / tmpfs 32.0M 84.0k 31.9M 0% /tmp tmpfs 32.0M 0 32.0M 0% /.eaccelerator.tmp /dev/md9 509.5M 148.4M 361.0M 29% /mnt/HDA_ROOT /dev/md0 5.4T 5.0T 375.7G 93% /share/MD0_DATA /dev/sda4 371.0M 238.0M 133.0M 64% /mnt/ext [~] # cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md13 : active raid1 sda4[0] sdd4[3] sdc4[2] sdb4[1] 458880 blocks [4/4] [UUUU] bitmap: 0/57 pages [0KB], 4KB chunk md4 : active raid1 sdd2[2](S) sdc2[3](S) sdb2[1] sda2[0] 530048 blocks [2/2] [UU] md9 : active raid1 sda1[0] sdd1[3] sdc1[2] sdb1[1] 530048 blocks [4/4] [UUUU] bitmap: 0/65 pages [0KB], 4KB chunk md0 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1] 5855836800 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU] unused devices: <none>
So the data seems to be there and accessible, how to I persist this? Can I issue a reboot command?
I'm holding my horses until you give the go-ahead.
Patrick M. Wilson
Victoria, BC Canada
QNAP TS-470 Pro w/ 4 * Western Digital WD30EFRX WD Reds (RAID5) - - Single 8.1TB Storage Pool FW: QTS 4.2.0 Build 20151023 - Kali Linux v1.06 (64bit)
Forums: View My Profile - Search My Posts - View My Photo - View My Location - Top Community Posters
QNAP: Turbo NAS User Manual - QNAP Wiki - QNAP Tutorials - QNAP FAQs
Please review: When you're asking a question, please include the following.
-
- Getting the hang of things
- Posts: 71
- Joined: Wed Nov 14, 2012 11:04 pm
Re: red/green led flashing - 2 days+
I issued a reboot command, after which the NAS rebooted. During the reboot the situation was back at green/red flashing. During boot I only heard a single beep.
The four drive-leds were flashing during boot, now they're steady green.
During boot the disks were active, now they're silent (spinning but no read/write activity)
The four drive-leds were flashing during boot, now they're steady green.
During boot the disks were active, now they're silent (spinning but no read/write activity)
- pwilson
- Guru
- Posts: 22533
- Joined: Fri Mar 06, 2009 11:20 am
- Location: Victoria, BC, Canada (UTC-08:00)
Re: red/green led flashing - 2 days+
Okay. Boot it up again without drives, like I showed you before, so that it mounts the drives temporarily again. Once you have done that, we can examine the drives individually.Atrejoe wrote:I issued a reboot command, after which the NAS rebooted. During the reboot the situation was back at green/red flashing. During boot I only heard a single beep.
The four drive-leds were flashing during boot, now they're steady green.
During boot the disks were active, now they're silent (spinning but no read/write activity)
Code: Select all
for i in {a..d}; do echo -n /dev/sd$i ; hdparm -i /dev/sd$i | grep "Model"; done
for i in {1..4}; do echo "HDD$i" ; /sbin/get_hd_smartinfo -d $i; echo " "; done
cat /proc/mdstat
mdadm --detail /dev/md0
#done
Patrick M. Wilson
Victoria, BC Canada
QNAP TS-470 Pro w/ 4 * Western Digital WD30EFRX WD Reds (RAID5) - - Single 8.1TB Storage Pool FW: QTS 4.2.0 Build 20151023 - Kali Linux v1.06 (64bit)
Forums: View My Profile - Search My Posts - View My Photo - View My Location - Top Community Posters
QNAP: Turbo NAS User Manual - QNAP Wiki - QNAP Tutorials - QNAP FAQs
Please review: When you're asking a question, please include the following.
-
- Getting the hang of things
- Posts: 71
- Joined: Wed Nov 14, 2012 11:04 pm
Re: red/green led flashing - 2 days+
That will be tomorrow, I'm turning in for the night.
-
- Getting the hang of things
- Posts: 71
- Joined: Wed Nov 14, 2012 11:04 pm
Re: red/green led flashing - 2 days+
Here you go, seems to look good, right? (except for the first Grep for what seeems to be disk models)
For debugging the first part, the contents of /dev is:
Code: Select all
[~] # for i in {a..d}; do echo -n /dev/sd$i ; hdparm -i /dev/sd$i | grep "Model"; done
/dev/sda HDIO_GET_IDENTITY failed: Invalid argument
/dev/sdb HDIO_GET_IDENTITY failed: Invalid argument
/dev/sdc HDIO_GET_IDENTITY failed: Invalid argument
/dev/sdd HDIO_GET_IDENTITY failed: Invalid argument
[~] # for i in {1..4}; do echo "HDD$i" ; /sbin/get_hd_smartinfo -d $i; echo " "; done
HDD1
001 Raw_Read_Error_Rate 6011113 103 099 006 OK
003 Spin_Up_Time 0 100 100 000 OK
004 Start_Stop_Count 2748 098 098 020 OK
005 Reallocated_Sector_Ct 0 100 100 036 OK
007 Seek_Error_Rate 4789616550676 058 046 030 OK
009 Power_On_Hours 29735 067 067 000 OK
010 Spin_Retry_Count 0 100 100 097 OK
012 Power_Cycle_Count 67 100 100 020 OK
183 Unknown_Attribute 0 100 100 000 OK
184 End_To_End_Error 0 100 100 099 OK
187 Uncorrectable_Errors 12 088 088 000 OK
188 Unknown_Attribute 12885098499 100 099 000 OK
189 Unknown_Attribute 272 001 001 000 OK
190 Temperature_Celsius 454688795 073 057 045 OK
194 Temperature_Celsius 27 027 043 000 OK
195 Hardware_ECC_Recovered 6011113 049 028 000 OK
197 Current_Pending_Sector 2 100 100 000 OK
198 Offline_Uncorrectable 2 100 100 000 OK
199 UDMA_CRC_Error_Count 0 200 200 000 OK
240 Head_Flying_Hours 205363861288074 100 253 000 OK
241 Lifetime_Writes_From_Host 2967987848 100 253 000 OK
242 Lifetime_Reads_To_Host 3398032728 100 253 000 OK
HDD2
001 Raw_Read_Error_Rate 174140448 118 099 006 OK
003 Spin_Up_Time 0 092 092 000 OK
004 Start_Stop_Count 107 100 100 020 OK
005 Reallocated_Sector_Ct 0 100 100 010 OK
007 Seek_Error_Rate 18722404 072 060 030 OK
009 Power_On_Hours 919 099 099 000 OK
010 Spin_Retry_Count 0 100 100 097 OK
012 Power_Cycle_Count 10 100 100 020 OK
183 Unknown_Attribute 0 100 100 000 OK
184 End_To_End_Error 0 100 100 099 OK
187 Uncorrectable_Errors 0 100 100 000 OK
188 Unknown_Attribute 0 100 100 000 OK
189 Unknown_Attribute 0 100 100 000 OK
190 Temperature_Celsius 437846042 074 063 045 OK
191 G-Sense_Error_Rate 0 100 100 000 OK
192 Power-Off_Retract_Count 9 100 100 000 OK
193 Load_Cycle_Count 24166 088 088 000 OK
194 Temperature_Celsius 26 026 040 000 OK
197 Current_Pending_Sector 0 100 100 000 OK
198 Offline_Uncorrectable 0 100 100 000 OK
199 UDMA_CRC_Error_Count 0 200 200 000 OK
240 Head_Flying_Hours 175732881883949 100 253 000 OK
241 Lifetime_Writes_From_Host 4625342094 100 253 000 OK
242 Lifetime_Reads_To_Host 1262983186 100 253 000 OK
HDD3
001 Raw_Read_Error_Rate 0 200 200 051 OK
003 Spin_Up_Time 6250 175 174 021 OK
004 Start_Stop_Count 1453 099 099 000 OK
005 Reallocated_Sector_Ct 0 200 200 140 OK
007 Seek_Error_Rate 0 200 200 000 OK
009 Power_On_Hours 17482 077 077 000 OK
010 Spin_Retry_Count 0 100 100 000 OK
011 Calibration_Retry_Count 0 100 100 000 OK
012 Power_Cycle_Count 183 100 100 000 OK
192 Power-Off_Retract_Count 181 200 200 000 OK
193 Load_Cycle_Count 933758 001 001 000 OK
194 Temperature_Celsius 28 122 108 000 OK
196 Reallocated_Event_Count 0 200 200 000 OK
197 Current_Pending_Sector 0 200 200 000 OK
198 Offline_Uncorrectable 0 200 200 000 OK
199 UDMA_CRC_Error_Count 0 200 200 000 OK
200 Multi_Zone_Error_Rate 0 200 200 000 OK
HDD4
001 Raw_Read_Error_Rate 80805168 114 099 006 OK
003 Spin_Up_Time 0 094 094 000 OK
004 Start_Stop_Count 1442 099 099 020 OK
005 Reallocated_Sector_Ct 0 100 100 010 OK
007 Seek_Error_Rate 6674626371825 052 047 030 OK
009 Power_On_Hours 15382 083 083 000 OK
010 Spin_Retry_Count 0 100 100 097 OK
012 Power_Cycle_Count 184 100 100 020 OK
183 Unknown_Attribute 0 100 100 000 OK
184 End_To_End_Error 0 100 100 099 OK
187 Uncorrectable_Errors 0 100 100 000 OK
188 Unknown_Attribute 0 100 100 000 OK
189 Unknown_Attribute 0 100 100 000 OK
190 Temperature_Celsius 437780506 074 058 045 OK
191 G-Sense_Error_Rate 0 100 100 000 OK
192 Power-Off_Retract_Count 183 100 100 000 OK
193 Load_Cycle_Count 81361 060 060 000 OK
194 Temperature_Celsius 26 026 042 000 OK
197 Current_Pending_Sector 0 100 100 000 OK
198 Offline_Uncorrectable 0 100 100 000 OK
199 UDMA_CRC_Error_Count 0 200 200 000 OK
240 Head_Flying_Hours 215534343829976 100 253 000 OK
241 Lifetime_Writes_From_Host 13386797022 100 253 000 OK
242 Lifetime_Reads_To_Host 55097727444 100 253 000 OK
[~] # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md13 : active raid1 sda4[0] sdd4[3] sdc4[2] sdb4[1]
458880 blocks [4/4] [UUUU]
bitmap: 0/57 pages [0KB], 4KB chunk
md4 : active raid1 sdd2[2](S) sdc2[3](S) sdb2[1] sda2[0]
530048 blocks [2/2] [UU]
md9 : active raid1 sda1[0] sdd1[3] sdc1[2] sdb1[1]
530048 blocks [4/4] [UUUU]
bitmap: 0/65 pages [0KB], 4KB chunk
md0 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1]
5855836800 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
unused devices: <none>
[~] # mdadm --detail /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Tue Mar 29 14:14:54 2011
Raid Level : raid5
Array Size : 5855836800 (5584.56 GiB 5996.38 GB)
Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Mon Feb 2 08:56:31 2015
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
UUID : 11c4dca7:47615b17:ab1a3306:17e17844
Events : 0.2275467
Number Major Minor RaidDevice State
0 8 3 0 active sync /dev/sda3
1 8 19 1 active sync /dev/sdb3
2 8 35 2 active sync /dev/sdc3
3 8 51 3 active sync /dev/sdd3
Code: Select all
aes loop148 loop227 loop77 sdc sdm3 sdt11 sdyb sdyh7 sdzf4
audio@ loop149 loop228 loop78 sdc1 sdm4 sdt12 sdyb1 sdyh8 sdzf5
audio0 loop15 loop229 loop79 sdc2 sdm5 sdt2 sdyb10 sdyh9 sdzf6
audio1 loop150 loop23 loop8 sdc3 sdm6 sdt3 sdyb11 sdz sdzf7
audio2 loop151 loop230 loop80 sdc4 sdm7 sdt4 sdyb12 sdz1 sdzf8
audio3 loop152 loop231 loop81 sdd sdm8 sdt5 sdyb2 sdz10 sdzf9
audio4 loop153 loop232 loop82 sdd1 sdm9 sdt6 sdyb3 sdz11 sdzg
console loop154 loop233 loop83 sdd2 sdn sdt7 sdyb4 sdz12 sdzg1
crypto loop155 loop234 loop84 sdd3 sdn1 sdt8 sdyb5 sdz2 sdzg10
dsp@ loop156 loop235 loop85 sdd4 sdn10 sdt9 sdyb6 sdz3 sdzg11
dsp0 loop157 loop236 loop86 sde sdn11 sdu sdyb7 sdz4 sdzg12
dsp1 loop158 loop237 loop87 sde1 sdn12 sdu1 sdyb8 sdz5 sdzg2
dsp2 loop159 loop238 loop88 sde2 sdn2 sdu10 sdyb9 sdz6 sdzg3
dsp3 loop16 loop239 loop89 sde3 sdn3 sdu11 sdyc sdz7 sdzg4
dsp4 loop160 loop24 loop9 sde4 sdn4 sdu12 sdyc1 sdz8 sdzg5
fb0 loop161 loop240 loop90 sdf sdn5 sdu2 sdyc10 sdz9 sdzg6
fb1 loop162 loop241 loop91 sdf1 sdn6 sdu3 sdyc11 sdza sdzg7
fd@ loop163 loop242 loop92 sdf2 sdn7 sdu4 sdyc12 sdza1 sdzg8
fnotify loop164 loop243 loop93 sdf3 sdn8 sdu5 sdyc2 sdza10 sdzg9
fuse loop165 loop244 loop94 sdf4 sdn9 sdu6 sdyc3 sdza11 sdzh
hda loop166 loop245 loop95 sdg sdo sdu7 sdyc4 sdza12 sdzh1
hda1 loop167 loop246 loop96 sdg1 sdo1 sdu8 sdyc5 sdza2 sdzh10
hda2 loop168 loop247 loop97 sdg2 sdo10 sdu9 sdyc6 sdza3 sdzh11
hda3 loop169 loop248 loop98 sdg3 sdo11 sdv sdyc7 sdza4 sdzh12
hda4 loop17 loop249 loop99 sdg4 sdo12 sdv1 sdyc8 sdza5 sdzh2
hda5 loop170 loop25 md0 sdh sdo2 sdv10 sdyc9 sdza6 sdzh3
hda6 loop171 loop250 md1 sdh1 sdo3 sdv11 sdyd sdza7 sdzh4
hdb loop172 loop251 md10 sdh2 sdo4 sdv12 sdyd1 sdza8 sdzh5
hdb1 loop173 loop252 md11 sdh3 sdo5 sdv2 sdyd10 sdza9 sdzh6
hdb2 loop174 loop253 md12 sdh4 sdo6 sdv3 sdyd11 sdzb sdzh7
hdb3 loop175 loop254 md2 sdi sdo7 sdv4 sdyd12 sdzb1 sdzh8
hdb4 loop176 loop255 md3 sdi1 sdo8 sdv5 sdyd2 sdzb10 sdzh9
log@ loop177 loop26 md4 sdi10 sdo9 sdv6 sdyd3 sdzb11 sg0
loop0 loop178 loop27 md5 sdi11 sdp sdv7 sdyd4 sdzb12 sg1
loop1 loop179 loop28 md6 sdi12 sdp1 sdv8 sdyd5 sdzb2 sg10
loop10 loop18 loop29 md7 sdi2 sdp10 sdv9 sdyd6 sdzb3 sg11
loop100 loop180 loop3 md8 sdi3 sdp11 sdw sdyd7 sdzb4 sg12
loop101 loop181 loop30 md9 sdi4 sdp12 sdw1 sdyd8 sdzb5 sg13
loop102 loop182 loop31 mem sdi5 sdp2 sdw10 sdyd9 sdzb6 sg14
loop103 loop183 loop32 mixer@ sdi6 sdp3 sdw11 sdye sdzb7 sg15
loop104 loop184 loop33 mixer0 sdi7 sdp4 sdw12 sdye1 sdzb8 sg16
loop105 loop185 loop34 mixer1 sdi8 sdp5 sdw2 sdye10 sdzb9 sg17
loop106 loop186 loop35 mixer2 sdi9 sdp6 sdw3 sdye11 sdzc sg18
loop107 loop187 loop36 mixer3 sdj sdp7 sdw4 sdye12 sdzc1 sg19
loop108 loop188 loop37 mixer4 sdj1 sdp8 sdw5 sdye2 sdzc10 sg2
loop109 loop189 loop38 mtd0 sdj10 sdp9 sdw6 sdye3 sdzc11 sg20
loop11 loop19 loop39 mtd1 sdj11 sdq sdw7 sdye4 sdzc12 sg21
loop110 loop190 loop4 mtd2 sdj12 sdq1 sdw8 sdye5 sdzc2 sg22
loop111 loop191 loop40 mtd3 sdj2 sdq10 sdw9 sdye6 sdzc3 sg23
loop112 loop192 loop41 mtd4 sdj3 sdq11 sdx sdye7 sdzc4 sg24
loop113 loop193 loop42 mtd5 sdj4 sdq12 sdx1 sdye8 sdzc5 sg25
loop114 loop194 loop43 mtd6 sdj5 sdq2 sdx10 sdye9 sdzc6 sg3
loop115 loop195 loop44 mtdblock0 sdj6 sdq3 sdx11 sdyf sdzc7 sg4
loop116 loop196 loop45 mtdblock1 sdj7 sdq4 sdx12 sdyf1 sdzc8 sg5
loop117 loop197 loop46 mtdblock2 sdj8 sdq5 sdx2 sdyf10 sdzc9 sg6
loop118 loop198 loop47 mtdblock3 sdj9 sdq6 sdx3 sdyf11 sdzd sg7
loop119 loop199 loop48 mtdblock4 sdk sdq7 sdx4 sdyf12 sdzd1 sg8
loop12 loop2 loop49 mtdblock5 sdk1 sdq8 sdx5 sdyf2 sdzd10 sg9
loop120 loop20 loop5 mtdblock6 sdk10 sdq9 sdx6 sdyf3 sdzd11 sga@
loop121 loop200 loop50 net/ sdk11 sdr sdx7 sdyf4 sdzd12 sgb@
loop122 loop201 loop51 null sdk12 sdr1 sdx8 sdyf5 sdzd2 sgc@
loop123 loop202 loop52 pic sdk2 sdr10 sdx9 sdyf6 sdzd3 sgd@
loop124 loop203 loop53 ptmx sdk3 sdr11 sdy sdyf7 sdzd4 sge@
loop125 loop204 loop54 pts/ sdk4 sdr12 sdy1 sdyf8 sdzd5 sgf@
loop126 loop205 loop55 qraid1 sdk5 sdr2 sdy10 sdyf9 sdzd6 sgg@
loop127 loop206 loop56 ram@ sdk6 sdr3 sdy11 sdyg sdzd7 sgh@
loop128 loop207 loop57 ram0 sdk7 sdr4 sdy12 sdyg1 sdzd8 snd/
loop129 loop208 loop58 ram1 sdk8 sdr5 sdy2 sdyg10 sdzd9 stderr@
loop13 loop209 loop59 ram2 sdk9 sdr6 sdy3 sdyg11 sdze stdin@
loop130 loop21 loop6 ram3 sdl sdr7 sdy4 sdyg12 sdze1 stdout@
loop131 loop210 loop60 ram4 sdl1 sdr8 sdy5 sdyg2 sdze10 tty
loop132 loop211 loop61 ram5 sdl10 sdr9 sdy6 sdyg3 sdze11 tty0
loop133 loop212 loop62 ramdisk@ sdl11 sds sdy7 sdyg4 sdze12 tty1
loop134 loop213 loop63 random sdl12 sds1 sdy8 sdyg5 sdze2 tty2
loop135 loop214 loop64 rtc@ sdl2 sds10 sdy9 sdyg6 sdze3 ttyS0
loop136 loop215 loop65 rtc0 sdl3 sds11 sdya sdyg7 sdze4 ttyS1
loop137 loop216 loop66 rtcmon sdl4 sds12 sdya1 sdyg8 sdze5 ttyS2
loop138 loop217 loop67 sda sdl5 sds2 sdya10 sdyg9 sdze6 urandom
loop139 loop218 loop68 sda1 sdl6 sds3 sdya11 sdyh sdze7 usb/
loop14 loop219 loop69 sda2 sdl7 sds4 sdya12 sdyh1 sdze8 video@
loop140 loop22 loop7 sda3 sdl8 sds5 sdya2 sdyh10 sdze9 video0
loop141 loop220 loop70 sda4 sdl9 sds6 sdya3 sdyh11 sdzf video1
loop142 loop221 loop71 sdareal4 sdm sds7 sdya4 sdyh12 sdzf1 video2
loop143 loop222 loop72 sdb sdm1 sds8 sdya5 sdyh2 sdzf10 video3
loop144 loop223 loop73 sdb1 sdm10 sds9 sdya6 sdyh3 sdzf11 video4
loop145 loop224 loop74 sdb2 sdm11 sdt sdya7 sdyh4 sdzf12 watchdog
loop146 loop225 loop75 sdb3 sdm12 sdt1 sdya8 sdyh5 sdzf2 zero
loop147 loop226 loop76 sdb4 sdm2 sdt10 sdya9 sdyh6 sdzf3
- pwilson
- Guru
- Posts: 22533
- Joined: Fri Mar 06, 2009 11:20 am
- Location: Victoria, BC, Canada (UTC-08:00)
Re: red/green led flashing - 2 days+
I don't see anything obvious in that S.M.A.R.T. output. It shows very high usage, on aging drives. Anyway, as we can't identify what is preventing your NAS from booting properly, I think it is time to submit a ticket with the QNAP Helpdesk for further assistance.Atrejoe wrote:Here you go, seems to look good, right? (except for the first Grep for what seeems to be disk models)
Code: Select all
[~] # for i in {a..d}; do echo -n /dev/sd$i ; hdparm -i /dev/sd$i | grep "Model"; done /dev/sda HDIO_GET_IDENTITY failed: Invalid argument /dev/sdb HDIO_GET_IDENTITY failed: Invalid argument /dev/sdc HDIO_GET_IDENTITY failed: Invalid argument /dev/sdd HDIO_GET_IDENTITY failed: Invalid argument [~] # for i in {1..4}; do echo "HDD$i" ; /sbin/get_hd_smartinfo -d $i; echo " "; done HDD1 001 Raw_Read_Error_Rate 6011113 103 099 006 OK 003 Spin_Up_Time 0 100 100 000 OK 004 Start_Stop_Count 2748 098 098 020 OK 005 Reallocated_Sector_Ct 0 100 100 036 OK 007 Seek_Error_Rate 4789616550676 058 046 030 OK 009 Power_On_Hours 29735 067 067 000 OK 010 Spin_Retry_Count 0 100 100 097 OK 012 Power_Cycle_Count 67 100 100 020 OK 183 Unknown_Attribute 0 100 100 000 OK 184 End_To_End_Error 0 100 100 099 OK 187 Uncorrectable_Errors 12 088 088 000 OK 188 Unknown_Attribute 12885098499 100 099 000 OK 189 Unknown_Attribute 272 001 001 000 OK 190 Temperature_Celsius 454688795 073 057 045 OK 194 Temperature_Celsius 27 027 043 000 OK 195 Hardware_ECC_Recovered 6011113 049 028 000 OK 197 Current_Pending_Sector 2 100 100 000 OK 198 Offline_Uncorrectable 2 100 100 000 OK 199 UDMA_CRC_Error_Count 0 200 200 000 OK 240 Head_Flying_Hours 205363861288074 100 253 000 OK 241 Lifetime_Writes_From_Host 2967987848 100 253 000 OK 242 Lifetime_Reads_To_Host 3398032728 100 253 000 OK HDD2 001 Raw_Read_Error_Rate 174140448 118 099 006 OK 003 Spin_Up_Time 0 092 092 000 OK 004 Start_Stop_Count 107 100 100 020 OK 005 Reallocated_Sector_Ct 0 100 100 010 OK 007 Seek_Error_Rate 18722404 072 060 030 OK 009 Power_On_Hours 919 099 099 000 OK 010 Spin_Retry_Count 0 100 100 097 OK 012 Power_Cycle_Count 10 100 100 020 OK 183 Unknown_Attribute 0 100 100 000 OK 184 End_To_End_Error 0 100 100 099 OK 187 Uncorrectable_Errors 0 100 100 000 OK 188 Unknown_Attribute 0 100 100 000 OK 189 Unknown_Attribute 0 100 100 000 OK 190 Temperature_Celsius 437846042 074 063 045 OK 191 G-Sense_Error_Rate 0 100 100 000 OK 192 Power-Off_Retract_Count 9 100 100 000 OK 193 Load_Cycle_Count 24166 088 088 000 OK 194 Temperature_Celsius 26 026 040 000 OK 197 Current_Pending_Sector 0 100 100 000 OK 198 Offline_Uncorrectable 0 100 100 000 OK 199 UDMA_CRC_Error_Count 0 200 200 000 OK 240 Head_Flying_Hours 175732881883949 100 253 000 OK 241 Lifetime_Writes_From_Host 4625342094 100 253 000 OK 242 Lifetime_Reads_To_Host 1262983186 100 253 000 OK HDD3 001 Raw_Read_Error_Rate 0 200 200 051 OK 003 Spin_Up_Time 6250 175 174 021 OK 004 Start_Stop_Count 1453 099 099 000 OK 005 Reallocated_Sector_Ct 0 200 200 140 OK 007 Seek_Error_Rate 0 200 200 000 OK 009 Power_On_Hours 17482 077 077 000 OK 010 Spin_Retry_Count 0 100 100 000 OK 011 Calibration_Retry_Count 0 100 100 000 OK 012 Power_Cycle_Count 183 100 100 000 OK 192 Power-Off_Retract_Count 181 200 200 000 OK 193 Load_Cycle_Count 933758 001 001 000 OK 194 Temperature_Celsius 28 122 108 000 OK 196 Reallocated_Event_Count 0 200 200 000 OK 197 Current_Pending_Sector 0 200 200 000 OK 198 Offline_Uncorrectable 0 200 200 000 OK 199 UDMA_CRC_Error_Count 0 200 200 000 OK 200 Multi_Zone_Error_Rate 0 200 200 000 OK HDD4 001 Raw_Read_Error_Rate 80805168 114 099 006 OK 003 Spin_Up_Time 0 094 094 000 OK 004 Start_Stop_Count 1442 099 099 020 OK 005 Reallocated_Sector_Ct 0 100 100 010 OK 007 Seek_Error_Rate 6674626371825 052 047 030 OK 009 Power_On_Hours 15382 083 083 000 OK 010 Spin_Retry_Count 0 100 100 097 OK 012 Power_Cycle_Count 184 100 100 020 OK 183 Unknown_Attribute 0 100 100 000 OK 184 End_To_End_Error 0 100 100 099 OK 187 Uncorrectable_Errors 0 100 100 000 OK 188 Unknown_Attribute 0 100 100 000 OK 189 Unknown_Attribute 0 100 100 000 OK 190 Temperature_Celsius 437780506 074 058 045 OK 191 G-Sense_Error_Rate 0 100 100 000 OK 192 Power-Off_Retract_Count 183 100 100 000 OK 193 Load_Cycle_Count 81361 060 060 000 OK 194 Temperature_Celsius 26 026 042 000 OK 197 Current_Pending_Sector 0 100 100 000 OK 198 Offline_Uncorrectable 0 100 100 000 OK 199 UDMA_CRC_Error_Count 0 200 200 000 OK 240 Head_Flying_Hours 215534343829976 100 253 000 OK 241 Lifetime_Writes_From_Host 13386797022 100 253 000 OK 242 Lifetime_Reads_To_Host 55097727444 100 253 000 OK [~] # cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] md13 : active raid1 sda4[0] sdd4[3] sdc4[2] sdb4[1] 458880 blocks [4/4] [UUUU] bitmap: 0/57 pages [0KB], 4KB chunk md4 : active raid1 sdd2[2](S) sdc2[3](S) sdb2[1] sda2[0] 530048 blocks [2/2] [UU] md9 : active raid1 sda1[0] sdd1[3] sdc1[2] sdb1[1] 530048 blocks [4/4] [UUUU] bitmap: 0/65 pages [0KB], 4KB chunk md0 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1] 5855836800 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU] unused devices: <none> [~] # mdadm --detail /dev/md0 /dev/md0: Version : 00.90.03 Creation Time : Tue Mar 29 14:14:54 2011 Raid Level : raid5 Array Size : 5855836800 (5584.56 GiB 5996.38 GB) Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Mon Feb 2 08:56:31 2015 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K UUID : 11c4dca7:47615b17:ab1a3306:17e17844 Events : 0.2275467 Number Major Minor RaidDevice State 0 8 3 0 active sync /dev/sda3 1 8 19 1 active sync /dev/sdb3 2 8 35 2 active sync /dev/sdc3 3 8 51 3 active sync /dev/sdd3
You might want to use this time to get a complete backup of all of your NAS data and settings. Going forward you might want to consider buying RAID certified drives. Both Western Digital and Seagate sell NAS-specific drives now, so there is no need to buy non-RAID/Eco-Green drives any longer. I use WD Reds here.
Perhaps the output of:
Code: Select all
dmesg
Patrick M. Wilson
Victoria, BC Canada
QNAP TS-470 Pro w/ 4 * Western Digital WD30EFRX WD Reds (RAID5) - - Single 8.1TB Storage Pool FW: QTS 4.2.0 Build 20151023 - Kali Linux v1.06 (64bit)
Forums: View My Profile - Search My Posts - View My Photo - View My Location - Top Community Posters
QNAP: Turbo NAS User Manual - QNAP Wiki - QNAP Tutorials - QNAP FAQs
Please review: When you're asking a question, please include the following.
-
- Getting the hang of things
- Posts: 71
- Joined: Wed Nov 14, 2012 11:04 pm
Re: red/green led flashing - 2 days+
Comment noted, when I will upgrade or replace my drives I will look for better compatible models. I will also contact QNAP support.
Do you have any idea on how I could backup this data now, as I can only see it from the SSH command prompt.
dmesg returns:
Do you have any idea on how I could backup this data now, as I can only see it from the SSH command prompt.
dmesg returns:
Code: Select all
[~] # dmesg
[ 516.100000] sd 2:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.
81 TiB)
[ 516.100000] sd 2:0:0:0: [sda] 0-byte physical blocks
[ 516.100000] sd 2:0:0:0: Attached scsi generic sg0 type 0
[ 516.110000] sd 2:0:0:0: [sda] Write Protect is off
[ 516.110000] sd 2:0:0:0: [sda] Mode Sense: 23 00 00 00
[ 516.120000] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, does
n't support DPO or FUA
[ 516.120000] sd 2:0:0:0: [sda] Sector size 0 reported, assuming 512.
[ 516.120000] sda: sda1 sda2 sda3 sda4
[ 516.200000] sd 2:0:0:0: [sda] Sector size 0 reported, assuming 512.
[ 516.200000] sd 2:0:0:0: [sda] Attached SCSI disk
[ 534.090000] ENABLE_WRITE_CACHE (current: enabled).
[ 534.100000] scsi 3:0:0:0: Direct-Access Seagate ST4000DM000-1F21 CC52 PQ
: 0 ANSI: 5
[ 534.100000] Check proc_name[mvSata].
[ 534.100000] Check proc_name[mvSata].
[ 534.110000] sd 3:0:0:0: [sdb] Sector size 0 reported, assuming 512.
[ 534.110000] sd 3:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.
63 TiB)
[ 534.110000] sd 3:0:0:0: [sdb] 0-byte physical blocks
[ 534.110000] sd 3:0:0:0: Attached scsi generic sg1 type 0
[ 534.120000] sd 3:0:0:0: [sdb] Write Protect is off
[ 534.120000] sd 3:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 534.130000] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, does
n't support DPO or FUA
[ 534.130000] sd 3:0:0:0: [sdb] Sector size 0 reported, assuming 512.
[ 534.130000] sdb: sdb1 sdb2 sdb3 sdb4
[ 534.240000] sd 3:0:0:0: [sdb] Sector size 0 reported, assuming 512.
[ 534.240000] sd 3:0:0:0: [sdb] Attached SCSI disk
[ 577.100000] ENABLE_WRITE_CACHE (current: enabled).
[ 577.110000] scsi 4:0:0:0: Direct-Access WDC WD30EZRX-00DC0B0 80.0 PQ
: 0 ANSI: 5
[ 577.110000] Check proc_name[mvSata].
[ 577.110000] Check proc_name[mvSata].
[ 577.120000] sd 4:0:0:0: [sdc] Sector size 0 reported, assuming 512.
[ 577.120000] sd 4:0:0:0: [sdc] 5860533168 512-byte logical blocks: (3.00 TB/2.
72 TiB)
[ 577.120000] sd 4:0:0:0: [sdc] 0-byte physical blocks
[ 577.120000] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 577.130000] sd 4:0:0:0: [sdc] Write Protect is off
[ 577.130000] sd 4:0:0:0: [sdc] Mode Sense: 23 00 00 00
[ 577.140000] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, does
n't support DPO or FUA
[ 577.140000] sd 4:0:0:0: [sdc] Sector size 0 reported, assuming 512.
[ 577.140000] sdc: sdc1 sdc2 sdc3 sdc4
[ 577.260000] sd 4:0:0:0: [sdc] Sector size 0 reported, assuming 512.
[ 577.260000] sd 4:0:0:0: [sdc] Attached SCSI disk
[ 613.110000] ENABLE_WRITE_CACHE (current: enabled).
[ 613.120000] scsi 5:0:0:0: Direct-Access Seagate ST2000DM001-1CH1 CC24 PQ
: 0 ANSI: 5
[ 613.120000] Check proc_name[mvSata].
[ 613.120000] Check proc_name[mvSata].
[ 613.130000] sd 5:0:0:0: [sdd] Sector size 0 reported, assuming 512.
[ 613.130000] sd 5:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.
81 TiB)
[ 613.130000] sd 5:0:0:0: [sdd] 0-byte physical blocks
[ 613.130000] sd 5:0:0:0: Attached scsi generic sg3 type 0
[ 613.140000] sd 5:0:0:0: [sdd] Write Protect is off
[ 613.140000] sd 5:0:0:0: [sdd] Mode Sense: 23 00 00 00
[ 613.150000] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, does
n't support DPO or FUA
[ 613.150000] sd 5:0:0:0: [sdd] Sector size 0 reported, assuming 512.
[ 613.150000] sdd: sdd1 sdd2 sdd3 sdd4
[ 613.220000] sd 5:0:0:0: [sdd] Sector size 0 reported, assuming 512.
[ 613.220000] sd 5:0:0:0: [sdd] Attached SCSI disk
[ 617.260000] kjournald starting. Commit interval 5 seconds
[ 617.260000] EXT3-fs (sda1): mounted filesystem with writeback data mode
[ 617.410000] kjournald starting. Commit interval 5 seconds
[ 617.410000] EXT3-fs (sdb1): mounted filesystem with writeback data mode
[ 617.570000] kjournald starting. Commit interval 5 seconds
[ 617.570000] EXT3-fs (sdc1): mounted filesystem with writeback data mode
[ 617.770000] kjournald starting. Commit interval 5 seconds
[ 617.770000] EXT3-fs (sdd1): mounted filesystem with writeback data mode
[ 618.290000] md: md9 stopped.
[ 618.390000] md: bind<sdb1>
[ 618.390000] md: bind<sdc1>
[ 618.390000] md: bind<sdd1>
[ 618.390000] md: bind<sda1>
[ 618.400000] raid1: raid set md9 active with 4 out of 4 mirrors
[ 618.410000] md9: bitmap initialized from disk: read 5/5 pages, set 0 bits
[ 618.410000] created bitmap (65 pages) for device md9
[ 618.440000] md9: detected capacity change from 0 to 542769152
[ 618.470000] md9: unknown partition table
[ 621.310000] kjournald starting. Commit interval 5 seconds
[ 621.320000] EXT3-fs (md9): using internal journal
[ 621.320000] EXT3-fs (md9): mounted filesystem with writeback data mode
[ 621.980000] kjournald starting. Commit interval 5 seconds
[ 621.990000] EXT3-fs (md9): using internal journal
[ 621.990000] EXT3-fs (md9): mounted filesystem with writeback data mode
[ 628.880000] md: bind<sda2>
[ 628.880000] raid1: raid set md4 active with 1 out of 1 mirrors
[ 628.880000] md4: detected capacity change from 0 to 542769152
[ 629.920000] md4: unknown partition table
[ 632.010000] Adding 530040k swap on /dev/md4. Priority:-1 extents:1 across:53
0040k
[ 638.140000] md: bind<sdb2>
[ 638.170000] RAID1 conf printout:
[ 638.170000] --- wd:1 rd:2
[ 638.170000] disk 0, wo:0, o:1, dev:sda2
[ 638.170000] disk 1, wo:1, o:1, dev:sdb2
[ 638.170000] md: recovery of RAID array md4
[ 638.170000] md: minimum _guaranteed_ speed: 5000 KB/sec/disk.
[ 638.170000] md: using maximum available idle IO bandwidth (but not more than
200000 KB/sec) for recovery.
[ 638.170000] md: using 128k window, over a total of 530048 blocks.
[ 640.450000] md: bind<sdc2>
[ 642.760000] md: bind<sdd2>
[ 645.920000] md: md4: recovery done.
[ 645.980000] RAID1 conf printout:
[ 645.980000] --- wd:2 rd:2
[ 645.980000] disk 0, wo:0, o:1, dev:sda2
[ 645.980000] disk 1, wo:0, o:1, dev:sdb2
[ 653.760000] md: md0 still in use.
[ 653.880000] md: bind<sdb3>
[ 653.880000] md: bind<sdc3>
[ 653.880000] md: bind<sdd3>
[ 653.880000] md: bind<sda3>
[ 653.890000] raid5: device sda3 operational as raid disk 0
[ 653.890000] raid5: device sdd3 operational as raid disk 3
[ 653.890000] raid5: device sdc3 operational as raid disk 2
[ 653.890000] raid5: device sdb3 operational as raid disk 1
[ 653.910000] raid5: allocated 67488kB for md0
[ 653.910000] 0: w=1 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[ 653.910000] 3: w=2 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[ 653.910000] 2: w=3 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[ 653.910000] 1: w=4 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[ 653.910000] raid5: raid level 5 set md0 active with 4 out of 4 devices, algor
ithm 2
[ 653.910000] RAID5 conf printout:
[ 653.910000] --- rd:4 wd:4
[ 653.910000] disk 0, o:1, dev:sda3
[ 653.910000] disk 1, o:1, dev:sdb3
[ 653.910000] disk 2, o:1, dev:sdc3
[ 653.910000] disk 3, o:1, dev:sdd3
[ 653.910000] md0: detected capacity change from 0 to 5996376883200
[ 655.140000] md0: unknown partition table
[ 678.090000] EXT4-fs (md0): mounted filesystem with ordered data mode
[ 687.000000] md: md13 stopped.
[ 687.060000] md: bind<sdb4>
[ 687.060000] md: bind<sdc4>
[ 687.060000] md: bind<sdd4>
[ 687.060000] md: bind<sda4>
[ 687.070000] raid1: raid set md13 active with 4 out of 4 mirrors
[ 687.080000] md13: bitmap initialized from disk: read 4/4 pages, set 0 bits
[ 687.080000] created bitmap (57 pages) for device md13
[ 687.090000] md13: detected capacity change from 0 to 469893120
[ 687.120000] md13: unknown partition table
[ 692.290000] kjournald starting. Commit interval 5 seconds
[ 692.290000] EXT3-fs (md13): using internal journal
[ 692.290000] EXT3-fs (md13): recovery complete
[ 692.290000] EXT3-fs (md13): mounted filesystem with writeback data mode
[~] #
- pwilson
- Guru
- Posts: 22533
- Joined: Fri Mar 06, 2009 11:20 am
- Location: Victoria, BC, Canada (UTC-08:00)
Re: red/green led flashing - 2 days+
I would probably do it from the command line with commands like:Atrejoe wrote:Comment noted, when I will upgrade or replace my drives I will look for better compatible models. I will also contact QNAP support.
Do you have any idea on how I could backup this data now, as I can only see it from the SSH command prompt.
dmesg returns:Code: Select all
[~] # dmesg [ 516.100000] sd 2:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1. 81 TiB) [ 516.100000] sd 2:0:0:0: [sda] 0-byte physical blocks [ 516.100000] sd 2:0:0:0: Attached scsi generic sg0 type 0 [ 516.110000] sd 2:0:0:0: [sda] Write Protect is off [ 516.110000] sd 2:0:0:0: [sda] Mode Sense: 23 00 00 00 [ 516.120000] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, does n't support DPO or FUA [ 516.120000] sd 2:0:0:0: [sda] Sector size 0 reported, assuming 512. [ 516.120000] sda: sda1 sda2 sda3 sda4 [ 516.200000] sd 2:0:0:0: [sda] Sector size 0 reported, assuming 512. [ 516.200000] sd 2:0:0:0: [sda] Attached SCSI disk [ 534.090000] ENABLE_WRITE_CACHE (current: enabled). [ 534.100000] scsi 3:0:0:0: Direct-Access Seagate ST4000DM000-1F21 CC52 PQ : 0 ANSI: 5 [ 534.100000] Check proc_name[mvSata]. [ 534.100000] Check proc_name[mvSata]. [ 534.110000] sd 3:0:0:0: [sdb] Sector size 0 reported, assuming 512. [ 534.110000] sd 3:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3. 63 TiB) [ 534.110000] sd 3:0:0:0: [sdb] 0-byte physical blocks [ 534.110000] sd 3:0:0:0: Attached scsi generic sg1 type 0 [ 534.120000] sd 3:0:0:0: [sdb] Write Protect is off [ 534.120000] sd 3:0:0:0: [sdb] Mode Sense: 23 00 00 00 [ 534.130000] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, does n't support DPO or FUA [ 534.130000] sd 3:0:0:0: [sdb] Sector size 0 reported, assuming 512. [ 534.130000] sdb: sdb1 sdb2 sdb3 sdb4 [ 534.240000] sd 3:0:0:0: [sdb] Sector size 0 reported, assuming 512. [ 534.240000] sd 3:0:0:0: [sdb] Attached SCSI disk [ 577.100000] ENABLE_WRITE_CACHE (current: enabled). [ 577.110000] scsi 4:0:0:0: Direct-Access WDC WD30EZRX-00DC0B0 80.0 PQ : 0 ANSI: 5 [ 577.110000] Check proc_name[mvSata]. [ 577.110000] Check proc_name[mvSata]. [ 577.120000] sd 4:0:0:0: [sdc] Sector size 0 reported, assuming 512. [ 577.120000] sd 4:0:0:0: [sdc] 5860533168 512-byte logical blocks: (3.00 TB/2. 72 TiB) [ 577.120000] sd 4:0:0:0: [sdc] 0-byte physical blocks [ 577.120000] sd 4:0:0:0: Attached scsi generic sg2 type 0 [ 577.130000] sd 4:0:0:0: [sdc] Write Protect is off [ 577.130000] sd 4:0:0:0: [sdc] Mode Sense: 23 00 00 00 [ 577.140000] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, does n't support DPO or FUA [ 577.140000] sd 4:0:0:0: [sdc] Sector size 0 reported, assuming 512. [ 577.140000] sdc: sdc1 sdc2 sdc3 sdc4 [ 577.260000] sd 4:0:0:0: [sdc] Sector size 0 reported, assuming 512. [ 577.260000] sd 4:0:0:0: [sdc] Attached SCSI disk [ 613.110000] ENABLE_WRITE_CACHE (current: enabled). [ 613.120000] scsi 5:0:0:0: Direct-Access Seagate ST2000DM001-1CH1 CC24 PQ : 0 ANSI: 5 [ 613.120000] Check proc_name[mvSata]. [ 613.120000] Check proc_name[mvSata]. [ 613.130000] sd 5:0:0:0: [sdd] Sector size 0 reported, assuming 512. [ 613.130000] sd 5:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1. 81 TiB) [ 613.130000] sd 5:0:0:0: [sdd] 0-byte physical blocks [ 613.130000] sd 5:0:0:0: Attached scsi generic sg3 type 0 [ 613.140000] sd 5:0:0:0: [sdd] Write Protect is off [ 613.140000] sd 5:0:0:0: [sdd] Mode Sense: 23 00 00 00 [ 613.150000] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, does n't support DPO or FUA [ 613.150000] sd 5:0:0:0: [sdd] Sector size 0 reported, assuming 512. [ 613.150000] sdd: sdd1 sdd2 sdd3 sdd4 [ 613.220000] sd 5:0:0:0: [sdd] Sector size 0 reported, assuming 512. [ 613.220000] sd 5:0:0:0: [sdd] Attached SCSI disk [ 617.260000] kjournald starting. Commit interval 5 seconds [ 617.260000] EXT3-fs (sda1): mounted filesystem with writeback data mode [ 617.410000] kjournald starting. Commit interval 5 seconds [ 617.410000] EXT3-fs (sdb1): mounted filesystem with writeback data mode [ 617.570000] kjournald starting. Commit interval 5 seconds [ 617.570000] EXT3-fs (sdc1): mounted filesystem with writeback data mode [ 617.770000] kjournald starting. Commit interval 5 seconds [ 617.770000] EXT3-fs (sdd1): mounted filesystem with writeback data mode [ 618.290000] md: md9 stopped. [ 618.390000] md: bind<sdb1> [ 618.390000] md: bind<sdc1> [ 618.390000] md: bind<sdd1> [ 618.390000] md: bind<sda1> [ 618.400000] raid1: raid set md9 active with 4 out of 4 mirrors [ 618.410000] md9: bitmap initialized from disk: read 5/5 pages, set 0 bits [ 618.410000] created bitmap (65 pages) for device md9 [ 618.440000] md9: detected capacity change from 0 to 542769152 [ 618.470000] md9: unknown partition table [ 621.310000] kjournald starting. Commit interval 5 seconds [ 621.320000] EXT3-fs (md9): using internal journal [ 621.320000] EXT3-fs (md9): mounted filesystem with writeback data mode [ 621.980000] kjournald starting. Commit interval 5 seconds [ 621.990000] EXT3-fs (md9): using internal journal [ 621.990000] EXT3-fs (md9): mounted filesystem with writeback data mode [ 628.880000] md: bind<sda2> [ 628.880000] raid1: raid set md4 active with 1 out of 1 mirrors [ 628.880000] md4: detected capacity change from 0 to 542769152 [ 629.920000] md4: unknown partition table [ 632.010000] Adding 530040k swap on /dev/md4. Priority:-1 extents:1 across:53 0040k [ 638.140000] md: bind<sdb2> [ 638.170000] RAID1 conf printout: [ 638.170000] --- wd:1 rd:2 [ 638.170000] disk 0, wo:0, o:1, dev:sda2 [ 638.170000] disk 1, wo:1, o:1, dev:sdb2 [ 638.170000] md: recovery of RAID array md4 [ 638.170000] md: minimum _guaranteed_ speed: 5000 KB/sec/disk. [ 638.170000] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery. [ 638.170000] md: using 128k window, over a total of 530048 blocks. [ 640.450000] md: bind<sdc2> [ 642.760000] md: bind<sdd2> [ 645.920000] md: md4: recovery done. [ 645.980000] RAID1 conf printout: [ 645.980000] --- wd:2 rd:2 [ 645.980000] disk 0, wo:0, o:1, dev:sda2 [ 645.980000] disk 1, wo:0, o:1, dev:sdb2 [ 653.760000] md: md0 still in use. [ 653.880000] md: bind<sdb3> [ 653.880000] md: bind<sdc3> [ 653.880000] md: bind<sdd3> [ 653.880000] md: bind<sda3> [ 653.890000] raid5: device sda3 operational as raid disk 0 [ 653.890000] raid5: device sdd3 operational as raid disk 3 [ 653.890000] raid5: device sdc3 operational as raid disk 2 [ 653.890000] raid5: device sdb3 operational as raid disk 1 [ 653.910000] raid5: allocated 67488kB for md0 [ 653.910000] 0: w=1 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0 [ 653.910000] 3: w=2 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0 [ 653.910000] 2: w=3 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0 [ 653.910000] 1: w=4 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0 [ 653.910000] raid5: raid level 5 set md0 active with 4 out of 4 devices, algor ithm 2 [ 653.910000] RAID5 conf printout: [ 653.910000] --- rd:4 wd:4 [ 653.910000] disk 0, o:1, dev:sda3 [ 653.910000] disk 1, o:1, dev:sdb3 [ 653.910000] disk 2, o:1, dev:sdc3 [ 653.910000] disk 3, o:1, dev:sdd3 [ 653.910000] md0: detected capacity change from 0 to 5996376883200 [ 655.140000] md0: unknown partition table [ 678.090000] EXT4-fs (md0): mounted filesystem with ordered data mode [ 687.000000] md: md13 stopped. [ 687.060000] md: bind<sdb4> [ 687.060000] md: bind<sdc4> [ 687.060000] md: bind<sdd4> [ 687.060000] md: bind<sda4> [ 687.070000] raid1: raid set md13 active with 4 out of 4 mirrors [ 687.080000] md13: bitmap initialized from disk: read 4/4 pages, set 0 bits [ 687.080000] created bitmap (57 pages) for device md13 [ 687.090000] md13: detected capacity change from 0 to 469893120 [ 687.120000] md13: unknown partition table [ 692.290000] kjournald starting. Commit interval 5 seconds [ 692.290000] EXT3-fs (md13): using internal journal [ 692.290000] EXT3-fs (md13): recovery complete [ 692.290000] EXT3-fs (md13): mounted filesystem with writeback data mode [~] #
Code: Select all
/usr/bin/cp -rpav /share/MD0_DATA/Public /share/USBDisk1/Public
Code: Select all
/usr/bin/cp --help
Usage: /usr/bin/cp [OPTION]... [-T] SOURCE DEST
or: /usr/bin/cp [OPTION]... SOURCE... DIRECTORY
or: /usr/bin/cp [OPTION]... -t DIRECTORY SOURCE...
Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY.
Mandatory arguments to long options are mandatory for short options too.
-a, --archive same as -dpPR
--backup[=CONTROL] make a backup of each existing destination file
-b like --backup but does not accept an argument
--copy-contents copy contents of special files when recursive
-d same as --no-dereference --preserve=link
-f, --force if an existing destination file cannot be
opened, remove it and try again
-i, --interactive prompt before overwrite
-H follow command-line symbolic links
-l, --link link files instead of copying
-L, --dereference always follow symbolic links
-P, --no-dereference never follow symbolic links
-p same as --preserve=mode,ownership,timestamps
--preserve[=ATTR_LIST] preserve the specified attributes (default:
mode,ownership,timestamps), if possible
additional attributes: links, all
--no-preserve=ATTR_LIST don't preserve the specified attributes
--parents use full source file name under DIRECTORY
-R, -r, --recursive copy directories recursively
--remove-destination remove each existing destination file before
attempting to open it (contrast with --force)
--sparse=WHEN control creation of sparse files
--strip-trailing-slashes remove any trailing slashes from each SOURCE
argument
-s, --symbolic-link make symbolic links instead of copying
-S, --suffix=SUFFIX override the usual backup suffix
-t, --target-directory=DIRECTORY copy all SOURCE arguments into DIRECTORY
-T, --no-target-directory treat DEST as a normal file
-u, --update copy only when the SOURCE file is newer
than the destination file or when the
destination file is missing
-v, --verbose explain what is being done
-x, --one-file-system stay on this file system
--help display this help and exit
--version output version information and exit
Patrick M. Wilson
Victoria, BC Canada
QNAP TS-470 Pro w/ 4 * Western Digital WD30EFRX WD Reds (RAID5) - - Single 8.1TB Storage Pool FW: QTS 4.2.0 Build 20151023 - Kali Linux v1.06 (64bit)
Forums: View My Profile - Search My Posts - View My Photo - View My Location - Top Community Posters
QNAP: Turbo NAS User Manual - QNAP Wiki - QNAP Tutorials - QNAP FAQs
Please review: When you're asking a question, please include the following.