December 15, 201213 yr I have one disk just sitting in a CSE-M35T cage. I unassigned it yesterday and is no longer part of the array. It is still connected to power and M1015 controller though. The following happens: I enter the Main menu of the Web GUI and open the log window. It just shows a fews disk spindowns nothing more. When I open Disk Management in unmenu trouble? begins. I see numerous of the following lines appear in the log window: Dec 15 11:04:50 Tower1 kernel: end_request: I/O error, dev sdn, sector 192 (Errors) Dec 15 11:04:50 Tower1 kernel: sd 10:0:0:0: [sdn] Device not ready (Drive related) Dec 15 11:04:50 Tower1 kernel: sd 10:0:0:0: [sdn] Result: hostbyte=0x00 driverbyte=0x08 (System) Dec 15 11:04:50 Tower1 kernel: sd 10:0:0:0: [sdn] Sense Key : 0x2 [current] (Drive related) Dec 15 11:04:50 Tower1 kernel: sd 10:0:0:0: [sdn] ASC=0x4 ASCQ=0x2 (Drive related) Dec 15 11:04:50 Tower1 kernel: sd 10:0:0:0: [sdn] CDB: cdb[0]=0x28: 28 00 00 00 00 40 00 00 08 00 (Drive related) This goes on till I close the Web GUI and log window. Is it a cable that has come loose? The disk still holds data that I want to copy off it. Is this still possible?
December 15, 201213 yr Author The filesystem is screwed. Output from Reiser fsck: Will read-only check consistency of the filesystem on /dev/sde 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/sde. 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.
December 15, 201213 yr The filesystem is screwed. Output from Reiser fsck: Will read-only check consistency of the filesystem on /dev/sde 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/sde. 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. The file system is NEVER on the raw device name, but on the FIRST PARTITION. use reiserfsck --check /dev/sde1 (note the trailing "1" indicating the FIRST PARTITION)
December 15, 201213 yr note... the errors in your first post are on /dev/sdn, not /dev/sde. Did you move the disk? or is this a different issue/disk?
December 15, 201213 yr Author note... the errors in your first post are on /dev/sdn, not /dev/sde. Did you move the disk? or is this a different issue/disk? Yes Joe, You are right, that is why I am a noob. I moved the disk indeed. And no errors were detected on dev/sde1. I could mount the drive in unmenu and now it is at mnt/disk/sde1. BTW the disk mounted with a read only filesystem. I hope I can copy all files of it and then I will preclear the disk a couple of times. I use the nohup cp command for that.
Archived
This topic is now archived and is closed to further replies.