SuperW2 Posted October 6, 2011 Author Share Posted October 6, 2011 You may need to run reiserfsck to retrieve any data on this drives. I get this; reiserfs_open: the reiserfs superblock cannot be found on /dev/md9. Failed to open the filesystem. If the partition table has not been changed, and the partition is valid and it really contains a reiserfs partition, then the superblock is corrupted and you need to run this utility with --rebuild-sb. I've backed up all data from Drive 9 and 17, so don't really care if it formats and starts over...I just want to have a protected Array again! ***EDIT*** I clicked the Checkbox and Format button... it failed...it said 'formatting'... I hit refresh and both Drive 9 and 17 went back to "Unformatted"... HELP! ***EDIT2*** Oct 5 20:33:42 Media kernel: REISERFS warning (device md9): sh-2021 reiserfs_fill_super: can not find reiserfs on md9 Oct 5 20:33:42 Media logger: mount: wrong fs type, bad option, bad superblock on /dev/md9, Oct 5 20:33:42 Media logger: missing codepage or helper program, or other error Oct 5 20:33:42 Media logger: In some cases useful info is found in syslog - try Oct 5 20:33:42 Media logger: dmesg | tail or so Oct 5 20:33:42 Media logger: Oct 5 20:33:42 Media emhttp: _shcmd: shcmd (127): exit status: 32 Oct 5 20:33:42 Media emhttp: disk9 mount error: 32 Oct 5 20:33:42 Media emhttp: shcmd (128): rmdir /mnt/disk9 Oct 5 20:34:11 Media emhttp: shcmd (129): mkdir /mnt/disk17 Oct 5 20:34:11 Media emhttp: shcmd (130): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md17 /mnt/disk17 |& logger Oct 5 20:34:11 Media kernel: REISERFS warning (device md17): sh-2021 reiserfs_fill_super: can not find reiserfs on md17 Oct 5 20:34:11 Media logger: mount: wrong fs type, bad option, bad superblock on /dev/md17, Oct 5 20:34:11 Media logger: missing codepage or helper program, or other error Oct 5 20:34:11 Media logger: In some cases useful info is found in syslog - try Oct 5 20:34:11 Media logger: dmesg | tail or so Link to comment
SuperW2 Posted October 6, 2011 Author Share Posted October 6, 2011 I did the reiserfsck --rebuild-sb /dev/md9 per instructed by the following reiserfsck --check /dev/md9, and using the inputs from these threads... http://lime-technology.com/forum/index.php?topic=1483 http://lime-technology.com/forum/index.php?topic=4021 root@Media:~# reiserfsck --rebuild-sb /dev/md9 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 reiserfs_open: the reiserfs superblock cannot be found on /dev/md9. what the version of ReiserFS do you use[1-4] (1) 3.6.x (2) >=3.5.9 (introduced in the middle of 1999) (if you use linux 2.2, choose this one) (3) < 3.5.9 converted to new format (don't choose if unsure) (4) < 3.5.9 (this is very old format, don't choose if unsure) (X) exit 1 Enter block size [4096]: 4096 No journal device was specified. (If journal is not available, re-run with --no-journal-available option specified). Is journal default? (y/n)[y]: y Did you use resizer(y/n)[n]: n rebuild-sb: no uuid found, a new uuid was generated (18e871e2-0a42-4023-bf7d-eab7b3b53feb) rebuild-sb: You either have a corrupted journal or have just changed the start of the partition with some partition table editor. If you are sure that the start of the partition is ok, rebuild the journal header. Do you want to rebuild the journal header? (y/n)[n]: y Reiserfs super block in block 16 on 0x909 of format 3.6 with standard journal Count of blocks on the device: 183143632 Number of bitmaps: 5590 Blocksize: 4096 Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 0 Root block: 0 Filesystem is NOT clean Tree height: 0 Hash function used to sort names: not set Objectid map size 0, max 972 Journal parameters: Device [0x0] Magic [0x0] Size 8193 blocks (including 1 for journal header) (first block 18) Max transaction length 1024 blocks Max batch size 900 blocks Max commit age 30 Blocks reserved by journal: 0 Fs state field: 0x1: some corruptions exist. sb_version: 2 inode generation number: 0 UUID: 18e871e2-0a42-4023-bf7d-eab7b3b53feb LABEL: Set flags in SB: Mount count: 1 Maximum mount count: 30 Last fsck run: Wed Oct 5 20:44:24 2011 Check interval in days: 180 Is this ok ? (y/n)[n]: y The fs may still be unconsistent. Run reiserfsck --check. root@Media:~# at the end, doing another reiserfsck --check /dev/md9 results in another reiserfs_open: the reiserfs superblock cannot be found on /dev/md9. Failed to open the filesystem. If the partition table has not been changed, and the partition is valid and it really contains a reiserfs partition, then the superblock is corrupted and you need to run this utility with --rebuild-sb. Link to comment
mbryanr Posted October 6, 2011 Share Posted October 6, 2011 Lets try to run this on the file system <remember your disk failed to mount> http://lime-technology.com/forum/index.php?topic=15385.msg144520#msg144520 reiserfsck --check /dev/sdX1 where "X" is your drive assignment Do this for disk17 only for now. Edit: I don't know what may have been the result of you running --rebuild already. http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems Link to comment
SuperW2 Posted October 6, 2011 Author Share Posted October 6, 2011 Lets try to run this on the file system <remember your disk failed to mount> http://lime-technology.com/forum/index.php?topic=15385.msg144520#msg144520 reiserfsck --check /dev/sdX1 where "X" is your drive assignment Do this for disk17 only for now. Edit: I don't know what may have been the result of you running --rebuild already. http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems Results... Media login: root Linux 3.0.3-unRAID. root@Media:~# reiserfsck --check /dev/sds1 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/sds1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Thu Oct 6 07:27:45 2011 ########### Replaying journal: Done. Reiserfs journal '/dev/sds1' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Checking Semantic tree: finished 1 found corruptions can be fixed when running with --fix-fixable ########### reiserfsck finished at Thu Oct 6 08:03:14 2011 ########### root@Media:~# Link to comment
mbryanr Posted October 6, 2011 Share Posted October 6, 2011 Good - it found a problem. reiserfsck --fix-fixable/dev/md3 <not on sdX!> I believe samba is already stopped and the drive unmounted...but from the command line cd samba stop umount /dev/md3 reiserfsck --fix-fixable /dev/md3 Link to comment
SuperW2 Posted October 6, 2011 Author Share Posted October 6, 2011 Good - it found a problem. reiserfsck --fix-fixable/dev/md3 <not on sdX!> I believe samba is already stopped and the drive unmounted...but from the command line cd samba stop umount /dev/md3 reiserfsck --fix-fixable /dev/md3 It won't run on /dev/md17 root@Media:~# reiserfsck --fix-fixable /dev/md17 Will check consistency of the filesystem on /dev/md17 and will fix what can be fixed without --rebuild-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 reiserfs_open: the reiserfs superblock cannot be found on /dev/md17. Failed to open the filesystem. If the partition table has not been changed, and the partition is valid and it really contains a reiserfs partition, then the superblock is corrupted and you need to run this utility with --rebuild-sb. root@Media:~# But it did run on the /dev/sds1 (that I started before you replied) root@Media:~# reiserfsck --fix-fixable /dev/sds1 Will check consistency of the filesystem on /dev/sds1 and will fix what can be fixed without --rebuild-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 ########### reiserfsck --fix-fixable started at Thu Oct 6 08:18:00 2011 ########### Replaying journal: Done. Reiserfs journal '/dev/sds1' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..vpf-10630: The on-disk and the correct bitmaps differs. Will be fixed later. Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 140887 Internal nodes 868 Directories 96 Other files 1328 Data block pointers 142249376 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Thu Oct 6 08:53:52 2011 ########### Link to comment
SuperW2 Posted October 6, 2011 Author Share Posted October 6, 2011 ^^^ and the above Fix command appeared to do nothing to change anything positively... Link to comment
mbryanr Posted October 6, 2011 Share Posted October 6, 2011 Alright...more information needed type dd if=/dev/sdd count=195 | od -c -A d | sed 30q http://lime-technology.com/forum/index.php?topic=15385.msg144723#msg144723 I know your data is backed-up; and you could reformat 17 and rebuild 9; but lets try to get this right first. Link to comment
SuperW2 Posted October 6, 2011 Author Share Posted October 6, 2011 Alright...more information needed type dd if=/dev/sdd count=195 | od -c -A d | sed 30q http://lime-technology.com/forum/index.php?topic=15385.msg144723#msg144723 I know your data is backed-up; and you could reformat 17 and rebuild 9; but lets try to get this right first. I'd be fine reformatting both 9 and 17 actually... I'd be OK removing them both from the Array Completly (later wiping and re-adding as blank new drives) -?If I knew how! Link to comment
mbryanr Posted October 6, 2011 Share Posted October 6, 2011 ok. That showed nothing wrong. Did you get rid of these errors on Disk17? Oct 4 16:48:13 Media kernel: ata11.00: exception Emask 0x10 SAct 0x1 SErr 0x780100 action 0x6 Oct 4 16:48:13 Media kernel: ata11.00: irq_stat 0x08000000 Oct 4 16:48:13 Media kernel: ata11: SError: { UnrecovData 10B8B Dispar BadCRC Handshk } Oct 4 16:48:13 Media kernel: ata11.00: failed command: READ FPDMA QUEUED Oct 4 16:48:13 Media kernel: ata11.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0 ncq 4096 in Oct 4 16:48:13 Media kernel: res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) what is the result of: fdisk -lu /dev/sdX replace X with the actual assignment then smartctl -a -A /dev/sdX replace X with the actual assignment If nothing obvious, and since you have the data.. You'll need to create a new configuration <initconfig> 1. screen shot the devices tab 2. stop the array 3. unassign the drives 9 and 17 4. power down and physically remove them 5. power up and do initconfig in the console <believe there is a "NewConfig" option in unRAID 5Beta> 6. Reassign drives. 7. Start array 6. let parity rebuild and then do a parity check Link to comment
SuperW2 Posted October 6, 2011 Author Share Posted October 6, 2011 ok. That showed nothing wrong. Did you get rid of these errors on Disk17? Oct 4 16:48:13 Media kernel: ata11.00: exception Emask 0x10 SAct 0x1 SErr 0x780100 action 0x6 Oct 4 16:48:13 Media kernel: ata11.00: irq_stat 0x08000000 Oct 4 16:48:13 Media kernel: ata11: SError: { UnrecovData 10B8B Dispar BadCRC Handshk } Oct 4 16:48:13 Media kernel: ata11.00: failed command: READ FPDMA QUEUED Oct 4 16:48:13 Media kernel: ata11.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0 ncq 4096 in Oct 4 16:48:13 Media kernel: res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Yes, I think those were actually tied to my Cache Disk, which I just removed/disabled/unplugged, last reboot shows none of these errors in my Syslog! what is the result of: fdisk -lu /dev/sdX replace X with the actual assignment then smartctl -a -A /dev/sdX replace X with the actual assignment If nothing obvious, and since you have the data.. You'll need to create a new configuration <initconfig> 1. screen shot the devices tab 2. stop the array 3. unassign the drives 9 and 17 4. power down and physically remove them 5. power up and do initconfig in the console <believe there is a "NewConfig" option in unRAID 5Beta> 6. Reassign drives. 7. Start array 6. let parity rebuild and then do a parity check I ran the other two things and nothing seemed out of line... I have removed the drives and am now rebuilding parity after initconfig. I'll preclear those two drives and re-add them as new... hopefully that won't be too difficult. Thanks for ALL your help and patience with me! Link to comment
SuperW2 Posted October 7, 2011 Author Share Posted October 7, 2011 Well... after attemping a Parity Build for a number of hours today, it appears I'm in the exact same position I was when I started this thread... During Parity Build I lose the ability to connect to the GUI... I can still Ping, I can Telnet, but No GUI... All Lights on all my drives are Green (no Red Activity Blinking) and I'm pretty sure the Parity wasn't scheduled to be done for 2+ more hours... So I still have a server with what I expect is unprotected Parity... one that I will have to Hard Reboot and no idea how to Fix... The Last Activity from Syslog (attached as Zip), was over an hour ago... If this were a horse, I think I'd "put it down" by now... Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[5]:rc= 0 Oct 6 18:26:25 Media kernel: sas: I_T 0600000000000000 recovered Oct 6 18:26:25 Media kernel: sas: sas_ata_task_done: SAS error 8d Oct 6 18:26:25 Media last message repeated 4 times Oct 6 18:26:25 Media kernel: ata13: sas eh calling libata port error handler Oct 6 18:26:25 Media kernel: ata14: sas eh calling libata port error handler Oct 6 18:26:25 Media kernel: ata15: sas eh calling libata port error handler Oct 6 18:26:25 Media kernel: ata16: sas eh calling libata port error handler Oct 6 18:26:25 Media kernel: ata17: sas eh calling libata port error handler Oct 6 18:26:25 Media kernel: ata18: sas eh calling libata port error handler Oct 6 18:26:25 Media kernel: ata18: log page 10h reported inactive tag 26 Oct 6 18:26:25 Media kernel: ata18.00: exception Emask 0x1 SAct 0x1f SErr 0x0 action 0x6 t0 Oct 6 18:26:25 Media kernel: ata18.00: failed command: READ FPDMA QUEUED Oct 6 18:26:25 Media kernel: ata18.00: cmd 60/00:00:48:7b:04/02:00:71:00:00/40 tag 0 ncq 262144 in Oct 6 18:26:25 Media kernel: res 01/04:08:c0:79:04/00:00:71:00:00/40 Emask 0x3 (HSM violation) Oct 6 18:26:25 Media kernel: ata18.00: status: { ERR } Oct 6 18:26:25 Media kernel: ata18.00: error: { ABRT } Oct 6 18:26:25 Media kernel: ata18.00: failed command: READ FPDMA QUEUED Oct 6 18:26:25 Media kernel: ata18.00: cmd 60/88:00:c0:79:04/01:00:71:00:00/40 tag 1 ncq 200704 in Oct 6 18:26:25 Media kernel: res 01/04:08:c0:79:04/00:00:71:00:00/40 Emask 0x3 (HSM violation) Oct 6 18:26:25 Media kernel: ata18.00: status: { ERR } Oct 6 18:26:25 Media kernel: ata18.00: error: { ABRT } Oct 6 18:26:25 Media kernel: ata18.00: failed command: READ FPDMA QUEUED Oct 6 18:26:25 Media kernel: ata18.00: cmd 60/00:00:48:7d:04/02:00:71:00:00/40 tag 2 ncq 262144 in Oct 6 18:26:25 Media kernel: res 01/04:08:c0:79:04/00:00:71:00:00/40 Emask 0x3 (HSM violation) Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 6 ctrl sts=0x199800. Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 6 irq sts = 0x80000 Oct 6 18:26:25 Media kernel: ata18.00: status: { ERR } Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 6 ctrl sts=0x199800. Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 6 irq sts = 0x80000 Oct 6 18:26:25 Media kernel: ata18.00: error: { ABRT } Oct 6 18:26:25 Media kernel: ata18.00: failed command: READ FPDMA QUEUED Oct 6 18:26:25 Media kernel: ata18.00: cmd 60/78:00:48:7f:04/01:00:71:00:00/40 tag 3 ncq 192512 in Oct 6 18:26:25 Media kernel: res 01/04:08:c0:79:04/00:00:71:00:00/40 Emask 0x3 (HSM violation) Oct 6 18:26:25 Media kernel: ata18.00: status: { ERR } Oct 6 18:26:25 Media kernel: ata18.00: error: { ABRT } Oct 6 18:26:25 Media kernel: ata18.00: failed command: READ FPDMA QUEUED Oct 6 18:26:25 Media kernel: ata18.00: cmd 60/00:00:c0:80:04/02:00:71:00:00/40 tag 4 ncq 262144 in Oct 6 18:26:25 Media kernel: res 01/04:08:c0:79:04/00:00:71:00:00/40 Emask 0x3 (HSM violation) Oct 6 18:26:25 Media kernel: ata18.00: status: { ERR } Oct 6 18:26:25 Media kernel: ata18.00: error: { ABRT } Oct 6 18:26:25 Media kernel: ata18: hard resetting link Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 6 ctrl sts=0x89800. Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 6 irq sts = 0x1001 Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy6 Unplug Notice Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 6 ctrl sts=0x199800. Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 6 irq sts = 0x11081 Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2253:notify plug in on phy[6] Oct 6 18:26:25 Media kernel: drivers/scsi/mvsas/mv_sas.c 2278:plugin interrupt but phy6 is gone Oct 6 18:26:26 Media kernel: mvsas 0000:01:00.0: Phy6 : No sig fis Oct 6 18:26:26 Media kernel: drivers/scsi/mvsas/mv_sas.c 2139:phy6 Attached Device Oct 6 18:26:26 Media kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 6 ctrl sts=0x89800. Oct 6 18:26:26 Media kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 6 irq sts = 0x1001 Oct 6 18:26:26 Media kernel: drivers/scsi/mvsas/mv_sas.c 2226:phy6 Unplug Notice Oct 6 18:26:26 Media kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 6 ctrl sts=0x199800. Oct 6 18:26:26 Media kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 6 irq sts = 0x81 Oct 6 18:26:27 Media kernel: drivers/scsi/mvsas/mv_sas.c 2198:port 6 ctrl sts=0x199800. Oct 6 18:26:27 Media kernel: drivers/scsi/mvsas/mv_sas.c 2200:Port 6 irq sts = 0x10000 Oct 6 18:26:27 Media kernel: drivers/scsi/mvsas/mv_sas.c 2253:notify plug in on phy[6] Oct 6 18:26:27 Media kernel: drivers/scsi/mvsas/mv_sas.c 1338:port 6 attach dev info is 0 Oct 6 18:26:27 Media kernel: drivers/scsi/mvsas/mv_sas.c 1340:port 6 attach sas addr is 6 Oct 6 18:26:27 Media kernel: drivers/scsi/mvsas/mv_sas.c 379:phy 6 byte dmaded. Oct 6 18:26:27 Media kernel: sas: sas_form_port: phy6 belongs to port5 already(1)! Oct 6 18:26:27 Media kernel: drivers/scsi/mvsas/mv_sas.c 1701:mvs_I_T_nexus_reset for device[5]:rc= 0 Oct 6 18:26:27 Media kernel: sas: sas_ata_hard_reset: Found ATA device. Oct 6 18:26:27 Media kernel: ata18.00: configured for UDMA/133 Oct 6 18:26:27 Media kernel: ata18: EH complete Oct 6 18:26:27 Media kernel: ata19: sas eh calling libata port error handler Oct 6 18:26:27 Media kernel: sas: --- Exit sas_scsi_recover_host Oct 6 18:26:58 Media kernel: sas: command 0xede30cc0, task 0xedcff180, timed out: BLK_EH_NOT_HANDLED Oct 6 18:26:58 Media kernel: sas: command 0xede30540, task 0xedcff680, timed out: BLK_EH_NOT_HANDLED Oct 6 18:26:58 Media kernel: sas: command 0xede30900, task 0xedcfe8c0, timed out: BLK_EH_NOT_HANDLED Oct 6 18:26:58 Media kernel: sas: command 0xeff1cb40, task 0xedcfe000, timed out: BLK_EH_NOT_HANDLED Oct 6 18:26:58 Media kernel: sas: command 0xede303c0, task 0xedcff900, timed out: BLK_EH_NOT_HANDLED Oct 6 19:45:50 Media in.telnetd[11024]: connect from 192.168.1.120 (192.168.1.120) Oct 6 19:45:54 Media login[11025]: ROOT LOGIN on '/dev/pts/0' from 'Win7Main' syslog.zip Link to comment
dgaschk Posted October 7, 2011 Share Posted October 7, 2011 A lot of people are having trouble with beta12a and the mvsas driver. Check the announcement thread. Link to comment
mbryanr Posted October 7, 2011 Share Posted October 7, 2011 Oct 6 18:26:58 Media kernel: sas: command 0xede30cc0, task 0xedcff180, timed out: BLK_EH_NOT_HANDLED Search for "BLK_EH_NOT_HANDLED" http://lime-technology.com/forum/index.php?topic=15049.msg142329;topicseen#msg142329 http://lime-technology.com/forum/index.php?topic=15049.msg142711;topicseen#msg142711 Link to comment
SuperW2 Posted October 7, 2011 Author Share Posted October 7, 2011 A lot of people are having trouble with beta12a and the mvsas driver. Check the announcement thread. I never was able to get 12A to boot....never got past the rows and rows of Periods on the initial boot... Link to comment
SuperW2 Posted October 7, 2011 Author Share Posted October 7, 2011 Oct 6 18:26:58 Media kernel: sas: command 0xede30cc0, task 0xedcff180, timed out: BLK_EH_NOT_HANDLED Search for "BLK_EH_NOT_HANDLED" http://lime-technology.com/forum/index.php?topic=15049.msg142329;topicseen#msg142329 http://lime-technology.com/forum/index.php?topic=15049.msg142711;topicseen#msg142711 Yes, I see I have that same SAS Card and similar issues... the joys of running Beta Software... BUT, I did remove 1 more of my "new" 1.5TB Drives, which was disk 18 (one that had a few SMART Errors that I didn't copy down). I redid INITCONFIG, removed that drive and let it rebuild Parity over night, AND IT FINISHED... as of right now I have a fully protected Array for the first time in a week (granted it's almost 4 TB smaller than it was previously). So I guess I'll do a through test on these 3 drives, preclear them all if good and try to add 1 at a time and see what happens. Link to comment
SuperW2 Posted October 7, 2011 Author Share Posted October 7, 2011 Oct 6 18:26:58 Media kernel: sas: command 0xede30cc0, task 0xedcff180, timed out: BLK_EH_NOT_HANDLED Search for "BLK_EH_NOT_HANDLED" http://lime-technology.com/forum/index.php?topic=15049.msg142329;topicseen#msg142329 http://lime-technology.com/forum/index.php?topic=15049.msg142711;topicseen#msg142711 Yes, I see I have that same SAS Card and similar issues... the joys of running Beta Software... BUT, I did remove 1 more of my "new" 1.5TB Drives, which was disk 18 (one that had a few SMART Errors that I didn't copy down). I redid INITCONFIG, removed that drive and let it rebuild Parity over night, AND IT FINISHED... as of right now I have a fully protected Array for the first time in a week (granted it's almost 4 TB smaller than it was previously). So I guess I'll do a through test on these 3 drives, preclear them all if good and try to add 1 at a time and see what happens. Correction, the Parity Rebuild Finished... the subsequent Parity Check Hung after less than an hour and again, no WebGUI, but I can Ping/Telnet fine! Link to comment
SuperW2 Posted October 8, 2011 Author Share Posted October 8, 2011 One last reply and I'll stop spamming... Downgraded to Beta 11 Parity Re-build - Good Parity Check - Good Add re-precleared drives - Good Copy 250GB of Backed up stuff from Removed Drives - Good! Beta 12 did not like my SAS Card per a couple posts above... I'll stay on b11 until it's confirmed that issue is done! Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.