January 20, 201115 yr One drive has an orange circle, the other red. Both are showing as unformatted. They are being detected correctly in the BIOS and by unraid. I remember reading somwhere that there is a low level format I can do to try and bring these back online? At least one, then I can parity the other back I'm assuming? Here's a log, I hope I'm doing this right. Please excuse my newbie-ness: Jan 20 06:08:13 Flo emhttp: Start CIFS... Jan 20 06:08:13 Flo emhttp: shcmd (171): /etc/rc.d/rc.samba start | logger Jan 20 06:08:13 Flo logger: Starting Samba: /usr/sbin/nmbd -D Jan 20 06:08:13 Flo logger: /usr/sbin/smbd -D Jan 20 06:08:13 Flo emhttp: shcmd (172): /usr/local/emhttp/emhttp_event svcs_started Jan 20 06:08:13 Flo emhttp_event: svcs_started Jan 20 06:08:16 Flo emhttp: Start array... Jan 20 06:08:16 Flo emhttp: shcmd (173): /usr/local/sbin/set_ncq sdr 1 >/dev/null Jan 20 06:08:16 Flo emhttp: shcmd (174): /usr/local/sbin/set_ncq sdk 1 >/dev/null Jan 20 06:08:16 Flo emhttp: shcmd (175): /usr/local/sbin/set_ncq sdm 1 >/dev/null Jan 20 06:08:16 Flo emhttp: shcmd (176): /usr/local/sbin/set_ncq sdo 1 >/dev/null Jan 20 06:08:16 Flo emhttp: shcmd (177): /usr/local/sbin/set_ncq sdb 1 >/dev/null Jan 20 06:08:16 Flo emhttp: shcmd (178): /usr/local/sbin/set_ncq sdn 1 >/dev/null Jan 20 06:08:16 Flo emhttp: shcmd (179): /usr/local/sbin/set_ncq sdh 1 >/dev/null Jan 20 06:08:16 Flo emhttp: shcmd (180): /usr/local/sbin/set_ncq sdg 1 >/dev/null Jan 20 06:08:16 Flo emhttp: shcmd (181): /usr/local/sbin/set_ncq sdj 1 >/dev/null Jan 20 06:08:16 Flo emhttp: shcmd (182): /usr/local/sbin/set_ncq sdp 1 >/dev/null Jan 20 06:08:16 Flo emhttp: shcmd (183): /usr/local/sbin/set_ncq sdq 1 >/dev/null Jan 20 06:08:16 Flo emhttp: shcmd (184): /usr/local/sbin/set_ncq sdf 1 >/dev/null Jan 20 06:08:16 Flo emhttp: shcmd (185): /usr/local/sbin/set_ncq sdl 1 >/dev/null Jan 20 06:08:16 Flo emhttp: shcmd (186): /usr/local/sbin/set_ncq sdd 1 >/dev/null Jan 20 06:08:16 Flo emhttp: shcmd (187): /usr/local/sbin/set_ncq sde 1 >/dev/null Jan 20 06:08:16 Flo emhttp: shcmd (188): /usr/local/sbin/set_ncq sds 1 >/dev/null Jan 20 06:08:16 Flo emhttp: shcmd (189): /usr/local/sbin/set_ncq sdi 1 >/dev/null Jan 20 06:08:16 Flo emhttp: shcmd (190): /usr/local/sbin/set_ncq sdc 1 >/dev/null Jan 20 06:08:16 Flo kernel: mdcmd (100): start STOPPED Jan 20 06:08:16 Flo kernel: unraid: allocating 95160K for 1280 stripes (18 disks) Jan 20 06:08:16 Flo kernel: md1: running, size: 976762552 blocks Jan 20 06:08:16 Flo kernel: md2: running, size: 976762552 blocks Jan 20 06:08:16 Flo kernel: md3: running, size: 732574552 blocks Jan 20 06:08:16 Flo kernel: md4: running, size: 732574552 blocks Jan 20 06:08:16 Flo kernel: md5: running, size: 976762552 blocks Jan 20 06:08:16 Flo kernel: md6: running, size: 1465138552 blocks Jan 20 06:08:16 Flo kernel: md7: running, size: 488386552 blocks Jan 20 06:08:16 Flo kernel: md8: running, size: 1465138552 blocks Jan 20 06:08:16 Flo kernel: md9: running, size: 1465138552 blocks Jan 20 06:08:16 Flo kernel: md10: running, size: 1953514552 blocks Jan 20 06:08:16 Flo kernel: md11: running, size: 488386552 blocks Jan 20 06:08:16 Flo kernel: md12: running, size: 976762552 blocks Jan 20 06:08:16 Flo kernel: md13: running, size: 488386552 blocks Jan 20 06:08:16 Flo kernel: md14: running, size: 488386552 blocks Jan 20 06:08:16 Flo kernel: md15: running, size: 1953514552 blocks Jan 20 06:08:16 Flo kernel: md16: running, size: 1465138552 blocks Jan 20 06:08:16 Flo kernel: md17: running, size: 488386552 blocks Jan 20 06:08:16 Flo emhttp: shcmd (191): udevadm settle Jan 20 06:08:16 Flo emhttp: shcmd (192): /usr/local/emhttp/emhttp_event array_started Jan 20 06:08:16 Flo emhttp_event: array_started Jan 20 06:08:16 Flo emhttp: Mounting disks... Jan 20 06:08:16 Flo emhttp: shcmd (193): mkdir /mnt/disk2 Jan 20 06:08:16 Flo emhttp: shcmd (193): mkdir /mnt/disk3 Jan 20 06:08:16 Flo emhttp: shcmd (193): mkdir /mnt/disk1 Jan 20 06:08:16 Flo emhttp: shcmd (193): mkdir /mnt/disk7 Jan 20 06:08:16 Flo kernel: mdcmd (102): check Jan 20 06:08:16 Flo kernel: md: recovery thread woken up ... Jan 20 06:08:16 Flo emhttp: shcmd (193): mkdir /mnt/disk8 Jan 20 06:08:16 Flo emhttp: shcmd (193): mkdir /mnt/disk5 Jan 20 06:08:16 Flo emhttp: shcmd (193): mkdir /mnt/disk4 Jan 20 06:08:16 Flo emhttp: shcmd (193): mkdir /mnt/disk6 Jan 20 06:08:16 Flo emhttp: shcmd (194): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md3 /mnt/disk3 2>&1 | logger Jan 20 06:08:16 Flo emhttp: shcmd (195): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md7 /mnt/disk7 2>&1 | logger Jan 20 06:08:16 Flo emhttp: shcmd (194): mkdir /mnt/disk9 Jan 20 06:08:16 Flo emhttp: shcmd (196): mkdir /mnt/disk10 Jan 20 06:08:16 Flo emhttp: shcmd (197): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md2 /mnt/disk2 2>&1 | logger Jan 20 06:08:16 Flo emhttp: shcmd (197): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md5 /mnt/disk5 2>&1 | logger Jan 20 06:08:16 Flo emhttp: shcmd (197): mkdir /mnt/disk11 Jan 20 06:08:16 Flo emhttp: shcmd (199): mkdir /mnt/disk15 Jan 20 06:08:16 Flo emhttp: shcmd (199): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md4 /mnt/disk4 2>&1 | logger Jan 20 06:08:16 Flo emhttp: shcmd (198): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md8 /mnt/disk8 2>&1 | logger Jan 20 06:08:16 Flo emhttp: shcmd (197): mkdir /mnt/disk13 Jan 20 06:08:16 Flo emhttp: shcmd (201): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md6 /mnt/disk6 2>&1 | logger Jan 20 06:08:16 Flo emhttp: shcmd (199): mkdir /mnt/disk16 Jan 20 06:08:16 Flo emhttp: shcmd (201): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 2>&1 | logger Jan 20 06:08:16 Flo emhttp: shcmd (197): mkdir /mnt/disk12 Jan 20 06:08:16 Flo emhttp: shcmd (199): mkdir /mnt/disk14 Jan 20 06:08:16 Flo emhttp: shcmd (202): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md9 /mnt/disk9 2>&1 | logger Jan 20 06:08:16 Flo emhttp: shcmd (203): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md11 /mnt/disk11 2>&1 | logger Jan 20 06:08:16 Flo emhttp: shcmd (204): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md13 /mnt/disk13 2>&1 | logger Jan 20 06:08:16 Flo emhttp: shcmd (204): mkdir /mnt/disk17 Jan 20 06:08:16 Flo emhttp: shcmd (205): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md10 /mnt/disk10 2>&1 | logger Jan 20 06:08:16 Flo logger: mount: wrong fs type, bad option, bad superblock on /dev/md7, Jan 20 06:08:16 Flo logger: missing codepage or helper program, or other error Jan 20 06:08:16 Flo logger: In some cases useful info is found in syslog - try Jan 20 06:08:16 Flo logger: dmesg | tail or so Jan 20 06:08:16 Flo logger: Jan 20 06:08:16 Flo emhttp: shcmd (206): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md14 /mnt/disk14 2>&1 | logger Jan 20 06:08:16 Flo emhttp: _shcmd: shcmd (206): exit status: 32 Jan 20 06:08:16 Flo emhttp: disk7 mount error: 32 Jan 20 06:08:16 Flo emhttp: shcmd (207): rmdir /mnt/disk7 Jan 20 06:08:16 Flo emhttp: shcmd (208): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md15 /mnt/disk15 2>&1 | logger Jan 20 06:08:16 Flo kernel: REISERFS warning (device md7): sh-2006 read_super_block: bread failed (dev md7, block 2, size 4096) Jan 20 06:08:16 Flo kernel: REISERFS warning (device md7): sh-2006 read_super_block: bread failed (dev md7, block 16, size 4096) Jan 20 06:08:16 Flo kernel: REISERFS warning (device md7): sh-2021 reiserfs_fill_super: can not find reiserfs on md7 Jan 20 06:08:16 Flo emhttp: shcmd (209): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md16 /mnt/disk16 2>&1 | logger Jan 20 06:08:16 Flo emhttp: shcmd (210): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md17 /mnt/disk17 2>&1 | logger Jan 20 06:08:16 Flo emhttp: shcmd (211): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md12 /mnt/disk12 2>&1 | logger Jan 20 06:08:16 Flo logger: mount: wrong fs type, bad option, bad superblock on /dev/md9, Jan 20 06:08:16 Flo logger: missing codepage or helper program, or other error Jan 20 06:08:16 Flo logger: In some cases useful info is found in syslog - try Jan 20 06:08:16 Flo logger: dmesg | tail or so Jan 20 06:08:16 Flo logger: Jan 20 06:08:16 Flo emhttp: _shcmd: shcmd (212): exit status: 32 Jan 20 06:08:16 Flo emhttp: disk9 mount error: 32 Jan 20 06:08:16 Flo emhttp: shcmd (213): rmdir /mnt/disk9 Jan 20 06:08:16 Flo kernel: REISERFS warning (device md9): sh-2006 read_super_block: bread failed (dev md9, block 2, size 4096) Jan 20 06:08:16 Flo kernel: REISERFS warning (device md9): sh-2006 read_super_block: bread failed (dev md9, block 16, size 4096) Jan 20 06:08:16 Flo kernel: REISERFS warning (device md9): sh-2021 reiserfs_fill_super: can not find reiserfs on md9 Jan 20 06:08:16 Flo kernel: md: recovery thread has nothing to resync Jan 20 06:08:16 Flo kernel: REISERFS (device md17): found reiserfs format "3.6" with standard journal Jan 20 06:08:16 Flo kernel: REISERFS (device md17): using ordered data mode Jan 20 06:08:16 Flo kernel: REISERFS (device md16): found reiserfs format "3.6" with standard journal Jan 20 06:08:16 Flo kernel: REISERFS (device md16): using ordered data mode Jan 20 06:08:16 Flo kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal Jan 20 06:08:16 Flo kernel: REISERFS (device md3): using ordered data mode Jan 20 06:08:16 Flo kernel: REISERFS (device md11): found reiserfs format "3.6" with standard journal Jan 20 06:08:16 Flo kernel: REISERFS (device md11): using ordered data mode Jan 20 06:08:16 Flo kernel: REISERFS (device md10): found reiserfs format "3.6" with standard journal Jan 20 06:08:16 Flo kernel: REISERFS (device md10): using ordered data mode Jan 20 06:08:16 Flo kernel: REISERFS (device md6): found reiserfs format "3.6" with standard journal Jan 20 06:08:16 Flo kernel: REISERFS (device md6): using ordered data mode Jan 20 06:08:16 Flo kernel: REISERFS (device md14): found reiserfs format "3.6" with standard journal Jan 20 06:08:16 Flo kernel: REISERFS (device md14): using ordered data mode Jan 20 06:08:16 Flo kernel: REISERFS (device md8): found reiserfs format "3.6" with standard journal Jan 20 06:08:16 Flo kernel: REISERFS (device md8): using ordered data mode Jan 20 06:08:16 Flo kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal Jan 20 06:08:16 Flo kernel: REISERFS (device md2): using ordered data mode Jan 20 06:08:16 Flo kernel: REISERFS (device md4): found reiserfs format "3.6" with standard journal Jan 20 06:08:16 Flo kernel: REISERFS (device md4): using ordered data mode Jan 20 06:08:16 Flo kernel: REISERFS (device md12): found reiserfs format "3.6" with standard journal Jan 20 06:08:16 Flo kernel: REISERFS (device md12): using ordered data mode Jan 20 06:08:16 Flo kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal Jan 20 06:08:16 Flo kernel: REISERFS (device md1): using ordered data mode Jan 20 06:08:16 Flo kernel: REISERFS (device md5): found reiserfs format "3.6" with standard journal Jan 20 06:08:16 Flo kernel: REISERFS (device md5): using ordered data mode Jan 20 06:08:16 Flo kernel: REISERFS (device md13): found reiserfs format "3.6" with standard journal Jan 20 06:08:16 Flo kernel: REISERFS (device md13): using ordered data mode Jan 20 06:08:16 Flo kernel: REISERFS (device md15): found reiserfs format "3.6" with standard journal Jan 20 06:08:16 Flo kernel: REISERFS (device md15): using ordered data mode Jan 20 06:08:16 Flo kernel: REISERFS (device md15): journal params: device md15, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 20 06:08:16 Flo kernel: REISERFS (device md16): journal params: device md16, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 20 06:08:16 Flo kernel: REISERFS (device md16): checking transaction log (md16) Jan 20 06:08:16 Flo kernel: REISERFS (device md3): journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 20 06:08:16 Flo kernel: REISERFS (device md3): checking transaction log (md3) Jan 20 06:08:16 Flo kernel: REISERFS (device md11): journal params: device md11, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 20 06:08:16 Flo kernel: REISERFS (device md11): checking transaction log (md11) Jan 20 06:08:16 Flo kernel: REISERFS (device md4): journal params: device md4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 20 06:08:16 Flo kernel: REISERFS (device md4): checking transaction log (md4) Jan 20 06:08:16 Flo kernel: REISERFS (device md13): journal params: device md13, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 20 06:08:16 Flo kernel: REISERFS (device md13): checking transaction log (md13) Jan 20 06:08:16 Flo kernel: REISERFS (device md8): journal params: device md8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 20 06:08:16 Flo kernel: REISERFS (device md8): checking transaction log (md8) Jan 20 06:08:16 Flo kernel: REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 20 06:08:16 Flo kernel: REISERFS (device md2): checking transaction log (md2) Jan 20 06:08:16 Flo kernel: REISERFS (device md10): journal params: device md10, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 20 06:08:16 Flo kernel: REISERFS (device md10): checking transaction log (md10) Jan 20 06:08:16 Flo kernel: REISERFS (device md12): journal params: device md12, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 20 06:08:16 Flo kernel: REISERFS (device md12): checking transaction log (md12) Jan 20 06:08:16 Flo kernel: REISERFS (device md6): journal params: device md6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 20 06:08:16 Flo kernel: REISERFS (device md6): checking transaction log (md6) Jan 20 06:08:16 Flo kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 20 06:08:16 Flo kernel: REISERFS (device md1): checking transaction log (md1) Jan 20 06:08:16 Flo kernel: REISERFS (device md17): journal params: device md17, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 20 06:08:16 Flo kernel: REISERFS (device md17): checking transaction log (md17) Jan 20 06:08:16 Flo kernel: REISERFS (device md14): journal params: device md14, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 20 06:08:16 Flo kernel: REISERFS (device md14): checking transaction log (md14) Jan 20 06:08:16 Flo kernel: REISERFS (device md5): journal params: device md5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 20 06:08:16 Flo kernel: REISERFS (device md5): checking transaction log (md5) Jan 20 06:08:16 Flo kernel: REISERFS (device md15): checking transaction log (md15) Jan 20 06:08:16 Flo kernel: REISERFS (device md15): Using r5 hash to sort names Jan 20 06:08:16 Flo kernel: REISERFS (device md17): Using r5 hash to sort names Jan 20 06:08:16 Flo kernel: REISERFS (device md16): Using r5 hash to sort names Jan 20 06:08:16 Flo kernel: REISERFS (device md14): Using r5 hash to sort names Jan 20 06:08:16 Flo kernel: REISERFS (device md13): Using r5 hash to sort names Jan 20 06:08:16 Flo kernel: REISERFS (device md6): Using r5 hash to sort names Jan 20 06:08:16 Flo kernel: REISERFS (device md5): Using r5 hash to sort names Jan 20 06:08:16 Flo kernel: REISERFS (device md8): Using r5 hash to sort names Jan 20 06:08:16 Flo kernel: REISERFS (device md3): Using r5 hash to sort names Jan 20 06:08:16 Flo kernel: REISERFS (device md12): Using r5 hash to sort names Jan 20 06:08:16 Flo kernel: REISERFS (device md1): Using r5 hash to sort names Jan 20 06:08:16 Flo kernel: REISERFS (device md10): Using r5 hash to sort names Jan 20 06:08:16 Flo kernel: REISERFS (device md4): Using r5 hash to sort names Jan 20 06:08:16 Flo kernel: REISERFS (device md11): Using r5 hash to sort names Jan 20 06:08:16 Flo kernel: REISERFS (device md2): Using r5 hash to sort names Jan 20 06:08:17 Flo emhttp: shcmd (229): mkdir /mnt/user Jan 20 06:08:17 Flo emhttp: shcmd (230): /usr/local/sbin/shfs /mnt/user -o noatime,big_writes,allow_other,default_permissions Jan 20 06:08:17 Flo emhttp: shcmd (231): /usr/local/emhttp/emhttp_event disks_mounted Jan 20 06:08:17 Flo emhttp_event: disks_mounted Jan 20 06:08:17 Flo emhttp: shcmd (232): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Jan 20 06:08:17 Flo emhttp: shcmd (233): cp /etc/exports- /etc/exports Jan 20 06:08:17 Flo emhttp: Restart CIFS... Jan 20 06:08:17 Flo emhttp: shcmd (234): killall -HUP smbd Jan 20 06:08:17 Flo emhttp: shcmd (235): /usr/local/emhttp/emhttp_event svcs_restarted Jan 20 06:08:17 Flo emhttp_event: svcs_restarted
January 20, 201115 yr HI From your syslog there is a problem with the filesystem for disk 7 and 9 i would run the check disk procedure as descibed here http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems
January 20, 201115 yr Author Thanks for the reply. I am getting this when I try that (note, my server is now named Cooper instead of Flo): root@Cooper:~# cd root@Cooper:~# samba stop root@Cooper:~# umount /dev/md7 umount: /dev/md7: not mounted root@Cooper:~# reiserfsck --check /dev/md7 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md7 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (2): (Input/output error). Aborted root@Cooper:~# It's doing this for both disks 7 and 9. If I understand correctly, the array must be running to do this, correct?
January 20, 201115 yr Thanks for the reply. I am getting this when I try that (note, my server is now named Cooper instead of Flo): root@Cooper:~# cd root@Cooper:~# samba stop root@Cooper:~# umount /dev/md7 umount: /dev/md7: not mounted root@Cooper:~# reiserfsck --check /dev/md7 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md7 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (2): (Input/output error). Aborted root@Cooper:~# It's doing this for both disks 7 and 9. If I understand correctly, the array must be running to do this, correct? Yes, the array must be "started" Joe L.
January 20, 201115 yr Author So I ran this on a "green" disk (/dev/md1) just to see if it was working. And sure enough it scanned just fine. The thing is I am noticing that the problem occurs before I even run reiserfsck, but rather on the umount. Notice how when I try "umount /dev/md7" it says "umount: /dev/md7: not mounted" Might be an indication of what's going on? EDIT: On second thought I guess this is just because unraid is having a problem with the disk, so it never tried to mount it in the first place.
January 20, 201115 yr EDIT: On second thought I guess this is just because unraid is having a problem with the disk, so it never tried to mount it in the first place. Since it was not mounted, you could not un-mount it. It was not mounted because it was corrupted, and that is what you are attempting to fix. Joe L.
January 20, 201115 yr Do the drives respond at all? Can you type smartctl -d ata -a /dev/sdX where sdX = the device for disk7 and disk9. You can try power cycling. (power down power back up, see if the disk will respond) Then try the reiserfsck again. What specific brand/model power supply are you using? You have a lot of disks and it might be stressing even a large supply. Could you have a loose or poorly connected power splitter feeding those two disks?
January 20, 201115 yr Author Thanks again for the replies. root@Cooper:~# smartctl -d ata -a /dev/sd7 smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Smartctl open device: /dev/sd7 failed: No such file or directory root@Cooper:~# It's reporting this for both drives (7 and 9) The power supply is a 750watt corsair, and this build is brand new in an RPC-4220. All power and SAS connections are very secure. I've power cycled several times, and no change. If the drives aren't responding at all, why are they detected properly in the BIOS, and unraid sees them as unformatted? I see activity on them when I refresh the main page in the web admin as well. This is progress as the setup I had these drives in before didn't even do that, which I attributed to faulty cables / cheap sata controllers and mobo. This new build is copied directly from the wiki. EDIT: Just tried this, which came up with a different error. Not sure if this means anything. root@Cooper:~# smartctl -d ata -a /dev/md7 smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
January 20, 201115 yr Thanks again for the replies. It's reporting this for both drives (7 and 9) The power supply is a 750watt corsair, and this build is brand new in an RPC-4220. All power and SAS connections are very secure. I've power cycled several times, and no change. If by power cycling you are rebooting the machine try to shut it down fully, pull the power plug on the back, and start it back up. It can actually help sometimes. If the drives aren't responding at all, why are they detected properly in the BIOS, and unraid sees them as unformatted? unRAID sees it as unformatted because it is not mounted and it is detect in the BIOS because the BIOS does not give a rats behind what is on the disk, it only cares that it is there and it can send a signal to it.
January 20, 201115 yr Author If by power cycling you are rebooting the machine try to shut it down fully, pull the power plug on the back, and start it back up. It can actually help sometimes. Trying that now.
January 20, 201115 yr Author Nope, still the same. Here is a full syslog that might shed some light? Thanks again for your help! syslog.txt
January 20, 201115 yr Thanks again for the replies. root@Cooper:~# smartctl -d ata -a /dev/sd7 smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Smartctl open device: /dev/sd7 failed: No such file or directory root@Cooper:~# It's reporting this for both drives (7 and 9) True... and is exactly why I asked the questions I did. It is very rare for two disks to fail exactly the same way at the same time. It is EASY if they both lose power at the same time. If that server has a backplane, are you connected to ALL the power connectors behind the disks? The power supply is a 750watt corsair,If it is the one with the single rail, it should be fine... and this build is brand new in an RPC-4220. All power and SAS connections are very secure. I've power cycled several times, and no change. If the drives aren't responding at all, why are they detected properly in the BIOS, and unraid sees them as unformatted? I see activity on them when I refresh the main page in the web admin as well. This is progress as the setup I had these drives in before didn't even do that, which I attributed to faulty cables / cheap sata controllers and mobo. This new build is copied directly from the wiki. EDIT: Just tried this, which came up with a different error. Not sure if this means anything. root@Cooper:~# smartctl -d ata -a /dev/md7 smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. It indicates you did not follow instructions. I asked you run it on the /dev/sdX device, not the /dev/mdX device. Since you did not supply a full syslog, thinking your segment at the end was enough, I cannot give you more specific help on which native "/dev/sd?" devices correspond to disk7 and disk9. If this is a brand new server, did you try other slots in the array for those disks? Are these EARS drives? They frequently lock up and refuse to do anything if you change the jumper setting on the back. Are they? Did you? Joe L.
January 20, 201115 yr I looked back at an earlier post where you admitted that you NEVER formatted those two drives. If they were never formatted, they will never be able to be mounted. Did you, in the interim, format those drives successfully and get them on line? Joe L.
January 20, 201115 yr Author Do the drives respond at all? Can you type smartctl -d ata -a /dev/sdX where sdX = the device for disk7 and disk9. You can try power cycling. (power down power back up, see if the disk will respond) Then try the reiserfsck again. What specific brand/model power supply are you using? You have a lot of disks and it might be stressing even a large supply. Could you have a loose or poorly connected power splitter feeding those two disks? Okay, I wasn't doing that command correctly. Apparently sdX isn't a numeric value, but rather sdG and sdP for the drives. Sorry, I am totally new to all of this This is what I'm getting now: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Alle n Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Second Generation Serial ATA family Device Model: WDC WD5000AAJS-22TKA0 Serial Number: WD-WCAPW5449900 Firmware Version: 12.01C01 User Capacity: 500,107,862,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Thu Jan 20 10:09:39 2011 PST 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: (12000) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off supp ort. 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: ( 150) minutes. Conveyance self-test routine recommended polling time: ( 6) minutes. SCT capabilities: (0x303f) 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 0x000f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0003 178 176 021 Pre-fail Always - 6075 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1894 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x000e 200 200 051 Old_age Always - 0 9 Power_On_Hours 0x0032 074 074 000 Old_age Always - 19155 10 Spin_Retry_Count 0x0012 100 100 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0012 100 100 051 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 279 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 199 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1896 194 Temperature_Celsius 0x0022 108 078 000 Old_age Always - 42 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 2464 200 Multi_Zone_Error_Rate 0x0008 200 200 051 Old_age Offline - 0 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. And: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD15EADS-00S2B0 Serial Number: WD-WCAVY0907597 Firmware Version: 04.05G04 User Capacity: 1,500,301,910,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 Jan 20 10:14:11 2011 PST 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: (28860) 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: (0x303f) 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 - 2 3 Spin_Up_Time 0x0027 142 139 021 Pre-fail Always - 9866 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 989 5 Reallocated_Sector_Ct 0x0033 199 199 140 Pre-fail Always - 3 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 087 087 000 Old_age Always - 9689 10 Spin_Retry_Count 0x0032 100 100 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 - 97 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 42 193 Load_Cycle_Count 0x0032 182 182 000 Old_age Always - 54313 194 Temperature_Celsius 0x0022 116 074 000 Old_age Always - 36 196 Reallocated_Event_Count 0x0032 198 198 000 Old_age Always - 2 197 Current_Pending_Sector 0x0032 195 195 000 Old_age Always - 1311 198 Offline_Uncorrectable 0x0030 195 195 000 Old_age Offline - 1301 199 UDMA_CRC_Error_Count 0x0032 200 192 000 Old_age Always - 29512 200 Multi_Zone_Error_Rate 0x0008 001 001 000 Old_age Offline - 114056 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.
January 20, 201115 yr Author I looked back at an earlier post where you admitted that you NEVER formatted those two drives. If they were never formatted, they will never be able to be mounted. Did you, in the interim, format those drives successfully and get them on line? Joe L. Both of these drives used to be part of the array, and working. But due to a move and faulty connections (I believe) my futile attempts to bring the array back online may have been more destructive than good. (Including upgrading to 5.0 beta 2) I'm almost certain it is not a power issue. Again thank you for the help and patience with my idiocy!
January 20, 201115 yr The second drive you post the smart report for has a lot of current pending sectors for allocation. There were 3 that were relocatted already. The second drive should be RMA'ed. The first drive appears to be OK. Also, as JoeL. mentioned you should have both molex power supply connectors connected to the backplane of the 4220. That case will supposedly work with only one power connection to each backplane but I found it to be less stable that way.
January 20, 201115 yr According to your syslog, your disks are: Jan 20 10:05:54 Cooper kernel: md: import disk0: [65,16] (sdr) ST32000542AS 5XW1XKYR offset: 63 size: 1953514552 Jan 20 10:05:54 Cooper kernel: md: import disk1: [8,160] (sdk) Hitachi HDT72101 STF604MR2903TP offset: 63 size: 976762552 Jan 20 10:05:54 Cooper kernel: md: import disk2: [8,192] (sdm) Hitachi HDT72101 STF604MR2B34XP offset: 63 size: 976762552 Jan 20 10:05:54 Cooper kernel: md: import disk3: [8,224] (sdo) ST3750640AS 3QD0QBLC offset: 63 size: 732574552 Jan 20 10:05:54 Cooper kernel: md: import disk4: [8,16] (sdb) ST3750640AS 3QD0Q9TR offset: 63 size: 732574552 Jan 20 10:05:54 Cooper kernel: md: import disk5: [8,208] (sdn) WDC WD10EACS-00D WD-WCAU45550258 offset: 63 size: 976762552 Jan 20 10:05:54 Cooper kernel: md: import disk6: [8,112] (sdh) WDC WD15EARS-00Z WD-WCAVU0452333 offset: 63 size: 1465138552 Jan 20 10:05:54 Cooper kernel: md: import disk7: [8,96] (sdg) WDC WD5000AAJS-2 WD-WCAPW5449900 offset: 63 size: 488386552 Jan 20 10:05:54 Cooper kernel: md: import disk8: [8,144] (sdj) WDC WD15EARS-00Z WD-WMAVU3012356 offset: 63 size: 1465138552 Jan 20 10:05:54 Cooper kernel: md: import disk9: [8,240] (sdp) WDC WD15EADS-00S WD-WCAVY0907597 offset: 63 size: 1465138552 Jan 20 10:05:54 Cooper kernel: md: import disk10: [65,0] (sdq) ST32000542AS 5XW1XP9F offset: 63 size: 1953514552 Jan 20 10:05:54 Cooper kernel: md: import disk11: [8,80] (sdf) Maxtor 6H500F0 H808PWZH offset: 63 size: 488386552 Jan 20 10:05:54 Cooper kernel: md: import disk12: [8,176] (sdl) ST31000528AS 6VP25KSJ offset: 63 size: 976762552 Jan 20 10:05:54 Cooper kernel: md: import disk13: [8,48] (sdd) WDC WD5000AAKS-2 WD-WCAS81618822 offset: 63 size: 488386552 Jan 20 10:05:54 Cooper kernel: md: import disk14: [8,64] (sde) WDC WD5000AAJS-2 WD-WCAPW5639136 offset: 63 size: 488386552 Jan 20 10:05:54 Cooper kernel: md: import disk15: [65,32] (sds) ST32000542AS 5XW16QBX offset: 63 size: 1953514552 Jan 20 10:05:54 Cooper kernel: md: import disk16: [8,128] (sdi) WDC WD15EADS-00S WD-WCAVY0776356 offset: 63 size: 1465138552 Jan 20 10:05:54 Cooper kernel: md: import disk17: [8,32] (sdc) WDC WD5000AAKS-0 WD-WCASY0208552 offset: 63 size: 488386552 So, /dev/sdg and /dev/sdp are the two disk devices. It looks like the one is responding. That is a good sign. Now, let's see the output of: fdisk -l /dev/sdg and fdisk -l /dev/sdp and vol_id /dev/sdg1 and vol_id /dev/sdp1 Joe L.
January 20, 201115 yr Author root@Cooper:~# fdisk -l /dev/sdg Disk /dev/sdg: 500.1 GB, 500107862016 bytes 1 heads, 63 sectors/track, 15504336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdg1 2 15504336 488386552+ 83 Linux Partition 1 does not end on cylinder boundary. root@Cooper:~# fdisk -l /dev/sdp Disk /dev/sdp: 1500.3 GB, 1500301910016 bytes 1 heads, 63 sectors/track, 46512336 cylinders Units = cylinders of 63 * 512 = 32256 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdp1 2 46512336 1465138552+ 83 Linux Partition 1 does not end on cylinder boundary. root@Cooper:~# vol_id /dev/sdg1 ID_FS_USAGE=filesystem ID_FS_TYPE=reiserfs ID_FS_VERSION=3.6 ID_FS_UUID=2993620d-8936-47f6-9688-f324a606cf4b ID_FS_UUID_ENC=2993620d-8936-47f6-9688-f324a606cf4b ID_FS_LABEL= ID_FS_LABEL_ENC= root@Cooper:~# vol_id /dev/sdp1 ID_FS_USAGE=filesystem ID_FS_TYPE=reiserfs ID_FS_VERSION=3.6 ID_FS_UUID=0fdbbf1b-9aed-403d-ae77-2399704e0d5a ID_FS_UUID_ENC=0fdbbf1b-9aed-403d-ae77-2399704e0d5a ID_FS_LABEL= ID_FS_LABEL_ENC=
January 20, 201115 yr Author Also, as JoeL. mentioned you should have both molex power supply connectors connected to the backplane of the 4220. That case will supposedly work with only one power connection to each backplane but I found it to be less stable that way. All molex connectors have power going into them, and am only using 2 splitters.
January 20, 201115 yr As mentioned, the 1.5TB drive is failing badly. It shows: 197 Current_Pending_Sector 0x0032 195 195 000 Old_age Always - 1311 over 1300 sectors that are reported as unreadable. You WILL need to RMA it. The other (/dev/sdg) might be usable if you can repair the superblock in it using reiserfsck. When you use the --rebuild-sb option to reiserfsck you will be prompted for several items. The default answers are NOT correct for unRAID. See this thread for the correct responses: http://lime-technology.com/forum/index.php?topic=1483 The command to rebuild the superblock must be run on the "md" device. reiserfsck --rebuild-sb /dev/md7 Make sure you use the correct responses, see the thread I linked to. If you want, you can try the same command on /dev/md9 (assuming that "reiserfsck --check /dev/md9" also complains about a missing superblock,) but I feel that disk is probably not going to do too well with all the sectors pending re-allocation. But who knows. Joe L.
January 20, 201115 yr Author Sounds great, but we're kind of back to square one: root@Cooper:~# reiserfsck --rebuild-sb /dev/md7 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will check superblock and rebuild it if needed Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (2): (Input/output error). Aborted root@Cooper:~#
January 20, 201115 yr Sounds great, but we're kind of back to square one: root@Cooper:~# reiserfsck --rebuild-sb /dev/md7 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will check superblock and rebuild it if needed Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (2): (Input/output error). Aborted root@Cooper:~# Certainly looks like it. At first glance it appears your disk is defective. You could try it on a different PORT on your disk controller, with a different cable, just to be sure. You could try connecting it directly to the MB rather than through the back-plane of the case. You might have a defective back-plane. Joe L.
January 20, 201115 yr You have a Norco case and they use a backplanes. There is a chance that you may have a faulty one (cracked trace, etc.) I will suggest for you to identify the suspect drives and to move them around - to see if the errors will move with the drives. Since you have only 18 drives you have the two other drive slots available and you already have the necessary cables to perform this test.
Archived
This topic is now archived and is closed to further replies.