joseph mota
Jul 12, 2014, 7:26:58 PM7/12/14
to al...@googlegroups.com
Fist off i wanted to say thank you for taking the time to make and upgrade this firmware. I've only been using it for a couple of days and i'm amazed at what it can do. Attached is the system err, Im not very familiar with linux or code so you might have to have some patience me with. The main problem is that my main 2Tdrive, my only real drive connected to the box is in RO mode. I tried to ForceFix and Set mount point to default and it didn't work. Then I did a small disk test and the results will be on the next post. Thank you so much in advance for any help.
sda2 Filesystem Details
tune2fs 1.41.14 (22-Dec-2010) Filesystem volume name: APPERTURE Last mounted on: /mnt/sda2 Filesystem UUID: f1d725c2-8034-421f-9f60-3da2defed59a Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: unsigned_directory_hash Default mount options: (none) Filesystem state: clean with errors Errors behavior: Continue Filesystem OS type: Linux Inode count: 122068992 Block count: 488246928 Reserved block count: 0 Free blocks: 480433099 Free inodes: 122058277 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 907 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Flex block group size: 16 Filesystem created: Fri Jul 11 00:04:57 2014 Last mount time: Sat Jul 12 12:40:12 2014 Last write time: Sat Jul 12 18:51:28 2014 Mount count: 3 Maximum mount count: 50 Last checked: Fri Jul 11 00:04:57 2014 Check interval: 7776000 (3 months) Next check after: Thu Oct 9 00:04:57 2014 Lifetime writes: 1804 MB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: 8eb7b7ea-e5a1-4fa5-9240-38b1451bdd3d Journal backup: inode blocks FS Error count: 13 First error time: Sat Jul 12 15:53:32 2014 First error function: ext4_wait_block_bitmap First error line #: 466 First error inode #: 0 First error block #: 0 Last error time: Sat Jul 12 17:12:39 2014 Last error function: __ext4_get_inode_loc Last error line #: 4027 Last error inode #: 119537665 Last error block #: 478150688
joseph mota
Jul 12, 2014, 7:29:51 PM7/12/14
to al...@googlegroups.com
Im on a DNS-323 Rev-B1 and on a DNS-325 rev-A1 boxes.
joseph mota
Jul 12, 2014, 7:35:22 PM7/12/14
to al...@googlegroups.com
The short health test. i don't believe it is the hard drive that has a problem:
smartctl 6.2 2013-07-26 r3841 [armv5tel-linux-3.10.32] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (AF) Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA3127315 LU WWN Device Id: 5 0014ee 65618abfb Firmware Version: 51.0AB51 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: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 2.6, 3.0 Gb/s Local Time is: Sat Jul 12 19:33:12 2014 EDT 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 SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 189 189 051 Pre-fail Always - 11078 3 Spin_Up_Time 0x0027 253 173 021 Pre-fail Always - 2266 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1279 5 Reallocated_Sector_Ct 0x0033 190 190 140 Pre-fail Always - 207 7 Seek_Error_Rate 0x002e 200 197 000 Old_age Always - 0 9 Power_On_Hours 0x0032 073 073 000 Old_age Always - 19798 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 152 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 80 193 Load_Cycle_Count 0x0032 125 125 000 Old_age Always - 225271 194 Temperature_Celsius 0x0022 112 104 000 Old_age Always - 38 196 Reallocated_Event_Count 0x0032 132 132 000 Old_age Always - 68 197 Current_Pending_Sector 0x0032 197 001 000 Old_age Always - 1014 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 30 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 183 181 000 Old_age Offline - 4605 SMART Error Log Version: 1 ATA Error Count: 48 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 48 occurred at disk power-on lifetime: 19708 hours (821 days + 4 hours) When the command that caused the error occurred, the device was doing SMART Offline or Self-test. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 00 00 00 00 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- e0 00 00 00 00 00 00 00 01:16:52.820 STANDBY IMMEDIATE Error 47 occurred at disk power-on lifetime: 19667 hours (819 days + 11 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 00 00 00 00 00 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 00 00 00 00 00 00 03:22:13.160 SET FEATURES [Set transfer mode] ec 00 00 00 00 00 00 00 03:22:13.149 IDENTIFY DEVICE Error 46 occurred at disk power-on lifetime: 19667 hours (819 days + 11 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 00 00 00 00 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- e0 00 00 00 00 00 00 00 02:51:25.586 STANDBY IMMEDIATE Error 45 occurred at disk power-on lifetime: 18616 hours (775 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 00 00 00 00 00 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 00 00 00 00 00 00 31d+00:49:22.711 SET FEATURES [Set transfer mode] ec 00 00 00 00 00 00 00 31d+00:49:22.700 IDENTIFY DEVICE Error 44 occurred at disk power-on lifetime: 18375 hours (765 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 61 00 00 00 00 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- e0 00 00 00 00 00 00 00 20d+23:51:54.018 STANDBY IMMEDIATE SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 19797 446166864
# 2 Short offline Completed: read failure 10% 19713 446166864
João Cardoso
Jul 12, 2014, 8:20:18 PM7/12/14
to al...@googlegroups.com
On Sunday, July 13, 2014 12:26:58 AM UTC+1, joseph mota wrote:
Fist off i wanted to say thank you for taking the time to make and upgrade this firmware. I've only been using it for a couple of days and i'm amazed at what it can do. Attached is the system err,
That log is only a summary of what appears at the Status page. The real log is the "System Log", "Kernel Log" and the "System Configuration", which also contains other box info.
Im not very familiar with linux or code so you might have to have some patience me with. The main problem is that my main 2Tdrive, my only real drive connected to the box is in RO mode. I tried to ForceFix and Set mount point to default and it didn't work.
It's a serious issue. Even ForceFix fails (and it should be used *sparingly*)
From the attached *short* log and the disk details output bellow I would say that the filesystem extends beyond the disk capacity (short read in general means that).
Short log: Error reading block 478150688 (Attempt to read block from filesystem resulted in short read)
Logged in the disk filesystem:
Block count: 488246928
Last error block #: 478150688
So the error occurs very near the disk end. Unless the disk is full of data that wouldn't be noticed.
Used the Disk Partitioner? Was the disk formated/partitioned under Alt-F? Using the Disk Wizard?
Then I saw the SMART log... the disk is not new, it has 27 months of poweron
9 Power_On_Hours 0x0032 073 073 000 Old_age Always - 19798
But the worst are the errors that follows (from the SMART log).
BACKUP NOW while you can. Errors might keep growing.
Then try attaching it to a linux computer (as a secondary disk) and see if it works.
Luck
PS-have you enabled any of the "Power saving" modes in the Disk Utilities? Settings a too low Spindown timeout? The errors in the SMART log seems related with STANDBY commands?
No a SMART expert, better search for help on their FAQ/Forum (after doing the BACKUP!)
BACKUP NOW while you can. Errors might keep growing.
Then try attaching it to a linux computer (as a secondary disk) and see if it works.
Luck
PS-have you enabled any of the "Power saving" modes in the Disk Utilities? Settings a too low Spindown timeout? The errors in the SMART log seems related with STANDBY commands?
Start_Stop_Count: 1279 # number of power-on/off Load_Cycle_Count: 225271 # this value seems to be too high!
No a SMART expert, better search for help on their FAQ/Forum (after doing the BACKUP!)
joseph mota
Jul 12, 2014, 8:44:50 PM7/12/14
to al...@googlegroups.com
The disk was on for 27 months on the nas when it had the original firmware. The disk was formatted with Alt-F and i have formatted again with Alt-f and started installing things. This is my third time formatting it with Alt-f. It works all the way up to the point where i install user accounts and then it goes into RO mode. Im going to try changing the standby power setting and see how it goes. But I think you might be right and the drive is on its way out. If thats so then i'm just going to use it a an internal desktop drive ad see how that goes.
João Cardoso
Jul 16, 2014, 6:12:53 PM7/16/14
to al...@googlegroups.com
On Sunday, July 13, 2014 1:44:50 AM UTC+1, joseph mota wrote:
The disk was on for 27 months on the nas when it had the original firmware. The disk was formatted with Alt-F and i have formatted again with Alt-f and started installing things. This is my third time formatting it with Alt-f. It works all the way up to the point where i install user accounts and then it goes into RO mode. Im going to try changing the standby power setting and see how it goes. But I think you might be right and the drive is on its way out. If thats so then i'm just going to use it a an internal desktop drive ad see how that goes.
As the error occurs near the disk's end, I would define a partition on that disk area and *not* use it, hopping that the errors don't start spreading "around".
I have done that once with a USB pen and it worked pretty well.
Start_Stop_Count: 1279 # number of power-on/off
Load_Cycle_Count: 225271 # this value seems to be too high!
The Load_Cycle_Count seems too high to me for a desktop disk (that's about 11 times per hour! What timeout did you set for the the Disk Spindown?).
If it was for a laptop or other mobile device, where it is expected that the disk goes to standby often, that would be OK, but not for a 3.5" desktop disk, where typically it goes to standby after 30/60 minutes.
Although the disk is not new, it's far from being old! My test disks have 46015 power-on hours, but only 8669 Load_Cycle_Count.
If it was for a laptop or other mobile device, where it is expected that the disk goes to standby often, that would be OK, but not for a 3.5" desktop disk, where typically it goes to standby after 30/60 minutes.
Although the disk is not new, it's far from being old! My test disks have 46015 power-on hours, but only 8669 Load_Cycle_Count.
Reply all
Reply to author
Forward
0 new messages