j5428
Members-
Posts
96 -
Joined
-
Last visited
Converted
-
Gender
Undisclosed
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
j5428's Achievements
Apprentice (3/14)
0
Reputation
-
Has anyone tried to get a Liebert GXT3 1500 UPS connected with a USB cable to work? When I try to start the Nut plugin I get the following: Writing nut config Updating permissions... Network UPS Tools - UPS driver controller 2.7.4.1 Network UPS Tools - Generic HID driver 0.55 (2.7.4.1) USB communication driver 0.43 This Liebert device (10af:0000) is not (or perhaps not yet) supported by usbhid-ups. Please make sure you have an up-to-date version of NUT. If this does not fix the problem, try running the driver with the '-x productid=0000' option. Please report your results to the NUT user's mailing list <[email protected]>. No matching HID UPS found Driver failed to start (exit status=1) Here is the ups.conf file I tried to add the suggestion in the error log to and it did not help. [ups] driver = Usbhid-ups -x productid=0000 port = 10af:0000 Thank you in advance for any help.
-
j5428 started following LSI SATA 8 port 6GB/sec card... , Parity Drive Current_Pending_Sector 1 , Kernal Panic out of memory Version 4.7 final and 1 other
-
Awesome!
-
Just received a G3 from Amazon. Key was blacklisted.
-
[XEN VM IMG] ArchVM <--- deprecated 01/07/2014
j5428 replied to ironicbadger's topic in VM Templates
After mounting the share: mount -t cifs //Tower/data /mnt/tmp -o guest,rw Trying to change the temp directory in sabnzbd to /mnt/tmp I get this error: 2014-02-04 17:52:31,893 ERROR: download_dir directory: /mnt/tmp error accessing Not sure if that is what I should put in sabnzb for the temporary folder. -
[XEN VM IMG] ArchVM <--- deprecated 01/07/2014
j5428 replied to ironicbadger's topic in VM Templates
Any idea about this? I've spent a few hours yesterday trying to figure it out... My NFS shares are exported as rw under unRAID, and autofs seems to mount them as rw also, but a simple touch isn't working... I went back to unRAID 5 for the time being. I must say, having unRAID6 uncrippled by the plugins I'm running under v5 was great. This whole virtualization thing is awesome I am having the same issue. Thanks for the awesome write-ups!!!!! -
Got it working... using the above thread.
-
I did find this post: http://lime-technology.com/forum/index.php?topic=27234.0 I am a little confused at this point and was looking for a setup from scratch on unraid.
-
What would be the easiest way to setup PXE booting Openelec from scratch on Unraid? I have read so many posts and tried so many different programs such as: http://www.vercot.com/~serva/ http://www.ultimatedeployment.org/ I can get them to boot .iso files ok but have had no luck importing OpenElec. Looks like people have this working from their unraid boxes. I run DHCP from my router w/tomato firmware. I would like to be able to PXE boot Openelec on a foxconn NT-330i which is ION based. Thanks for any help.
-
+1 for Easeus Todo Backup
-
I'm seeing $170 at amazon: http://www.amazon.com/Seagate-3-5-Inch-Internal-Surveillance-ST3000VX000/dp/B007JUFKLI/ref=sr_1_1?s=electronics&ie=UTF8&qid=1352123567&sr=1-1&keywords=ST3000VX000
-
Seagate SV35 Series ST3000VX000 3TB 7200 RPM 64MB Cache SATA 6.0Gb/s 3.5 Inch Internal Hard Drive -Bare Drive $139.99 $139.99 With Promo Code: EMCYTZT2482 Free Shipping! http://www.newegg.com/Product/Product.aspx?SID=p-yXhidHEeK_-6YqsUvgHA0_GbpF3_0_0_0&AID=10440897&PID=1225267&Item=N82E16822148901&Tpk=22-148-901&nm_mc=AFC-C8Junction&cm_mmc=AFC-C8Junction-_-cables-_-na-_-na I am wondering if this would be a good choice for a parity drive. 3yr warranty is a plus. They say it has lower read rates but higher write rates. http://www.seagate.com/internal-hard-drives/consumer-electronics/sv35/#tTabContentSpecifications
-
I finally got tired of my UnRAID machine sucking up all that power and sitting idle most of the time. So I upgraded the motherboard and processor to a ASRock 970 Extreme 4 and FX 6100 and installed ESXi. I tested version 5.0-rc8a using a M1015 and a few spare drives. I copied over several gigs of data overnight as a test last night and everything seems to be working fine. I have to get to work but I will update this post with Pics and specs later this week. I built a few ESXi whiteboxes before but I never had a motherboard/cpu combination that passthrough would actually work on. Thanks to Johnm and the ATLAS thread. I used it as a guide to get the UnRAID virtual machine part up and running.
-
Parity Drive Current_Pending_Sector 1
j5428 replied to j5428's topic in General Support (V5 and Older)
Thats what I was thinking also. RMA being sent out today. I wish hitachi would cross ship. -
Just looking for an opinion on the smart report for this drive. It is the parity drive and has disabled itself 2 times now for the current pending sector error. First time the parity rebuilt ok. Wondering whether to let it rebuild again or just rma the drive. I see there are 81 re-allocated sectors on the drive: === START OF INFORMATION SECTION === Device Model: Hitachi HDS722020ALA330 Serial Number: JK1101Y Firmware Version: JKAOA3EA User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Thu Jul 19 16:09:01 2012 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 General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (22330) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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. SCT capabilities: (0x003d) SCT Status 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 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 133 133 054 Pre-fail Offline - 102 3 Spin_Up_Time 0x0007 115 115 024 Pre-fail Always - 626 (Average 627) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 789 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 81 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 121 121 020 Pre-fail Offline - 35 9 Power_On_Hours 0x0012 099 099 000 Old_age Always - 8761 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 71 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1053 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 1053 194 Temperature_Celsius 0x0002 153 153 000 Old_age Always - 39 (Lifetime Min/Max 16/68) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 81 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 8 (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 8 occurred at disk power-on lifetime: 8760 hours (365 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 a1 66 72 3f 04 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 07 71 3f 40 00 40d+16:50:35.334 READ FPDMA QUEUED 60 00 00 07 6f 3f 40 00 40d+16:50:35.312 READ FPDMA QUEUED 60 00 00 07 6d 3f 40 00 40d+16:50:35.298 READ FPDMA QUEUED 60 00 00 07 6b 3f 40 00 40d+16:50:35.233 READ FPDMA QUEUED 60 00 00 07 69 3f 40 00 40d+16:50:35.221 READ FPDMA QUEUED Error 7 occurred at disk power-on lifetime: 8273 hours (344 days + 17 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 b6 99 78 3f 04 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 4f 78 3f 40 00 16d+04:58:44.479 READ FPDMA QUEUED 60 10 00 3f 78 3f 40 00 16d+04:58:44.447 READ FPDMA QUEUED 60 00 00 3f 76 3f 40 00 16d+04:58:44.433 READ FPDMA QUEUED 60 40 00 ff 75 3f 40 00 16d+04:58:44.430 READ FPDMA QUEUED 60 00 00 ff 73 3f 40 00 16d+04:58:44.416 READ FPDMA QUEUED Error 6 occurred at disk power-on lifetime: 6901 hours (287 days + 13 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 d9 3e 27 dd 07 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 17 27 dd 40 00 15d+08:54:05.629 READ FPDMA QUEUED 60 00 00 17 25 dd 40 00 15d+08:54:05.622 READ FPDMA QUEUED 60 00 00 17 23 dd 40 00 15d+08:54:05.615 READ FPDMA QUEUED 60 00 00 17 21 dd 40 00 15d+08:54:05.608 READ FPDMA QUEUED 61 00 00 17 1f dd 40 00 15d+08:54:05.562 WRITE FPDMA QUEUED Error 5 occurred at disk power-on lifetime: 4635 hours (193 days + 3 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 11 76 ad 52 0a Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 b8 00 cf ac 52 40 00 35d+10:10:24.192 READ FPDMA QUEUED 60 48 00 87 ab 52 40 00 35d+10:10:24.184 READ FPDMA QUEUED 60 08 00 7f aa 52 40 00 35d+10:10:24.176 READ FPDMA QUEUED 60 f8 00 87 a9 52 40 00 35d+10:10:24.167 READ FPDMA QUEUED 60 78 00 0f a9 52 40 00 35d+10:10:24.159 READ FPDMA QUEUED Error 4 occurred at disk power-on lifetime: 4212 hours (175 days + 12 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 3c 43 a7 52 0a Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 7f a5 52 40 00 27d+07:14:19.329 READ FPDMA QUEUED 60 e8 00 97 a4 52 40 00 27d+07:14:19.318 READ FPDMA QUEUED 60 18 00 7f a3 52 40 00 27d+07:14:19.307 READ FPDMA QUEUED 60 00 00 7f a1 52 40 00 27d+07:14:19.294 READ FPDMA QUEUED 60 00 00 7f 9f 52 40 00 27d+07:14:19.286 READ FPDMA QUEUED SMART 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 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.