January 17, 201016 yr One of my disc has gone broken. Instead to bye a new disc I have one data disk in my unRAID that's almost empty. I planning to move this data to another disk and use this as a "new" disk for my broken one. My parity data is OK How should I do that? EDIT when I had the disk it in the refrigerator for an hour, the it works for a short time //Peter
January 17, 201016 yr http://lime-technology.com/wiki/index.php?title=FAQ#How_do_I_remove_a_hard_disk_that_I_do_not_plan_on_replacing.3F
January 17, 201016 yr http://lime-technology.com/wiki/index.php?title=FAQ#How_do_I_remove_a_hard_disk_that_I_do_not_plan_on_replacing.3F It says "...if you use it when a drive has failed, you will likely lose the data on that drive" Meaning the procedure is not intended for the case when you have a failed drive and don't plan to replace it. It is only for the case when you reducing the number of drives while all of them are healthy.
January 17, 201016 yr Author So far I have reach 50% of the data to another disk, I have placed the disk outside the case and put a fan on top if the disk, so it's looks like I getting all the data from the disk :-) Then I going to preeclear it to see if the problem have disappeared :-) :-) but I think it not worth to use that disk longer. EDIT This was some info I saw in the logfile Jan 17 11:36:22 Tower kernel: sd 4:0:0:0: [sdc] 3907711 512-byte logical blocks: (2.00 GB/1.86 GiB) Jan 17 11:36:22 Tower kernel: sd 4:0:0:0: [sdc] Write Protect is off Jan 17 11:36:22 Tower kernel: sd 4:0:0:0: [sdc] Mode Sense: 45 00 00 08 Jan 17 11:36:22 Tower kernel: sd 4:0:0:0: [sdc] Assuming drive cache: write through Jan 17 11:36:22 Tower kernel: sd 4:0:0:0: [sdc] Assuming drive cache: write through Jan 17 11:36:22 Tower kernel: sdc: sdc1 Jan 17 11:36:22 Tower kernel: sd 4:0:0:0: [sdc] Assuming drive cache: write through Jan 17 11:36:22 Tower kernel: sd 4:0:0:0: [sdc] Attached SCSI removable disk Jan 17 11:36:22 Tower kernel: ata5: softreset failed (device not ready) Jan 17 11:36:22 Tower kernel: ata5: softreset failed (device not ready) Jan 17 11:36:22 Tower kernel: ata5: link is slow to respond, please be patient (ready=0) Jan 17 11:36:22 Tower kernel: ata5: softreset failed (device not ready) Jan 17 11:36:22 Tower kernel: ata5: limiting SATA link speed to 1.5 Gbps Jan 17 11:36:22 Tower kernel: ata5: softreset failed (device not ready) Jan 17 11:36:22 Tower kernel: ata5: reset failed, giving up
January 19, 201016 yr Author I manage to move all data from the disk, I have now run preclear one time and I have started the second preclear to verifies if some things change. One thing I saw in the logfile during first preclear was this. Jan 18 18:00:34 Tower kernel: ata5.00: exception Emask 0x50 SAct 0x1 SErr 0x280900 action 0x6 frozen Jan 18 18:00:34 Tower kernel: ata5.00: irq_stat 0x08000000, interface fatal error Jan 18 18:00:34 Tower kernel: ata5: SError: { UnrecovData HostInt 10B8B BadCRC } Jan 18 18:00:34 Tower kernel: ata5.00: cmd 60/00:00:00:fa:9f/02:00:3d:00:00/40 tag 0 ncq 262144 in Jan 18 18:00:34 Tower kernel: res 40/00:04:00:fa:9f/00:00:3d:00:00/40 Emask 0x50 (ATA bus error) Jan 18 18:00:34 Tower kernel: ata5.00: status: { DRDY } Jan 18 18:00:34 Tower kernel: ata5: hard resetting link Jan 18 18:00:34 Tower kernel: ata5: softreset failed (device not ready) Jan 18 18:00:34 Tower kernel: ata5: applying SB600 PMP SRST workaround and retrying Jan 18 18:00:34 Tower kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 18 18:00:34 Tower kernel: ata5.00: configured for UDMA/133 Jan 18 18:00:34 Tower kernel: ata5: EH complete I have attached some info from preclear,smarttest and som info from the logfile in atatched file Can someone see if the disc is bad ? I'm not sure if I can trust this disk regarding what have going on previous preeclear_1.txt
January 20, 201016 yr Author Hi I ahve now data from my second run of preeclear and smart information in the logfil. Can someone give some advise how my disk is feeling :-) Thanks Have a nice day Peter preclear_2.txt
January 21, 201016 yr Author The last preeclear test, I have attached a log file from the preclear and smart test. I would be very pleased if some one could give me som input how the disk are. Thanks and have a nice day Peter EDIT I tried to add this disk to the array, but the unraid doesn't like this disk see info from my syslog below. Jan 21 16:20:11 Tower emhttp: shcmd (40): /etc/rc.d/rc.samba stop | logger Jan 21 16:20:11 Tower emhttp: shcmd (41): /etc/rc.d/rc.nfsd stop | logger Jan 21 16:20:11 Tower mountd[1465]: Caught signal 15, un-registering and exiting. Jan 21 16:20:12 Tower kernel: nfsd: last server has exited, flushing export cache Jan 21 16:20:12 Tower emhttp: Spinning up all drives... Jan 21 16:20:12 Tower emhttp: shcmd (42): sync Jan 21 16:20:12 Tower kernel: mdcmd (31150): spinup 0 Jan 21 16:20:12 Tower kernel: mdcmd (31151): spinup 1 Jan 21 16:20:12 Tower kernel: mdcmd (31152): spinup 2 Jan 21 16:20:12 Tower kernel: mdcmd (31153): spinup 3 Jan 21 16:20:12 Tower kernel: mdcmd (31154): spinup 4 Jan 21 16:20:12 Tower kernel: mdcmd (31155): spinup 5 Jan 21 16:20:12 Tower kernel: mdcmd (31156): spinup 6 Jan 21 16:20:23 Tower emhttp: shcmd (43): umount /mnt/user >/dev/null 2>&1 Jan 21 16:20:23 Tower emhttp: shcmd (44): rmdir /mnt/user >/dev/null 2>&1 Jan 21 16:20:23 Tower emhttp: shcmd (45): umount /mnt/disk1 >/dev/null 2>&1 Jan 21 16:20:23 Tower emhttp: shcmd (46): rmdir /mnt/disk1 >/dev/null 2>&1 Jan 21 16:20:23 Tower emhttp: shcmd (47): umount /mnt/disk2 >/dev/null 2>&1 Jan 21 16:20:23 Tower emhttp: shcmd (48): rmdir /mnt/disk2 >/dev/null 2>&1 Jan 21 16:20:23 Tower emhttp: shcmd (49): umount /mnt/disk3 >/dev/null 2>&1 Jan 21 16:20:24 Tower emhttp: shcmd (50): rmdir /mnt/disk3 >/dev/null 2>&1 Jan 21 16:20:24 Tower emhttp: shcmd (51): umount /mnt/disk4 >/dev/null 2>&1 Jan 21 16:20:24 Tower emhttp: shcmd (52): rmdir /mnt/disk4 >/dev/null 2>&1 Jan 21 16:20:24 Tower emhttp: shcmd (53): umount /mnt/disk5 >/dev/null 2>&1 Jan 21 16:20:24 Tower emhttp: shcmd (54): rmdir /mnt/disk5 >/dev/null 2>&1 Jan 21 16:20:24 Tower emhttp: shcmd (55): umount /mnt/disk6 >/dev/null 2>&1 Jan 21 16:20:24 Tower emhttp: shcmd (56): rmdir /mnt/disk6 >/dev/null 2>&1 Jan 21 16:20:24 Tower kernel: mdcmd (31160): stop Jan 21 16:20:24 Tower kernel: md1: stopping Jan 21 16:20:24 Tower kernel: md2: stopping Jan 21 16:20:24 Tower kernel: md3: stopping Jan 21 16:20:24 Tower kernel: md4: stopping Jan 21 16:20:24 Tower kernel: md5: stopping Jan 21 16:20:24 Tower kernel: md6: stopping Jan 21 16:20:24 Tower emhttp: shcmd (57): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Jan 21 16:20:24 Tower emhttp: shcmd (58): cp /etc/exports- /etc/exports Jan 21 16:20:24 Tower emhttp: shcmd (59): /etc/rc.d/rc.samba start | logger Jan 21 16:20:24 Tower logger: Starting Samba: /usr/sbin/nmbd -D Jan 21 16:20:24 Tower logger: /usr/sbin/smbd -D Jan 21 16:20:24 Tower emhttp: shcmd (60): /etc/rc.d/rc.nfsd start | logger Jan 21 16:20:25 Tower spin_disks: User-shares not online... Jan 21 16:20:25 Tower spinup[3661]: spin_disks: User-shares not online... Jan 21 16:20:30 Tower emhttp: shcmd (61): rmmod md-mod >>/var/log/go 2>&1 Jan 21 16:20:30 Tower emhttp: shcmd (62): modprobe md-mod super=/boot/config/super.dat slots=8,96,8,112,8,0,8,48,8,64,8,80,8,16,8,32,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 >>/var/log/go 2>&1 Jan 21 16:20:30 Tower kernel: md: unRAID driver removed Jan 21 16:20:30 Tower kernel: md: unRAID driver 0.95.3 installed Jan 21 16:20:30 Tower kernel: md: import disk0: [8,96] (sdg) WDC WD15EADS-00S2B0 WD-WCAVY0802799 offset: 63 size: 1465138552 Jan 21 16:20:30 Tower kernel: md: import disk1: [8,112] (sdh) WDC WD15EADS-00R6B0 WD-WCAVY0164770 offset: 63 size: 1465138552 Jan 21 16:20:30 Tower kernel: md: import disk2: [8,0] (sda) WDC WD15EADS-00P8B0 WD-WMAVU0799207 offset: 63 size: 1465138552 Jan 21 16:20:30 Tower kernel: md: import disk3: [8,48] (sdd) WDC WD10EADS-00L5B1 WD-WCAU4D312833 offset: 63 size: 976762552 Jan 21 16:20:30 Tower kernel: md: import disk4: [8,64] (sde) WDC WD10EAVS-00D7B0 WD-WCAU40258662 offset: 63 size: 976762552 Jan 21 16:20:30 Tower kernel: md: import disk5: [8,80] (sdf) SAMSUNG HD103UJ S13PJ1KQ612827 offset: 63 size: 976761496 Jan 21 16:20:30 Tower kernel: md: import disk6: [8,16] (sdb) ST3500630AS 9QG0V4HA offset: 63 size: 488386552 Jan 21 16:20:30 Tower kernel: md: import disk7: [8,32] (sdc) WDC WD10EACS-00ZJB0 WD-WCASJ1110243 offset: 63 size: 976762552 Jan 21 16:20:30 Tower kernel: md: disk7 new disk Jan 21 16:20:30 Tower kernel: mdcmd (2): set md_num_stripes 1280 Jan 21 16:20:30 Tower kernel: mdcmd (3): set md_write_limit 768 Jan 21 16:20:30 Tower kernel: mdcmd (4): set md_sync_window 288 Jan 21 16:20:30 Tower kernel: mdcmd (5): set spinup_group 0 0 Jan 21 16:20:30 Tower kernel: mdcmd (6): set spinup_group 1 0 Jan 21 16:20:30 Tower kernel: mdcmd (7): set spinup_group 2 0 Jan 21 16:20:30 Tower kernel: mdcmd (: set spinup_group 3 0 Jan 21 16:20:30 Tower kernel: mdcmd (9): set spinup_group 4 0 Jan 21 16:20:30 Tower kernel: mdcmd (10): set spinup_group 5 0 Jan 21 16:20:30 Tower kernel: mdcmd (11): set spinup_group 6 0 Jan 21 16:20:30 Tower kernel: mdcmd (12): set spinup_group 7 0 Jan 21 16:20:46 Tower emhttp: disk_temperature: ioctl (smart_enable): Input/output error Jan 21 16:22:21 Tower last message repeated 2 times Jan 21 16:22:21 Tower emhttp: shcmd (63): /usr/local/sbin/set_ncq sdg 1 >/dev/null Jan 21 16:22:21 Tower emhttp: shcmd (64): /usr/local/sbin/set_ncq sdh 1 >/dev/null Jan 21 16:22:21 Tower emhttp: shcmd (65): /usr/local/sbin/set_ncq sda 1 >/dev/null Jan 21 16:22:21 Tower emhttp: shcmd (66): /usr/local/sbin/set_ncq sdd 1 >/dev/null Jan 21 16:22:21 Tower emhttp: shcmd (67): /usr/local/sbin/set_ncq sde 1 >/dev/null Jan 21 16:22:21 Tower emhttp: shcmd (68): /usr/local/sbin/set_ncq sdf 1 >/dev/null Jan 21 16:22:21 Tower emhttp: shcmd (69): /usr/local/sbin/set_ncq sdb 1 >/dev/null Jan 21 16:22:21 Tower emhttp: shcmd (70): /usr/local/sbin/set_ncq sdc 1 >/dev/null Jan 21 16:22:21 Tower emhttp: clearing disk7* ... Jan 21 16:22:21 Tower emhttp: writing mbr on disk 7 (/dev/sdc) Jan 21 16:22:21 Tower emhttp: re-reading /dev/sdc partition table Jan 21 16:22:21 Tower kernel: sdc: sdc1 Jan 21 16:22:52 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 21 16:22:52 Tower kernel: ata5.00: cmd b0/d8:00:01:4f:c2/00:00:00:00:00/00 tag 0 Jan 21 16:22:52 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 21 16:22:52 Tower kernel: ata5.00: status: { DRDY } Jan 21 16:22:52 Tower kernel: ata5: hard resetting link Jan 21 16:23:02 Tower kernel: ata5: softreset failed (device not ready) Jan 21 16:23:02 Tower kernel: ata5: hard resetting link Jan 21 16:23:12 Tower kernel: ata5: softreset failed (device not ready) Jan 21 16:23:12 Tower kernel: ata5: hard resetting link Jan 21 16:23:23 Tower kernel: ata5: link is slow to respond, please be patient (ready=0) Jan 21 16:23:47 Tower kernel: ata5: SATA link down (SStatus 0 SControl 300) Jan 21 16:23:48 Tower kernel: ata5: hard resetting link Jan 21 16:23:58 Tower kernel: ata5: softreset failed (device not ready) Jan 21 16:23:58 Tower kernel: ata5: hard resetting link Jan 21 16:24:08 Tower kernel: ata5: softreset failed (device not ready) Jan 21 16:24:08 Tower kernel: ata5: hard resetting link Jan 21 16:24:18 Tower kernel: ata5: link is slow to respond, please be patient (ready=0) Jan 21 16:24:43 Tower kernel: ata5: softreset failed (device not ready) Jan 21 16:24:43 Tower kernel: ata5: limiting SATA link speed to 1.5 Gbps Jan 21 16:24:43 Tower kernel: ata5: hard resetting link Jan 21 16:24:48 Tower kernel: ata5: softreset failed (device not ready) Jan 21 16:24:48 Tower kernel: ata5: reset failed, giving up Jan 21 16:24:48 Tower kernel: ata5.00: disabled Jan 21 16:24:48 Tower kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4080000 action 0xe frozen t4 Jan 21 16:24:48 Tower kernel: ata5: irq_stat 0x00000040, connection status changed Jan 21 16:24:48 Tower kernel: ata5: SError: { 10B8B DevExch } Jan 21 16:24:48 Tower kernel: ata5: hard resetting link Jan 21 16:24:58 Tower kernel: ata5: softreset failed (device not ready) Jan 21 16:24:58 Tower kernel: ata5: hard resetting link Jan 21 16:25:08 Tower kernel: ata5: softreset failed (device not ready) Jan 21 16:25:08 Tower kernel: ata5: hard resetting link Jan 21 16:25:19 Tower kernel: ata5: link is slow to respond, please be patient (ready=0) Jan 21 16:25:42 Tower kernel: ata5: softreset failed (device not ready) Jan 21 16:25:42 Tower kernel: ata5: applying SB600 PMP SRST workaround and retrying Jan 21 16:25:43 Tower kernel: ata5: softreset failed (device not ready) Jan 21 16:25:43 Tower kernel: ata5: limiting SATA link speed to 1.5 Gbps Jan 21 16:25:43 Tower kernel: ata5: hard resetting link Jan 21 16:25:48 Tower emhttp: disk_temperature: ioctl (smart_enable): Input/output error Jan 21 16:25:48 Tower kernel: ata5: softreset failed (device not ready) Jan 21 16:25:48 Tower kernel: ata5: reset failed, giving up Jan 21 16:25:48 Tower kernel: sd 5:0:0:0: rejecting I/O to offline device Jan 21 16:25:48 Tower kernel: ata5: EH complete Jan 21 16:25:48 Tower kernel: sd 5:0:0:0: [sdc] Unhandled error code Jan 21 16:25:48 Tower kernel: sd 5:0:0:0: [sdc] Result: hostbyte=0x01 driverbyte=0x00 Jan 21 16:25:48 Tower kernel: end_request: I/O error, dev sdc, sector 63 Jan 21 16:25:48 Tower kernel: Buffer I/O error on device sdc1, logical block 0 Jan 21 16:25:48 Tower kernel: Buffer I/O error on device sdc1, logical block 1 Jan 21 16:25:48 Tower kernel: Buffer I/O error on device sdc1, logical block 2 Jan 21 16:25:48 Tower kernel: Buffer I/O error on device sdc1, logical block 3 Jan 21 16:25:48 Tower kernel: Buffer I/O error on device sdc1, logical block 4 Jan 21 16:25:48 Tower kernel: Buffer I/O error on device sdc1, logical block 5 Jan 21 16:25:48 Tower kernel: Buffer I/O error on device sdc1, logical block 6 Jan 21 16:25:48 Tower kernel: Buffer I/O error on device sdc1, logical block 7 Jan 21 16:25:48 Tower kernel: Buffer I/O error on device sdc1, logical block 8 Jan 21 16:25:48 Tower kernel: Buffer I/O error on device sdc1, logical block 9 Jan 21 16:25:48 Tower kernel: sd 5:0:0:0: rejecting I/O to offline device Jan 21 16:25:48 Tower kernel: ata5.00: detaching (SCSI 5:0:0:0) Jan 21 16:25:48 Tower kernel: sd 5:0:0:0: [sdc] Synchronizing SCSI cache Jan 21 16:25:48 Tower kernel: mdcmd (20): start PROTECTED_EXPANSION Jan 21 16:25:48 Tower kernel: sd 5:0:0:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00 Jan 21 16:25:48 Tower kernel: sd 5:0:0:0: [sdc] Stopping disk Jan 21 16:25:48 Tower kernel: sd 5:0:0:0: [sdc] START_STOP FAILED Jan 21 16:25:48 Tower kernel: sd 5:0:0:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00 Jan 21 16:25:48 Tower kernel: md: do_run: lock_rdev error: -6 Jan 21 16:25:48 Tower emhttp: disk_spinning: open: No such file or directory Jan 21 16:25:48 Tower emhttp: disk_temperature: open: No such file or directory Jan 21 16:25:49 Tower emhttp: shcmd (71): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Jan 21 16:25:49 Tower emhttp: shcmd (72): cp /etc/exports- /etc/exports Jan 21 16:25:49 Tower emhttp: shcmd (73): killall -HUP smbd Jan 21 16:25:49 Tower emhttp: shcmd (74): /etc/rc.d/rc.nfsd restart | logger Jan 21 16:26:00 Tower emhttp: disk_spinning: open: No such file or directory Jan 21 16:26:00 Tower emhttp: disk_temperature: open: No such file or directory Jan 21 16:26:07 Tower emhttp: disk_spinning: open: No such file or directory Jan 21 16:26:07 Tower emhttp: disk_temperature: open: No such file or directory Jan 21 16:26:20 Tower emhttp: disk_spinning: open: No such file or directory Jan 21 16:26:20 Tower emhttp: disk_temperature: open: No such file or directory Jan 21 16:26:21 Tower emhttp: shcmd (75): /usr/local/sbin/set_ncq sdg 1 >/dev/null Jan 21 16:26:21 Tower emhttp: shcmd (76): /usr/local/sbin/set_ncq sdh 1 >/dev/null Jan 21 16:26:21 Tower emhttp: shcmd (77): /usr/local/sbin/set_ncq sda 1 >/dev/null Jan 21 16:26:21 Tower emhttp: shcmd (78): /usr/local/sbin/set_ncq sdd 1 >/dev/null Jan 21 16:26:21 Tower emhttp: shcmd (79): /usr/local/sbin/set_ncq sde 1 >/dev/null Jan 21 16:26:21 Tower emhttp: shcmd (80): /usr/local/sbin/set_ncq sdf 1 >/dev/null Jan 21 16:26:21 Tower emhttp: shcmd (81): /usr/local/sbin/set_ncq sdb 1 >/dev/null Jan 21 16:26:21 Tower emhttp: shcmd (82): /usr/local/sbin/set_ncq sdc 1 >/dev/null Jan 21 16:26:21 Tower emhttp: clearing ... Jan 21 16:26:21 Tower kernel: mdcmd (25): start PROTECTED_EXPANSION Jan 21 16:26:21 Tower kernel: md: do_run: lock_rdev error: -6 Jan 21 16:26:21 Tower emhttp: disk_spinning: open: No such file or directory Jan 21 16:26:21 Tower emhttp: disk_temperature: open: No such file or directory Jan 21 16:26:21 Tower emhttp: shcmd (83): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Jan 21 16:26:21 Tower emhttp: shcmd (84): cp /etc/exports- /etc/exports Jan 21 16:26:21 Tower emhttp: shcmd (85): killall -HUP smbd Jan 21 16:26:21 Tower emhttp: shcmd (86): /etc/rc.d/rc.nfsd restart | logger Jan 21 16:26:22 Tower emhttp: disk_spinning: open: No such file or directory Jan 21 16:26:22 Tower emhttp: disk_temperature: open: No such file or directory Jan 21 16:27:28 Tower emhttp: disk_spinning: open: No such file or directory Jan 21 16:27:28 Tower emhttp: disk_temperature: open: No such file or directory Jan 21 16:27:34 Tower emhttp: disk_spinning: open: No such file or directory Jan 21 16:27:34 Tower emhttp: disk_temperature: open: No such file or directory Jan 21 16:27:35 Tower emhttp: disk_spinning: open: No such file or directory Jan 21 16:27:35 Tower emhttp: disk_temperature: open: No such file or directory Jan 21 16:28:04 Tower emhttp: disk_spinning: open: No such file or directory Jan 21 16:28:04 Tower emhttp: disk_temperature: open: No such file or directory Jan 21 16:28:13 Tower emhttp: disk_spinning: open: No such file or directory Jan 21 16:28:13 Tower emhttp: disk_temperature: open: No such file or directory Jan 21 16:28:14 Tower emhttp: shcmd (87): /usr/local/sbin/set_ncq sdg 1 >/dev/null Jan 21 16:28:14 Tower emhttp: shcmd (88): /usr/local/sbin/set_ncq sdh 1 >/dev/null Jan 21 16:28:14 Tower emhttp: shcmd (89): /usr/local/sbin/set_ncq sda 1 >/dev/null Jan 21 16:28:14 Tower emhttp: shcmd (90): /usr/local/sbin/set_ncq sdd 1 >/dev/null Jan 21 16:28:14 Tower emhttp: shcmd (91): /usr/local/sbin/set_ncq sde 1 >/dev/null Jan 21 16:28:14 Tower emhttp: shcmd (92): /usr/local/sbin/set_ncq sdf 1 >/dev/null Jan 21 16:28:14 Tower emhttp: shcmd (93): /usr/local/sbin/set_ncq sdb 1 >/dev/null Jan 21 16:28:14 Tower emhttp: shcmd (94): /usr/local/sbin/set_ncq sdc 1 >/dev/null Jan 21 16:28:14 Tower emhttp: clearing ... Jan 21 16:28:14 Tower kernel: mdcmd (35): start PROTECTED_EXPANSION Jan 21 16:28:14 Tower kernel: md: do_run: lock_rdev error: -6 Jan 21 16:28:14 Tower emhttp: disk_spinning: open: No such file or directory Jan 21 16:28:14 Tower emhttp: disk_temperature: open: No such file or directory Jan 21 16:28:14 Tower emhttp: shcmd (95): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Jan 21 16:28:14 Tower emhttp: shcmd (96): cp /etc/exports- /etc/exports Jan 21 16:28:14 Tower emhttp: shcmd (97): killall -HUP smbd Jan 21 16:28:14 Tower emhttp: shcmd (98): /etc/rc.d/rc.nfsd restart | logger Jan 21 16:28:15 Tower emhttp: disk_spinning: open: No such file or directory Jan 21 16:28:15 Tower emhttp: disk_temperature: open: No such file or directory Jan 21 16:28:31 Tower unmenu[8377]: cat: /sys/block/sdc/stat: No such file or directory Jan 21 16:30:01 Tower last message repeated 5 times preclear_3.txt
March 9, 201016 yr Howdy and sorry for this being so late, perhaps too late to help. I don't see anything at all wrong with the drive, rather a problem with the interface (or connection) to the drive. All SMART reports and all indications from the drive itself are very good. The SMART reports do indicate that something bad happened recently, causing ABRT's, but there are *no* errors of note recorded, no apparent damage. I would suspect a previous power problem. There are several cases of BadCRC, which point to a bad SATA cable, so that is the first thing to replace (also the easiest!). In other cases (without a BadCRC), contact is lost with the drive. A loose cable or backplane is a possibility, but I suspect there may be power problems, either too many drives on a rail, or bad connectors, or a bad splitter, or just plain bad power from the PSU. In other words, while there may be an issue with the power circuits or the connectors on the drive, it looks most likely to be a problem with the connections to the drive (the SATA cable and/or the power supplied), and not the drive itself. Edit: by the way, all of the PreClears were completely successful, with no errors at all.
Archived
This topic is now archived and is closed to further replies.