May 10, 201115 yr Anyone know why my share turned into a READ ONLY? May 7 20:28:55 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 20:28:55 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 20:28:55 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 20:28:55 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 20:28:55 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 20:28:55 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 20:28:55 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 20:28:55 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 20:28:55 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 20:28:55 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 20:28:55 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 20:28:55 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 20:28:55 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 20:28:55 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 20:28:55 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 20:28:55 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 20:28:55 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 20:28:55 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 20:28:55 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 20:28:55 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 20:28:55 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 20:28:55 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 20:28:55 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 20:28:55 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 20:28:55 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 20:28:55 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 20:28:55 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:04:39 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:04:39 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:04:39 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:04:39 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:04:39 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:04:39 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:04:39 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:04:39 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:04:39 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:04:39 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:04:39 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:04:39 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:04:39 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:04:39 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:04:39 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:04:39 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:04:39 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:04:39 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:04:39 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:04:39 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:04:39 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:04:39 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:04:39 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:04:39 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:04:39 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:04:39 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:04:39 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:13:24 sun mountd[4997]: authenticated mount request from 192.168.1.107:743 for /mnt/user/movies (/mnt/user/movies) May 7 23:15:38 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:15:38 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:15:38 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:15:38 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:15:38 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:15:38 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:15:38 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:15:38 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:15:38 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:15:38 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:15:38 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:15:38 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:15:38 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:15:38 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:15:38 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:15:38 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:15:38 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:15:38 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:15:38 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:15:38 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:15:38 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:15:38 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:15:38 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:15:38 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 7 23:15:38 sun kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 48438 does not match to the expected one 1 (Minor Issues) May 7 23:15:38 sun kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 127702204. Fsck? (Errors) May 7 23:15:38 sun kernel: REISERFS error (device md4): zam-7001 reiserfs_find_entry: io error (Errors) May 8 06:47:07 sun sSMTP[4142]: Sent mail for root@localhost (221 2.0.0 omta22.westchester.pa.mail.comcast.net comcast closing connection) uid=0 username=root outbytes=708 May 9 06:47:08 sun sSMTP[8303]: Sent mail for root@localhost (221 2.0.0 omta15.westchester.pa.mail.comcast.net comcast closing connection) uid=0 username=root outbytes=708 May 9 13:27:12 sun mountd[4997]: authenticated mount request from 192.168.1.107:743 for /mnt/user/movies (/mnt/user/movies) May 9 16:37:27 sun mountd[4997]: authenticated mount request from 192.168.1.107:745 for /mnt/user/movies (/mnt/user/movies) May 9 16:53:09 sun mountd[4997]: authenticated mount request from 192.168.1.101:870 for /mnt/user/movies (/mnt/user/movies) May 9 22:06:36 sun shfs: shfs_unlink: unlink: /mnt/disk4/movies/sab/Deadliest.Catch.S07E02.720p.HDTV.x264-MOMENTUM/deadliest.catch.s07e02.720p.hdtv.x264-momentum.nfo (30) Read-only file system May 9 22:06:36 sun shfs: shfs_unlink: unlink: /mnt/disk4/movies/sab/Deadliest.Catch.S07E02.720p.HDTV.x264-MOMENTUM/deadliest.catch.s07e02.720p.hdtv.x264-momentum.sfv (30) Read-only file system May 9 22:06:36 sun shfs: shfs_unlink: unlink: /mnt/disk4/movies/sab/Deadliest.Catch.S07E02.720p.HDTV.x264-MOMENTUM/deadliest.catch.s07e02.720p.hdtv.x264-momentum.srr (30) Read-only file system May 9 22:06:36 sun shfs: shfs_rmdir: rmdir: /mnt/disk4/movies/sab/Deadliest.Catch.S07E02.720p.HDTV.x264-MOMENTUM (30) Read-only file system
May 10, 201115 yr probably because the disk you are trying to write to has been set read only because of file system corruption.
May 11, 201115 yr Author I have to do a file system check on every individual drive? I found "file system check" button using unmenu.
May 11, 201115 yr Author Well, here are my results. I have to ask...my system is not heavily used at all. How do these corruptions happen so easily? This scares me a little. Do I actually have to use that rebuild-tree option now? Replaying journal: Done. Reiserfs journal '/dev/md4' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. \/ 1 (of 9|/ 58 (of 109-/118 (of 170|block 125927290: The level of the node (46769) is not correct, (1) expected the problem in the internal node occured (125927290), whol/103 (of 109|/ 16 (of 86|block 125927289: The level of the node (53493) is not correct, (1) expected the problem in the internal node occured (125/ 2 (of 9-/ 70 (of 165|/ 91 (of 170\block 125927287: The level of the node (51397) is not correct, (1) expected the problem in the internal node occured (125927287), whol/ 71 (of 165|block 127699586: The level of the node (5388) is not correct, (2) expected the problem in the internal node occured (127699586), whol/ 4 (of 9// 46 (of 170// 71 (of 144|block 129728513: The level of the node (45018) is not correct, (1) expected the problem in the internal node occured (129728513), whol/ 47 (of 170/block 129728555: The level of the node (20511) is not correct, (2) expected the problem in the internal node occured (129728555), whol/ 9 (of 9// 95 (of 104-/ 96 (of 162-block 125927291: The level of the node (45035) is not correct, (1) expected the problem in the internal node occured (12finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 7 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Wed May 11 15:14:57 2011 ########### root@sun:/#
May 11, 201115 yr They usually happen due to power outage or system crash. Yes, run with rebuild tree.
May 12, 201115 yr Author I have a UPS attached, the system has never crashed. I've ran regular RAID systems for years without file corruption, I need my data intact. Here goes a rebuild. This is gonna take the whole array offline for a long time. Not such a good thing.
May 12, 201115 yr I have a UPS attached, the system has never crashed. I've ran regular RAID systems for years without file corruption, I need my data intact. Here goes a rebuild. This is gonna take the whole array offline for a long time. Not such a good thing. No, it is not necessary to take the whole array offline, just necessary to un-mount the one disk being fixed. The array itself must not be stopped, although you might need to stop samba in order to un-mount the disk, you can re-start samba once the disk is un-mounted. Joe L.
May 12, 201115 yr Author Ok, here is the crazy output of that resierfsck tree rebuild. I'm really lost here. This is a brand new array as many of you followed me as I put it together. It has ran just perfect until now and it seems I can't get out of this mess. I very seriously doubt there is a hardware problem. I've used this same system with a couple of different operating system, including Linux. The cables aren't touched and all were working fine. What's the problem here? I'm a little upset since this is the kind of stuff that I didn't want to happen when I had a choice between mega expensive RAID box or UNraid. Please help. I included the entire syslog also. ***Update...I just noticed that after doing the rebuild tree unRAID sees this drive as UNFORMATTED now. How can I go from having almost 1TB of data on it, do a simple reiserfsck on it and then there's no data at all on it? Please tell me if this is the best thing to do....format the drive and then let the system rebuild the entire disk via the parity information which does indicate is correct. God for bid. Looks like that may be my only option here. Will rebuild the filesystem (/dev/md4) tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Replaying journal: Done. Reiserfs journal '/dev/md4' in blocks [18..8211]: 0 transactions replayed ########### reiserfsck --rebuild-tree started at Wed May 11 21:18:44 2011 ########### Pass 0: ####### Pass 0 ####### Loading on-disk bitmap .. ok, 224287336 blocks marked used Skipping 23115 blocks (super block, journal, bitmaps) 224264221 blocks will be read 0%.... left 0, 31044 /secc 9959 directory entries were hashed with "r5" hash. "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 224264221 Leaves among those 223661 Objectids found 9942 Pass 1 (will try to insert 223661 leaves): ####### Pass 1 ####### Looking for allocable blocks .. finished 0%....20%.... left 139131, 1432 /sec The problem has occurred looks like a hardware problem (perhaps memory). Send us the bug report only if the second run dies at the same place with the same block number. build_the_tree: Nothing but leaves are expected. Block 125894519 - unknown Aborted root@sun:/# syslog-2011-05-12.txt
May 12, 201115 yr Author Here is the SMART report. I also noticed now I'm getting "errors" in the error column on unMENUS main screen. Is this actually a bad drive? smartctl -a -d ata /dev/sdl smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD2002FAEX-007BA0 Serial Number: WD-WMAY01288299 Firmware Version: 05.01D05 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: Exact ATA specification draft version not indicated Local Time is: Thu May 12 07:33:06 2011 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: (29280) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3037) 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 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 7366 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 13 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1351 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 12 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 5 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 7 194 Temperature_Celsius 0x0022 113 108 000 Old_age Always - 39 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 196 196 000 Old_age Always - 1465 198 Offline_Uncorrectable 0x0030 196 196 000 Old_age Offline - 1465 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 116 116 000 Old_age Offline - 16959 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% 1345 - # 2 Short offline Completed: read failure 90% 1313 1011424701 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.
May 12, 201115 yr Author Well this just got more confusing. It looked like I had no choice but to format the drive that was "bad". After the format nothing started to rebuild, but all drives have green dots next to them. I have so much data multi terabytes it is really hard to see if anything was lost, but I'm assuming yes since there was data on that drive. Where did it go? You'll notice disk4 in my list has nothing on it.
May 12, 201115 yr I'm really not sure what happened on your disk. You might have to try the reiserfsck commands again now that your formatted the disk. The most likely to work would be the --scan-whole-partition which should find any old files that were "left behind". Peter
May 12, 201115 yr Author I'm confused as heck. I thought the array would re-build itself after the format. Ouch.
May 12, 201115 yr No, it would not just rebuild on it's own. Your parity reflects a damaged file system so the rebuild would be useless anyways. Peter
May 13, 201115 yr Author I ran a parity check and it found 87 errors. I'm assuming it is because of my disappearing data. I have a drive that is empty now, a green ball, corrected parity now and really not sure what to do now. I'm still trying to determine if that /dev/md4 drive is actually defective or not. I re-ran reiserfsck --check and it came back with no corruptions found. Any suggestions where to go from here?
May 14, 201115 yr Author Ok, I did that and ended up with this. Also, if I go to the disk itself there is no data on it at all. It is a empty drive. I still can't tell if the drive is physically bad. Flushing..finished Objects without names 1105 Empty lost dirs removed 120 Dirs linked to /lost+found: 697 Dirs without stat data found 12 Files linked to /lost+found 408 Objects having used objectids: 377 files fixed 242 dirs fixed 135 Pass 4 - finisheddone 253038, 220 /sec Deleted unreachable items 16573 Flushing..finished Syncing..finished ########### reiserfsck finished at Sat May 14 07:55:51 2011 ###########
May 14, 201115 yr Author I do have to add... I pulled the drive out. Stuck it in a PC and installed Windows 7. Ran a sector by sector check using HDTune and everything was fine. Could someone check out my last post and see the results to my reiserfsck -S? Is it time to RMA this drive?
May 15, 201115 yr Can tell from those results whether the disk is bad. Run a pre-clear and see if it passes.
May 20, 201115 yr Author To be on the safe side I RMA'ed the drive and it is now doing a re-build now. Hopefully it was just a bad drive. I haven't had a bad drive in years and the drive was only 5 months old.
Archived
This topic is now archived and is closed to further replies.