red/green led flashing - rebuilding for 2 days?

[pwilson]

Were you referring to my posting or SergioPlayboy's?

Both apparently.

[ihuetg]

Hi,

I have QnAP 212
Recently I tried to update firmware to 4.0.2... but it seemed to fail. When I read in forum I noticed that many people was posting issues with this new firmware ..so I decided NOT to update.

Today I added a second HDD 1 TB (the other is 2TB WD HDD). So I power off the unit, installed the new hdd and reboot... BUT AS ALL OF YOU: Continuous Red/green light... for hours... and NO device found by QFINDER.

I started to read forum and tried with unplugin alld hdd and boot...and OK ..my qfinder could now find it...but surprise : 4.0.2 FIRMWARE????

I connect (yes hot plug) my original HDD but light turn red/green and again nothing can be found....

I repeteated twice with the same result..negative.

I installed putty and followed the procedure:... (only issue is that never the HDD light was static green..it was always blinking)

4. Plug the disks back to NAS one by one in original order.
push in till the previous HDD led flashes constantly green.(Not Blinking)

5. Connect the NAS by SSH port 22, login as admin
(Putty Tutorial: http://www.webmasters-central.com/artic ... sh-client/)

6. Issue the commands to check disk space
# config_util 1 -> Start mirroring of the first partitions.
# storage_boot_init 1
# df

7. Please issue the following commands to copy back default configfile
# cp /etc/default_config/uLinux.conf /mnt/HDA_ROOT/.config/ (You can also replace the text 'uLinux.conf' with others )
# rm -r /etc/config
# ln -sf /mnt/HDA_ROOT/.config /etc/config
#setcfg -f /etc/config/uLinux.conf Misc configured TRUE
# reboot


this is a copy of answer to dmesg command: (After green light is blinking with NO HDD plugged)

login as: admin
admin@192.168.1.34's password:
[~] # dmesg
QNAP RTC initializing....
[ 3.360000] Initializing RTC is completed.
[ 3.380000] rtc kw_rtc: rtc core: registered kw-rtc as rtc0
[ 3.380000] RTC registered
[ 3.380000] watchdog_init: succeed to register misc device
[ 3.380000] Init WDT and Active SYSREST if WDT timeout
[ 3.380000] XOR registered 4 channels
[ 3.380000] XOR 2nd invalidate WA enabled
[ 3.380000] MV Buttons Driver Load
[ 3.380000] NetWinder Floating Point Emulator V0.97 (double precision)
[ 3.380000] audit: initializing netlink socket (disabled)
[ 3.380000] type=2000 audit(1378055662.000:1): initialized
[ 3.380000] VFS: Disk quotas dquot_6.5.2
[ 3.380000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 3.380000] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 3.380000] fuse init (API version 7.13)
[ 3.380000] msgmni has been set to 498
[ 3.380000] alg: No test for stdrng (krng)
[ 3.380000] io scheduler noop registered
[ 3.380000] io scheduler deadline registered
[ 3.380000] io scheduler cfq registered (default)
[ 3.390000] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 3.390000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[ 3.400000] console [ttyS0] enabled
[ 3.410000] serial8250.1: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A
[ 3.410000] brd: module loaded
[ 3.420000] loop: module loaded
[ 3.420000] qnap_pic_init: succeed to register misc device
[ 3.430000] tsinfo: create proc ata_time successfully
[ 3.430000] tsinfo: create proc ata_retry successfully
[ 3.440000] tsinfo: create proc systemp successfully
[ 3.440000] tsinfo: create proc systemp successfully
[ 3.450000] tsinfo: create proc systemp successfully
[ 3.450000] tsinfo: create proc systemp successfully
[ 3.460000] serial8250_PIC_init..uartclk = 200000000,baudDivisor = 651,irq = 34
[ 3.470000] Integrated Sata device found
[ 3.470000] IRQ 21/mvSata: IRQF_DISABLED is not guaranteed on shared IRQs
[ 5.520000] Spin up ...(0:0)
[ 7.520000] Spin up ...(0:1)
[ 9.520000] Spin up all...
[ 12.530000] [0 0]: Waiting for channel initialization.
[ 13.530000] [0 1]: Waiting for channel initialization.
[ 14.540000] scsi0 : Marvell SCSI to SATA adapter
[ 14.540000] scsi1 : Marvell SCSI to SATA adapter
[ 14.550000] SPI Serial flash detected @ 0xf4000000, 16384KB (64sec x 256KB)
[ 14.560000] Creating 6 MTD partitions on "spi_flash":
[ 14.560000] 0x000000000000-0x000000080000 : "U-Boot"
[ 14.570000] 0x000000200000-0x000000400000 : "Kernel"
[ 14.570000] 0x000000400000-0x000000d00000 : "RootFS"
[ 14.580000] 0x000000d00000-0x000001000000 : "RootFS2"
[ 14.590000] 0x000000080000-0x0000000c0000 : "U-Boot Config"
[ 14.590000] 0x0000000c0000-0x000000200000 : "NAS Config"
[ 14.600000] Loading Marvell Ethernet Driver:
[ 14.600000] o Cached descriptors in DRAM
[ 14.610000] o DRAM SW cache-coherency
[ 14.610000] o 1 Giga ports supported
[ 14.610000] o Single RX Queue support - ETH_DEF_RXQ=0
[ 14.620000] o Single TX Queue support - ETH_DEF_TXQ=0
[ 14.620000] o TCP segmentation offload (TSO) supported
[ 14.630000] o Large Receive offload (LRO) supported
[ 14.630000] o Receive checksum offload supported
[ 14.640000] o Transmit checksum offload supported
[ 14.640000] o Network Fast Processing (Routing) supported - (Disabled)
[ 14.650000] o Proc tool API enabled
[ 14.650000] o SKB Reuse supported - (Disabled)
[ 14.660000] o SKB Recycle supported - (Disabled)
[ 14.660000] o Rx descripors: q0=128
[ 14.670000] o Tx descripors: q0=532
[ 14.670000] o Loading network interface(s):
[ 14.680000] o register under mv88fx_eth platform
[ 14.680000] o eth0, ifindex = 2, GbE port = 0
[ 14.690000]
[ 14.690000] mvFpRuleDb (00000010): 0 entries, 0 bytes
[ 14.700000] Marvell debug tracing is on
[ 14.700000] Initializing USB Mass Storage driver...
[ 14.700000] usbcore: registered new interface driver usb-storage
[ 14.710000] USB Mass Storage support registered.
[ 14.720000] usb: create proc systemp successfully
[ 14.720000] usb: create proc systemp successfully
[ 14.720000] mice: PS/2 mouse device common for all mice
[ 14.730000] md: linear personality registered for level -1
[ 14.740000] md: raid0 personality registered for level 0
[ 14.740000] md: raid1 personality registered for level 1
[ 14.750000] TCP cubic registered
[ 14.750000] NET: Registered protocol family 17
[ 14.770000] rtc kw_rtc: setting system clock to 2013-09-01 17:14:34 UTC (1378055674)
[ 14.780000] md: Waiting for all devices to be available before autodetect
[ 14.790000] md: If you don't use raid, use raid=noautodetect
[ 14.800000] md: Autodetecting RAID arrays.
[ 14.800000] md: Scanned 0 and added 0 devices.
[ 14.800000] md: autorun ...
[ 14.810000] md: ... autorun DONE.
[ 14.810000] RAMDISK: gzip image found at block 0
[ 15.800000] VFS: Mounted root (ext2 filesystem) on device 1:0.
[ 15.800000] Freeing init memory: 136K
[ 16.190000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 16.200000] orion-ehci orion-ehci.0: Marvell Orion EHCI
[ 16.200000] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[ 16.240000] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[ 16.260000] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[ 16.260000] hub 1-0:1.0: USB hub found
[ 16.270000] hub 1-0:1.0: 1 port detected
[ 16.590000] usb 1-1: new high speed USB device using orion-ehci and address 2
[ 16.740000] hub 1-1:1.0: USB hub found
[ 16.790000] hub 1-1:1.0: 4 ports detected
[ 27.860000] xor: measuring software checksum speed
[ 27.910000] arm4regs : 1090.000 MB/sec
[ 27.960000] 8regs : 819.200 MB/sec
[ 28.010000] 32regs : 918.000 MB/sec
[ 28.010000] xor: using function: arm4regs (1090.000 MB/sec)
[ 28.200000] raid6: int32x1 84 MB/s
[ 28.370000] raid6: int32x2 116 MB/s
[ 28.540000] raid6: int32x4 122 MB/s
[ 28.710000] raid6: int32x8 114 MB/s
[ 28.710000] raid6: using algorithm int32x4 (122 MB/s)
[ 28.820000] md: raid6 personality registered for level 6
[ 28.830000] md: raid5 personality registered for level 5
[ 28.830000] md: raid4 personality registered for level 4
[ 28.880000] device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: dm-devel@redhat.com
[ 29.020000] cryptodev: driver 0.9 loaded.
[ 29.100000] usbcore: registered new interface driver usbhid
[ 29.100000] usbhid: USB HID core driver
[ 29.150000] usbcore: registered new interface driver usblp
[ 29.170000] sysinfo: Module loaded.
[ 29.310000] fnotify: module license 'non-GPL' taints kernel.
[ 29.310000] Disabling lock debugging due to kernel taint
[ 29.330000] fnotify: Load file notify kernel module.
[ 29.350000] fnotify: Global_Private_Data_List_Init()
[ 29.350000] fnotify: Launch the fnotify thread: 736
[ 29.360000] fnotify: The fnotify thread starts...
[ 29.420000] Enable WDT...
[ 31.310000] eth0: mac address changed
[ 31.340000] eth0: link down
[ 31.340000] eth0: started
[ 34.900000] eth0: link up, full duplex, speed 1 Gbps
[ 38.370000] eth0: stopped
[ 39.450000] eth0: link down
[ 39.460000] eth0: started
[ 43.380000] eth0: link up, full duplex, speed 1 Gbps
[ 63.640000] eth0: stopped
[ 65.200000] eth0: link down
[ 65.210000] eth0: started
[ 68.910000] eth0: link up, full duplex, speed 1 Gbps
[ 85.010000] eth0: stopped
[ 85.040000] eth0: link down
[ 85.040000] eth0: started
[ 88.840000] eth0: link up, full duplex, speed 1 Gbps
[ 101.170000] warning: process `pic_raw' used the deprecated sysctl system call with 8.1.2.
[~] #

(((((WITH NO HDD PLUGGED)))) ((( Light is GREEN blinking)))
System:
[~] # getcfg system version
4.0.2

[~] # df -h
Filesystem Size Used Available Use% Mounted on
/dev/ram0 32.9M 30.2M 2.7M 92% /
tmpfs 32.0M 40.0k 32.0M 0% /tmp
tmpfs 32.0M 0 32.0M 0% /.eaccelerator.tmp
[~] #

[~] # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]
unused devices: <none>

[~] # mount
/proc on /proc type proc (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
sysfs on /sys type sysfs (rw)
tmpfs on /tmp type tmpfs (rw,size=32M)
none on /proc/bus/usb type usbfs (rw)
tmpfs on /.eaccelerator.tmp type tmpfs (rw,size=32M)
[~] #


Now I follow your procedure and this is the result :

Plug IN HDD: (Green light Hdd Fixed)

dmesg
[ 364.150000] sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
[ 364.150000] sda: sda1 sda2 sda3 sda4
[ 364.210000] sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
[ 364.230000] sd 0:0:0:0: [sda] Attached SCSI disk
[ 401.200000] kjournald starting. Commit interval 5 seconds
[ 401.210000] EXT3-fs (sda1): mounted filesystem with writeback data mode
[ 401.330000] md: md9 stopped.
[ 401.350000] md: bind<sda1>
[ 401.350000] raid1: raid set md9 active with 1 out of 2 mirrors
[ 401.410000] md9: bitmap initialized from disk: read 5/5 pages, set 105244 bits

putt:y: config_util 1

[ 401.410000] created bitmap (65 pages) for device md9
[ 401.430000] md9: detected capacity change from 0 to 542769152
[ 401.450000] md9: unknown partition table
[ 403.560000] kjournald starting. Commit interval 5 seconds
[ 403.560000] EXT3-fs (md9): using internal journal
[ 403.570000] EXT3-fs (md9): mounted filesystem with writeback data mode

putty: storage_boot_init 1

[ 480.740000] md: bind<sda2>
[ 480.740000] raid1: raid set md2 active with 1 out of 1 mirrors
[ 480.750000] md2: detected capacity change from 0 to 542769152
[ 481.770000] md2: unknown partition table
[ 483.870000] Adding 530040k swap on /dev/md2. Priority:-1 extents:1 across:530040k

df:

[~] # df
Filesystem Size Used Available Use% Mounted on
/dev/ram0 32.9M 30.2M 2.7M 92% /
tmpfs 32.0M 68.0k 31.9M 0% /tmp
tmpfs 32.0M 0 32.0M 0% /.eaccelerator.tmp
/dev/md9 509.5M 117.4M 392.1M 23% /mnt/HDA_ROOT

then I type:

[~] # rm -r /etc/config
[~] # ln -sf /mnt/HDA_ROOT/.config /etc/config
[~] # setcfg -f /etc/config/uLinux.conf Misc configured TRUE
[~] # reboot

and it reboots.... HDD light is fixed green... status is off during at least 1 minute... the beep.... and again RED/GREEN LIGHT ¡¡¡¡¡

PLS HELP..REMOTE SUPPORT or whichever thing but I DONT WANT TO LOOSE MY 2TB DATA ¡¡¡

thx ¡¡
Ignacio.

[l.almeida]

hello all,

Same problem over here like Sergioplayboy and ihuetg, on a TS-419U! Didn't had the "guts" to use SSH acess, Qnapfinder works without the 4 WD 2TB disks on the device. Please help, the 4.0.2 firmware update went VERY WRONG!

Best regards, Luis Almeida (PT)

[fantomas]

I have QnAP 212
Recently I tried to update firmware to 4.0.2... but it seemed to fail. When I read in forum I noticed that many people was posting issues with this new firmware ..so I decided NOT to update.

Today I added a second HDD 1 TB (the other is 2TB WD HDD). So I power off the unit, installed the new hdd and reboot... BUT AS ALL OF YOU: Continuous Red/green light... for hours... and NO device found by QFINDER.

I started to read forum and tried with unplugin alld hdd and boot...and OK ..my qfinder could now find it...but surprise : 4.0.2 FIRMWARE????

Completely different issue, please open new topic.

[mouseball]

Hi there, new to the forums and have been reading up on issues that are similar - and this thread seems the most similar - I think my issue is similar to ihuetg.

I have the following:
- TS-421
- 2 x 3tb WD HDD (red)
- Upgraded to 4.0.2
- RAID 1 configuration

So I am getting the red/green flashing every 0.5 seconds and the two HDD lights are static green. The LED screen says "QNAP Turbo NAS Welcome," but then reboots after about five minutes and says "System booting >>>", and the cycle continues. Also, when running QFinder, it is not detected.
> I don't know if it is rebuilding the RAID as it keeps rebooting every five minutes

However, when I have removed the HDDs, it seems to boot up fine, and is detected when running QFinder - and it clearly shows that it has 4.0.2. And according to the QNAP wiki, the firmware seems right.

[jack22]

I have the same issue, update 4.0.2. the QNAP don't boot anymore with the harddrive inserted. If I remove the harddrives the QNAP boots fine and show up into the QFinder.

What are the next steps to get back my 1Tb Datas ?

Outch, I feel so nervous about this issue!!!!

[pwilson]

Hi there, new to the forums and have been reading up on issues that are similar - and this thread seems the most similar - I think my issue is similar to ihuetg.

I have the following:
- TS-421
- 2 x 3tb WD HDD (red)
- Upgraded to 4.0.2
- RAID 1 configuration

So I am getting the red/green flashing every 0.5 seconds and the two HDD lights are static green. The LED screen says "QNAP Turbo NAS Welcome," but then reboots after about five minutes and says "System booting >>>", and the cycle continues. Also, when running QFinder, it is not detected.
> I don't know if it is rebuilding the RAID as it keeps rebooting every five minutes

However, when I have removed the HDDs, it seems to boot up fine, and is detected when running QFinder - and it clearly shows that it has 4.0.2. And according to the QNAP wiki, the firmware seems right.

Finally. Someone in this thread, that actually provided some useful information to work with.

Please login to your NAS via SSH, login as "admin", and execute the following commands:

Code: Select all

echo "NAS Model: $(getsysinfo model)"
echo "Firmware:  $(getcfg system version)"
df -h
cat /proc/mdstat
dmesg
#done

Please cut&paste the output back to this message thread.

[erango]

HI All
same issue and did all the process of the re mounting .......same results
we can all copy past but seems that QNAP is missing something here
my 5T is down .....I am finish !!!!!

dear Patrick , how can I copy paste while the machine is red/green .... should I do the same process again ? I did it twice and nothing change

we need your urgent support , I also opened a ticket on the support Ticket ID: KCX-709-74699
thanks
Gonen

4. Plug the disks back to NAS one by one in original order.
push in till the previous HDD led flashes constantly green.(Not Blinking)

5. Connect the NAS by SSH port 22, login as admin
(Putty Tutorial: http://www.webmasters-central.com/artic ... sh-client/)

6. Issue the commands to check disk space
# config_util 1 -> Start mirroring of the first partitions.
# storage_boot_init 1
# df

7. Please issue the following commands to copy back default configfile
# cp /etc/default_config/uLinux.conf /mnt/HDA_ROOT/.config/ (You can also replace the text 'uLinux.conf' with others )
# rm -r /etc/config
# ln -sf /mnt/HDA_ROOT/.config /etc/config
#setcfg -f /etc/config/uLinux.conf Misc configured TRUE
# reboot

[jcharwell]

I have had a similar problem to the one described above. I went away for holidays and came back and one of the drives showed a failure. I did a bad block scan and it showed 185 bad blocks (drive #1). I was not able to get the exact same drive (Samsung HD204UI) SO I got a WD 3Tb RED drive (WD30EFRX-68EUZN0).
I plugged it in and the system started to rebuild the raid. After about 1.5 days, It completed.
Then spontaneously drive #4 showed a red light. I had problems earlier on with the drives not seating properly so I withdrew it and reseated it. It went green for a few moments then red again.
Then the new WD drive also went red. I also unseated it and reseated.
I followed the procedure for unplugging all the drives starting the NAS and replugging the drives 1 at a time.
It first has all drives green then after the boot is finished - #1 & #4 are red.
I can still access the NAS through SSH and I can use Windows to access the shares. I cannot access through the web gui, it gives the login screen then when I login it goes away for a long time (forever?) saying "Loading..."

I am now copying the necessary data from the shares onto a drive.

I ran the commands requested:
[~] # echo "NAS Model: $(getsysinfo model)"
NAS Model: TS-419P+
[~] # echo "Firmware: $(getcfg system version)"
Firmware: 4.0.2
[~] # df -h
Filesystem Size Used Available Use% Mounted on
/dev/ram0 32.9M 15.4M 17.6M 47% /
tmpfs 32.0M 356.0k 31.7M 1% /tmp
/dev/sda4 364.2M 319.6M 44.6M 88% /mnt/ext
/dev/md9 509.5M 139.0M 370.5M 27% /mnt/HDA_ROOT
/dev/md0 5.4T 2.7T 2.7T 50% /share/MD0_DATA
tmpfs 32.0M 1.3M 30.7M 4% /.eaccelerator.tmp
[~] # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md0 : active (read-only) raid5 sdb3[1] sdd3[3] sdc3[2]
5855836800 blocks level 5, 64k chunk, algorithm 2 [4/3] [_UUU]

md4 : active raid1 sdc2[1] sdb2[0]
530048 blocks [2/2] [UU]

md13 : active raid1 sdc4[0] sdb4[3] sda4[2] sdd4[1]
458880 blocks [4/4] [UUUU]
bitmap: 0/57 pages [0KB], 4KB chunk

md9 : active raid1 sda1[0] sdc1[3] sdb1[2] sdd1[1]
530048 blocks [4/4] [UUUU]
bitmap: 0/65 pages [0KB], 4KB chunk

unused devices: <none>
[~] # dmesg
86.570000] e8 d1 94 b0
[ 86.570000] sd 5:0:0:0: [sdd] ASC=0x0 ASCQ=0x0
[ 86.570000] sd 5:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 e8 d1 94 38 00 00 a0 00
[ 86.570000] end_request: I/O error, dev sdd, sector 3906049200
[ 86.570000] raid1: sdd4: rescheduling sector 37104
[ 86.570000] netlink_broadcast fail = -3
[ 119.240000] sd 5:0:0:0: [sdd] Unhandled sense code
[ 119.240000] sd 5:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x08
[ 119.240000] sd 5:0:0:0: [sdd] Sense Key : 0x3 [current] [descriptor]
[ 119.240000] Descriptor sense data with sense descriptors (in hex):
[ 119.240000] 72 03 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 119.250000] e8 d1 94 b0
[ 119.250000] sd 5:0:0:0: [sdd] ASC=0x0 ASCQ=0x0
[ 119.250000] sd 5:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 e8 d1 94 b0 00 00 08 00
[ 119.250000] end_request: I/O error, dev sdd, sector 3906049200
[ 119.250000] netlink_broadcast fail = -3
[ 119.910000] raid1:md13: read error corrected (8 sectors at 37224 on sdd4)
[ 119.910000] netlink_broadcast fail = -3
[ 119.940000] raid1: sdd4: redirecting sector 37104 to another mirror
[ 138.430000] fuse init (API version 7.13)
[ 138.700000] NET: Registered protocol family 5
[ 139.490000] xor: measuring software checksum speed
[ 139.540000] arm4regs : 1446.800 MB/sec
[ 139.590000] 8regs : 1096.400 MB/sec
[ 139.640000] 32regs : 1230.400 MB/sec
[ 139.640000] xor: using function: arm4regs (1446.800 MB/sec)
[ 139.880000] raid6: int32x1 112 MB/s
[ 140.050000] raid6: int32x2 155 MB/s
[ 140.220000] raid6: int32x4 162 MB/s
[ 140.390000] raid6: int32x8 151 MB/s
[ 140.390000] raid6: using algorithm int32x4 (162 MB/s)
[ 140.580000] md: raid6 personality registered for level 6
[ 140.580000] md: raid5 personality registered for level 5
[ 140.580000] md: raid4 personality registered for level 4
[ 140.640000] device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: dm-devel@redhat.com
[ 140.790000] cryptodev: driver 0.9 loaded.
[ 140.890000] usbcore: registered new interface driver usbhid
[ 140.890000] usbhid: USB HID core driver
[ 140.920000] usbcore: registered new interface driver usblp
[ 140.940000] sysinfo: Module loaded.
[ 141.080000] ufsd: module license 'Commercial product' taints kernel.
[ 141.080000] Disabling lock debugging due to kernel taint
[ 141.130000] ufsd: driver (8.6 U86_r184988_b10, LBD=ON, delalloc, acl, ioctl, ws, bdi, sd) loaded at bf1fb000
[ 141.130000] NTFS (with native replay) support included
[ 141.130000] Hfs+/HfsX support included
[ 141.130000] optimized: speed
[ 141.130000] Build_for__QNAP_TS_219_ARM_2012-02-09_U86_r184991_b10
[ 141.130000]
[ 141.320000] Slow work thread pool: Starting up
[ 141.320000] Slow work thread pool: Ready
[ 141.420000] fnotify: Load file notify kernel module.
[ 141.420000] fnotify: Global_Private_Data_List_Init()
[ 141.420000] fnotify: Launch the fnotify thread: 1341
[ 141.420000] fnotify: The fnotify thread starts...
[ 141.440000] lib80211: common routines for IEEE802.11 drivers
[ 141.440000] lib80211_crypt: registered algorithm 'NULL'
[ 141.590000] cfg80211: Calling CRDA to update world regulatory domain
[ 141.760000] Enable WDT...
[ 143.640000] usbcore: registered new interface driver snd-usb-audio
[ 143.690000] usbcore: registered new interface driver snd-usb-caiaq
[ 143.740000] Linux video capture interface: v2.00
[ 143.800000] usbcore: registered new interface driver uvcvideo
[ 143.800000] USB Video Class driver (v0.1.0)
[ 144.920000] eth0: mac address changed
[ 144.940000] eth0: started
[ 144.980000] eth1: mac address changed
[ 145.010000] eth1: link down
[ 145.010000] eth1: started
[ 147.900000] eth1: link up, full duplex, speed 1 Gbps
[ 156.470000] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended
[ 159.660000] kjournald starting. Commit interval 5 seconds
[ 159.670000] EXT3-fs (md9): using internal journal
[ 159.670000] EXT3-fs (md9): mounted filesystem with writeback data mode
[ 162.150000] active port 0 :139
[ 162.150000] active port 1 :445
[ 162.150000] active port 2 :20
[ 164.920000] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended
[ 168.410000] md: bind<sdb2>
[ 168.410000] raid1: raid set md4 active with 1 out of 1 mirrors
[ 168.410000] md4: detected capacity change from 0 to 542769152
[ 169.260000] md: md0 stopped.
[ 169.290000] md: md0 stopped.
[ 169.400000] md: bind<sdc3>
[ 169.400000] md: bind<sdd3>
[ 169.400000] md: bind<sda3>
[ 169.400000] md: bind<sdb3>
[ 169.400000] md: kicking non-fresh sda3 from array!
[ 169.400000] md: unbind<sda3>
[ 169.400000] md: export_rdev(sda3)
[ 169.410000] raid5: device sdb3 operational as raid disk 1
[ 169.410000] raid5: device sdd3 operational as raid disk 3
[ 169.410000] raid5: device sdc3 operational as raid disk 2
[ 169.420000] raid5: allocated 67488kB for md0
[ 169.420000] 1: w=1 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[ 169.420000] 3: w=2 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[ 169.420000] 2: w=3 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[ 169.420000] raid5: raid level 5 set md0 active with 3 out of 4 devices, algorithm 2
[ 169.420000] RAID5 conf printout:
[ 169.420000] --- rd:4 wd:3
[ 169.420000] disk 1, o:1, dev:sdb3
[ 169.420000] disk 2, o:1, dev:sdc3
[ 169.420000] disk 3, o:1, dev:sdd3
[ 169.420000] md0: detected capacity change from 0 to 5996376883200
[ 169.430000] md4: unknown partition table
[ 170.470000] md0: unknown partition table
[ 171.510000] Adding 530040k swap on /dev/md4. Priority:-1 extents:1 across:530040k
[ 172.550000] raid5: some error occurred in a active device:3 of md0.
[ 172.550000] raid5: Keep the raid device active in degraded mode but set readonly.
[ 174.570000] md: cannot remove active disk sdd3 from md0 ...
[ 177.860000] md: bind<sdc2>
[ 177.870000] RAID1 conf printout:
[ 177.870000] --- wd:1 rd:2
[ 177.870000] disk 0, wo:0, o:1, dev:sdb2
[ 177.870000] disk 1, wo:1, o:1, dev:sdc2
[ 177.880000] md: recovery of RAID array md4
[ 177.880000] md: minimum _guaranteed_ speed: 5000 KB/sec/disk.
[ 177.880000] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
[ 177.880000] md: using 128k window, over a total of 530048 blocks.
[ 184.720000] md: md4: recovery done.
[ 184.760000] RAID1 conf printout:
[ 184.760000] --- wd:2 rd:2
[ 184.760000] disk 0, wo:0, o:1, dev:sdb2
[ 184.760000] disk 1, wo:0, o:1, dev:sdc2
[ 186.870000] EXT4-fs (md0): mounted filesystem with ordered data mode
[ 187.590000] md: md0 switched to read-only mode.
[ 187.770000] EXT4-fs (md0): mounted filesystem with ordered data mode
[ 202.370000] eth0: stopped
[ 202.380000] eth1: stopped
[ 203.820000] eth0: started
[ 206.940000] eth1: link down
[ 206.940000] eth1: started
[ 211.680000] eth1: link up, full duplex, speed 1 Gbps
[ 228.520000] eth0: stopped
[ 228.550000] eth0: started
[ 228.610000] eth1: stopped
[ 228.640000] eth1: link down
[ 228.640000] eth1: started
[ 231.650000] eth1: link up, full duplex, speed 1 Gbps
[ 263.460000] active port 0 :139
[ 263.460000] active port 1 :445
[ 263.460000] active port 2 :20
[ 263.890000] warning: `proftpd' uses 32-bit capabilities (legacy support in use)
[ 275.430000] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e2fsck is recommended
[ 283.530000] warning: process `pic_raw' used the deprecated sysctl system call with 8.1.2.
[ 290.140000] rule type=2, num=0
[ 290.470000] WOL disable
[ 290.540000] eth1: link up, full duplex, speed 1 Gbps
[ 290.540000] WOL disable
[ 294.460000] Loading iSCSI transport class v2.0-871.
[ 294.870000] iscsi: registered transport (tcp)
[~] # #done
[~] #


Copying the data will take a LONG TIME at the current rate. I have most elsewhere but this is my backup drive.

Not sure what to do??

[pwilson]

I have had a similar problem to the one described above. I went away for holidays and came back and one of the drives showed a failure. I did a bad block scan and it showed 185 bad blocks (drive #1). I was not able to get the exact same drive (Samsung HD204UI) SO I got a WD 3Tb RED drive (WD30EFRX-68EUZN0).
I plugged it in and the system started to rebuild the raid. After about 1.5 days, It completed.
Then spontaneously drive #4 showed a red light. I had problems earlier on with the drives not seating properly so I withdrew it and reseated it. It went green for a few moments then red again.
Then the new WD drive also went red. I also unseated it and reseated.
I followed the procedure for unplugging all the drives starting the NAS and replugging the drives 1 at a time.
It first has all drives green then after the boot is finished - #1 & #4 are red.
I can still access the NAS through SSH and I can use Windows to access the shares. I cannot access through the web gui, it gives the login screen then when I login it goes away for a long time (forever?) saying "Loading..."

I don't quite understand why you are asking questions about this one. With both HDD1 and HDD4 showing Red, this shows 2 drives Failed. RAID can only tolerate 1 drive failure, so your RAID array is in Read-Only mode, (which the "df -h" command also identifies). Replace the failed drives, setup your NAS as if it is a new NAS, and restore from Backup to the new array.

When you replaced HDD1 did you "Hot-swap" it, per the instructions in QNAP Tutorial: Hot-swapping the hard drives when the RAID crashes? If you cold-swapped it, (ie turned off the NAS to change drives), then the RAID array would not have attempted to rebuild the RAID array, as it would not have recognized the drive change.

If you drives are all the same age, and 2 of 4 have failed, then I would recommend replacing all 4 drives. HDD1 has already been kicked from the array. And you've already identified that HDD4 is also failed/Red as well.

Please consider updating your Forums Profile to include your TS-419P+ as your "NAS Model", as this will assist us in helping you going forward.

I am now copying the necessary data from the shares onto a drive.

I ran the commands requested:

NAS Model: TS-419P+
Firmware: 4.0.2

Code: Select all

[~] # df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/ram0                32.9M     15.4M     17.6M  47% /
tmpfs                    32.0M    356.0k     31.7M   1% /tmp
/dev/sda4               364.2M    319.6M     44.6M  88% /mnt/ext
/dev/md9                509.5M    139.0M    370.5M  27% /mnt/HDA_ROOT
/dev/md0                  5.4T      2.7T      2.7T  50% /share/MD0_DATA
tmpfs                    32.0M      1.3M     30.7M   4% /.eaccelerator.tmp

Code: Select all

[~] # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md0 : active (read-only) raid5 sdb3[1] sdd3[3] sdc3[2]
      5855836800 blocks level 5, 64k chunk, algorithm 2 [4/3] [_UUU]

md4 : active raid1 sdc2[1] sdb2[0]
      530048 blocks [2/2] [UU]

md13 : active raid1 sdc4[0] sdb4[3] sda4[2] sdd4[1]
      458880 blocks [4/4] [UUUU]
      bitmap: 0/57 pages [0KB], 4KB chunk

md9 : active raid1 sda1[0] sdc1[3] sdb1[2] sdd1[1]
      530048 blocks [4/4] [UUUU]
      bitmap: 0/65 pages [0KB], 4KB chunk

unused devices: <none>

[/quote]

See my comments above.

[pwilson]

This thread is now Locked.

It has simply become too confusing and unmanagable to help people in this thread, as there are too many people here that has attempted to open "Me too" replies, rather than opening their own "NewTopic".

Half of the people in this thread have not provided sufficient information, and it is simply too difficult to try to help so many people at the same time with completely unrelated, (although similar) issues. I am prepared to continue to help everyone individually, but I respectfully request that you each open your own threads, and that you provide all the information requested in article: When you're asking a question, please include the following when you do so.

This thread has simply become so unmanagable, that I am Locking it, so that no further replies can be posted to it. Please understand, I am not denying assistance to anyone, I am merely locking an unmanagable thread. Note: It is no harder to start a NewTopic than to press "Quote", or "Reply". (Your Firmware versions, Disk drives, and Drive failures are all different, so "Me Too" style replies are not appropriate for this type of issue, as this leads to confusing unmanagable threads, which simply generate further "Me Too" replies, with no assistance offered, as the Community helpers start ignoring such threads once they become unmanagable, which ultimately leads to no assistance for anyone).

Please start individual new threads, with complete information provided. (Again, please review article: When you're asking a question, please include the following so that you provide all the informations needed in order to help you.