snoopy86 Posted January 8, 2015 Share Posted January 8, 2015 Hello, what is the solution to this error: Parity not installed. It just stopped working. I think the disk is still ok. Should i reformat partition drive and then add it back to the server to rebuild itself? Unraid 6.0-beta12. Quote Link to comment
trurl Posted January 8, 2015 Share Posted January 8, 2015 The parity drive doesn't have a file system, so formatting it is meaningless. Check all connections to the drive. Does your BIOS see the drive? Can unRAID see the drive? If so post a syslog and smart report. See this sticky Quote Link to comment
snoopy86 Posted January 14, 2015 Author Share Posted January 14, 2015 Syslog shows both drives: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1 Jan 14 22:08:49 Tower kernel: ata2.00: failed command: READ DMA Jan 14 22:08:49 Tower kernel: ata2.00: cmd c8/00:06:02:00:00/00:00:00:00:00/e0 tag 28 dma 3072 in Jan 14 22:08:49 Tower kernel: res 61/04:06:02:00:00/00:00:00:00:00/e0 Emask 0x1 (device error) Jan 14 22:08:49 Tower kernel: ata2.00: status: { DRDY DF ERR } Jan 14 22:08:49 Tower kernel: ata2.00: error: { ABRT } Jan 14 22:08:49 Tower logger: Scanning for Btrfs filesystems Jan 14 22:08:49 Tower emhttp: Device inventory: Jan 14 22:08:49 Tower emhttp: SAMSUNG_HD642JJ_S1AFJ1NQ901481 (sdb) 625131864 Jan 14 22:08:49 Tower emhttp: SAMSUNG_HD753LI_S1PHJ1NQ500163 (sdc) 732573527 Jan 14 22:08:49 Tower emhttp: shcmd (259): modprobe md-mod super=/boot/config/super.dat slots=2 |& logger Jan 14 22:08:49 Tower kernel: ata2.00: configured for UDMA/133 Jan 14 22:08:49 Tower kernel: sd 2:0:0:0: [sdc] Jan 14 22:08:49 Tower kernel: Result: hostbyte=0x00 driverbyte=0x08 Jan 14 22:08:49 Tower kernel: sd 2:0:0:0: [sdc] Jan 14 22:08:49 Tower kernel: Sense Key : 0x4 [current] [descriptor] Jan 14 22:08:49 Tower kernel: Descriptor sense data with sense descriptors (in hex): Jan 14 22:08:49 Tower kernel: 72 04 44 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Jan 14 22:08:49 Tower kernel: 00 00 00 02 Jan 14 22:08:49 Tower kernel: sd 2:0:0:0: [sdc] Jan 14 22:08:49 Tower kernel: ASC=0x44 ASCQ=0x0 Jan 14 22:08:49 Tower kernel: sd 2:0:0:0: [sdc] CDB: Jan 14 22:08:49 Tower kernel: cdb[0]=0x28: 28 00 00 00 00 02 00 00 06 00 Jan 14 22:08:49 Tower kernel: quiet_error: 96 callbacks suppressed Jan 14 22:08:49 Tower kernel: Buffer I/O error on device sdc, logical block 2 Jan 14 22:08:49 Tower kernel: Buffer I/O error on device sdc, logical block 3 Jan 14 22:08:49 Tower kernel: Buffer I/O error on device sdc, logical block 4 Jan 14 22:08:49 Tower kernel: Buffer I/O error on device sdc, logical block 5 Jan 14 22:08:49 Tower kernel: Buffer I/O error on device sdc, logical block 6 Jan 14 22:08:49 Tower kernel: Buffer I/O error on device sdc, logical block 7 Jan 14 22:08:49 Tower kernel: ata2: EH complete Jan 14 22:08:49 Tower kernel: md: unRAID driver 2.3.1 installed Jan 14 22:08:49 Tower kernel: mdcmd (1): import 0 0,0 Jan 14 22:08:49 Tower kernel: md: disk0 removed Jan 14 22:08:49 Tower emhttp: import 2 cache device: no device Jan 14 22:08:49 Tower emhttp: import flash device: sda Jan 14 22:08:49 Tower kernel: mdcmd (2): import 1 8,16 625131832 SAMSUNG_HD642JJ_S1AFJ1NQ901481 Jan 14 22:08:49 Tower kernel: md: import disk1: [8,16] (sdb) SAMSUNG_HD642JJ_S1AFJ1NQ901481 size: 625131832 Jan 14 22:08:49 Tower emhttp: read_line: client closed the connection Jan 14 22:08:49 Tower emhttp: read_line: client closed the connection Jan 14 22:08:49 Tower emhttp: read_line: client closed the connection Jan 14 22:08:49 Tower emhttp: read_line: client closed the connection Jan 14 22:08:49 Tower emhttp: read_line: client closed the connection I can choose the disk, but when i start array it removes it (picture1). Then i have it under unassigned devices(picture2). Smart report smartctl -a -d ata /dev/sdc smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.17.4-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: SAMSUNG SpinPoint F1 EG Device Model: SAMSUNG HD753LI Serial Number: S1PHJ1NQ500163 LU WWN Device Id: 5 0000f0 000051036 Firmware Version: 1AA01111 User Capacity: 750,155,292,160 bytes [750 GB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA/ATAPI-7, ATA8-ACS T13/1699-D revision 3b Local Time is: Wed Jan 14 22:42:15 2015 CET 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: (14971) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 250) minutes. Conveyance self-test routine recommended polling time: ( 26) minutes. SCT capabilities: (0x003f) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. 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 0x000f 100 096 051 Pre-fail Always - 3 3 Spin_Up_Time 0x0007 076 076 011 Pre-fail Always - 8090 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2115 5 Reallocated_Sector_Ct 0x0033 099 099 010 Pre-fail Always - 31 7 Seek_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 0 9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 42528 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 4 12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 652 13 Read_Soft_Error_Rate 0x000e 100 096 000 Old_age Always - 3 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 3 184 End-to-End_Error 0x0033 100 100 099 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 233 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 076 055 000 Old_age Always - 24 (Min/Max 23/26) 194 Temperature_Celsius 0x0022 076 054 000 Old_age Always - 24 (Min/Max 23/26) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 4718209 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x000a 099 099 000 Old_age Always - 4306 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 25 (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 25 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 -- -- -- -- -- -- -- 40 51 00 2b 38 00 e0 Error: UNC at LBA = 0x0000382b = 14379 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 60 20 38 00 e0 08 2d+01:53:42.710 READ DMA ef 10 02 00 00 00 a0 08 2d+01:53:42.710 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 2d+01:53:42.700 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 2d+01:53:42.700 SET FEATURES [set transfer mode] ef 10 02 00 00 00 a0 08 2d+01:53:42.700 SET FEATURES [Enable SATA feature] Error 24 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 -- -- -- -- -- -- -- 40 51 00 2b 38 00 e0 Error: UNC at LBA = 0x0000382b = 14379 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 60 20 38 00 e0 08 2d+01:53:40.260 READ DMA ef 10 02 00 00 00 a0 08 2d+01:53:40.260 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 2d+01:53:40.260 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 2d+01:53:40.260 SET FEATURES [set transfer mode] ef 10 02 00 00 00 a0 08 2d+01:53:40.260 SET FEATURES [Enable SATA feature] Error 23 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 -- -- -- -- -- -- -- 40 51 00 2b 38 00 e0 Error: UNC at LBA = 0x0000382b = 14379 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 60 20 38 00 e0 08 2d+01:53:37.820 READ DMA ef 10 02 00 00 00 a0 08 2d+01:53:37.820 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 2d+01:53:37.810 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 2d+01:53:37.810 SET FEATURES [set transfer mode] ef 10 02 00 00 00 a0 08 2d+01:53:37.810 SET FEATURES [Enable SATA feature] Error 22 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 -- -- -- -- -- -- -- 40 51 00 2b 38 00 e0 Error: UNC at LBA = 0x0000382b = 14379 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 60 20 38 00 e0 08 2d+01:53:35.380 READ DMA ef 10 02 00 00 00 a0 08 2d+01:53:35.380 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 2d+01:53:35.370 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 2d+01:53:35.370 SET FEATURES [set transfer mode] ef 10 02 00 00 00 a0 08 2d+01:53:35.370 SET FEATURES [Enable SATA feature] Error 21 occurred at disk power-on lifetime: 0 hours (0 days + 0 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 -- -- -- -- -- -- -- 40 51 00 2b 38 00 e0 Error: UNC at LBA = 0x0000382b = 14379 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 60 20 38 00 e0 08 2d+01:53:32.930 READ DMA ef 10 02 00 00 00 a0 08 2d+01:53:32.920 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 2d+01:53:32.920 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 2d+01:53:32.920 SET FEATURES [set transfer mode] ef 10 02 00 00 00 a0 08 2d+01:53:32.920 SET FEATURES [Enable SATA feature] SMART Self-test log structure revision number 0 Warning: ATA Specification requires self-test log structure revision number = 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run 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. Quote Link to comment
trurl Posted January 15, 2015 Share Posted January 15, 2015 Post a complete syslog Quote Link to comment
snoopy86 Posted January 15, 2015 Author Share Posted January 15, 2015 In my syslog which i got with (cp /var/log/syslog /boot/syslog.txt), there are only logs from transmission now like this: Jan 15 05:14:23 Tower transmission-daemon[22014]: Nodi.Reši.Boži?.2004.SLOSiNH.x264 Could not connect to tracker (announcer.c:999) Jan 15 05:14:23 Tower transmission-daemon[22014]: Quote Link to comment
trurl Posted January 15, 2015 Share Posted January 15, 2015 In my syslog which i got with (cp /var/log/syslog /boot/syslog.txt), there are only logs from transmission now like this: Jan 15 05:14:23 Tower transmission-daemon[22014]: Nodi.Reši.Boži?.2004.SLOSiNH.x264 Could not connect to tracker (announcer.c:999) Jan 15 05:14:23 Tower transmission-daemon[22014]: The log must have rotated. What do you get with ls -al /var/log Quote Link to comment
snoopy86 Posted January 15, 2015 Author Share Posted January 15, 2015 I get this. Quote Link to comment
trurl Posted January 15, 2015 Share Posted January 15, 2015 Get syslog.1 with cp /var/log/syslog.1 /boot/syslog.txt Zip and post Quote Link to comment
snoopy86 Posted January 15, 2015 Author Share Posted January 15, 2015 See the attachment. The newer syslog contains only logs from transmission. http://www.filedropper.com/syslog Quote Link to comment
trurl Posted January 15, 2015 Share Posted January 15, 2015 Run a preclear on it and if it passes try to add it again. Quote Link to comment
trurl Posted January 15, 2015 Share Posted January 15, 2015 I see from your post history that you are building a new server, so maybe you already have another drive ready to go. If so you could just put that in as parity, then see if you can get this one precleared. Quote Link to comment
snoopy86 Posted February 28, 2015 Author Share Posted February 28, 2015 Till now my parity was dead. Yesterday i upgraded to the lastest beta version and it started to work again. So strange but thumbs up anyway Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.