NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
3 drive failures w/in 10 days of 4.2.22 upgrade? #19570015
Within two days of upgrading my Ultra 6 with 6 2 TB drives in it to 4.2.22, it marked a drive dead. I always keep a spare so I swapped the drive out and completed a cross-ship RMA with Seagate. Before the new drive even arrived, a second drive was marked dead due to the same symptoms (spin-control/command retry latency) and I was away on travel so I remotely disabled the Power Scheduler and powered the NAS down for a couple days.
Last night, I returned home to find the first replacement drive at my door so I powered up the NAS to grab the logs for RMA processing with Seagate and the NAS started re-syncing the drive that it previously marked dead. I let it resync overnight and at this point, the purported dead drive seems to be working fine.
I haven't had a drive failure in a long time but experienced 2 dead drives within one week of the 4.2.22 firmware upgrade. In both cases, the drives passed the daily SMART tests but it failed due to spin/command latencies. Is it possible that the drives are fine but that there is a bug in the 4.2.22 firmware where it improperly detects/diagnoses a dead drive?
Chronology of Events:
9/20 - Upgrade to 4.2.22
9/24 - First Dead Disk. Replace drive, resync. Cross-ship to Seagate
9/26 - Second Dead Disk. Shutdown remotely and disable power scheduler so I could deal with it when the first replacement drive arrived
9/28 - Replacement drive arrived. Powered up NAS, second Dead Disk no longer Dead. Resync completed, array fully operational
9/29 - Post experience to rule-in/out 4.2.22 firmware regression bug before RMA'ing another drive
Here are the relevant log snippets and SMART reports for the two drive failures:
Abridged User Log from 9/22 upgrade -> 9/24 first failure, replace, resync -> 9/26 second failure with just resync on 9/28)
System Log for first drive failure on 9/24
First drive failure SMART log
System Log for second drive failure on 9/26
System log for 9/28 Bootup and resync (i.e. I did not replace the second dead drive) in next post because I exceeded the character limit
NOTE: On 10/1, a third drive failed within 10 days of my upgrading the Ultra6 to 4.2.22 - see recent post below.
Last night, I returned home to find the first replacement drive at my door so I powered up the NAS to grab the logs for RMA processing with Seagate and the NAS started re-syncing the drive that it previously marked dead. I let it resync overnight and at this point, the purported dead drive seems to be working fine.
I haven't had a drive failure in a long time but experienced 2 dead drives within one week of the 4.2.22 firmware upgrade. In both cases, the drives passed the daily SMART tests but it failed due to spin/command latencies. Is it possible that the drives are fine but that there is a bug in the 4.2.22 firmware where it improperly detects/diagnoses a dead drive?
Chronology of Events:
9/20 - Upgrade to 4.2.22
9/24 - First Dead Disk. Replace drive, resync. Cross-ship to Seagate
9/26 - Second Dead Disk. Shutdown remotely and disable power scheduler so I could deal with it when the first replacement drive arrived
9/28 - Replacement drive arrived. Powered up NAS, second Dead Disk no longer Dead. Resync completed, array fully operational
9/29 - Post experience to rule-in/out 4.2.22 firmware regression bug before RMA'ing another drive
Here are the relevant log snippets and SMART reports for the two drive failures:
Abridged User Log from 9/22 upgrade -> 9/24 first failure, replace, resync -> 9/26 second failure with just resync on 9/28)
Sep 21 23:00:12 nas RAIDiator: System power-on scheduled for 09/22/2012 08:00
Sep 22 08:01:13 nas RAIDiator: System is up.
Sep 22 08:06:21 nas RAIDiator: Backup finished. [Job 002]
Sep 22 08:08:11 nas RAIDiator: Backup finished. [Job 003]
Sep 22 08:08:37 nas RAIDiator: Please reboot your ReadyNAS device to continue with the update process.
Sep 22 08:08:46 nas RAIDiator: Backup finished. [Job 004]
Sep 22 08:09:03 nas RAIDiator: Please close this browser session and use RAIDar to reconnect to the device. System rebooting...
Sep 22 08:09:03 nas RAIDiator: Rebooting device...
Sep 22 08:09:08 nas shutdown[4561]: shutting down for system reboot
Sep 22 08:11:56 nas RAIDiator: System Update Status (nas) : Your ReadyNAS device has been updated with a new firmware image. (RAIDiator-x86 4.2.22)
Sep 22 08:12:07 nas RAIDiator: System is up.
Sep 22 08:12:25 nas RAIDiator: Reallocated sector count has increased in the last day.\n\nDisk 0:\n Previous count: 51\n Current count: 93\n\nGrowing SMART errors indicate a disk that may fail soon. If the errors continue to increase, you should be prepared to replace the disk.
Sep 22 08:12:25 nas RAIDiator: New SMART disk errors detected! (nas) : Reallocated sector count has increased in the last day.\n\nDisk 0:\n Previous count: 51\n Current count: 93\n\nGrowing SMART errors indicate a disk that may fail soon. If the errors continue to increase, you should be prepared to replace the disk.
Sep 22 09:05:58 nas RAIDiator: Backup finished. [Job 002]
Sep 22 10:05:10 nas RAIDiator: Backup finished. [Job 003]
Sep 22 12:05:08 nas RAIDiator: Backup finished. [Job 005]
Sep 22 12:05:13 nas RAIDiator: Backup finished. [Job 001]
Sep 22 23:01:08 nas RAIDiator: System power-on scheduled for 09/23/2012 08:00
Sep 23 08:01:07 nas RAIDiator: nic.agent: "nice -n 5 /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf" failed to start.
Sep 23 08:01:17 nas RAIDiator: System is up.
Sep 23 08:05:47 nas RAIDiator: Backup finished. [Job 003]
Sep 23 21:05:42 nas RAIDiator: Backup finished. [Job 002]
Sep 23 22:00:13 nas RAIDiator: System power-on scheduled for 09/24/2012 07:00
Sep 24 07:01:14 nas RAIDiator: System is up.
Sep 24 07:05:40 nas RAIDiator: Backup finished. [Job 002]
Sep 24 07:18:28 nas RAIDiator: Detected increasing reallocated sector count on disk 2 [-1, 0]
Sep 24 07:18:28 nas RAIDiator: Reallocation event count: [-1, 0]
Sep 24 07:18:28 nas RAIDiator: Detected increasing spin retry count on disk 2 [168626698, 0]
Sep 24 07:18:28 nas RAIDiator: Detected increasing spin retry count[168626698] on disk 2 [ST32000542AS, 6XW1KLP1]. This often indicates an impending failure. Please be prepared to replace this disk to maintain data redundancy.
Sep 24 07:18:49 nas RAIDiator: Detected increasing end-to-end errors on disk 2 [-1, 0]
Sep 24 07:18:49 nas RAIDiator: Detected increasing command timeouts on disk 2 [-1, 0]
Sep 24 07:18:49 nas RAIDiator: Detected increasing pending sector count on disk 2 [-1, 0]
Sep 24 07:18:49 nas RAIDiator: Detected increasing uncorrectable errors on disk 2 [-1, 0]
Sep 24 07:18:49 nas RAIDiator: Current (temp, start_stop_cnt, power_on_hrs, power_cycle_cnt, load_cycle_cnt) = (-1, -1, -1, -1, -1)
Sep 24 08:01:33 nas RAIDiator: Disk failure detected.
Sep 24 08:01:33 nas RAIDiator: If the failed disk is used in a RAID level 1, 5, or X-RAID volume, please note that volume is now unprotected, and an additional disk failure may render that volume dead. If this disk is a part of a RAID 6 volume, your volume is still protected if this is your first failure. A 2nd disk failure will make your volume unprotected. If this disk is a part of a RAID 10 volume,your volume is still protected if more than half of the disks alive. But another failure of disks been marked may render that volume dead. It is recommended that you replace the failed disk as soon as possible to maintain optimal protection of your volume.
Sep 24 08:01:33 nas RAIDiator: Disk failure detected. (nas) : Disk failure detected.\n\nIf the failed disk is used in a RAID level 1, 5, or X-RAID volume, please note that volume is now unprotected, and an additional disk failure may render that volume dead. If this disk is a part of a RAID 6 volume, your volume is still protected if this is your first failure. A 2nd disk failure will make your volume unprotected. If this disk is a part of a RAID 10 volume,your volume is still protected if more than half of the disks alive. But another failure of disks been marked may render that volume dead. It is recommended that you replace the failed disk as soon as possible to maintain optimal protection of your volume.\n\n[Mon Sep 24 08:01:33 PDT 2012]
Sep 24 08:06:27 nas RAIDiator: Backup finished. [Job 002]
Sep 24 08:06:27 nas RAIDiator: Backup finished. [Job 003]
Sep 24 08:06:54 nas RAIDiator: Backup finished. [Job 004]
Sep 24 12:05:08 nas RAIDiator: Backup finished. [Job 005]
Sep 24 20:32:52 nas shutdown[28336]: shutting down for system halt
Sep 24 20:33:03 nas RAIDiator: System power-on scheduled for 09/25/2012 07:00
Sep 24 20:34:31 nas RAIDiator: nic.agent: "nice -n 5 /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf" failed to start.
Sep 24 20:34:41 nas RAIDiator: System is up.
Sep 24 20:35:02 nas RAIDiator: Reallocated sector count has increased in the last day.\n\nDisk 1:\n Previous count: 10\n Current count: 13\n\nGrowing SMART errors indicate a disk that may fail soon. If the errors continue to increase, you should be prepared to replace the disk.
Sep 24 20:35:03 nas RAIDiator: New SMART disk errors detected! (nas) : Reallocated sector count has increased in the last day.\n\nDisk 1:\n Previous count: 10\n Current count: 13\n\nGrowing SMART errors indicate a disk that may fail soon. If the errors continue to increase, you should be prepared to replace the disk.
Sep 24 20:35:50 nas RAIDiator: RAID sync started on volume C.
Sep 24 20:35:50 nas RAIDiator: RAID event detected. (nas) : RAID sync started on volume C.\n\n[Mon Sep 24 20:35:50 PDT 2012]
Sep 24 20:35:54 nas RAIDiator: Detected increasing reallocated sector count on disk 1 [13, 10]
Sep 24 20:35:54 nas RAIDiator: Reallocation event count: [13, 10]
Sep 24 20:35:54 nas RAIDiator: Current (temp, start_stop_cnt, power_on_hrs, power_cycle_cnt, load_cycle_cnt) = (34, 14809, 10758, 629, -1)
Sep 24 21:05:43 nas RAIDiator: Backup finished. [Job 002]
Sep 24 22:05:10 nas RAIDiator: Backup finished. [Job 003]
Sep 25 00:05:08 nas RAIDiator: Backup finished. [Job 005]
Sep 25 00:06:46 nas RAIDiator: Backup finished. [Job 004]
Sep 25 06:05:45 nas RAIDiator: Backup finished. [Job 002]
Sep 25 06:07:46 nas RAIDiator: RAID sync finished on volume C.
Sep 25 06:07:47 nas RAIDiator: RAID event detected. (nas) : RAID sync finished on volume C.\n\n[Tue Sep 25 06:07:42 PDT 2012]
Sep 25 07:06:09 nas RAIDiator: Backup finished. [Job 002]
Sep 25 08:05:37 nas RAIDiator: Backup finished. [Job 003]
Sep 25 21:05:46 nas RAIDiator: Backup finished. [Job 002]
Sep 25 22:00:57 nas RAIDiator: System power-on scheduled for 09/26/2012 07:00
Sep 25 22:08:31 nas RAIDiator: System is up.
Sep 25 23:05:58 nas RAIDiator: Backup finished. [Job 002]
Sep 26 06:05:16 nas RAIDiator: Backup finished. [Job 001]
Sep 26 06:25:02 nas RAIDiator: Volume C is approaching capacity:\n99% used\n121G available
Sep 26 07:06:15 nas RAIDiator: Backup finished. [Job 002]
Sep 26 08:05:49 nas RAIDiator: Backup finished. [Job 003]
Sep 26 08:07:12 nas RAIDiator: Backup finished. [Job 004]
Sep 26 12:05:40 nas RAIDiator: Backup finished. [Job 005]
Sep 26 20:07:14 nas RAIDiator: Backup finished. [Job 004]
Sep 26 21:06:22 nas RAIDiator: Detected increasing reallocated sector count on disk 1 [-1, 13]
Sep 26 21:06:22 nas RAIDiator: Reallocation event count: [-1, 13]
Sep 26 21:06:22 nas RAIDiator: Detected increasing spin retry count on disk 1 [1701265709, 0]
Sep 26 21:06:22 nas RAIDiator: Detected increasing spin retry count[1701265709] on disk 1 [ST32000542AS, 5XW1BJZ6]. This often indicates an impending failure. Please be prepared to replace this disk to maintain data redundancy.
Sep 26 21:06:43 nas RAIDiator: Detected increasing end-to-end errors on disk 1 [-1, 0]
Sep 26 21:06:43 nas RAIDiator: Detected increasing command timeouts on disk 1 [-1, 65537]
Sep 26 21:06:43 nas RAIDiator: Detected increasing pending sector count on disk 1 [-1, 0]
Sep 26 21:06:43 nas RAIDiator: Detected increasing uncorrectable errors on disk 1 [-1, 0]
Sep 26 21:06:43 nas RAIDiator: Current (temp, start_stop_cnt, power_on_hrs, power_cycle_cnt, load_cycle_cnt) = (-1, -1, -1, -1, -1)
Sep 26 21:07:04 nas RAIDiator: Backup finished. [Job 002]
Sep 26 21:07:10 nas RAIDiator: Disk failure detected.
Sep 26 21:07:10 nas RAIDiator: If the failed disk is used in a RAID level 1, 5, or X-RAID volume, please note that volume is now unprotected, and an additional disk failure may render that volume dead. If this disk is a part of a RAID 6 volume, your volume is still protected if this is your first failure. A 2nd disk failure will make your volume unprotected. If this disk is a part of a RAID 10 volume,your volume is still protected if more than half of the disks alive. But another failure of disks been marked may render that volume dead. It is recommended that you replace the failed disk as soon as possible to maintain optimal protection of your volume.
Sep 26 21:07:11 nas RAIDiator: Disk failure detected. (nas) : Disk failure detected.\n\nIf the failed disk is used in a RAID level 1, 5, or X-RAID volume, please note that volume is now unprotected, and an additional disk failure may render that volume dead. If this disk is a part of a RAID 6 volume, your volume is still protected if this is your first failure. A 2nd disk failure will make your volume unprotected. If this disk is a part of a RAID 10 volume,your volume is still protected if more than half of the disks alive. But another failure of disks been marked may render that volume dead. It is recommended that you replace the failed disk as soon as possible to maintain optimal protection of your volume.\n\n[Wed Sep 26 21:07:10 PDT 2012]
Sep 26 22:00:12 nas RAIDiator: System power-on scheduled for 09/27/2012 07:00
Sep 26 22:13:34 nas RAIDiator: Detected increasing reallocated sector count on disk 1 [13, -1]
Sep 26 22:13:34 nas RAIDiator: Reallocation event count: [13, -1]
Sep 26 22:13:34 nas RAIDiator: Detected increasing spin retry count on disk 1 [0, 1701265709]
Sep 26 22:13:34 nas RAIDiator: Detected increasing end-to-end errors on disk 1 [0, -1]
Sep 26 22:13:34 nas RAIDiator: Detected increasing command timeouts on disk 1 [131074, -1]
Sep 26 22:13:34 nas RAIDiator: Detected increasing command timeouts[131074] on disk 1 [ST32000542AS, 5XW1BJZ6]. This often indicates an impending failure. Please be prepared to replace this disk to maintain data redundancy.
Sep 26 22:13:35 nas RAIDiator: Detected increasing pending sector count on disk 1 [0, -1]
Sep 26 22:13:35 nas RAIDiator: Detected increasing uncorrectable errors on disk 1 [0, -1]
Sep 26 22:13:35 nas RAIDiator: Current (temp, start_stop_cnt, power_on_hrs, power_cycle_cnt, load_cycle_cnt) = (32, 14863, 10805, 631, -1)
Sep 26 22:19:12 nas RAIDiator: Please close this browser session and use RAIDar to reconnect to the device after it is powered back on. System powering off...
Sep 26 22:19:12 nas RAIDiator: Powering off device
Sep 26 22:19:22 nas shutdown[4917]: shutting down for system halt
Sep 28 19:06:03 nas RAIDiator: Backup finished. [Job 002]
Sep 28 20:05:15 nas RAIDiator: Backup finished. [Job 003]
Sep 28 20:07:31 nas RAIDiator: Backup finished. [Job 004]
Sep 29 00:05:07 nas RAIDiator: Backup finished. [Job 005]
Sep 29 02:25:37 nas RAIDiator: RAID sync finished on volume C.
Sep 29 02:25:37 nas RAIDiator: RAID event detected. (nas) : RAID sync finished on volume C.\n\n[Sat Sep 29 02:25:33 PDT 2012]
Sep 29 03:06:02 nas RAIDiator: Backup finished. [Job 002]
Sep 29 04:05:41 nas RAIDiator: Backup finished. [Job 003]
Sep 29 04:06:44 nas RAIDiator: Backup finished. [Job 004]
Sep 29 09:06:28 nas RAIDiator: Backup finished. [Job 002]
System Log for first drive failure on 9/24
Sep 24 07:16:45 nas noflushd[2186]: Spinning down disks.
Sep 24 07:17:11 nas noflushd[2186]: Disks spinning up after 0 minutes.
Sep 24 07:17:28 nas kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 24 07:18:28 nas kernel: ata2.00: failed command: SMART
Sep 24 07:18:28 nas kernel: ata2.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/40 tag 0 pio 512 in
Sep 24 07:18:28 nas kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Sep 24 07:18:28 nas kernel: ata2.00: status: { DRDY }
Sep 24 07:18:28 nas kernel: ata2: hard resetting link
Sep 24 07:18:28 nas kernel: ata2: link is slow to respond, please be patient (ready=0)
Sep 24 07:18:28 nas kernel: ata2: COMRESET failed (errno=-16)
Sep 24 07:18:28 nas kernel: ata2: hard resetting link
Sep 24 07:18:28 nas kernel: ata2: link is slow to respond, please be patient (ready=0)
Sep 24 07:18:28 nas kernel: ata2: COMRESET failed (errno=-16)
Sep 24 07:18:28 nas kernel: ata2: hard resetting link
Sep 24 07:18:28 nas kernel: ata2: link is slow to respond, please be patient (ready=0)
Sep 24 07:18:28 nas kernel: ata2: COMRESET failed (errno=-16)
Sep 24 07:18:28 nas kernel: ata2: limiting SATA link speed to 1.5 Gbps
Sep 24 07:18:28 nas kernel: ata2: hard resetting link
Sep 24 07:18:28 nas kernel: ata2: COMRESET failed (errno=-16)
Sep 24 07:18:28 nas kernel: ata2: reset failed, giving up
Sep 24 07:18:28 nas kernel: ata2.00: disabled
Sep 24 07:18:28 nas kernel: ata2: EH complete
Sep 24 07:18:28 nas kernel: sd 1:0:0:0: [sdb] Unhandled error code
Sep 24 07:18:28 nas kernel: sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Sep 24 07:18:28 nas kernel: sd 1:0:0:0: [sdb] CDB: Write(10): 2a 00 00 00 00 48 00 00 02 00
Sep 24 07:18:28 nas kernel: end_request: I/O error, dev sdb, sector 72
Sep 24 07:18:28 nas kernel: end_request: I/O error, dev sdb, sector 72
Sep 24 07:18:28 nas kernel: md: super_written gets error=-5, uptodate=0
Sep 24 07:18:28 nas kernel: md/raid1:md0: Disk failure on sdb1, disabling device.
Sep 24 07:18:28 nas kernel: <1>md/raid1:md0: Operation continuing on 5 devices.
Sep 24 07:18:28 nas kernel: RAID1 conf printout:
Sep 24 07:18:28 nas kernel: --- wd:5 rd:6
Sep 24 07:18:28 nas kernel: disk 0, wo:0, o:1, dev:sda1
Sep 24 07:18:28 nas kernel: disk 1, wo:1, o:0, dev:sdb1
Sep 24 07:18:28 nas kernel: disk 2, wo:0, o:1, dev:sdc1
Sep 24 07:18:28 nas kernel: disk 3, wo:0, o:1, dev:sdd1
Sep 24 07:18:28 nas kernel: disk 4, wo:0, o:1, dev:sde1
Sep 24 07:18:28 nas kernel: disk 5, wo:0, o:1, dev:sdf1
Sep 24 07:18:28 nas kernel: RAID1 conf printout:
Sep 24 07:18:28 nas kernel: --- wd:5 rd:6
Sep 24 07:18:28 nas kernel: disk 0, wo:0, o:1, dev:sda1
Sep 24 07:18:28 nas kernel: disk 2, wo:0, o:1, dev:sdc1
Sep 24 07:18:28 nas kernel: disk 3, wo:0, o:1, dev:sdd1
Sep 24 07:18:28 nas kernel: disk 4, wo:0, o:1, dev:sde1
Sep 24 07:18:28 nas kernel: disk 5, wo:0, o:1, dev:sdf1
Sep 24 07:18:28 nas RAIDiator: Detected increasing reallocated sector count on disk 2 [-1, 0]
Sep 24 07:18:28 nas RAIDiator: Reallocation event count: [-1, 0]
Sep 24 07:18:28 nas RAIDiator: Detected increasing spin retry count on disk 2 [168626698, 0]
Sep 24 07:18:28 nas RAIDiator: Detected increasing spin retry count[168626698] on disk 2 [ST32000542AS, 6XW1KLP1]. This often indicates an impending failure. Please be prepared to replace this disk to maintain data redundancy.
Sep 24 07:18:49 nas RAIDiator: Detected increasing end-to-end errors on disk 2 [-1, 0]
Sep 24 07:18:49 nas RAIDiator: Detected increasing command timeouts on disk 2 [-1, 0]
Sep 24 07:18:49 nas RAIDiator: Detected increasing pending sector count on disk 2 [-1, 0]
Sep 24 07:18:49 nas RAIDiator: Detected increasing uncorrectable errors on disk 2 [-1, 0]
Sep 24 07:18:49 nas RAIDiator: Current (temp, start_stop_cnt, power_on_hrs, power_cycle_cnt, load_cycle_cnt) = (-1, -1, -1, -1, -1)
Sep 24 07:27:11 nas noflushd[2186]: Spinning down disks.
Sep 24 07:27:12 nas noflushd[2186]: Spindown for /dev/sdb failed: Input/output error
Sep 24 07:27:30 nas noflushd[2186]: Disks spinning up after 0 minutes.
Sep 24 07:32:33 nas noflushd[2186]: Spinning down disks.
Sep 24 07:32:34 nas noflushd[2186]: Spindown for /dev/sdb failed: Input/output error
Sep 24 07:32:51 nas noflushd[2186]: Disks spinning up after 0 minutes.
Sep 24 07:37:54 nas noflushd[2186]: Spinning down disks.
Sep 24 07:37:55 nas noflushd[2186]: Spindown for /dev/sdb failed: Input/output error
Sep 24 07:38:13 nas noflushd[2186]: Disks spinning up after 0 minutes.
Sep 24 07:43:16 nas noflushd[2186]: Spinning down disks.
Sep 24 07:43:17 nas noflushd[2186]: Spindown for /dev/sdb failed: Input/output error
Sep 24 07:43:34 nas noflushd[2186]: Disks spinning up after 0 minutes.
Sep 24 07:45:00 nas rsyncd[4686]: connect from miniduo1.home (192.168.0.103)
Sep 24 07:45:00 nas rsyncd[4686]: unknown module 'backup' tried from miniduo1.home (192.168.0.103)
Sep 24 07:48:37 nas noflushd[2186]: Spinning down disks.
Sep 24 07:48:38 nas noflushd[2186]: Spindown for /dev/sdb failed: Input/output error
Sep 24 07:48:55 nas noflushd[2186]: Disks spinning up after 0 minutes.
Sep 24 07:53:58 nas noflushd[2186]: Spinning down disks.
Sep 24 07:53:59 nas noflushd[2186]: Spindown for /dev/sdb failed: Input/output error
Sep 24 07:54:17 nas noflushd[2186]: Disks spinning up after 0 minutes.
Sep 24 07:59:20 nas noflushd[2186]: Spinning down disks.
Sep 24 07:59:21 nas noflushd[2186]: Spindown for /dev/sdb failed: Input/output error
Sep 24 07:59:38 nas noflushd[2186]: Disks spinning up after 0 minutes.
Sep 24 08:01:01 nas udhcpc[2728]: Sending renew...
Sep 24 08:01:01 nas udhcpc[2728]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 24 08:01:29 nas kernel: sd 1:0:0:0: [sdb] Unhandled error code
Sep 24 08:01:29 nas kernel: sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Sep 24 08:01:29 nas kernel: sd 1:0:0:0: [sdb] CDB: Write(10): 2a 00 00 90 00 50 00 00 02 00
Sep 24 08:01:29 nas kernel: end_request: I/O error, dev sdb, sector 9437264
Sep 24 08:01:29 nas kernel: end_request: I/O error, dev sdb, sector 9437264
Sep 24 08:01:29 nas kernel: md: super_written gets error=-5, uptodate=0
Sep 24 08:01:29 nas kernel: md/raid:md2: Disk failure on sdb5, disabling device.
Sep 24 08:01:29 nas kernel: <1>md/raid:md2: Operation continuing on 5 devices.
Sep 24 08:01:29 nas kernel: RAID conf printout:
Sep 24 08:01:29 nas kernel: --- level:5 rd:6 wd:5
Sep 24 08:01:29 nas kernel: disk 0, o:1, dev:sda5
Sep 24 08:01:29 nas kernel: disk 1, o:0, dev:sdb5
Sep 24 08:01:29 nas kernel: disk 2, o:1, dev:sdc5
Sep 24 08:01:29 nas kernel: disk 3, o:1, dev:sdd5
Sep 24 08:01:29 nas kernel: disk 4, o:1, dev:sde5
Sep 24 08:01:29 nas kernel: disk 5, o:1, dev:sdf5
Sep 24 08:01:29 nas kernel: RAID conf printout:
Sep 24 08:01:29 nas kernel: --- level:5 rd:6 wd:5
Sep 24 08:01:29 nas kernel: disk 0, o:1, dev:sda5
Sep 24 08:01:29 nas kernel: disk 2, o:1, dev:sdc5
Sep 24 08:01:29 nas kernel: disk 3, o:1, dev:sdd5
Sep 24 08:01:29 nas kernel: disk 4, o:1, dev:sde5
Sep 24 08:01:29 nas kernel: disk 5, o:1, dev:sdf5
Sep 24 08:01:33 nas RAIDiator: Disk failure detected.
Sep 24 08:01:33 nas RAIDiator: If the failed disk is used in a RAID level 1, 5, or X-RAID volume, please note that volume is now unprotected, and an additional disk failure may render that volume dead. If this disk is a part of a RAID 6 volume, your volume is still protected if this is your first failure. A 2nd disk failure will make your volume unprotected. If this disk is a part of a RAID 10 volume,your volume is still protected if more than half of the disks alive. But another failure of disks been marked may render that volume dead. It is recommended that you replace the failed disk as soon as possible to maintain optimal protection of your volume.
Sep 24 08:01:33 nas RAIDiator: Disk failure detected. (nas) : Disk failure detected.\n\nIf the failed disk is used in a RAID level 1, 5, or X-RAID volume, please note that volume is now unprotected, and an additional disk failure may render that volume dead. If this disk is a part of a RAID 6 volume, your volume is still protected if this is your first failure. A 2nd disk failure will make your volume unprotected. If this disk is a part of a RAID 10 volume,your volume is still protected if more than half of the disks alive. But another failure of disks been marked may render that volume dead. It is recommended that you replace the failed disk as soon as possible to maintain optimal protection of your volume.\n\n[Mon Sep 24 08:01:33 PDT 2012]
Sep 24 08:06:02 nas kernel: sd 1:0:0:0: [sdb] Unhandled error code
Sep 24 08:06:02 nas kernel: sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Sep 24 08:06:02 nas kernel: sd 1:0:0:0: [sdb] CDB: Write(10): 2a 00 00 80 00 48 00 00 02 00
Sep 24 08:06:02 nas kernel: end_request: I/O error, dev sdb, sector 8388680
Sep 24 08:06:02 nas kernel: end_request: I/O error, dev sdb, sector 8388680
Sep 24 08:06:02 nas kernel: md: super_written gets error=-5, uptodate=0
Sep 24 08:06:02 nas kernel: md/raid:md1: Disk failure on sdb2, disabling device.
Sep 24 08:06:02 nas kernel: <1>md/raid:md1: Operation continuing on 5 devices.
Sep 24 08:06:02 nas kernel: RAID conf printout:
Sep 24 08:06:02 nas kernel: --- level:6 rd:6 wd:5
Sep 24 08:06:02 nas kernel: disk 0, o:1, dev:sda2
Sep 24 08:06:02 nas kernel: disk 1, o:0, dev:sdb2
Sep 24 08:06:02 nas kernel: disk 2, o:1, dev:sdc2
Sep 24 08:06:02 nas kernel: disk 3, o:1, dev:sdd2
Sep 24 08:06:02 nas kernel: disk 4, o:1, dev:sde2
Sep 24 08:06:02 nas kernel: disk 5, o:1, dev:sdf2
Sep 24 08:06:02 nas kernel: RAID conf printout:
Sep 24 08:06:02 nas kernel: --- level:6 rd:6 wd:5
Sep 24 08:06:02 nas kernel: disk 0, o:1, dev:sda2
Sep 24 08:06:02 nas kernel: disk 2, o:1, dev:sdc2
Sep 24 08:06:02 nas kernel: disk 3, o:1, dev:sdd2
Sep 24 08:06:02 nas kernel: disk 4, o:1, dev:sde2
Sep 24 08:06:02 nas kernel: disk 5, o:1, dev:sdf2
Sep 24 08:06:27 nas RAIDiator: Backup finished. [Job 002]
Sep 24 08:06:27 nas RAIDiator: Backup finished. [Job 003]
Sep 24 08:06:54 nas RAIDiator: Backup finished. [Job 004]
Sep 24 08:28:04 nas noflushd[2186]: Spinning down disks.
Sep 24 08:28:05 nas noflushd[2186]: Spindown for /dev/sdb failed: Input/output error
Sep 24 08:28:23 nas noflushd[2186]: Disks spinning up after 0 minutes.
Sep 24 08:33:25 nas noflushd[2186]: Spinning down disks.
Sep 24 08:33:26 nas noflushd[2186]: Spindown for /dev/sdb failed: Input/output error
Sep 24 08:33:43 nas noflushd[2186]: Disks spinning up after 0 minutes.
Sep 24 08:38:46 nas noflushd[2186]: Spinning down disks.
Sep 24 08:38:47 nas noflushd[2186]: Spindown for /dev/sdb failed: Input/output error
Sep 24 08:39:04 nas noflushd[2186]: Disks spinning up after 0 minutes.
Sep 24 08:44:17 nas noflushd[2186]: Spinning down disks.
Sep 24 08:44:18 nas noflushd[2186]: Spindown for /dev/sdb failed: Input/output error
Sep 24 08:44:35 nas noflushd[2186]: Disks spinning up after 0 minutes.
Sep 24 08:49:48 nas noflushd[2186]: Spinning down disks.
Sep 24 08:49:49 nas noflushd[2186]: Spindown for /dev/sdb failed: Input/output error
Sep 24 08:50:07 nas noflushd[2186]: Disks spinning up after 0 minutes.
Sep 24 08:55:09 nas noflushd[2186]: Spinning down disks.
Sep 24 08:55:10 nas noflushd[2186]: Spindown for /dev/sdb failed: Input/output error
Sep 24 08:55:28 nas noflushd[2186]: Disks spinning up after 0 minutes.
Sep 24 09:00:30 nas noflushd[2186]: Spinning down disks.
Sep 24 09:00:32 nas noflushd[2186]: Spindown for /dev/sdb failed: Input/output error
Sep 24 09:00:49 nas noflushd[2186]: Disks spinning up after 0 minutes.
First drive failure SMART log
***** Disk SMART log for channel 2 [sdb] *****
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.37.6.RNx86_64.2.4] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda LP
Device Model: ST32000542AS
Serial Number: 6XW1KLP1
LU WWN Device Id: 5 000c50 0228e9b48
Firmware Version: CC34
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Thu Sep 20 07:01:46 2012 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 643) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 228790855
3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 091 091 020 Old_age Always - 9786
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 044 044 030 Pre-fail Always - 15212863609781
9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 6658
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 357
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 077 055 045 Old_age Always - 23 (Min/Max 22/23)
194 Temperature_Celsius 0x0022 023 045 000 Old_age Always - 23 (0 20 0 0 0)
195 Hardware_ECC_Recovered 0x001a 046 034 000 Old_age Always - 228790855
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 51973399256608
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2100760496
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2052664029
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 0 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
System Log for second drive failure on 9/26
Sep 26 20:35:26 nas noflushd[2202]: Spinning down disks.
Sep 26 21:05:13 nas noflushd[2202]: Disks spinning up after 29 minutes.
Sep 26 21:06:22 nas kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 26 21:06:22 nas kernel: ata1.00: failed command: SMART
Sep 26 21:06:22 nas kernel: ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/40 tag 0 pio 512 in
Sep 26 21:06:22 nas kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Sep 26 21:06:22 nas kernel: ata1.00: status: { DRDY }
Sep 26 21:06:22 nas kernel: ata1: hard resetting link
Sep 26 21:06:22 nas kernel: ata1: link is slow to respond, please be patient (ready=0)
Sep 26 21:06:22 nas kernel: ata1: COMRESET failed (errno=-16)
Sep 26 21:06:22 nas kernel: ata1: hard resetting link
Sep 26 21:06:22 nas kernel: ata1: link is slow to respond, please be patient (ready=0)
Sep 26 21:06:22 nas kernel: ata1: COMRESET failed (errno=-16)
Sep 26 21:06:22 nas kernel: ata1: hard resetting link
Sep 26 21:06:22 nas kernel: ata1: link is slow to respond, please be patient (ready=0)
Sep 26 21:06:22 nas kernel: ata1: COMRESET failed (errno=-16)
Sep 26 21:06:22 nas kernel: ata1: limiting SATA link speed to 1.5 Gbps
Sep 26 21:06:22 nas kernel: ata1: hard resetting link
Sep 26 21:06:22 nas kernel: ata1: COMRESET failed (errno=-16)
Sep 26 21:06:22 nas kernel: ata1: reset failed, giving up
Sep 26 21:06:22 nas kernel: ata1.00: disabled
Sep 26 21:06:22 nas kernel: ata1: EH complete
Sep 26 21:06:22 nas kernel: sd 0:0:0:0: [sda] Unhandled error code
Sep 26 21:06:22 nas kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Sep 26 21:06:22 nas kernel: sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 20 08 70 00 00 08 00
Sep 26 21:06:22 nas kernel: end_request: I/O error, dev sda, sector 2099312
Sep 26 21:06:22 nas kernel: md/raid1:md0: sda1: rescheduling sector 2097200
Sep 26 21:06:22 nas kernel: sd 0:0:0:0: [sda] Unhandled error code
Sep 26 21:06:22 nas kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Sep 26 21:06:22 nas kernel: sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 00 00 00 48 00 00 02 00
Sep 26 21:06:22 nas kernel: end_request: I/O error, dev sda, sector 72
Sep 26 21:06:22 nas kernel: end_request: I/O error, dev sda, sector 72
Sep 26 21:06:22 nas kernel: md: super_written gets error=-5, uptodate=0
Sep 26 21:06:22 nas kernel: md/raid1:md0: Disk failure on sda1, disabling device.
Sep 26 21:06:22 nas kernel: <1>md/raid1:md0: Operation continuing on 5 devices.
Sep 26 21:06:22 nas kernel: RAID1 conf printout:
Sep 26 21:06:22 nas kernel: --- wd:5 rd:6
Sep 26 21:06:22 nas kernel: disk 0, wo:1, o:0, dev:sda1
Sep 26 21:06:22 nas kernel: disk 1, wo:0, o:1, dev:sdb1
Sep 26 21:06:22 nas kernel: disk 2, wo:0, o:1, dev:sdc1
Sep 26 21:06:22 nas kernel: disk 3, wo:0, o:1, dev:sdd1
Sep 26 21:06:22 nas kernel: disk 4, wo:0, o:1, dev:sde1
Sep 26 21:06:22 nas kernel: disk 5, wo:0, o:1, dev:sdf1
Sep 26 21:06:22 nas kernel: RAID1 conf printout:
Sep 26 21:06:22 nas kernel: --- wd:5 rd:6
Sep 26 21:06:22 nas kernel: disk 1, wo:0, o:1, dev:sdb1
Sep 26 21:06:22 nas kernel: disk 2, wo:0, o:1, dev:sdc1
Sep 26 21:06:22 nas kernel: disk 3, wo:0, o:1, dev:sdd1
Sep 26 21:06:22 nas kernel: disk 4, wo:0, o:1, dev:sde1
Sep 26 21:06:22 nas kernel: disk 5, wo:0, o:1, dev:sdf1
Sep 26 21:06:22 nas kernel: md/raid1:md0: redirecting sector 2097200 to other mirror: sdf1
Sep 26 21:06:22 nas RAIDiator: Detected increasing reallocated sector count on disk 1 [-1, 13]
Sep 26 21:06:22 nas RAIDiator: Reallocation event count: [-1, 13]
Sep 26 21:06:22 nas RAIDiator: Detected increasing spin retry count on disk 1 [1701265709, 0]
Sep 26 21:06:22 nas RAIDiator: Detected increasing spin retry count[1701265709] on disk 1 [ST32000542AS, 5XW1BJZ6]. This often indicates an impending failure. Please be prepared to replace this disk to maintain data redundancy.
Sep 26 21:06:43 nas RAIDiator: Detected increasing end-to-end errors on disk 1 [-1, 0]
Sep 26 21:06:43 nas RAIDiator: Detected increasing command timeouts on disk 1 [-1, 65537]
Sep 26 21:06:43 nas RAIDiator: Detected increasing pending sector count on disk 1 [-1, 0]
Sep 26 21:06:43 nas RAIDiator: Detected increasing uncorrectable errors on disk 1 [-1, 0]
Sep 26 21:06:43 nas RAIDiator: Current (temp, start_stop_cnt, power_on_hrs, power_cycle_cnt, load_cycle_cnt) = (-1, -1, -1, -1, -1)
Sep 26 21:06:54 nas kernel: sd 0:0:0:0: [sda] Unhandled error code
Sep 26 21:06:54 nas kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Sep 26 21:06:54 nas kernel: sd 0:0:0:0: [sda] CDB: Read(10): 28 00 28 50 09 38 00 00 10 00
Sep 26 21:06:54 nas kernel: end_request: I/O error, dev sda, sector 676333880
Sep 26 21:06:54 nas kernel: sd 0:0:0:0: [sda] Unhandled error code
Sep 26 21:06:54 nas kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Sep 26 21:06:54 nas kernel: sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 28 50 09 40 00 00 08 00
Sep 26 21:06:54 nas kernel: end_request: I/O error, dev sda, sector 676333888
Sep 26 21:06:54 nas kernel: md/raid:md2: Disk failure on sda5, disabling device.
Sep 26 21:06:54 nas kernel: <1>md/raid:md2: Operation continuing on 5 devices.
Sep 26 21:06:54 nas kernel: md: recovery of RAID array md2
Sep 26 21:06:54 nas kernel: md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
Sep 26 21:06:54 nas kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
Sep 26 21:06:54 nas kernel: md: using 128k window, over a total of 1948792192 blocks.
Sep 26 21:06:54 nas kernel: md: resuming recovery of md2 from checkpoint.
Sep 26 21:06:54 nas kernel: md: md2: recovery done.
Sep 26 21:06:54 nas kernel: RAID conf printout:
Sep 26 21:06:54 nas kernel: --- level:5 rd:6 wd:5
Sep 26 21:06:54 nas kernel: disk 0, o:0, dev:sda5
Sep 26 21:06:54 nas kernel: disk 1, o:1, dev:sdb5
Sep 26 21:06:54 nas kernel: disk 2, o:1, dev:sdc5
Sep 26 21:06:54 nas kernel: disk 3, o:1, dev:sdd5
Sep 26 21:06:54 nas kernel: disk 4, o:1, dev:sde5
Sep 26 21:06:54 nas kernel: disk 5, o:1, dev:sdf5
Sep 26 21:06:54 nas kernel: RAID conf printout:
Sep 26 21:06:54 nas kernel: --- level:5 rd:6 wd:5
Sep 26 21:06:54 nas kernel: disk 0, o:0, dev:sda5
Sep 26 21:06:54 nas kernel: disk 1, o:1, dev:sdb5
Sep 26 21:06:54 nas kernel: disk 2, o:1, dev:sdc5
Sep 26 21:06:54 nas kernel: disk 3, o:1, dev:sdd5
Sep 26 21:06:54 nas kernel: disk 4, o:1, dev:sde5
Sep 26 21:06:54 nas kernel: disk 5, o:1, dev:sdf5
Sep 26 21:06:54 nas kernel: RAID conf printout:
Sep 26 21:06:54 nas kernel: --- level:5 rd:6 wd:5
Sep 26 21:06:54 nas kernel: disk 1, o:1, dev:sdb5
Sep 26 21:06:54 nas kernel: disk 2, o:1, dev:sdc5
Sep 26 21:06:54 nas kernel: disk 3, o:1, dev:sdd5
Sep 26 21:06:54 nas kernel: disk 4, o:1, dev:sde5
Sep 26 21:06:54 nas kernel: disk 5, o:1, dev:sdf5
Sep 26 21:07:04 nas RAIDiator: Backup finished. [Job 002]
Sep 26 21:07:10 nas RAIDiator: Disk failure detected.
Sep 26 21:07:10 nas RAIDiator: If the failed disk is used in a RAID level 1, 5, or X-RAID volume, please note that volume is now unprotected, and an additional disk failure may render that volume dead. If this disk is a part of a RAID 6 volume, your volume is still protected if this is your first failure. A 2nd disk failure will make your volume unprotected. If this disk is a part of a RAID 10 volume,your volume is still protected if more than half of the disks alive. But another failure of disks been marked may render that volume dead. It is recommended that you replace the failed disk as soon as possible to maintain optimal protection of your volume.
Sep 26 21:07:11 nas RAIDiator: Disk failure detected. (nas) : Disk failure detected.\n\nIf the failed disk is used in a RAID level 1, 5, or X-RAID volume, please note that volume is now unprotected, and an additional disk failure may render that volume dead. If this disk is a part of a RAID 6 volume, your volume is still protected if this is your first failure. A 2nd disk failure will make your volume unprotected. If this disk is a part of a RAID 10 volume,your volume is still protected if more than half of the disks alive. But another failure of disks been marked may render that volume dead. It is recommended that you replace the failed disk as soon as possible to maintain optimal protection of your volume.\n\n[Wed Sep 26 21:07:10 PDT 2012]
Sep 26 21:08:28 nas udhcpc[2807]: Sending renew...
Sep 26 21:08:28 nas udhcpc[2807]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 26 21:35:16 nas noflushd[2202]: Spinning down disks.
Sep 26 21:35:16 nas noflushd[2202]: Spindown for /dev/sda failed: Input/output error
Sep 26 21:35:21 nas noflushd[2202]: Disks spinning up after 0 minutes.
Sep 26 21:42:47 nas noflushd[2202]: Spinning down disks.
Sep 26 21:42:47 nas noflushd[2202]: Spindown for /dev/sda failed: Input/output error
Sep 26 21:43:05 nas noflushd[2202]: Disks spinning up after 0 minutes.
Sep 26 21:48:08 nas noflushd[2202]: Spinning down disks.
Sep 26 21:48:08 nas noflushd[2202]: Spindown for /dev/sda failed: Input/output error
Sep 26 21:48:25 nas noflushd[2202]: Disks spinning up after 0 minutes.
Sep 26 21:53:28 nas noflushd[2202]: Spinning down disks.
Sep 26 21:53:28 nas noflushd[2202]: Spindown for /dev/sda failed: Input/output error
Sep 26 21:53:46 nas noflushd[2202]: Disks spinning up after 0 minutes.
Sep 26 22:00:01 nas init: Switching to runlevel: 0
Sep 26 22:00:03 nas kernel: ata2.00: configured for UDMA/133
Sep 26 22:00:03 nas kernel: ata2: EH complete
Sep 26 22:00:03 nas kernel: sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Sep 26 22:00:03 nas kernel: ata3.00: configured for UDMA/133
Sep 26 22:00:03 nas kernel: ata3: EH complete
Sep 26 22:00:03 nas kernel: sd 2:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Sep 26 22:00:04 nas kernel: ata4.00: configured for UDMA/133
Sep 26 22:00:04 nas kernel: ata4: EH complete
Sep 26 22:00:04 nas kernel: sd 3:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Sep 26 22:00:04 nas kernel: ata5.00: configured for UDMA/133
Sep 26 22:00:04 nas kernel: ata5: EH complete
Sep 26 22:00:04 nas kernel: sd 4:0:0:0: [sde] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Sep 26 22:00:04 nas kernel: ata6.00: configured for UDMA/133
Sep 26 22:00:04 nas kernel: ata6: EH complete
Sep 26 22:00:04 nas kernel: sd 5:0:0:0: [sdf] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Sep 26 22:00:06 nas kernel: sd 0:0:0:0: [sda] Unhandled error code
Sep 26 22:00:06 nas kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Sep 26 22:00:06 nas kernel: sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 80 07 c0 00 00 10 00
Sep 26 22:00:06 nas kernel: end_request: I/O error, dev sda, sector 8390592
Sep 26 22:00:06 nas kernel: sd 0:0:0:0: [sda] Unhandled error code
Sep 26 22:00:06 nas kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Sep 26 22:00:06 nas kernel: sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 00 80 07 c0 00 00 08 00
Sep 26 22:00:06 nas kernel: end_request: I/O error, dev sda, sector 8390592
Sep 26 22:00:06 nas kernel: md/raid:md1: Disk failure on sda2, disabling device.
Sep 26 22:00:06 nas kernel: <1>md/raid:md1: Operation continuing on 5 devices.
Sep 26 22:00:06 nas kernel: RAID conf printout:
Sep 26 22:00:06 nas kernel: --- level:6 rd:6 wd:5
Sep 26 22:00:06 nas kernel: disk 0, o:0, dev:sda2
Sep 26 22:00:06 nas kernel: disk 1, o:1, dev:sdb2
Sep 26 22:00:06 nas kernel: disk 2, o:1, dev:sdc2
Sep 26 22:00:06 nas kernel: disk 3, o:1, dev:sdd2
Sep 26 22:00:06 nas kernel: disk 4, o:1, dev:sde2
Sep 26 22:00:06 nas kernel: disk 5, o:1, dev:sdf2
Sep 26 22:00:06 nas kernel: RAID conf printout:
Sep 26 22:00:06 nas kernel: --- level:6 rd:6 wd:5
Sep 26 22:00:06 nas kernel: disk 1, o:1, dev:sdb2
Sep 26 22:00:06 nas kernel: disk 2, o:1, dev:sdc2
Sep 26 22:00:06 nas kernel: disk 3, o:1, dev:sdd2
Sep 26 22:00:06 nas kernel: disk 4, o:1, dev:sde2
Sep 26 22:00:06 nas kernel: disk 5, o:1, dev:sdf2
System log for 9/28 Bootup and resync (i.e. I did not replace the second dead drive) in next post because I exceeded the character limit
NOTE: On 10/1, a third drive failed within 10 days of my upgrading the Ultra6 to 4.2.22 - see recent post below.
44 Replies
Replies have been turned off for this discussion
- System log for 9/28 Bootup and resync (i.e. I did not replace the second dead drive)
Sep 28 18:50:58 nas syslogd 1.4.1#18: restart.
Sep 28 18:50:58 nas kernel: klogd 1.4.1#18, log source = /proc/kmsg started.
Sep 28 18:50:58 nas kernel: Initializing cgroup subsys cpu
Sep 28 18:50:58 nas kernel: Linux version 2.6.37.6.RNx86_64.2.4 (jmaggard@calzone) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Thu Jul 26 05:00:36 PDT 2012
Sep 28 18:50:58 nas kernel: Command line: initrd=initrd.gz reason=normal BOOT_IMAGE=kernel
Sep 28 18:50:58 nas kernel: BIOS-provided physical RAM map:
Sep 28 18:50:58 nas kernel: BIOS-e820: 0000000000000000 - 000000000009c800 (usable)
Sep 28 18:50:58 nas kernel: BIOS-e820: 000000000009c800 - 00000000000a0000 (reserved)
Sep 28 18:50:58 nas kernel: BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
Sep 28 18:50:58 nas kernel: BIOS-e820: 0000000000100000 - 000000003f690000 (usable)
Sep 28 18:50:58 nas kernel: BIOS-e820: 000000003f690000 - 000000003f69e000 (ACPI data)
Sep 28 18:50:58 nas kernel: BIOS-e820: 000000003f69e000 - 000000003f6e0000 (ACPI NVS)
Sep 28 18:50:58 nas kernel: BIOS-e820: 000000003f6e0000 - 0000000040000000 (reserved)
Sep 28 18:50:58 nas kernel: BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
Sep 28 18:50:58 nas kernel: BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
Sep 28 18:50:58 nas kernel: NX (Execute Disable) protection: active
Sep 28 18:50:58 nas kernel: DMI present.
Sep 28 18:50:58 nas kernel: DMI: / , BIOS 080016 06/10/2010
Sep 28 18:50:58 nas kernel: e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
Sep 28 18:50:58 nas kernel: e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
Sep 28 18:50:58 nas kernel: last_pfn = 0x3f690 max_arch_pfn = 0x400000000
Sep 28 18:50:58 nas kernel: initial memory mapped : 0 - 20000000
Sep 28 18:50:58 nas kernel: init_memory_mapping: 0000000000000000-000000003f690000
Sep 28 18:50:58 nas kernel: 0000000000 - 003f600000 page 2M
Sep 28 18:50:58 nas kernel: 003f600000 - 003f690000 page 4k
Sep 28 18:50:58 nas kernel: kernel direct mapping tables up to 3f690000 @ 1fffd000-20000000
Sep 28 18:50:58 nas kernel: RAMDISK: 3f50c000 - 3f690000
Sep 28 18:50:58 nas kernel: ACPI: RSDP 00000000000f9bb0 00014 (v00 ACPIAM)
Sep 28 18:50:58 nas kernel: ACPI: RSDT 000000003f690000 0003C (v01 061010 RSDT1112 20100610 MSFT 00000097)
Sep 28 18:50:58 nas kernel: ACPI: FACP 000000003f690200 00084 (v01 061010 FACP1112 20100610 MSFT 00000097)
Sep 28 18:50:58 nas kernel: ACPI: DSDT 000000003f690440 05B7D (v01 1AEOS 1AEOS005 00000005 INTL 20051117)
Sep 28 18:50:58 nas kernel: ACPI: FACS 000000003f69e000 00040
Sep 28 18:50:58 nas kernel: ACPI: APIC 000000003f690390 0006C (v01 061010 APIC1112 20100610 MSFT 00000097)
Sep 28 18:50:58 nas kernel: ACPI: MCFG 000000003f690400 0003C (v01 061010 OEMMCFG 20100610 MSFT 00000097)
Sep 28 18:50:58 nas kernel: ACPI: OEMB 000000003f69e040 00072 (v01 061010 OEMB1112 20100610 MSFT 00000097)
Sep 28 18:50:58 nas kernel: ACPI: HPET 000000003f69a440 00038 (v01 061010 OEMHPET 20100610 MSFT 00000097)
Sep 28 18:50:58 nas kernel: ACPI: GSCI 000000003f69e0c0 02024 (v01 061010 GMCHSCI 20100610 MSFT 00000097)
Sep 28 18:50:58 nas kernel: ACPI: Local APIC address 0xfee00000
Sep 28 18:50:58 nas kernel: [ffffea0000000000-ffffea0000dfffff] PMD -> [ffff88003dc00000-ffff88003e9fffff] on node 0
Sep 28 18:50:58 nas kernel: Zone PFN ranges:
Sep 28 18:50:58 nas kernel: DMA 0x00000010 -> 0x00001000
Sep 28 18:50:58 nas kernel: DMA32 0x00001000 -> 0x00100000
Sep 28 18:50:58 nas kernel: Normal empty
Sep 28 18:50:58 nas kernel: Movable zone start PFN for each node
Sep 28 18:50:58 nas kernel: early_node_map[2] active PFN ranges
Sep 28 18:50:58 nas kernel: 0: 0x00000010 -> 0x0000009c
Sep 28 18:50:58 nas kernel: 0: 0x00000100 -> 0x0003f690
Sep 28 18:50:58 nas kernel: On node 0 totalpages: 259612
Sep 28 18:50:58 nas kernel: DMA zone: 56 pages used for memmap
Sep 28 18:50:58 nas kernel: DMA zone: 2 pages reserved
Sep 28 18:50:58 nas kernel: DMA zone: 3922 pages, LIFO batch:0
Sep 28 18:50:58 nas kernel: DMA32 zone: 3495 pages used for memmap
Sep 28 18:50:58 nas kernel: DMA32 zone: 252137 pages, LIFO batch:31
Sep 28 18:50:58 nas kernel: ACPI: PM-Timer IO Port: 0x808
Sep 28 18:50:58 nas kernel: ACPI: Local APIC address 0xfee00000
Sep 28 18:50:58 nas kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Sep 28 18:50:58 nas kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 28 18:50:58 nas kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
Sep 28 18:50:58 nas kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
Sep 28 18:50:58 nas kernel: ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
Sep 28 18:50:58 nas kernel: IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
Sep 28 18:50:58 nas kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 28 18:50:58 nas kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 28 18:50:58 nas kernel: ACPI: IRQ0 used by override.
Sep 28 18:50:58 nas kernel: ACPI: IRQ2 used by override.
Sep 28 18:50:58 nas kernel: ACPI: IRQ9 used by override.
Sep 28 18:50:58 nas kernel: Using ACPI (MADT) for SMP configuration information
Sep 28 18:50:58 nas kernel: ACPI: HPET id: 0xffffffff base: 0xfed00000
Sep 28 18:50:58 nas kernel: SMP: Allowing 4 CPUs, 0 hotplug CPUs
Sep 28 18:50:58 nas kernel: nr_irqs_gsi: 40
Sep 28 18:50:58 nas kernel: Allocating PCI resources starting at 40000000 (gap: 40000000:bee00000)
Sep 28 18:50:58 nas kernel: setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_node_ids:1
Sep 28 18:50:58 nas kernel: PERCPU: Embedded 26 pages/cpu @ffff88003f200000 s73856 r8192 d24448 u524288
Sep 28 18:50:58 nas kernel: pcpu-alloc: s73856 r8192 d24448 u524288 alloc=1*2097152
Sep 28 18:50:58 nas kernel: pcpu-alloc: [0] 0 1 2 3
Sep 28 18:50:58 nas kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 256059
Sep 28 18:50:58 nas kernel: Kernel command line: console=ttyS0 hpet=disable initrd=initrd.gz reason=normal BOOT_IMAGE=kernel
Sep 28 18:50:58 nas kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 28 18:50:58 nas kernel: Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Sep 28 18:50:58 nas kernel: Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 28 18:50:58 nas kernel: Memory: 1010840k/1038912k available (5851k kernel code, 464k absent, 27608k reserved, 2835k data, 400k init)
Sep 28 18:50:58 nas kernel: SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Sep 28 18:50:58 nas kernel: Hierarchical RCU implementation.
Sep 28 18:50:58 nas kernel: ^IRCU-based detection of stalled CPUs is disabled.
Sep 28 18:50:58 nas kernel: NR_IRQS:512
Sep 28 18:50:58 nas kernel: Console: colour VGA+ 80x25
Sep 28 18:50:58 nas kernel: console [ttyS0] enabled
Sep 28 18:50:58 nas kernel: Fast TSC calibration failed
Sep 28 18:50:58 nas kernel: TSC: PIT calibration matches PMTIMER. 1 loops
Sep 28 18:50:58 nas kernel: Detected 1662.465 MHz processor.
Sep 28 18:50:58 nas kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 3324.93 BogoMIPS (lpj=1662465)
Sep 28 18:50:58 nas kernel: pid_max: default: 32768 minimum: 301
Sep 28 18:50:58 nas kernel: Mount-cache hash table entries: 256
Sep 28 18:50:58 nas kernel: Initializing cgroup subsys blkio
Sep 28 18:50:58 nas kernel: CPU: Physical Processor ID: 0
Sep 28 18:50:58 nas kernel: CPU: Processor Core ID: 0
Sep 28 18:50:58 nas kernel: mce: CPU supports 5 MCE banks
Sep 28 18:50:58 nas kernel: CPU0: Thermal monitoring enabled (TM1)
Sep 28 18:50:58 nas kernel: using mwait in idle threads.
Sep 28 18:50:58 nas kernel: Performance Events: PEBS fmt0+, Atom events, Intel PMU driver.
Sep 28 18:50:58 nas kernel: ... version: 3
Sep 28 18:50:58 nas kernel: ... bit width: 40
Sep 28 18:50:58 nas kernel: ... generic registers: 2
Sep 28 18:50:58 nas kernel: ... value mask: 000000ffffffffff
Sep 28 18:50:58 nas kernel: ... max period: 000000007fffffff
Sep 28 18:50:58 nas kernel: ... fixed-purpose events: 3
Sep 28 18:50:58 nas kernel: ... event mask: 0000000700000003
Sep 28 18:50:58 nas kernel: ACPI: Core revision 20101013
Sep 28 18:50:58 nas kernel: Setting APIC routing to flat
Sep 28 18:50:58 nas kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 28 18:50:58 nas kernel: CPU0: Intel(R) Atom(TM) CPU D510 @ 1.66GHz stepping 0a
Sep 28 18:50:58 nas kernel: Booting Node 0, Processors #1 #2 #3 Ok.
Sep 28 18:50:58 nas kernel: Brought up 4 CPUs
Sep 28 18:50:58 nas kernel: Total of 4 processors activated (13298.50 BogoMIPS).
Sep 28 18:50:58 nas kernel: xor: automatically using best checksumming function: generic_sse
Sep 28 18:50:58 nas kernel: generic_sse: 5056.000 MB/sec
Sep 28 18:50:58 nas kernel: xor: using function: generic_sse (5056.000 MB/sec)
Sep 28 18:50:58 nas kernel: NET: Registered protocol family 16
Sep 28 18:50:58 nas kernel: ACPI: bus type pci registered
Sep 28 18:50:58 nas kernel: dca service started, version 1.12.1
Sep 28 18:50:58 nas kernel: PCI: Using configuration type 1 for base access
Sep 28 18:50:58 nas kernel: bio: create slab <bio-0> at 0
Sep 28 18:50:58 nas kernel: raid6: int64x1 371 MB/s
Sep 28 18:50:58 nas kernel: raid6: int64x2 574 MB/s
Sep 28 18:50:58 nas kernel: raid6: int64x4 574 MB/s
Sep 28 18:50:58 nas kernel: raid6: int64x8 687 MB/s
Sep 28 18:50:58 nas kernel: raid6: sse2x1 621 MB/s
Sep 28 18:50:58 nas kernel: raid6: sse2x2 1136 MB/s
Sep 28 18:50:58 nas kernel: raid6: sse2x4 2003 MB/s
Sep 28 18:50:58 nas kernel: raid6: using algorithm sse2x4 (2003 MB/s)
Sep 28 18:50:58 nas kernel: ACPI: EC: Look up EC in DSDT
Sep 28 18:50:58 nas kernel: ACPI: Executed 1 blocks of module-level executable AML code
Sep 28 18:50:58 nas kernel: ACPI: Interpreter enabled
Sep 28 18:50:58 nas kernel: ACPI: (supports S0 S5)
Sep 28 18:50:58 nas kernel: ACPI: Using IOAPIC for interrupt routing
Sep 28 18:50:58 nas kernel: ACPI Exception: AE_NOT_FOUND, Evaluating _PRW (20101013/scan-723)
Sep 28 18:50:58 nas kernel: ACPI: No dock devices found.
Sep 28 18:50:58 nas kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 28 18:50:58 nas kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
Sep 28 18:50:58 nas kernel: pci_root PNP0A08:00: host bridge window [io 0x0000-0x0cf7]
Sep 28 18:50:58 nas kernel: pci_root PNP0A08:00: host bridge window [io 0x0d00-0xffff]
Sep 28 18:50:58 nas kernel: pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff]
Sep 28 18:50:58 nas kernel: pci_root PNP0A08:00: host bridge window [mem 0x000d0000-0x000dffff]
Sep 28 18:50:58 nas kernel: pci_root PNP0A08:00: host bridge window [mem 0x3f700000-0xdfffffff]
Sep 28 18:50:58 nas kernel: pci_root PNP0A08:00: host bridge window [mem 0xf0000000-0xfed8ffff]
Sep 28 18:50:58 nas kernel: pci 0000:00:00.0: [8086:a000] type 0 class 0x000600
Sep 28 18:50:58 nas kernel: pci 0000:00:02.0: [8086:a001] type 0 class 0x000300
Sep 28 18:50:58 nas kernel: pci 0000:00:02.0: reg 10: [mem 0xfe880000-0xfe8fffff]
Sep 28 18:50:58 nas kernel: pci 0000:00:02.0: reg 14: [io 0xcc00-0xcc07]
Sep 28 18:50:58 nas kernel: pci 0000:00:02.0: reg 18: [mem 0xd0000000-0xdfffffff pref]
Sep 28 18:50:58 nas kernel: pci 0000:00:02.0: reg 1c: [mem 0xfe900000-0xfe9fffff]
Sep 28 18:50:58 nas kernel: pci 0000:00:02.1: [8086:a002] type 0 class 0x000380
Sep 28 18:50:58 nas kernel: pci 0000:00:02.1: reg 10: [mem 0xfe780000-0xfe7fffff]
Sep 28 18:50:58 nas kernel: pci 0000:00:1a.0: [8086:2937] type 0 class 0x000c03
Sep 28 18:50:58 nas kernel: pci 0000:00:1a.0: reg 20: [io 0xc880-0xc89f]
Sep 28 18:50:58 nas kernel: pci 0000:00:1a.1: [8086:2938] type 0 class 0x000c03
Sep 28 18:50:58 nas kernel: pci 0000:00:1a.1: reg 20: [io 0xc800-0xc81f]
Sep 28 18:50:58 nas kernel: pci 0000:00:1a.2: [8086:2939] type 0 class 0x000c03
Sep 28 18:50:58 nas kernel: pci 0000:00:1a.2: reg 20: [io 0xc480-0xc49f]
Sep 28 18:50:58 nas kernel: pci 0000:00:1a.7: [8086:293c] type 0 class 0x000c03
Sep 28 18:50:58 nas kernel: pci 0000:00:1a.7: reg 10: [mem 0xfe87bc00-0xfe87bfff]
Sep 28 18:50:58 nas kernel: pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
Sep 28 18:50:58 nas kernel: pci 0000:00:1a.7: PME# disabled
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.0: [8086:2940] type 1 class 0x000604
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.0: PME# disabled
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.1: [8086:2942] type 1 class 0x000604
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.1: PME# disabled
Sep 28 18:50:58 nas kernel: pci 0000:00:1d.0: [8086:2934] type 0 class 0x000c03
Sep 28 18:50:58 nas kernel: pci 0000:00:1d.0: reg 20: [io 0xc400-0xc41f]
Sep 28 18:50:58 nas kernel: pci 0000:00:1d.1: [8086:2935] type 0 class 0x000c03
Sep 28 18:50:58 nas kernel: pci 0000:00:1d.1: reg 20: [io 0xc080-0xc09f]
Sep 28 18:50:58 nas kernel: pci 0000:00:1d.2: [8086:2936] type 0 class 0x000c03
Sep 28 18:50:58 nas kernel: pci 0000:00:1d.2: reg 20: [io 0xc000-0xc01f]
Sep 28 18:50:58 nas kernel: pci 0000:00:1d.7: [8086:293a] type 0 class 0x000c03
Sep 28 18:50:58 nas kernel: pci 0000:00:1d.7: reg 10: [mem 0xfe87b800-0xfe87bbff]
Sep 28 18:50:58 nas kernel: pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
Sep 28 18:50:58 nas kernel: pci 0000:00:1d.7: PME# disabled
Sep 28 18:50:58 nas kernel: pci 0000:00:1e.0: [8086:244e] type 1 class 0x000604
Sep 28 18:50:58 nas kernel: pci 0000:00:1f.0: [8086:2916] type 0 class 0x000601
Sep 28 18:50:58 nas kernel: pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0a00 (mask 00ff)
Sep 28 18:50:58 nas kernel: pci 0000:00:1f.2: [8086:2922] type 0 class 0x000106
Sep 28 18:50:58 nas kernel: pci 0000:00:1f.2: reg 10: [io 0xb400-0xb407]
Sep 28 18:50:58 nas kernel: pci 0000:00:1f.2: reg 14: [io 0xbc00-0xbc03]
Sep 28 18:50:58 nas kernel: pci 0000:00:1f.2: reg 18: [io 0xb880-0xb887]
Sep 28 18:50:58 nas kernel: pci 0000:00:1f.2: reg 1c: [io 0xb800-0xb803]
Sep 28 18:50:58 nas kernel: pci 0000:00:1f.2: reg 20: [io 0xb480-0xb49f]
Sep 28 18:50:58 nas kernel: pci 0000:00:1f.2: reg 24: [mem 0xfe87b000-0xfe87b7ff]
Sep 28 18:50:58 nas kernel: pci 0000:00:1f.2: PME# supported from D3hot
Sep 28 18:50:58 nas kernel: pci 0000:00:1f.2: PME# disabled
Sep 28 18:50:58 nas kernel: pci 0000:00:1f.3: [8086:2930] type 0 class 0x000c05
Sep 28 18:50:58 nas kernel: pci 0000:00:1f.3: reg 10: [mem 0xfe87ac00-0xfe87acff 64bit]
Sep 28 18:50:58 nas kernel: pci 0000:00:1f.3: reg 20: [io 0x0400-0x041f]
Sep 28 18:50:58 nas kernel: pci 0000:01:00.0: [11ab:4380] type 0 class 0x000200
Sep 28 18:50:58 nas kernel: pci 0000:01:00.0: reg 10: [mem 0xfeadc000-0xfeadffff 64bit]
Sep 28 18:50:58 nas kernel: pci 0000:01:00.0: reg 18: [io 0xd800-0xd8ff]
Sep 28 18:50:58 nas kernel: pci 0000:01:00.0: reg 30: [mem 0xfeae0000-0xfeafffff pref]
Sep 28 18:50:58 nas kernel: pci 0000:01:00.0: supports D1 D2
Sep 28 18:50:58 nas kernel: pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Sep 28 18:50:58 nas kernel: pci 0000:01:00.0: PME# disabled
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.0: PCI bridge to [bus 01-01]
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.0: bridge window [io 0xd000-0xdfff]
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.0: bridge window [mem 0xfea00000-0xfeafffff]
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
Sep 28 18:50:58 nas kernel: pci 0000:02:00.0: [11ab:4380] type 0 class 0x000200
Sep 28 18:50:58 nas kernel: pci 0000:02:00.0: reg 10: [mem 0xfebdc000-0xfebdffff 64bit]
Sep 28 18:50:58 nas kernel: pci 0000:02:00.0: reg 18: [io 0xe800-0xe8ff]
Sep 28 18:50:58 nas kernel: pci 0000:02:00.0: reg 30: [mem 0xfebe0000-0xfebfffff pref]
Sep 28 18:50:58 nas kernel: pci 0000:02:00.0: supports D1 D2
Sep 28 18:50:58 nas kernel: pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Sep 28 18:50:58 nas kernel: pci 0000:02:00.0: PME# disabled
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.1: PCI bridge to [bus 02-02]
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.1: bridge window [io 0xe000-0xefff]
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.1: bridge window [mem 0xfeb00000-0xfebfffff]
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.1: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
Sep 28 18:50:58 nas kernel: pci 0000:00:1e.0: PCI bridge to [bus 03-03] (subtractive decode)
Sep 28 18:50:58 nas kernel: pci 0000:00:1e.0: bridge window [io 0xf000-0x0000] (disabled)
Sep 28 18:50:58 nas kernel: pci 0000:00:1e.0: bridge window [mem 0xfff00000-0x000fffff] (disabled)
Sep 28 18:50:58 nas kernel: pci 0000:00:1e.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
Sep 28 18:50:58 nas kernel: pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
Sep 28 18:50:58 nas kernel: pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
Sep 28 18:50:58 nas kernel: pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
Sep 28 18:50:58 nas kernel: pci 0000:00:1e.0: bridge window [mem 0x000d0000-0x000dffff] (subtractive decode)
Sep 28 18:50:58 nas kernel: pci 0000:00:1e.0: bridge window [mem 0x3f700000-0xdfffffff] (subtractive decode)
Sep 28 18:50:58 nas kernel: pci 0000:00:1e.0: bridge window [mem 0xf0000000-0xfed8ffff] (subtractive decode)
Sep 28 18:50:58 nas kernel: pci_bus 0000:00: on NUMA node 0
Sep 28 18:50:58 nas kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Sep 28 18:50:58 nas kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
Sep 28 18:50:58 nas kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT]
Sep 28 18:50:58 nas kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT]
Sep 28 18:50:58 nas kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 *10 11 12 14 15)
Sep 28 18:50:58 nas kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs *5)
Sep 28 18:50:58 nas kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 10 11 12 *14 15)
Sep 28 18:50:58 nas kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 11 12 14 *15)
Sep 28 18:50:58 nas kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12 14 15) *0, disabled.
Sep 28 18:50:58 nas kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 7 10 *11 12 14 15)
Sep 28 18:50:58 nas kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 6 7 10 11 12 14 15) *0, disabled.
Sep 28 18:50:58 nas kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 6 *7 10 11 12 14 15)
Sep 28 18:50:58 nas kernel: SCSI subsystem initialized
Sep 28 18:50:58 nas kernel: libata version 3.00 loaded.
Sep 28 18:50:58 nas kernel: usbcore: registered new interface driver usbfs
Sep 28 18:50:58 nas kernel: usbcore: registered new interface driver hub
Sep 28 18:50:58 nas kernel: usbcore: registered new device driver usb
Sep 28 18:50:58 nas kernel: PCI: Using ACPI for IRQ routing
Sep 28 18:50:58 nas kernel: PCI: pci_cache_line_size set to 64 bytes
Sep 28 18:50:58 nas kernel: Expanded resource reserved due to conflict with PCI Bus 0000:00
Sep 28 18:50:58 nas kernel: reserve RAM buffer: 000000000009c800 - 000000000009ffff
Sep 28 18:50:58 nas kernel: reserve RAM buffer: 000000003f690000 - 000000003fffffff
Sep 28 18:50:58 nas kernel: Switching to clocksource tsc
Sep 28 18:50:58 nas kernel: pnp: PnP ACPI init
Sep 28 18:50:58 nas kernel: ACPI: bus type pnp registered
Sep 28 18:50:58 nas kernel: pnp 00:00: [bus 00-ff]
Sep 28 18:50:58 nas kernel: pnp 00:00: [io 0x0cf8-0x0cff]
Sep 28 18:50:58 nas kernel: pnp 00:00: [io 0x0000-0x0cf7 window]
Sep 28 18:50:58 nas kernel: pnp 00:00: [io 0x0d00-0xffff window]
Sep 28 18:50:58 nas kernel: pnp 00:00: [mem 0x000a0000-0x000bffff window]
Sep 28 18:50:58 nas kernel: pnp 00:00: [mem 0x000d0000-0x000dffff window]
Sep 28 18:50:58 nas kernel: pnp 00:00: [mem 0x3f700000-0xdfffffff window]
Sep 28 18:50:58 nas kernel: pnp 00:00: [mem 0xf0000000-0xfed8ffff window]
Sep 28 18:50:58 nas kernel: pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active)
Sep 28 18:50:58 nas kernel: pnp 00:01: [mem 0xfed14000-0xfed19fff]
Sep 28 18:50:58 nas kernel: pnp 00:01: [mem 0xfed90000-0xfed93fff]
Sep 28 18:50:58 nas kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0c01 (active)
Sep 28 18:50:58 nas kernel: pnp 00:02: [dma 4]
Sep 28 18:50:58 nas kernel: pnp 00:02: [io 0x0000-0x000f]
Sep 28 18:50:58 nas kernel: pnp 00:02: [io 0x0081-0x0083]
Sep 28 18:50:58 nas kernel: pnp 00:02: [io 0x0087]
Sep 28 18:50:58 nas kernel: pnp 00:02: [io 0x0089-0x008b]
Sep 28 18:50:58 nas kernel: pnp 00:02: [io 0x008f]
Sep 28 18:50:58 nas kernel: pnp 00:02: [io 0x00c0-0x00df]
Sep 28 18:50:58 nas kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 28 18:50:58 nas kernel: pnp 00:03: [io 0x0070-0x0071]
Sep 28 18:50:58 nas kernel: pnp 00:03: [irq 8]
Sep 28 18:50:58 nas kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 28 18:50:58 nas kernel: pnp 00:04: [io 0x0061]
Sep 28 18:50:58 nas kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 28 18:50:58 nas kernel: pnp 00:05: [io 0x00f0-0x00ff]
Sep 28 18:50:58 nas kernel: pnp 00:05: [irq 13]
Sep 28 18:50:58 nas kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 28 18:50:58 nas kernel: pnp 00:06: [io 0x03f8-0x03ff]
Sep 28 18:50:58 nas kernel: pnp 00:06: [irq 4]
Sep 28 18:50:58 nas kernel: pnp 00:06: [dma 0 disabled]
Sep 28 18:50:58 nas kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 28 18:50:58 nas kernel: pnp 00:07: [io 0x02f8-0x02ff]
Sep 28 18:50:58 nas kernel: pnp 00:07: [irq 3]
Sep 28 18:50:58 nas kernel: pnp 00:07: [dma 0 disabled]
Sep 28 18:50:58 nas kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 28 18:50:58 nas kernel: pnp 00:08: [io 0x0000-0xffffffffffffffff disabled]
Sep 28 18:50:58 nas kernel: pnp 00:08: [io 0x0a00-0x0a0f]
Sep 28 18:50:58 nas kernel: pnp 00:08: [io 0x0a10-0x0a1f]
Sep 28 18:50:58 nas kernel: pnp 00:08: [io 0x0a20-0x0a2f]
Sep 28 18:50:58 nas kernel: pnp 00:08: [io 0x0a30-0x0a3f]
Sep 28 18:50:58 nas kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 28 18:50:58 nas kernel: pnp 00:09: [io 0x0010-0x001f]
Sep 28 18:50:58 nas kernel: pnp 00:09: [io 0x0022-0x003f]
Sep 28 18:50:58 nas kernel: pnp 00:09: [io 0x0044-0x005f]
Sep 28 18:50:58 nas kernel: pnp 00:09: [io 0x0062-0x0063]
Sep 28 18:50:58 nas kernel: pnp 00:09: [io 0x0065-0x006f]
Sep 28 18:50:58 nas kernel: pnp 00:09: [io 0x0072-0x007f]
Sep 28 18:50:58 nas kernel: pnp 00:09: [io 0x0080]
Sep 28 18:50:58 nas kernel: pnp 00:09: [io 0x0084-0x0086]
Sep 28 18:50:58 nas kernel: pnp 00:09: [io 0x0088]
Sep 28 18:50:58 nas kernel: pnp 00:09: [io 0x008c-0x008e]
Sep 28 18:50:58 nas kernel: pnp 00:09: [io 0x0090-0x009f]
Sep 28 18:50:58 nas kernel: pnp 00:09: [io 0x00a2-0x00bf]
Sep 28 18:50:58 nas kernel: pnp 00:09: [io 0x00e0-0x00ef]
Sep 28 18:50:58 nas kernel: pnp 00:09: [io 0x04d0-0x04d1]
Sep 28 18:50:58 nas kernel: pnp 00:09: [io 0x0800-0x087f]
Sep 28 18:50:58 nas kernel: pnp 00:09: [io 0x0000-0xffffffffffffffff disabled]
Sep 28 18:50:58 nas kernel: pnp 00:09: [io 0x0480-0x04ff]
Sep 28 18:50:58 nas kernel: pnp 00:09: [mem 0xfed1c000-0xfed1ffff]
Sep 28 18:50:58 nas kernel: pnp 00:09: [mem 0xfed20000-0xfed3ffff]
Sep 28 18:50:58 nas kernel: pnp 00:09: [mem 0xfed40000-0xfed8ffff]
Sep 28 18:50:58 nas kernel: pnp 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 28 18:50:58 nas kernel: pnp 00:0a: [mem 0xfed00000-0xfed003ff]
Sep 28 18:50:58 nas kernel: pnp 00:0a: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 28 18:50:58 nas kernel: pnp 00:0b: [mem 0xffb00000-0xffbfffff]
Sep 28 18:50:58 nas kernel: pnp 00:0b: [mem 0xfff00000-0xffffffff]
Sep 28 18:50:58 nas kernel: pnp 00:0b: Plug and Play ACPI device, IDs INT0800 (active)
Sep 28 18:50:58 nas kernel: pnp 00:0c: [mem 0xffc00000-0xffefffff]
Sep 28 18:50:58 nas kernel: pnp 00:0c: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 28 18:50:58 nas kernel: pnp 00:0d: [io 0x0060]
Sep 28 18:50:58 nas kernel: pnp 00:0d: [io 0x0064]
Sep 28 18:50:58 nas kernel: pnp 00:0d: [mem 0xfec00000-0xfec00fff]
Sep 28 18:50:58 nas kernel: pnp 00:0d: [mem 0xfee00000-0xfee00fff]
Sep 28 18:50:58 nas kernel: pnp 00:0d: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 28 18:50:58 nas kernel: pnp 00:0e: [mem 0xe0000000-0xefffffff]
Sep 28 18:50:58 nas kernel: pnp 00:0e: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 28 18:50:58 nas kernel: pnp 00:0f: [mem 0x00000000-0x0009ffff]
Sep 28 18:50:58 nas kernel: pnp 00:0f: [mem 0x000c0000-0x000cffff]
Sep 28 18:50:58 nas kernel: pnp 00:0f: [mem 0x000e0000-0x000fffff]
Sep 28 18:50:58 nas kernel: pnp 00:0f: [mem 0x00100000-0x3f6fffff]
Sep 28 18:50:58 nas kernel: pnp 00:0f: [mem 0xfed90000-0xffffffff]
Sep 28 18:50:58 nas kernel: pnp 00:0f: Plug and Play ACPI device, IDs PNP0c01 (active)
Sep 28 18:50:58 nas kernel: pnp: PnP ACPI: found 16 devices
Sep 28 18:50:58 nas kernel: ACPI: ACPI bus type pnp unregistered
Sep 28 18:50:58 nas kernel: system 00:01: [mem 0xfed14000-0xfed19fff] has been reserved
Sep 28 18:50:58 nas kernel: system 00:01: [mem 0xfed90000-0xfed93fff] has been reserved
Sep 28 18:50:58 nas kernel: system 00:08: [io 0x0a00-0x0a0f] has been reserved
Sep 28 18:50:58 nas kernel: system 00:08: [io 0x0a10-0x0a1f] has been reserved
Sep 28 18:50:58 nas kernel: system 00:08: [io 0x0a20-0x0a2f] has been reserved
Sep 28 18:50:58 nas kernel: system 00:08: [io 0x0a30-0x0a3f] has been reserved
Sep 28 18:50:58 nas kernel: system 00:09: [io 0x04d0-0x04d1] has been reserved
Sep 28 18:50:58 nas kernel: system 00:09: [io 0x0800-0x087f] has been reserved
Sep 28 18:50:58 nas kernel: system 00:09: [io 0x0480-0x04ff] could not be reserved
Sep 28 18:50:58 nas kernel: system 00:09: [mem 0xfed1c000-0xfed1ffff] has been reserved
Sep 28 18:50:58 nas kernel: system 00:09: [mem 0xfed20000-0xfed3ffff] has been reserved
Sep 28 18:50:58 nas kernel: system 00:09: [mem 0xfed40000-0xfed8ffff] has been reserved
Sep 28 18:50:58 nas kernel: system 00:0c: [mem 0xffc00000-0xffefffff] has been reserved
Sep 28 18:50:58 nas kernel: system 00:0d: [mem 0xfec00000-0xfec00fff] could not be reserved
Sep 28 18:50:58 nas kernel: system 00:0d: [mem 0xfee00000-0xfee00fff] has been reserved
Sep 28 18:50:58 nas kernel: system 00:0e: [mem 0xe0000000-0xefffffff] has been reserved
Sep 28 18:50:58 nas kernel: system 00:0f: [mem 0x00000000-0x0009ffff] could not be reserved
Sep 28 18:50:58 nas kernel: system 00:0f: [mem 0x000c0000-0x000cffff] has been reserved
Sep 28 18:50:58 nas kernel: system 00:0f: [mem 0x000e0000-0x000fffff] could not be reserved
Sep 28 18:50:58 nas kernel: system 00:0f: [mem 0x00100000-0x3f6fffff] could not be reserved
Sep 28 18:50:58 nas kernel: system 00:0f: [mem 0xfed90000-0xffffffff] could not be reserved
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.0: BAR 9: assigned [mem 0x40000000-0x401fffff 64bit pref]
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.1: BAR 9: assigned [mem 0x40200000-0x403fffff 64bit pref]
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.0: PCI bridge to [bus 01-01]
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.0: bridge window [io 0xd000-0xdfff]
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.0: bridge window [mem 0xfea00000-0xfeafffff]
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.0: bridge window [mem 0x40000000-0x401fffff 64bit pref]
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.1: PCI bridge to [bus 02-02]
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.1: bridge window [io 0xe000-0xefff]
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.1: bridge window [mem 0xfeb00000-0xfebfffff]
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.1: bridge window [mem 0x40200000-0x403fffff 64bit pref]
Sep 28 18:50:58 nas kernel: pci 0000:00:1e.0: PCI bridge to [bus 03-03]
Sep 28 18:50:58 nas kernel: pci 0000:00:1e.0: bridge window [io disabled]
Sep 28 18:50:58 nas kernel: pci 0000:00:1e.0: bridge window [mem disabled]
Sep 28 18:50:58 nas kernel: pci 0000:00:1e.0: bridge window [mem pref disabled]
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.0: setting latency timer to 64
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.1: PCI INT B -> GSI 16 (level, low) -> IRQ 16
Sep 28 18:50:58 nas kernel: pci 0000:00:1c.1: setting latency timer to 64
Sep 28 18:50:58 nas kernel: pci 0000:00:1e.0: setting latency timer to 64
Sep 28 18:50:58 nas kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
Sep 28 18:50:58 nas kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
Sep 28 18:50:58 nas kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
Sep 28 18:50:58 nas kernel: pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000dffff]
Sep 28 18:50:58 nas kernel: pci_bus 0000:00: resource 8 [mem 0x3f700000-0xdfffffff]
Sep 28 18:50:58 nas kernel: pci_bus 0000:00: resource 9 [mem 0xf0000000-0xfed8ffff]
Sep 28 18:50:58 nas kernel: pci_bus 0000:01: resource 0 [io 0xd000-0xdfff]
Sep 28 18:50:58 nas kernel: pci_bus 0000:01: resource 1 [mem 0xfea00000-0xfeafffff]
Sep 28 18:50:58 nas kernel: pci_bus 0000:01: resource 2 [mem 0x40000000-0x401fffff 64bit pref]
Sep 28 18:50:58 nas kernel: pci_bus 0000:02: resource 0 [io 0xe000-0xefff]
Sep 28 18:50:58 nas kernel: pci_bus 0000:02: resource 1 [mem 0xfeb00000-0xfebfffff]
Sep 28 18:50:58 nas kernel: pci_bus 0000:02: resource 2 [mem 0x40200000-0x403fffff 64bit pref]
Sep 28 18:50:58 nas kernel: pci_bus 0000:03: resource 4 [io 0x0000-0x0cf7]
Sep 28 18:50:58 nas kernel: pci_bus 0000:03: resource 5 [io 0x0d00-0xffff]
Sep 28 18:50:58 nas kernel: pci_bus 0000:03: resource 6 [mem 0x000a0000-0x000bffff]
Sep 28 18:50:58 nas kernel: pci_bus 0000:03: resource 7 [mem 0x000d0000-0x000dffff]
Sep 28 18:50:58 nas kernel: pci_bus 0000:03: resource 8 [mem 0x3f700000-0xdfffffff]
Sep 28 18:50:58 nas kernel: pci_bus 0000:03: resource 9 [mem 0xf0000000-0xfed8ffff]
Sep 28 18:50:58 nas kernel: NET: Registered protocol family 2
Sep 28 18:50:58 nas kernel: IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
Sep 28 18:50:58 nas kernel: TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
Sep 28 18:50:58 nas kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 28 18:50:58 nas kernel: TCP: Hash tables configured (established 131072 bind 65536)
Sep 28 18:50:58 nas kernel: TCP reno registered
Sep 28 18:50:58 nas kernel: UDP hash table entries: 512 (order: 2, 16384 bytes)
Sep 28 18:50:58 nas kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
Sep 28 18:50:58 nas kernel: NET: Registered protocol family 1
Sep 28 18:50:58 nas kernel: RPC: Registered udp transport module.
Sep 28 18:50:58 nas kernel: RPC: Registered tcp transport module.
Sep 28 18:50:58 nas kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Sep 28 18:50:58 nas kernel: pci 0000:00:02.0: Boot video device
Sep 28 18:50:58 nas kernel: PCI: CLS 32 bytes, default 64
Sep 28 18:50:58 nas kernel: Unpacking initramfs...
Sep 28 18:50:58 nas kernel: Freeing initrd memory: 1552k freed
Sep 28 18:50:58 nas kernel: VFS: Disk quotas dquot_6.5.2
Sep 28 18:50:58 nas kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 28 18:50:58 nas kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Sep 28 18:50:58 nas kernel: fuse init (API version 7.15)
Sep 28 18:50:58 nas kernel: Btrfs loaded
Sep 28 18:50:58 nas kernel: msgmni has been set to 1977
Sep 28 18:50:58 nas kernel: async_tx: api initialized (async)
Sep 28 18:50:58 nas kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
Sep 28 18:50:58 nas kernel: io scheduler noop registered
Sep 28 18:50:58 nas kernel: io scheduler deadline registered
Sep 28 18:50:58 nas kernel: io scheduler cfq registered (default)
Sep 28 18:50:58 nas kernel: pcieport 0000:00:1c.0: ACPI _OSC control granted for 0x14
Sep 28 18:50:58 nas kernel: pcieport 0000:00:1c.0: setting latency timer to 64
Sep 28 18:50:58 nas kernel: pcieport 0000:00:1c.0: irq 40 for MSI/MSI-X
Sep 28 18:50:58 nas kernel: pcieport 0000:00:1c.1: ACPI _OSC control granted for 0x14
Sep 28 18:50:58 nas kernel: pcieport 0000:00:1c.1: setting latency timer to 64
Sep 28 18:50:58 nas kernel: pcieport 0000:00:1c.1: irq 41 for MSI/MSI-X
Sep 28 18:50:58 nas kernel: input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 28 18:50:58 nas kernel: ACPI: Power Button [PWRB]
Sep 28 18:50:58 nas kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 28 18:50:58 nas kernel: ACPI: Power Button [PWRF]
Sep 28 18:50:58 nas kernel: ACPI: acpi_idle registered with cpuidle
Sep 28 18:50:58 nas kernel: Linux agpgart interface v0.103
Sep 28 18:50:58 nas kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
Sep 28 18:50:58 nas kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Sep 28 18:50:58 nas kernel: serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Sep 28 18:50:58 nas kernel: 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Sep 28 18:50:58 nas kernel: 00:07: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Sep 28 18:50:58 nas kernel: loop: module loaded
Sep 28 18:50:58 nas kernel: mpt2sas version 06.100.00.00 loaded
Sep 28 18:50:58 nas kernel: ahci 0000:00:1f.2: version 3.0
Sep 28 18:50:58 nas kernel: ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
Sep 28 18:50:58 nas kernel: ahci 0000:00:1f.2: irq 42 for MSI/MSI-X
Sep 28 18:50:58 nas kernel: ahci: SSS flag set, parallel bus scan disabled
Sep 28 18:50:58 nas kernel: ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x3f impl SATA mode
Sep 28 18:50:58 nas kernel: ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pio slum part ccc ems sxs
Sep 28 18:50:58 nas kernel: ahci 0000:00:1f.2: setting latency timer to 64
Sep 28 18:50:58 nas kernel: scsi0 : ahci
Sep 28 18:50:58 nas kernel: scsi1 : ahci
Sep 28 18:50:58 nas kernel: scsi2 : ahci
Sep 28 18:50:58 nas kernel: scsi3 : ahci
Sep 28 18:50:58 nas kernel: scsi4 : ahci
Sep 28 18:50:58 nas kernel: scsi5 : ahci
Sep 28 18:50:58 nas kernel: ata1: SATA max UDMA/133 abar m2048@0xfe87b000 port 0xfe87b100 irq 42
Sep 28 18:50:58 nas kernel: ata2: SATA max UDMA/133 abar m2048@0xfe87b000 port 0xfe87b180 irq 42
Sep 28 18:50:58 nas kernel: ata3: SATA max UDMA/133 abar m2048@0xfe87b000 port 0xfe87b200 irq 42
Sep 28 18:50:58 nas kernel: ata4: SATA max UDMA/133 abar m2048@0xfe87b000 port 0xfe87b280 irq 42
Sep 28 18:50:58 nas kernel: ata5: SATA max UDMA/133 abar m2048@0xfe87b000 port 0xfe87b300 irq 42
Sep 28 18:50:58 nas kernel: ata6: SATA max UDMA/133 abar m2048@0xfe87b000 port 0xfe87b380 irq 42
Sep 28 18:50:58 nas kernel: e1000e: Intel(R) PRO/1000 Network Driver - 1.2.7-k2
Sep 28 18:50:58 nas kernel: e1000e: Copyright (c) 1999 - 2010 Intel Corporation.
Sep 28 18:50:58 nas kernel: Intel(R) Gigabit Ethernet Network Driver - version 2.1.0-k2
Sep 28 18:50:58 nas kernel: Copyright (c) 2007-2009 Intel Corporation.
Sep 28 18:50:58 nas kernel: ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 2.0.84-k2
Sep 28 18:50:58 nas kernel: ixgbe: Copyright (c) 1999-2010 Intel Corporation.
Sep 28 18:50:58 nas kernel: bonding: Ethernet Channel Bonding Driver: v3.7.0 (June 2, 2010)
Sep 28 18:50:58 nas kernel: bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details.
Sep 28 18:50:58 nas kernel: sk98lin 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Sep 28 18:50:58 nas kernel: sk98lin: Network Device Driver v10.70.1.3
Sep 28 18:50:58 nas kernel: (C)Copyright 1999-2008 Marvell(R).
Sep 28 18:50:58 nas kernel: sk98lin 0000:01:00.0: setting latency timer to 64
Sep 28 18:50:58 nas kernel: eth0: Marvell Yukon 88E8057 Gigabit Ethernet Controller
Sep 28 18:50:58 nas kernel: PrefPort:A RlmtMode:Check Link State
Sep 28 18:50:58 nas kernel: sk98lin 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Sep 28 18:50:58 nas kernel: sk98lin 0000:02:00.0: setting latency timer to 64
Sep 28 18:50:58 nas kernel: eth1: Marvell Yukon 88E8057 Gigabit Ethernet Controller
Sep 28 18:50:58 nas kernel: PrefPort:A RlmtMode:Check Link State
Sep 28 18:50:58 nas kernel: tun: Universal TUN/TAP device driver, 1.6
Sep 28 18:50:58 nas kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 28 18:50:58 nas kernel: Fusion MPT base driver 3.04.17
Sep 28 18:50:58 nas kernel: Copyright (c) 1999-2008 LSI Corporation
Sep 28 18:50:58 nas kernel: Fusion MPT SAS Host driver 3.04.17
Sep 28 18:50:58 nas kernel: Fusion MPT misc device (ioctl) driver 3.04.17
Sep 28 18:50:58 nas kernel: mptctl: Registered with Fusion MPT base driver
Sep 28 18:50:58 nas kernel: mptctl: /dev/mptctl @ (major,minor=10,220)
Sep 28 18:50:58 nas kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 28 18:50:58 nas kernel: ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Sep 28 18:50:58 nas kernel: ehci_hcd 0000:00:1a.7: setting latency timer to 64
Sep 28 18:50:58 nas kernel: ehci_hcd 0000:00:1a.7: EHCI Host Controller
Sep 28 18:50:58 nas kernel: ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
Sep 28 18:50:58 nas kernel: ehci_hcd 0000:00:1a.7: debug port 1
Sep 28 18:50:58 nas kernel: ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
Sep 28 18:50:58 nas kernel: ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfe87bc00
Sep 28 18:50:58 nas kernel: ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
Sep 28 18:50:58 nas kernel: hub 1-0:1.0: USB hub found
Sep 28 18:50:58 nas kernel: hub 1-0:1.0: 6 ports detected
Sep 28 18:50:58 nas kernel: ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
Sep 28 18:50:58 nas kernel: ehci_hcd 0000:00:1d.7: setting latency timer to 64
Sep 28 18:50:58 nas kernel: ehci_hcd 0000:00:1d.7: EHCI Host Controller
Sep 28 18:50:58 nas kernel: ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
Sep 28 18:50:58 nas kernel: ehci_hcd 0000:00:1d.7: debug port 1
Sep 28 18:50:58 nas kernel: ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
Sep 28 18:50:58 nas kernel: ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfe87b800
Sep 28 18:50:58 nas kernel: ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
Sep 28 18:50:58 nas kernel: hub 2-0:1.0: USB hub found
Sep 28 18:50:58 nas kernel: hub 2-0:1.0: 6 ports detected
Sep 28 18:50:58 nas kernel: uhci_hcd: USB Universal Host Controller Interface driver
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1a.0: setting latency timer to 64
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1a.0: UHCI Host Controller
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000c880
Sep 28 18:50:58 nas kernel: hub 3-0:1.0: USB hub found
Sep 28 18:50:58 nas kernel: hub 3-0:1.0: 2 ports detected
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1a.1: setting latency timer to 64
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1a.1: UHCI Host Controller
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1a.1: irq 21, io base 0x0000c800
Sep 28 18:50:58 nas kernel: hub 4-0:1.0: USB hub found
Sep 28 18:50:58 nas kernel: hub 4-0:1.0: 2 ports detected
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1a.2: PCI INT D -> GSI 19 (level, low) -> IRQ 19
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1a.2: setting latency timer to 64
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1a.2: UHCI Host Controller
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1a.2: irq 19, io base 0x0000c480
Sep 28 18:50:58 nas kernel: hub 5-0:1.0: USB hub found
Sep 28 18:50:58 nas kernel: hub 5-0:1.0: 2 ports detected
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000c400
Sep 28 18:50:58 nas kernel: hub 6-0:1.0: USB hub found
Sep 28 18:50:58 nas kernel: hub 6-0:1.0: 2 ports detected
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000c080
Sep 28 18:50:58 nas kernel: hub 7-0:1.0: USB hub found
Sep 28 18:50:58 nas kernel: hub 7-0:1.0: 2 ports detected
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
Sep 28 18:50:58 nas kernel: uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000c000
Sep 28 18:50:58 nas kernel: hub 8-0:1.0: USB hub found
Sep 28 18:50:58 nas kernel: hub 8-0:1.0: 2 ports detected
Sep 28 18:50:58 nas kernel: usbcore: registered new interface driver usblp
Sep 28 18:50:58 nas kernel: usbcore: registered new interface driver uas
Sep 28 18:50:58 nas kernel: Initializing USB Mass Storage driver...
Sep 28 18:50:58 nas kernel: usbcore: registered new interface driver usb-storage
Sep 28 18:50:58 nas kernel: USB Mass Storage support registered.
Sep 28 18:50:58 nas kernel: rtc_cmos 00:03: RTC can wake from S4
Sep 28 18:50:58 nas kernel: rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
Sep 28 18:50:58 nas kernel: rtc0: alarms up to one month, y3k, 114 bytes nvram
Sep 28 18:50:58 nas kernel: i2c /dev entries driver
Sep 28 18:50:58 nas kernel: i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Sep 28 18:50:58 nas kernel: coretemp coretemp.0: Unable to read TjMax from CPU.
Sep 28 18:50:58 nas kernel: coretemp coretemp.0: Using relative temperature scale!
Sep 28 18:50:58 nas kernel: coretemp coretemp.1: Unable to read TjMax from CPU.
Sep 28 18:50:58 nas kernel: coretemp coretemp.1: Using relative temperature scale!
Sep 28 18:50:58 nas kernel: it87: Found IT8721F chip at 0xa10, revision 1
Sep 28 18:50:58 nas kernel: it87: in3 is VCC (+5V)
Sep 28 18:50:58 nas kernel: it87: in7 is VCCH (+5V Stand-By)
Sep 28 18:50:58 nas kernel: it87: Ultra 6: 87
Sep 28 18:50:58 nas kernel: md: raid0 personality registered for level 0
Sep 28 18:50:58 nas kernel: md: raid1 personality registered for level 1
Sep 28 18:50:58 nas kernel: md: raid10 personality registered for level 10
Sep 28 18:50:58 nas kernel: md: raid6 personality registered for level 6
Sep 28 18:50:58 nas kernel: md: raid5 personality registered for level 5
Sep 28 18:50:58 nas kernel: md: raid4 personality registered for level 4
Sep 28 18:50:58 nas kernel: device-mapper: ioctl: 4.18.0-ioctl (2010-06-29) initialised: dm-devel@redhat.com
Sep 28 18:50:58 nas kernel: cpuidle: using governor ladder
Sep 28 18:50:58 nas kernel: cpuidle: using governor menu
Sep 28 18:50:58 nas kernel: ioatdma: Intel(R) QuickData Technology Driver 4.00
Sep 28 18:50:58 nas kernel: usbcore: registered new interface driver usbhid
Sep 28 18:50:58 nas kernel: usbhid: USB HID core driver
Sep 28 18:50:58 nas kernel: IPv4 over IPv4 tunneling driver
Sep 28 18:50:58 nas kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 28 18:50:58 nas kernel: TCP bic registered
Sep 28 18:50:58 nas kernel: NET: Registered protocol family 10
Sep 28 18:50:58 nas kernel: lo: Disabled Privacy Extensions
Sep 28 18:50:58 nas kernel: tunl0: Disabled Privacy Extensions
Sep 28 18:50:58 nas kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Sep 28 18:50:58 nas kernel: NET: Registered protocol family 17
Sep 28 18:50:58 nas kernel: 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
Sep 28 18:50:58 nas kernel: All bugs added by David S. Miller <davem@redhat.com>
Sep 28 18:50:58 nas kernel: Registering the dns_resolver key type
Sep 28 18:50:58 nas kernel: rtc_cmos 00:03: setting system clock to 2012-09-29 01:50:29 UTC (1348883429)
Sep 28 18:50:58 nas kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 28 18:50:58 nas kernel: ata1.00: ATA-8: ST32000542AS, CC34, max UDMA/133
Sep 28 18:50:58 nas kernel: ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
Sep 28 18:50:58 nas kernel: ata1.00: configured for UDMA/133
Sep 28 18:50:58 nas kernel: scsi 0:0:0:0: Direct-Access ATA ST32000542AS CC34 PQ: 0 ANSI: 5
Sep 28 18:50:58 nas kernel: sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Sep 28 18:50:58 nas kernel: sd 0:0:0:0: [sda] Write Protect is off
Sep 28 18:50:58 nas kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Sep 28 18:50:58 nas kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Sep 28 18:50:58 nas kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 28 18:50:58 nas kernel: sda: sda1 sda2 sda5
Sep 28 18:50:58 nas kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Sep 28 18:50:58 nas kernel: usb 2-1: new high speed USB device using ehci_hcd and address 2
Sep 28 18:50:58 nas kernel: scsi6 : usb-storage 2-1:1.0
Sep 28 18:50:58 nas kernel: usb 7-1: new full speed USB device using uhci_hcd and address 2
Sep 28 18:50:58 nas kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 28 18:50:58 nas kernel: ata2.00: ATA-8: ST32000542AS, CC34, max UDMA/133
Sep 28 18:50:58 nas kernel: ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
Sep 28 18:50:58 nas kernel: ata2.00: configured for UDMA/133
Sep 28 18:50:58 nas kernel: scsi 1:0:0:0: Direct-Access ATA ST32000542AS CC34 PQ: 0 ANSI: 5
Sep 28 18:50:58 nas kernel: sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Sep 28 18:50:58 nas kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Sep 28 18:50:58 nas kernel: sd 1:0:0:0: [sdb] Write Protect is off
Sep 28 18:50:58 nas kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Sep 28 18:50:58 nas kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 28 18:50:58 nas kernel: sdb: sdb1 sdb2 sdb5
Sep 28 18:50:58 nas kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Sep 28 18:50:58 nas kernel: generic-usb 0003:0764:0501.0001: hiddev0: USB HID v1.10 Device [CP1500PFCLCD CRCA102-3I1] on usb-0000:00:1d.1-1/input0
Sep 28 18:50:58 nas kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 28 18:50:58 nas kernel: ata3.00: ATA-8: ST32000542AS, CC34, max UDMA/133
Sep 28 18:50:58 nas kernel: ata3.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
Sep 28 18:50:58 nas kernel: ata3.00: configured for UDMA/133
Sep 28 18:50:58 nas kernel: scsi 2:0:0:0: Direct-Access ATA ST32000542AS CC34 PQ: 0 ANSI: 5
Sep 28 18:50:58 nas kernel: sd 2:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Sep 28 18:50:58 nas kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0
Sep 28 18:50:58 nas kernel: sd 2:0:0:0: [sdc] Write Protect is off
Sep 28 18:50:58 nas kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Sep 28 18:50:58 nas kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 28 18:50:58 nas kernel: sdc: sdc1 sdc2 sdc5
Sep 28 18:50:58 nas kernel: sd 2:0:0:0: [sdc] Attached SCSI disk
Sep 28 18:50:58 nas kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 28 18:50:58 nas kernel: ata4.00: ATA-8: ST32000542AS, CC34, max UDMA/133
Sep 28 18:50:58 nas kernel: ata4.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
Sep 28 18:50:58 nas kernel: ata4.00: configured for UDMA/133
Sep 28 18:50:58 nas kernel: scsi 3:0:0:0: Direct-Access ATA ST32000542AS CC34 PQ: 0 ANSI: 5
Sep 28 18:50:58 nas kernel: sd 3:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Sep 28 18:50:58 nas kernel: sd 3:0:0:0: Attached scsi generic sg3 type 0
Sep 28 18:50:58 nas kernel: sd 3:0:0:0: [sdd] Write Protect is off
Sep 28 18:50:58 nas kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
Sep 28 18:50:58 nas kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 28 18:50:58 nas kernel: sdd: sdd1 sdd2 sdd5
Sep 28 18:50:58 nas kernel: sd 3:0:0:0: [sdd] Attached SCSI disk
Sep 28 18:50:58 nas kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 28 18:50:58 nas kernel: ata5.00: ATA-8: ST32000542AS, CC34, max UDMA/133
Sep 28 18:50:58 nas kernel: ata5.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
Sep 28 18:50:58 nas kernel: ata5.00: configured for UDMA/133
Sep 28 18:50:58 nas kernel: scsi 4:0:0:0: Direct-Access ATA ST32000542AS CC34 PQ: 0 ANSI: 5
Sep 28 18:50:58 nas kernel: sd 4:0:0:0: [sde] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Sep 28 18:50:58 nas kernel: sd 4:0:0:0: Attached scsi generic sg4 type 0
Sep 28 18:50:58 nas kernel: sd 4:0:0:0: [sde] Write Protect is off
Sep 28 18:50:58 nas kernel: sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00
Sep 28 18:50:58 nas kernel: sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 28 18:50:58 nas kernel: sde: sde1 sde2 sde5
Sep 28 18:50:58 nas kernel: sd 4:0:0:0: [sde] Attached SCSI disk
Sep 28 18:50:58 nas kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 28 18:50:58 nas kernel: ata6.00: ATA-8: ST32000542AS, CC34, max UDMA/133
Sep 28 18:50:58 nas kernel: ata6.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
Sep 28 18:50:58 nas kernel: ata6.00: configured for UDMA/133
Sep 28 18:50:58 nas kernel: scsi 5:0:0:0: Direct-Access ATA ST32000542AS CC34 PQ: 0 ANSI: 5
Sep 28 18:50:58 nas kernel: sd 5:0:0:0: [sdf] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Sep 28 18:50:58 nas kernel: sd 5:0:0:0: Attached scsi generic sg5 type 0
Sep 28 18:50:58 nas kernel: sd 5:0:0:0: [sdf] Write Protect is off
Sep 28 18:50:58 nas kernel: sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00
Sep 28 18:50:58 nas kernel: sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 28 18:50:58 nas kernel: sdf: sdf1 sdf2 sdf5
Sep 28 18:50:58 nas kernel: sd 5:0:0:0: [sdf] Attached SCSI disk
Sep 28 18:50:58 nas kernel: Freeing unused kernel memory: 400k freed
Sep 28 18:50:58 nas kernel: nv6vpd: module license 'Proprietary' taints kernel.
Sep 28 18:50:58 nas kernel: Disabling lock debugging due to kernel taint
Sep 28 18:50:58 nas kernel: ReadyNAS VPD device driver init...
Sep 28 18:50:58 nas kernel: DMI Product Version: 06/10/2010 FLAME6-2 V1.1
Sep 28 18:50:58 nas kernel: month = 6 day = 10 year = 2010 name = FLAME6-2 major = 1 minor = 1
Sep 28 18:50:58 nas kernel: core = 0 data = 0 model = 0
Sep 28 18:50:58 nas kernel: scsi 6:0:0:0: Direct-Access SMI USB DISK 1100 PQ: 0 ANSI: 0 CCS
Sep 28 18:50:58 nas kernel: scsi: killing requests for dead queue
Sep 28 18:50:58 nas last message repeated 7 times
Sep 28 18:50:58 nas kernel: sd 6:0:0:0: Attached scsi generic sg6 type 0
Sep 28 18:50:58 nas kernel: sd 6:0:0:0: [sdg] 250880 512-byte logical blocks: (128 MB/122 MiB)
Sep 28 18:50:58 nas kernel: sd 6:0:0:0: [sdg] Write Protect is off
Sep 28 18:50:58 nas kernel: sd 6:0:0:0: [sdg] Mode Sense: 43 00 00 00
Sep 28 18:50:58 nas kernel: sd 6:0:0:0: [sdg] Assuming drive cache: write through
Sep 28 18:50:58 nas kernel: sd 6:0:0:0: [sdg] Assuming drive cache: write through
Sep 28 18:50:58 nas kernel: sdg: sdg1
Sep 28 18:50:58 nas kernel: sd 6:0:0:0: [sdg] Assuming drive cache: write through
Sep 28 18:50:58 nas kernel: sd 6:0:0:0: [sdg] Attached SCSI removable disk
Sep 28 18:50:58 nas kernel: nv6lcd v2.1 loaded.
Sep 28 18:50:58 nas kernel: pvgpio v1.0: initialization complete (systype:2)
Sep 28 18:50:58 nas kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 28 18:50:58 nas kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 28 18:50:58 nas kernel: md: bind<sdb1>
Sep 28 18:50:58 nas kernel: md: bind<sdc1>
Sep 28 18:50:58 nas kernel: md: bind<sdd1>
Sep 28 18:50:58 nas kernel: md: bind<sde1>
Sep 28 18:50:58 nas kernel: md: bind<sdf1>
Sep 28 18:50:58 nas kernel: md: bind<sda1>
Sep 28 18:50:58 nas kernel: bio: create slab <bio-1> at 1
Sep 28 18:50:58 nas kernel: md/raid1:md0: active with 6 out of 6 mirrors
Sep 28 18:50:58 nas kernel: md0: detected capacity change from 0 to 4293906432
Sep 28 18:50:58 nas kernel: md0: unknown partition table
Sep 28 18:50:58 nas kernel: md: bind<sdb2>
Sep 28 18:50:58 nas kernel: md: bind<sdc2>
Sep 28 18:50:58 nas kernel: md: bind<sdd2>
Sep 28 18:50:58 nas kernel: md: bind<sde2>
Sep 28 18:50:58 nas kernel: md: bind<sdf2>
Sep 28 18:50:58 nas kernel: md: bind<sda2>
Sep 28 18:50:58 nas kernel: md/raid:md1: device sda2 operational as raid disk 0
Sep 28 18:50:58 nas kernel: md/raid:md1: device sdf2 operational as raid disk 5
Sep 28 18:50:58 nas kernel: md/raid:md1: device sde2 operational as raid disk 4
Sep 28 18:50:58 nas kernel: md/raid:md1: device sdd2 operational as raid disk 3
Sep 28 18:50:58 nas kernel: md/raid:md1: device sdc2 operational as raid disk 2
Sep 28 18:50:58 nas kernel: md/raid:md1: device sdb2 operational as raid disk 1
Sep 28 18:50:58 nas kernel: md/raid:md1: allocated 6372kB
Sep 28 18:50:58 nas kernel: md/raid:md1: raid level 6 active with 6 out of 6 devices, algorithm 2
Sep 28 18:50:58 nas kernel: RAID conf printout:
Sep 28 18:50:58 nas kernel: --- level:6 rd:6 wd:6
Sep 28 18:50:58 nas kernel: disk 0, o:1, dev:sda2
Sep 28 18:50:58 nas kernel: disk 1, o:1, dev:sdb2
Sep 28 18:50:58 nas kernel: disk 2, o:1, dev:sdc2
Sep 28 18:50:58 nas kernel: disk 3, o:1, dev:sdd2
Sep 28 18:50:58 nas kernel: disk 4, o:1, dev:sde2
Sep 28 18:50:58 nas kernel: disk 5, o:1, dev:sdf2
Sep 28 18:50:58 nas kernel: md1: detected capacity change from 0 to 2147221504
Sep 28 18:50:58 nas kernel: md1: unknown partition table
Sep 28 18:50:58 nas kernel: md: bind<sda5>
Sep 28 18:50:58 nas kernel: md: bind<sdc5>
Sep 28 18:50:58 nas kernel: md: bind<sdd5>
Sep 28 18:50:58 nas kernel: md: bind<sde5>
Sep 28 18:50:58 nas kernel: md: bind<sdf5>
Sep 28 18:50:58 nas kernel: md: bind<sdb5>
Sep 28 18:50:58 nas kernel: md: kicking non-fresh sda5 from array!
Sep 28 18:50:58 nas kernel: md: unbind<sda5>
Sep 28 18:50:58 nas kernel: md: export_rdev(sda5)
Sep 28 18:50:58 nas kernel: md/raid:md2: device sdb5 operational as raid disk 1
Sep 28 18:50:58 nas kernel: md/raid:md2: device sdf5 operational as raid disk 5
Sep 28 18:50:58 nas kernel: md/raid:md2: device sde5 operational as raid disk 4
Sep 28 18:50:58 nas kernel: md/raid:md2: device sdd5 operational as raid disk 3
Sep 28 18:50:58 nas kernel: md/raid:md2: device sdc5 operational as raid disk 2
Sep 28 18:50:58 nas kernel: md/raid:md2: allocated 6372kB
Sep 28 18:50:58 nas kernel: md/raid:md2: raid level 5 active with 5 out of 6 devices, algorithm 2
Sep 28 18:50:58 nas kernel: RAID conf printout:
Sep 28 18:50:58 nas kernel: --- level:5 rd:6 wd:5
Sep 28 18:50:58 nas kernel: disk 1, o:1, dev:sdb5
Sep 28 18:50:58 nas kernel: disk 2, o:1, dev:sdc5
Sep 28 18:50:58 nas kernel: disk 3, o:1, dev:sdd5
Sep 28 18:50:58 nas kernel: disk 4, o:1, dev:sde5
Sep 28 18:50:58 nas kernel: disk 5, o:1, dev:sdf5
Sep 28 18:50:58 nas kernel: md2: detected capacity change from 0 to 9977816023040
Sep 28 18:50:58 nas kernel: md2: unknown partition table
Sep 28 18:50:58 nas kernel: EXT3-fs: barriers not enabled
Sep 28 18:50:58 nas kernel: kjournald starting. Commit interval 5 seconds
Sep 28 18:50:58 nas kernel: EXT3-fs (md0): mounted filesystem with ordered data mode
Sep 28 18:50:58 nas kernel: eth0: network connection up using port A
Sep 28 18:50:58 nas kernel: speed: 1000
Sep 28 18:50:58 nas kernel: autonegotiation: yes
Sep 28 18:50:58 nas kernel: duplex mode: full
Sep 28 18:50:58 nas kernel: flowctrl: symmetric
Sep 28 18:50:58 nas kernel: role: slave
Sep 28 18:50:58 nas kernel: irq moderation: disabled
Sep 28 18:50:58 nas kernel: tcp offload: enabled
Sep 28 18:50:58 nas kernel: scatter-gather: enabled
Sep 28 18:50:58 nas kernel: tx-checksum: enabled
Sep 28 18:50:58 nas kernel: rx-checksum: enabled
Sep 28 18:50:58 nas kernel: rx-polling: enabled
Sep 28 18:50:58 nas kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep 28 18:50:58 nas kernel: EXT3-fs: barriers not enabled
Sep 28 18:50:58 nas kernel: kjournald starting. Commit interval 5 seconds
Sep 28 18:50:58 nas kernel: EXT3-fs (md0): using internal journal
Sep 28 18:50:58 nas kernel: EXT3-fs (md0): mounted filesystem with ordered data mode
Sep 28 18:50:58 nas kernel: scsi: killing requests for dead queue
Sep 28 18:50:58 nas kernel: eth0: no IPv6 routers present
Sep 28 18:50:58 nas kernel: udevd version 125 started
Sep 28 18:50:58 nas kernel: Adding 2096892k swap on /dev/md1. Priority:-1 extents:1 across:2096892k
Sep 28 18:50:58 nas kernel: ata1.00: configured for UDMA/133
Sep 28 18:50:58 nas kernel: ata1: EH complete
Sep 28 18:50:58 nas kernel: ata2.00: configured for UDMA/133
Sep 28 18:50:58 nas kernel: ata2: EH complete
Sep 28 18:50:58 nas kernel: ata3.00: configured for UDMA/133
Sep 28 18:50:58 nas kernel: ata3: EH complete
Sep 28 18:50:58 nas kernel: ata4.00: configured for UDMA/133
Sep 28 18:50:58 nas kernel: ata4: EH complete
Sep 28 18:50:58 nas kernel: ata5.00: configured for UDMA/133
Sep 28 18:50:58 nas kernel: ata5: EH complete
Sep 28 18:50:58 nas kernel: ata6.00: configured for UDMA/133
Sep 28 18:50:58 nas kernel: ata6: EH complete
Sep 28 18:50:58 nas kernel: EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv1
Sep 28 18:50:58 nas kernel: md: bind<sda5>
Sep 28 18:50:58 nas kernel: RAID conf printout:
Sep 28 18:50:58 nas kernel: --- level:5 rd:6 wd:5
Sep 28 18:50:58 nas kernel: disk 0, o:1, dev:sda5
Sep 28 18:50:58 nas kernel: disk 1, o:1, dev:sdb5
Sep 28 18:50:58 nas kernel: disk 2, o:1, dev:sdc5
Sep 28 18:50:58 nas kernel: disk 3, o:1, dev:sdd5
Sep 28 18:50:58 nas kernel: disk 4, o:1, dev:sde5
Sep 28 18:50:58 nas kernel: disk 5, o:1, dev:sdf5
Sep 28 18:50:58 nas kernel: md: recovery of RAID array md2
Sep 28 18:50:58 nas kernel: md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
Sep 28 18:50:58 nas kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
Sep 28 18:50:58 nas kernel: md: using 128k window, over a total of 1948792192 blocks.
Sep 28 18:51:13 nas ifplugd(eth0)[2512]: ifplugd 0.28 initializing.
Sep 28 18:51:13 nas ifplugd(eth0)[2512]: Using interface eth0/00:1F:33:EA:96:E4 with driver <sk98lin> (version: 10.70.1.3 (01))
Sep 28 18:51:13 nas ifplugd(eth0)[2512]: Using detection mode: SIOCETHTOOL
Sep 28 18:51:13 nas ifplugd(eth0)[2512]: Initialization complete, link beat detected.
Sep 28 18:51:13 nas ifplugd(eth0)[2512]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Sep 28 18:51:14 nas ifplugd(eth0)[2512]: client: 2514: old priority 0, new priority 0
Sep 28 18:51:14 nas ifplugd(eth0)[2512]: client: No udhcpc found running; none killed.
Sep 28 18:51:15 nas udhcpc[2519]: udhcpc (v1.18.4) started
Sep 28 18:51:15 nas ifplugd(eth0)[2512]: client: udhcpc (v1.18.4) started
Sep 28 18:51:15 nas udhcpc[2519]: Sending discover...
Sep 28 18:51:15 nas ifplugd(eth0)[2512]: client: Sending discover...
Sep 28 18:51:15 nas udhcpc[2519]: Sending select for 192.168.0.110...
Sep 28 18:51:15 nas ifplugd(eth0)[2512]: client: Sending select for 192.168.0.110...
Sep 28 18:51:16 nas udhcpc[2519]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 28 18:51:16 nas ifplugd(eth0)[2512]: client: Lease of 192.168.0.110 obtained, lease time 7200
Sep 28 18:51:21 nas ifplugd(eth0)[2512]: client: apache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.0.110 for ServerName
Sep 28 18:51:29 nas ifplugd(eth0)[2512]: client: Stopping rsync daemon: rsync.
Sep 28 18:51:30 nas ifplugd(eth0)[2512]: client: Running ntpd to synchronize clock.
Sep 28 18:51:30 nas chronyd[2654]: chronyd version 1.24 starting
Sep 28 18:51:30 nas upnpd(eth0)[2665]: Listening on 192.168.0.110:50000
Sep 28 18:51:30 nas rsyncd[2664]: rsyncd version 3.0.9 starting, listening on port 873
Sep 28 18:51:30 nas chronyd[2654]: Initial txc.tick=10000 txc.freq=0 (0.00000000) txc.offset=0 => hz=100 shift_hz=7
Sep 28 18:51:30 nas chronyd[2654]: set_config_hz=0 hz=100 shift_hz=7 basic_freq_scale=1.28000000 nominal_tick=10000 slew_delta_tick=833 max_tick_bias=1000
Sep 28 18:51:30 nas chronyd[2654]: Linux kernel major=2 minor=6 patch=37
Sep 28 18:51:30 nas chronyd[2654]: calculated_freq_scale=1.00000000 freq_scale=1.00000000
Sep 28 18:51:31 nas chronyd[2654]: System's initial offset : 0.523357 seconds slow of true (slew)
Sep 28 18:51:31 nas ifplugd(eth0)[2512]: client: Starting rsync daemon: rsync.
Sep 28 18:51:32 nas ifplugd(eth0)[2512]: client: Starting plexserver
Sep 28 18:51:38 nas ifplugd(eth0)[2512]: Program executed successfully.
Sep 28 18:51:39 nas ifplugd(eth1)[2825]: ifplugd 0.28 initializing.
Sep 28 18:51:39 nas ifplugd(eth1)[2825]: Using interface eth1/00:1F:33:EA:96:E5 with driver <sk98lin> (version: 10.70.1.3 (01))
Sep 28 18:51:39 nas ifplugd(eth1)[2825]: Using detection mode: SIOCETHTOOL
Sep 28 18:51:39 nas ifplugd(eth1)[2825]: Initialization complete, link beat not detected.
Sep 28 18:51:43 nas RAIDiator: System is up.
Sep 28 18:51:50 nas kernel: sk98lin 0000:01:00.0: PME# enabled
Sep 28 18:51:50 nas kernel: sk98lin 0000:02:00.0: PME# enabled
Sep 28 18:52:08 nas syslogd 1.4.1#18: restart.
Sep 28 18:52:11 nas avahi-daemon[3429]: Found user 'avahi' (UID 20) and group 'avahi' (GID 20).
Sep 28 18:52:11 nas avahi-daemon[3429]: Successfully dropped root privileges.
Sep 28 18:52:11 nas avahi-daemon[3429]: avahi-daemon 0.6.23 starting up.
Sep 28 18:52:11 nas avahi-daemon[3429]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Sep 28 18:52:11 nas avahi-daemon[3429]: Loading service file /etc/avahi/services/afp.service.
Sep 28 18:52:11 nas avahi-daemon[3429]: Loading service file /etc/avahi/services/frontview.service.
Sep 28 18:52:11 nas avahi-daemon[3429]: Loading service file /etc/avahi/services/readynas.service.
Sep 28 18:52:12 nas avahi-daemon[3429]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.110.
Sep 28 18:52:12 nas avahi-daemon[3429]: New relevant interface eth0.IPv4 for mDNS.
Sep 28 18:52:12 nas avahi-daemon[3429]: Network interface enumeration completed.
Sep 28 18:52:12 nas avahi-daemon[3429]: Registering new address record for 192.168.0.110 on eth0.IPv4.
Sep 28 18:52:12 nas avahi-daemon[3429]: Registering HINFO record with values 'X86_64'/'LINUX'.
Sep 28 18:52:13 nas avahi-daemon[3429]: Server startup complete. Host name is nas.local. Local service cookie is 150880404.
Sep 28 18:52:13 nas avahi-daemon[3429]: Service "ReadyNAS Discovery [nas]" (/etc/avahi/services/readynas.service) successfully established.
Sep 28 18:52:13 nas avahi-daemon[3429]: Service "FrontView on nas" (/etc/avahi/services/frontview.service) successfully established.
Sep 28 18:52:13 nas avahi-daemon[3429]: Service "nas (AFP)" (/etc/avahi/services/afp.service) successfully established.
Sep 28 18:52:14 nas ipwatchd[3447]: IPwatchD started
Sep 28 19:00:05 nas chronyd[2654]: Selected source 17.171.4.14
Sep 28 19:04:23 nas chronyd[2654]: Selected source 209.249.181.23
Sep 28 19:06:03 nas RAIDiator: Backup finished. [Job 002]
Sep 28 19:07:00 nas rsyncd[5651]: connect from miniduo1.home (192.168.0.103)
Sep 28 19:07:00 nas rsyncd[5651]: unknown module 'Projects' tried from miniduo1.home (192.168.0.103)
Sep 28 19:11:00 nas rsyncd[6113]: connect from miniduo1.home (192.168.0.103)
Sep 28 19:11:00 nas rsyncd[6113]: unknown module 'Music_Library' tried from miniduo1.home (192.168.0.103)
Sep 28 19:11:00 nas rsyncd[6114]: connect from miniduo1.home (192.168.0.103)
Sep 28 19:11:00 nas rsyncd[6114]: unknown module 'Music_Library' tried from miniduo1.home (192.168.0.103)
Sep 28 19:45:00 nas rsyncd[7215]: connect from miniduo1.home (192.168.0.103)
Sep 28 19:45:00 nas rsyncd[7215]: unknown module 'backup' tried from miniduo1.home (192.168.0.103)
Sep 28 19:51:16 nas udhcpc[2540]: Sending renew...
Sep 28 19:51:16 nas udhcpc[2540]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 28 20:05:15 nas RAIDiator: Backup finished. [Job 003]
Sep 28 20:05:59 nas RAIDiator: Backup finished. [Job 002]
Sep 28 20:07:31 nas RAIDiator: Backup finished. [Job 004]
Sep 28 20:51:16 nas udhcpc[2540]: Sending renew...
Sep 28 20:51:17 nas udhcpc[2540]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 28 21:06:36 nas RAIDiator: Backup finished. [Job 002]
Sep 28 21:51:17 nas udhcpc[2540]: Sending renew...
Sep 28 21:51:17 nas udhcpc[2540]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 28 22:05:20 nas RAIDiator: Backup finished. [Job 003]
Sep 28 22:06:32 nas RAIDiator: Backup finished. [Job 002]
Sep 28 22:51:18 nas udhcpc[2540]: Sending renew...
Sep 28 22:51:18 nas udhcpc[2540]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 28 23:05:39 nas RAIDiator: Backup finished. [Job 002]
Sep 28 23:51:19 nas udhcpc[2540]: Sending renew...
Sep 28 23:51:19 nas udhcpc[2540]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 29 00:05:05 nas RAIDiator: Backup finished. [Job 003]
Sep 29 00:05:07 nas RAIDiator: Backup finished. [Job 005]
Sep 29 00:05:58 nas RAIDiator: Backup finished. [Job 001]
Sep 29 00:06:42 nas RAIDiator: Backup finished. [Job 002]
Sep 29 00:09:38 nas RAIDiator: Backup finished. [Job 004]
Sep 29 00:51:19 nas udhcpc[2540]: Sending renew...
Sep 29 00:51:19 nas udhcpc[2540]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 29 01:06:48 nas RAIDiator: Backup finished. [Job 002]
Sep 29 01:51:20 nas udhcpc[2540]: Sending renew...
Sep 29 01:51:20 nas udhcpc[2540]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 29 02:05:24 nas RAIDiator: Backup finished. [Job 003]
Sep 29 02:06:04 nas RAIDiator: Backup finished. [Job 002]
Sep 29 02:25:23 nas kernel: md: md2: recovery done.
Sep 29 02:25:23 nas kernel: RAID conf printout:
Sep 29 02:25:23 nas kernel: --- level:5 rd:6 wd:6
Sep 29 02:25:23 nas kernel: disk 0, o:1, dev:sda5
Sep 29 02:25:23 nas kernel: disk 1, o:1, dev:sdb5
Sep 29 02:25:23 nas kernel: disk 2, o:1, dev:sdc5
Sep 29 02:25:23 nas kernel: disk 3, o:1, dev:sdd5
Sep 29 02:25:23 nas kernel: disk 4, o:1, dev:sde5
Sep 29 02:25:23 nas kernel: disk 5, o:1, dev:sdf5
Sep 29 02:25:37 nas RAIDiator: RAID sync finished on volume C.
Sep 29 02:25:37 nas RAIDiator: RAID event detected. (nas) : RAID sync finished on volume C.\n\n[Sat Sep 29 02:25:33 PDT 2012]
Sep 29 02:51:21 nas udhcpc[2540]: Sending renew...
Sep 29 02:51:21 nas udhcpc[2540]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 29 02:56:31 nas noflushd[2197]: Spinning down disks.
Sep 29 03:05:12 nas noflushd[2197]: Disks spinning up after 8 minutes.
Sep 29 03:06:02 nas RAIDiator: Backup finished. [Job 002]
Sep 29 03:20:36 nas noflushd[2197]: Spinning down disks.
Sep 29 03:23:12 nas noflushd[2197]: Disks spinning up after 2 minutes.
Sep 29 03:28:14 nas noflushd[2197]: Spinning down disks.
Sep 29 03:51:21 nas udhcpc[2540]: Sending renew...
Sep 29 03:51:21 nas udhcpc[2540]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 29 04:05:16 nas noflushd[2197]: Disks spinning up after 37 minutes.
Sep 29 04:05:41 nas RAIDiator: Backup finished. [Job 003]
Sep 29 04:05:52 nas RAIDiator: Backup finished. [Job 002]
Sep 29 04:06:44 nas RAIDiator: Backup finished. [Job 004]
Sep 29 04:50:45 nas noflushd[2197]: Spinning down disks.
Sep 29 04:51:21 nas udhcpc[2540]: Sending renew...
Sep 29 04:51:21 nas udhcpc[2540]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 29 04:51:36 nas noflushd[2197]: Disks spinning up after 0 minutes.
Sep 29 04:57:20 nas noflushd[2197]: Spinning down disks.
Sep 29 05:05:11 nas noflushd[2197]: Disks spinning up after 7 minutes.
Sep 29 05:06:32 nas RAIDiator: Backup finished. [Job 002]
Sep 29 05:22:12 nas noflushd[2197]: Spinning down disks.
Sep 29 05:23:13 nas noflushd[2197]: Disks spinning up after 1 minutes.
Sep 29 05:50:47 nas noflushd[2197]: Spinning down disks.
Sep 29 05:52:07 nas udhcpc[2540]: Sending renew...
Sep 29 05:52:07 nas udhcpc[2540]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 29 05:52:18 nas noflushd[2197]: Disks spinning up after 1 minutes.
Sep 29 05:58:06 nas noflushd[2197]: Spinning down disks.
Sep 29 06:05:12 nas noflushd[2197]: Disks spinning up after 7 minutes.
Sep 29 06:05:30 nas RAIDiator: Backup finished. [Job 001]
Sep 29 06:05:30 nas RAIDiator: Backup finished. [Job 003]
Sep 29 06:06:04 nas RAIDiator: Backup finished. [Job 002]
Sep 29 06:25:13 nas syslogd 1.4.1#18: restart.
Sep 29 06:30:18 nas noflushd[2197]: Spinning down disks.
Sep 29 06:38:15 nas noflushd[2197]: Disks spinning up after 7 minutes.
Sep 29 06:45:52 nas noflushd[2197]: Spinning down disks.
Sep 29 06:52:13 nas noflushd[2197]: Disks spinning up after 6 minutes.
Sep 29 06:52:44 nas udhcpc[2540]: Sending renew...
Sep 29 06:52:44 nas udhcpc[2540]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 29 07:05:33 nas RAIDiator: Backup finished. [Job 002]
Sep 29 07:07:01 nas rsyncd[28071]: connect from miniduo1.home (192.168.0.103)
Sep 29 07:07:01 nas rsyncd[28071]: unknown module 'Projects' tried from miniduo1.home (192.168.0.103)
Sep 29 07:24:11 nas noflushd[2197]: Spinning down disks.
Sep 29 07:24:17 nas noflushd[2197]: Disks spinning up after 0 minutes.
Sep 29 07:29:15 nas noflushd[2197]: Spinning down disks.
Sep 29 07:33:26 nas noflushd[2197]: Disks spinning up after 4 minutes.
Sep 29 07:44:02 nas noflushd[2197]: Spinning down disks.
Sep 29 07:45:00 nas rsyncd[28821]: connect from miniduo1.home (192.168.0.103)
Sep 29 07:45:00 nas rsyncd[28821]: unknown module 'backup' tried from miniduo1.home (192.168.0.103)
Sep 29 07:52:44 nas udhcpc[2540]: Sending renew...
Sep 29 07:52:44 nas udhcpc[2540]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 29 08:05:13 nas noflushd[2197]: Disks spinning up after 21 minutes.
Sep 29 08:05:42 nas RAIDiator: Backup finished. [Job 003]
Sep 29 08:05:49 nas RAIDiator: Backup finished. [Job 002]
Sep 29 08:06:45 nas RAIDiator: Backup finished. [Job 004]
Sep 29 08:36:07 nas noflushd[2197]: Spinning down disks.
Sep 29 08:52:33 nas noflushd[2197]: Disks spinning up after 16 minutes.
Sep 29 08:52:44 nas udhcpc[2540]: Sending renew...
Sep 29 08:52:44 nas udhcpc[2540]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 29 08:58:04 nas noflushd[2197]: Spinning down disks.
Sep 29 09:05:11 nas noflushd[2197]: Disks spinning up after 7 minutes.
Sep 29 09:06:28 nas RAIDiator: Backup finished. [Job 002]
Sep 29 09:36:16 nas noflushd[2197]: Spinning down disks.
Sep 29 09:38:12 nas noflushd[2197]: Disks spinning up after 1 minutes.
Sep 29 09:44:25 nas noflushd[2197]: Spinning down disks.
Sep 29 09:47:11 nas noflushd[2197]: Disks spinning up after 2 minutes.
Sep 29 09:52:52 nas udhcpc[2540]: Sending renew...
Sep 29 09:52:52 nas udhcpc[2540]: Lease of 192.168.0.110 obtained, lease time 7200
Sep 29 09:57:59 nas noflushd[2197]: Spinning down disks.
Sep 29 10:03:30 nas noflushd[2197]: Disks spinning up after 5 minutes. - What brand and model disks and what disk firmware version?
mdgm wrote: What brand and model disks and what disk firmware version?
Disks: Seagate 2TB
Model: ST32000542AS
Firmware: CC34- Ok, the third, yes 50% of my 6 drives, failed within 10 days of the 4.2.22 upgrade for the exact same reason!!! IMHO, I think there is an issue with the 4.2.22 firmware as I have not had a failure in months and all of the sudden 3 purportedly fail back-to-back after the upgrade? Looking to see if I can downgrade from 4.2.22 because I have 2 drives in cross-ship with Seagate already - it will be interesting to see what their diagnosis is.
- Open a support case and post your case number.
- Hi,
I have also update my Pro 6 to 4.2.22 and since then every now and then (several times a day) the fans start blowing faster. This was not the case before the update.
Also, I got this message:
Reallocated sector count has increased in the last day. Disk 4: Previous count: 1 Current count: 2 Growing SMART errors indicate a disk that may fail soon. If the errors continue to increase, you should be prepared to replace the disk.
Since this error message, in combination with the 'activity' of the fans, I'm paying more attention to the NAS (I don't want the reallocated sector count growing). I'm not doing anything other then usual with the system.
I also must say, that since June this year, I have counted 6 errors in total over all disks now. I got them brand new installed since this June.
I'm having 6 Seagate Constellation ES 2TB's (ST2000NM0011) installed with dual redundancy. - Many computers don't track/report them, which in the case of reallocated sectors is not a good thing.
A disk with one reallocated sectors should be watched, but is not a big concern. Netgear recommends replacement at 50. Hopefully you have email alerts turned on.
The NAS doesn't (and really can't) create these errors, they are detected and tracked by the disk itself. - :) I'm not upgrading until this is sorted.
Also, upgrade will mess up my startup scripts or stuff/programs installed on my Ultra6? - The update worked fine for me. I haven't seen any disk failures since the update. In fact I haven't had any of my SeaGate 1.5TB disks fail in my Ultra 6 since I put them in over 2 years ago now.
What startup scripts etc.? If you installed add-ons the worst that should happen is that you need to re-install those add-ons via Frontview or maybe even SSH. If you installed custom stuff via SSH then depending what you did that may/may not be broken.
Best to ensure your backup is up to date (you should do this whether or not you do a firmware update) regularly particularly before doing a firmware update.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
