heyme

okay. since it is a 4TB drive, to wait for a rebuild just to format it again, then copy the data back to it will just take days. Probaby do a new config. Thanks for the help

If I rebuild onto that disk won't it rebuild the corrupted MD11 image on it? how do I format a disk once it is in the array?

Since my parity is now corrupted, how do i force it to rebuild based on good disks?

never mind figured it out - unassigned device plugin from community plugins. not showing up under there, but the XFS_Repair on it is still running.. see what happens. Thanks for the fast help. last file I have on the array is from september 2016 - almost a year of data on that drive. should of replaced it sooner.

yes that is what happened where do I get the UD Plugin?

running xfs_Repair on the drive - looks like it is trying to find a backup of the superblock. If I can recover that drive, how do I mount it to get data off of it?

inode identifier 0 mismatch on inode 7297414737 bad CRC for inode 7297414738 bad magic number 0x0 on inode 7297414738 bad version number 0x0 on inode 7297414738 inode identifier 0 mismatch on inode 7297414738 bad CRC for inode 7297414739 bad magic number 0x0 on inode 7297414739 bad version number 0x0 on inode 7297414739 inode identifier 0 mismatch on inode 7297414739 bad CRC for inode 7297414740 bad magic number 0x0 on inode 7297414740 bad version number 0x0 on inode 7297414740 inode identifier 0 mismatch on inode 7297414740 bad CRC for inode 7297414741 bad magic number 0x0 on inode 7297414741 bad version number 0x0 on inode 7297414741 inode identifier 0 mismatch on inode 7297414741 bad CRC for inode 7297414742 bad magic number 0x0 on inode 7297414742 bad version number 0x0 on inode 7297414742 inode identifier 0 mismatch on inode 7297414742 bad CRC for inode 7297414743 bad magic number 0x0 on inode 7297414743 bad version number 0x0 on inode 7297414743 inode identifier 0 mismatch on inode 7297414743 bad CRC for inode 7297414744 bad magic number 0x0 on inode 7297414744 bad version number 0x0 on inode 7297414744 inode identifier 0 mismatch on inode 7297414744 bad CRC for inode 7297414745 bad magic number 0x0 on inode 7297414745 bad version number 0x0 on inode 7297414745 inode identifier 0 mismatch on inode 7297414745 bad CRC for inode 7297414746 bad magic number 0x0 on inode 7297414746 bad version number 0x0 on inode 7297414746 inode identifier 0 mismatch on inode 7297414746 bad CRC for inode 7297414747 bad magic number 0x0 on inode 7297414747 bad version number 0x0 on inode 7297414747 inode identifier 0 mismatch on inode 7297414747 bad CRC for inode 7297414748 bad magic number 0x0 on inode 7297414748 bad version number 0x0 on inode 7297414748 inode identifier 0 mismatch on inode 7297414748 bad CRC for inode 7297414749 bad magic number 0x0 on inode 7297414749 bad version number 0x0 on inode 7297414749 inode identifier 0 mismatch on inode 7297414749 bad CRC for inode 7297414750 bad magic number 0x0 on inode 7297414750 bad version number 0x0 on inode 7297414750 inode identifier 0 mismatch on inode 7297414750 bad CRC for inode 7297414751 bad magic number 0x0 on inode 7297414751 bad version number 0x0 on inode 7297414751 inode identifier 0 mismatch on inode 7297414751 bad CRC for inode 7297414752 bad magic number 0x0 on inode 7297414752 bad version number 0x0 on inode 7297414752 inode identifier 0 mismatch on inode 7297414752 bad CRC for inode 7297414753 bad magic number 0x0 on inode 7297414753 bad version number 0x0 on inode 7297414753 inode identifier 0 mismatch on inode 7297414753 bad CRC for inode 7297414754 bad magic number 0x0 on inode 7297414754 bad version number 0x0 on inode 7297414754 inode identifier 0 mismatch on inode 7297414754 bad CRC for inode 7297414755 bad magic number 0x0 on inode 7297414755 bad version number 0x0 on inode 7297414755 inode identifier 0 mismatch on inode 7297414755 bad CRC for inode 7297414756 bad magic number 0x0 on inode 7297414756 bad version number 0x0 on inode 7297414756 inode identifier 0 mismatch on inode 7297414756 bad CRC for inode 7297414757 bad magic number 0x0 on inode 7297414757 bad version number 0x0 on inode 7297414757 inode identifier 0 mismatch on inode 7297414757 bad CRC for inode 7297414758 bad magic number 0x0 on inode 7297414758 bad version number 0x0 on inode 7297414758 inode identifier 0 mismatch on inode 7297414758 bad CRC for inode 7297414759 bad magic number 0x0 on inode 7297414759 bad version number 0x0 on inode 7297414759 inode identifier 0 mismatch on inode 7297414759 bad CRC for inode 7297414760 bad magic number 0x0 on inode 7297414760 bad version number 0x0 on inode 7297414760 inode identifier 0 mismatch on inode 7297414760 bad CRC for inode 7297414761 bad magic number 0x0 on inode 7297414761 bad version number 0x0 on inode 7297414761 inode identifier 0 mismatch on inode 7297414761 bad CRC for inode 7297414762 bad magic number 0x0 on inode 7297414762 bad version number 0x0 on inode 7297414762 inode identifier 0 mismatch on inode 7297414762 bad CRC for inode 7297414763 bad magic number 0x0 on inode 7297414763 bad version number 0x0 on inode 7297414763 inode identifier 0 mismatch on inode 7297414763 bad CRC for inode 7297414764 bad magic number 0x0 on inode 7297414764 bad version number 0x0 on inode 7297414764 inode identifier 0 mismatch on inode 7297414764 bad CRC for inode 7297414765 bad magic number 0x0 on inode 7297414765 bad version number 0x0 on inode 7297414765 inode identifier 0 mismatch on inode 7297414765 bad CRC for inode 7297414766 bad magic number 0x0 on inode 7297414766 bad version number 0x0 on inode 7297414766 inode identifier 0 mismatch on inode 7297414766 bad CRC for inode 7297414767 bad magic number 0x0 on inode 7297414767 bad version number 0x0 on inode 7297414767 inode identifier 0 mismatch on inode 7297414767 bad CRC for inode 7297414768 bad magic number 0x0 on inode 7297414768 bad version number 0x0 on inode 7297414768 inode identifier 0 mismatch on inode 7297414768 bad CRC for inode 7297414769 bad magic number 0x0 on inode 7297414769 bad version number 0x0 on inode 7297414769 inode identifier 0 mismatch on inode 7297414769 bad CRC for inode 7297414770 bad magic number 0x0 on inode 7297414770 bad version number 0x0 on inode 7297414770 inode identifier 0 mismatch on inode 7297414770 bad CRC for inode 7297414771 bad magic number 0x0 on inode 7297414771 bad version number 0x0 on inode 7297414771 inode identifier 0 mismatch on inode 7297414771 bad CRC for inode 7297414772 bad magic number 0x0 on inode 7297414772 bad version number 0x0 on inode 7297414772 inode identifier 0 mismatch on inode 7297414772 bad CRC for inode 7297414773 bad magic number 0x0 on inode 7297414773 bad version number 0x0 on inode 7297414773 inode identifier 0 mismatch on inode 7297414773 bad CRC for inode 7297414774 bad magic number 0x0 on inode 7297414774 bad version number 0x0 on inode 7297414774 inode identifier 0 mismatch on inode 7297414774 bad CRC for inode 7297414775 bad magic number 0x0 on inode 7297414775 bad version number 0x0 on inode 7297414775 inode identifier 0 mismatch on inode 7297414775 bad CRC for inode 7297414776 bad magic number 0x0 on inode 7297414776 bad version number 0x0 on inode 7297414776 inode identifier 0 mismatch on inode 7297414776 bad CRC for inode 7297414777 bad magic number 0x0 on inode 7297414777 bad version number 0x0 on inode 7297414777 inode identifier 0 mismatch on inode 7297414777 bad CRC for inode 7297414778 bad magic number 0x0 on inode 7297414778 bad version number 0x0 on inode 7297414778 inode identifier 0 mismatch on inode 7297414778 bad CRC for inode 7297414779 bad magic number 0x0 on inode 7297414779 bad version number 0x0 on inode 7297414779 inode identifier 0 mismatch on inode 7297414779 bad CRC for inode 7297414780 bad magic number 0x0 on inode 7297414780 bad version number 0x0 on inode 7297414780 inode identifier 0 mismatch on inode 7297414780 bad CRC for inode 7297414781 bad magic number 0x0 on inode 7297414781 bad version number 0x0 on inode 7297414781 inode identifier 0 mismatch on inode 7297414781 bad CRC for inode 7297414782 bad magic number 0x0 on inode 7297414782 bad version number 0x0 on inode 7297414782 inode identifier 0 mismatch on inode 7297414782 bad CRC for inode 7297414783 bad magic number 0x0 on inode 7297414783 bad version number 0x0 on inode 7297414783 inode identifier 0 mismatch on inode 7297414783 - process newly discovered inodes... 2abfd65e7ec0: Badness in key lookup (length) bp=(bno 0xe93a6fd0, len 8192 bytes) key=(bno 0xe93a6fd0, len 4096 bytes) 2abfd65e7ec0: Badness in key lookup (length) bp=(bno 0xe93a6fe0, len 8192 bytes) key=(bno 0xe93a6fe0, len 4096 bytes) 2abfd65e7ec0: Badness in key lookup (length) bp=(bno 0xe93a6ff0, len 8192 bytes) key=(bno 0xe93a6ff0, len 4096 bytes) 2abfd65e7ec0: Badness in key lookup (length) bp=(bno 0xe93a7000, len 8192 bytes) key=(bno 0xe93a7000, len 4096 bytes) Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 0 entry "logs" in shortform directory 2147483744 references free inode 4299589491 junking entry "logs" in directory inode 2147483744 corrected i8 count in directory 2147483744, was 3, now 2 entry "backups" in shortform directory 96 references non-existent inode 6443893447 junking entry "backups" in directory inode 96 data fork in ino 2147483748 claims dup extent, off - 0, start - 302323328, cnt 240 correcting nextents for inode 2147483748 bad data fork in inode 2147483748 cleared inode 2147483748 corrected i8 count in directory 96, was 1, now 0 entry "Series" in shortform directory 2147483751 references free inode 4298782819 junking entry "Series" in directory inode 2147483751 corrected i8 count in directory 2147483751, was 1, now 0 corrected directory 2147483751 size, was 49, now 37 bogus .. inode number (0) in directory inode 2147483751, clearing inode number corrected directory 96 size, was 64, now 48 bogus .. inode number (0) in directory inode 96, clearing inode number xfs_repair: dir2.c:1419: process_dir2: Assertion `(ino != mp->m_sb.sb_rootino && ino != *parent) || (ino == mp->m_sb.sb_rootino && (ino == *parent || need_root_dotdot == 1))' failed. Aborted root@Tower:~#

sorry this should be the correct copy - more or less the same thing: xfs_repair -v /dev/md11 Phase 1 - find and verify superblock... - block cache size set to 676816 entries Phase 2 - using internal log - zero log... Log inconsistent or not a log (last==0, first!=1) empty log check failed zero_log: cannot find log head/tail (xlog_find_tail=22) fatal error -- ERROR: The log head and/or tail cannot be discovered. Attempt to mount the filesystem to replay the log or use the -L option to destroy the log and attempt a repair. Should I try a repair on the physical disk - sdi or destory the log?

xfs_repair -v /dev/md11 -bash: root@Tower:~#: command not found - block cache size set to 676816 entries root@Tower:~# Phase 1 - find and verify superblock... Phase 2 - using internal log -bash: Phase: command not found - zero log... root@Tower:~# - block cache size set to 676816 entries Log inconsistent or not a log (last==0, first!=1) empty log check failed zero_log: cannot find log head/tail (xlog_find_tail=22) -bash: -: command not found fatal error -- ERROR: The log head and/or tail cannot be discovered. Attempt to mount the filesystem to replay the log or use the -L option to destroy the log and attempt a repair.

see attached tower-diagnostics-20170630-1507.zip

started a parity check. found 1000's of errors, check aborted by itself now one of my drives is unmountable and the files that are on it seem lost as I can't see them any more even if the array is online. Drive is still showing up in the list of drives on unraid so it appears it can still see it. XFS file system un 30 14:43:05 Tower kernel: XFS (md11): Mounting V5 Filesystem Jun 30 14:43:05 Tower kernel: XFS (md11): Log inconsistent or not a log (last==0, first!=1) Jun 30 14:43:05 Tower kernel: XFS (md11): empty log check failed Jun 30 14:43:05 Tower kernel: XFS (md11): log mount/recovery failed: error -22 Jun 30 14:43:05 Tower kernel: XFS (md11): log mount failed Jun 30 14:43:05 Tower root: mount: wrong fs type, bad option, bad superblock on /dev/md11, Jun 30 14:43:05 Tower root: missing codepage or helper program, or other error Jun 30 14:43:05 Tower root: Jun 30 14:43:05 Tower root: In some cases useful info is found in syslog - try Jun 30 14:43:05 Tower root: dmesg | tail or so. Jun 30 14:43:05 Tower emhttp: err: shcmd: shcmd (147): exit status: 32 Jun 30 14:43:05 Tower emhttp: mount error: No file system (32) Jun 30 14:43:05 Tower emhttp: shcmd (148): umount /mnt/disk11 |& logger Jun 30 14:43:05 Tower root: umount: /mnt/disk11: not mounted Jun 30 14:43:05 Tower emhttp: shcmd (149): rmdir /mnt/disk11 Jun 30 14:43:05 Tower emhttp: shcmd (150): sync Jun 30 14:43:06 Tower emhttp: shcmd (151): mkdir /mnt/user Jun 30 14:43:06 Tower emhttp: shcmd (152): /usr/local/sbin/shfs /mnt/user -disks 4094 -o noatime,big_writes,allow_other -o remember=330 |& logger Jun 30 14:43:06 Tower emhttp: shcmd (153): rm -f /boot/config/plugins/dynamix/mover.cro

nevermind was using the wrong docker container. Now using the SercetAgent one. Just nothing is being found in my Newznab provided, manual searches find the books.

Aug-2015 09:44:54 - INFO :: GR-SEARCH : Now searching GoodReads API with keyword: king 08-Aug-2015 09:44:54 - DEBUG :: GR-SEARCH : Searching for king at: http://www.goodreads.com/search.xml?q=king&key=ckvsiSDsuqh7omh74ZZ6Q 08-Aug-2015 09:44:54 - INFO :: GR-SEARCH : Found 20 results with keyword: king 08-Aug-2015 09:44:54 - INFO :: GR-SEARCH : The GoodReads API was hit 1 times for keyword king 08-Aug-2015 09:44:58 - INFO :: DBIMPORT : Now adding new author: Stephen King to database 08-Aug-2015 09:44:59 - DEBUG :: DBIMPORT : Searching for author with name: {'id': 'Stephen King'} 08-Aug-2015 09:44:59 - ERROR :: DBIMPORT : Error fetching authorid: undefined entity: line 51, column 36 Exception in thread DBIMPORT: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner self.run() File "/usr/lib/python2.7/threading.py", line 763, in run self.__target(*self.__args, **self.__kwargs) File "/opt/lazylibrarian/lazylibrarian/importer.py", line 31, in addAuthorToDB author = GR.find_author_id() File "/opt/lazylibrarian/lazylibrarian/gr.py", line 158, in find_author_id rootxml = sourcexml.getroot() UnboundLocalError: local variable 'sourcexml' referenced before assignment

Same problem can't add books or authors. Log file shows: 2015-08-07 07:17:17 ERROR Error fetching authorid: undefined entity: line 51, column 36 2015-08-07 07:17:15 INFO Now updating author: Stephen King 2015-08-07 07:17:03

Thanks Joe. All Set new version worked. I think that was the first drive I cleared running a V5.0 of unraid...

This has now happened on two drives. Both these drives have previously red balled so I was testing them. Odd that the smart data seems OK. Running on a supermicro 8 port data card on the unrair server. Also tried on a Ubuntu server with a esata dock. Guess they are good for an RMA.

Just ran preclear on a disk last night: This morning this was the output as well as a smart report: Any ideas why the failure? Disk Temperature: 30C, Elapsed Time: 11:32:51 =========================================================================== = unRAID server Pre-Clear disk /dev/sdh = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Temperature: 30C, Elapsed Time: 11:32:56 ============================================================================ == == SORRY: Disk /dev/sdh MBR could NOT be precleared == == out4= 00092 == out5= 00092 ============================================================================ 0000000 0000 0000 0000 0000 0000 0000 0000 0000 1+0 records in 1+0 records out * 512 bytes (512 B) copied0000700 0000 0000 0000 003f 0000 8871 e8e0 0000 , 0.000543096 s, 943 kB/s 0000720 0000 0000 0000 0000 0000 0000 0000 0000 * 0000760 0000 0000 0000 0000 0000 0000 0000 5c5c 0001000 root@Tower:/boot# smartctl -a /dev/sdh smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST2000DL003-9VT166 Serial Number: 5YD4L855 Firmware Version: CC32 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 Sep 5 03:34:01 2013 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: ( 612) 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: (0x30b7) SCT Status 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 118 099 006 Pre-fail Always - 177387640 3 Spin_Up_Time 0x0003 093 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 096 096 020 Old_age Always - 5001 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 072 060 030 Pre-fail Always - 12938664274 9 Power_On_Hours 0x0032 069 065 000 Old_age Always - 27563 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 121 183 Runtime_Bad_Block 0x0032 099 099 000 Old_age Always - 1 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 070 056 045 Old_age Always - 30 (0 4 32 29) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 098 098 000 Old_age Always - 5073 194 Temperature_Celsius 0x0022 030 044 000 Old_age Always - 30 (Min/Max 0/32768) 195 Hardware_ECC_Recovered 0x001a 033 011 000 Old_age Always - 177387640 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 - 34239479288413 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2105668327 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 1517667442 SMART Error Log Version: 1 No Errors Logged 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.

working on a script to reduce the size of some of my tv recordings. the first part works correct - creates a file listing all the files within the recording directory that I want to convert. If handbrake can't work with a file, the script works and ties the next one, however, as soon as I get a encode successful from handbrake the script stops and does not start the next file. any ideas. sourcedir="/recording/" destdir="/recording/output" cd "$sourcedir" log="./log.log" echo "" > filelist.lst find . -type f -name '*.mkv' | while read fname do # junk = fname echo $fname >> filelist.lst done echo "new Run" > log.log while read -r fname; do echo $fname >> log.log echo "Converting $fname to $destdir/${fname##./}" >> log.log junk="$destdir/${fname##./}" junk1="${junk%/*v}" echo $junk1 >> log.log /usr/bin/HandBrakeCLI --no-dvdnav -e x264 -a 1,1 -B 160,160 -6 dp12,auto -R Auto,Auto -D 0.0,0.0 -f mkv -4 --decomb --loose-anamorphic -m -x b-adapt=2:rc-looahead=5- --crop 0:0:0:0 -E copy:ac3,copy:aac -B 192 --audio-fallback ffac3 --large-file --vfr -q 16 -O -s 1 -i "$fname" -o "$destdir/${fname##./}" done<filelist.lst

All good. thanks Joe. Also upgraded to RC11 - just need to start reading about the new pluggin system... time for more fun!

Okay that makes a little more sense. The UPS has been complaining about that for about 6 months now, yet it still has 30mins runtime. I think it's tripping on battery age.

Unraid 4.7 Just had a failure yesterday on my very stable system (other then drive failures) Lost drive 7 and the Cache drive. Could not cleanly power down the array as something was trying to deal with the cache drive, but kept failing - syslog was over 2GB and growing fast. Powered off the array, replaced drive 7, removed the cache drive (don't have another one kicking around here) Powered back up. Unassigned the cache drive, started the array. Drive 7 is rebuilding. Lost all of my user shares. In the configuration they were all blank. all data and shares are on the disk. Tried recreating one of them (Media) creates the "file" in /mnt/user/Media, but no files. Tried restarting Samba no effect.. Any Ideas? SysLog attached since reboot and start of rebuild syslog-2013-02-04.txt

Okay so I had a disk redball on me in my production server - no problem - had a spare disk on hand swapped it in and rebuilt the data - all is good. Now I am playing with the failed disk on my windows box - running unraid under virtualbox (Development/test rig) and mapped the drive as a raw drive. Was hopping to run preclear on it without commiting this machine to that task for a couple days - but can't see the smart data through vbox - oh well... Started the array no parity, only drive in the array, 3101 writes then happen to the disk - though that was odd maybe reiserfs commits? proceed to look at the system log and notice that it wrote a new mbr on disk. All the data seems to be there can read directories etc. Just wondering why the new MBR? attached is the syslog syslog-2012-07-29.txt

Result: Tower login: root Linux 2.6.32.9-unRAID. root@Tower:~# ls /sys/module/ 8250/ i2c_core/ md_mod/ scsi_transport_sas/ usbcore/ acpi/ i2c_dev/ mousedev/ scst/ usbhid/ ahci/ i8042/ mvsas/ spurious/ usblp/ atiixp/ kernel/ nfs/ sunrpc/ vboxdrv/ ehci_hcd/ keyboard/ printk/ tcp_cubic/ vboxnetadp/ fuse/ libata/ processor/ thermal/ vboxnetflt/ hid/ libsas/ r8169/ uhci_hcd/ vt/ hid_apple/ lockd/ scsi_mod/ usb_storage/ xor/ root@Tower:~# /etc/sysconfig/lm_sensors -bash: /etc/sysconfig/lm_sensors: Permission denied root@Tower:~# etc/sysconfig/lm_sensors -bash: etc/sysconfig/lm_sensors: No such file or directory root@Tower:/etc/sysconfig# sensors No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are. root@Tower:/etc/sysconfig# contents of /etc/sysconfig/lm_sensors lm_sensors [b---] 0 L:[ 15+ 0 15/ 36] *(699 /1468b) 35 0x023 # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, # MA 02110-1301 USA. # # # See also the lm_sensors homepage at: # http://www.lm-sensors.org/ # # This file is used by /etc/init.d/lm_sensors and defines the modules to # be loaded/unloaded. This file is sourced into /etc/init.d/lm_sensors. # # The format of this file is a shell script that simply defines the modules # in order as normal variables with the special names: # MODULE_0, MODULE_1, MODULE_2, etc. # # List the modules that are to be loaded for your system # # Generated by sensors-detect on Mon Apr 2 08:19:44 2012 MODULE_0=it87 MODULE_1=k8temp

for both of the modprobe commands I get module not found

I am trying to get LM_Sensors working on my rig. Sensors-Detect returns Driver `it87' (should be inserted): Detects correctly: * ISA bus, address 0x290 Chip `ITE IT8712F Super IO Sensors' (confidence: 9) Driver `to-be-written' (should be inserted): Detects correctly: * Chip `AMD K10 thermal sensors' (confidence: 9) if I then run sensors I get no Sensors Found! Can anyone point in a direction here?