January 12, 201016 yr I had 2 disks working fine yesterday, and now they show up as unformatted. i have these logs for them root@Tower:~# smartctl -d ata -tshort /dev/sd sda sdb sdc sdd sde sdf sdg sda1 sdb1 sdc1 sdd1 sde1 sdf1 sdg1 root@Tower:~# smartctl -d ata -tshort /dev/sde smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Sending command: "Execute SMART Short self-test routine immediately in off-line mode". Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful. Testing has begun. Please wait 2 minutes for test to complete. Test will complete after Tue Jan 12 17:17:37 2010 Use smartctl -X to abort test. root@Tower:~# smartctl -a -d ata /dev/sde smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD15EADS-00R6B0 Serial Number: WD-WCAVY0216212 Firmware Version: 01.00A01 User Capacity: 1,500,300,828,160 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: Tue Jan 12 17:16:21 2010 GMT-12 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: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 246) Self-test routine in progress... 60% of test remaining. Total time to complete Offline data collection: (36360) 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 - 0 3 Spin_Up_Time 0x0027 150 149 021 Pre-fail Always - 9475 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 151 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 094 094 000 Old_age Always - 4553 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 - 94 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 7 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 135 194 Temperature_Celsius 0x0022 110 101 000 Old_age Always - 42 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 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. root@Tower:~# reiserfsck /dev/md1 reiserfsck 3.6.19 (2003 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/md1 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 i tried different power cables and made sure the sata connections were secure and they were. but each time i power up the unraid server they appear as "unformatted". since this happened to 2 drives, and it happened over night, my parity drive wont help me retain any data, so i really want to fix this. theres one drive that i really need. any more info i need to require let me know TIA
January 12, 201016 yr Post a syslog. Instructions on how to grab a syslog are in the troubleshooting section of the wiki. Zip it up and attach it to your next post. DO NOT press the "restore" button. If you do, you will lose your data. (there's one exception, but you don't yet know if it applies... and too many situations where it is NOT the correct action.) The smart report you gave was only for 1 drive, /dev/sde. It seems to be working, but we have no idea of its file-system. You attempted to run reiserfsck on /dev/md1. This attempt failed... but we do not know which physical disk this corresponds to. So... Post a syslog, wait for guidance BEFORE doing anything else that might cause your situation to get worse. Did I mention you need to post a syslog? Joe L.
January 12, 201016 yr Author heres my system log. the smartdrive report and the reiserfsck where both for disk1 in my system. disk4 also reported the exact same thing when i ran reiserfsck thanks again john syslog-2010-01-13.txt.zip
January 12, 201016 yr As I suspected, the two disks BOTH show they are unable to be mounted because they both apparently have a corrupted reiserfsck superblock. You can see the kernel's attempt to mount the disks here: Jan 13 07:26:43 Tower emhttp: shcmd (13): mount -t reiserfs -o noatime,nodiratime /dev/md4 /mnt/disk4 >/dev/null 2>&1 Jan 13 07:26:43 Tower kernel: ReiserFS: md4: warning: sh-2006: read_super_block: bread failed (dev md4, block 2, size 4096) Jan 13 07:26:43 Tower kernel: ReiserFS: md4: warning: sh-2006: read_super_block: bread failed (dev md4, block 16, size 4096) Jan 13 07:26:43 Tower kernel: ReiserFS: md4: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on md4 Jan 13 07:26:43 Tower emhttp: shcmd: shcmd (13): exit status: 32 Jan 13 07:26:43 Tower emhttp: shcmd (14): rmdir /mnt/disk4 Jan 13 07:26:43 Tower emhttp: shcmd (13): mount -t reiserfs -o noatime,nodiratime /dev/md5 /mnt/disk5 >/dev/null 2>&1 Jan 13 07:26:43 Tower kernel: ReiserFS: md1: warning: sh-2006: read_super_block: bread failed (dev md1, block 2, size 4096) Jan 13 07:26:43 Tower kernel: ReiserFS: md1: warning: sh-2006: read_super_block: bread failed (dev md1, block 16, size 4096) Jan 13 07:26:43 Tower kernel: ReiserFS: md1: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on md1 Jan 13 07:26:43 Tower emhttp: shcmd: shcmd (13): exit status: 32 Jan 13 07:26:43 Tower emhttp: shcmd (14): rmdir /mnt/disk1 Jan 13 07:26:43 Tower emhttp: disk1 mount error: 32 Jan 13 07:26:43 Tower emhttp: disk4 mount error: 32 To have two file-systems get corrupted at the exact same time, with the exact same type of corruption seems very odd to me. Can you describe what was happening when the disks failed? was the server in use? or idle? Are you experimenting with s3? or plugging/un-plugging drives? There is only one possible fix I'm aware of at this point, and that is to attempt to rebuild the reiser file-system superblock. I'd start with the drive with the data you can most want to recover, but it really does not matter. You've had a two disk failure... (or at least unRAID thinks so) You need to rebuild the reiser file system superblock. Recovering corrupted superblock Each file system has a superblock, which contains information about file system such as: * File system type * Size * Status * Information about other metadata structures If this information lost, you are in trouble (data loss) so Linux maintains multiple redundant copies of the superblock in every file system. During check (reiserfsck --check /dev/md1) if you get an error superblock was missing, use following command to fix superblock: # reiserfsck --rebuild-sb /dev/md1 Where, * --rebuild-sb: This option recovers the superblock on a Reiserfs partition. Normally you only need this option if mount reports "read_super_block: can't find a reiserfs file system". Caution: Do not run above command twice on same drive. You will damage your partition (data). the rebuild-sb will prompt you for some information. These responses must be perfect: For guidance, See the wiki: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems For the proper responses, see this post: http://lime-technology.com/forum/index.php?topic=1483 After running the rebuild-sb command, once on each of the two failing drives, you can try the following commands to see if they will mount: First we need to create the mount-points (empty directories) mkdir -m 700 /mnt/disk1 mkdir -m 700 /mnt/disk4 And then attempt to mount the disks on the mount-points. mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1 mount -t reiserfs -o noatime,nodiratime /dev/md4 /mnt/disk4 If they mount, great... reboot the server and let unRAID mount them, then do a full parity check. Unrelated... I also see you have an HPA (host protected area) on one of your disks. Do you know about it? I also see you have an ext3 file-system mounted? on a loop device. What is it? Joe L.
January 12, 201016 yr Author at the time the server wasn't doing much. just sitting there. i noticed rtorrent wasn't running and no files were playing (i was watching videos off of it the day before without any issues) so i just rebooted the system (via the web interface). when it came back online both drives should up as unformatted. I also see you have an HPA (host protected area) on one of your disks. Do you know about it? no idea I also see you have an ext3 file-system mounted? on a loop device. What is it? no idea, all i have in the server is, 6 sata hdd and the flash usb key. i also have umenu, buddaraid, wtorrent, rtorrent, mysql, and unrar installed. other than that its a basic install. ill try what you suggested and get back with the results thanks again
January 12, 201016 yr I added a link to the wiki, and to the post that described the proper responses needed for the repair-sb option.
January 12, 201016 yr Author ok i ran the command and got the same error, and i didnt want to run it again since u warned me not to root@Tower:~# reiserfsck --rebuild-sb /dev/md1 reiserfsck 3.6.19 (2003 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
January 13, 201016 yr If you are unable to read the drive, then it is pointing to more of a hardware problem than something else. Are the two drives on the same power splitter? in the same cage? Anything common? If not wired directly to the drive, now is the time to do so. Since the repair-sb did not even get to read the disk, I don't think it did anything. Are you sure you can do a smartctl report on the drives???
January 13, 201016 yr Author two drives are on two different power points. i even tried switching the power leads from good drives to see if they reappeared, but still showed as unformatted. both drives are on different sata units on the mb, the other drives that are on the same unit are fine (2 drives per unit thingy on the mb). all drives are in a ejection type drive bay, but i removed them from them and plugged them directly into the mb, and that had no effect. so the drives have nothing in common that im aware of, they arent next to each other or using any of the same things, and they are two different brands, one western digital the other is seagate. im pretty sure i can do a smartctl on the drives, that is what i attached in the first post right?
January 13, 201016 yr two drives are on two different power points. i even tried switching the power leads from good drives to see if they reappeared, but still showed as unformatted. both drives are on different sata units on the mb, the other drives that are on the same unit are fine (2 drives per unit thingy on the mb). all drives are in a ejection type drive bay, but i removed them from them and plugged them directly into the mb, and that had no effect. so the drives have nothing in common that im aware of, they arent next to each other or using any of the same things, and they are two different brands, one western digital the other is seagate. im pretty sure i can do a smartctl on the drives, that is what i attached in the first post right? Well, the two devices are adjacent devices /dev/sde, and /dev/sdf so I'm leaning towards a hardware issue. Jan 12 21:51:22 Tower kernel: md: import disk1: [8,64] (sde) SAMSUNG HD103UJ S13PJ1NQ302479 offset: 63 size: 976762552 Jan 12 21:51:22 Tower kernel: md: import disk4: [8,80] (sdf) WDC WD1001FALS-75J7B0 WD-WMATV2330666 offset: 63 size: 976762552 Can you try swapping one of them to one of the "working" ports on the MB. (plug the cable form the non-working SAMSUNG to one of the working western-digitals.)
January 13, 201016 yr Author ok i may have mixed up the cables, i thought i had it so disk1/2 were on the same thingy, disk3/4 and disk 5/parity were on the same thing. i ejected disk2 and put disk1 in its place. and on the unmenu main page i have StatusDiskMountedDeviceModel/SerialTempReadsWritesErrorsSizeUsed%UsedFree OKparity/dev/sddWDC_WD15EADS-00R6B0_WD-WCAVY031710727°C2500 DISK_NP_MISSING/dev/md1WDC_WD15EADS-00R6B0_WD-WCAVY0216212000 DISK_WRONG/dev/md2/dev/sdeST31000340AS_5QJ10E87 <-- was old disk in this slot WDC WD15EADS-00R6B0 _ WD-WCAVY0216212 <-- current disk in this slot29°C2900 OK/dev/md3/dev/sdaST31500341AS_9VS0E6HW30°C2900 DISK_INVALID/dev/md4/dev/sdbST31500341AS_9VS09S4T30°C2900 OK/dev/md5/dev/sdcWDC_WD7500AACS-00ZJB0_WD-WCASN005715826°C3100 ive attached the log. syslog-2010-01-14.zip
January 13, 201016 yr ok i may have mixed up the cables, i thought i had it so disk1/2 were on the same thingy, disk3/4 and disk 5/parity were on the same thing. i ejected disk2 and put disk1 in its place. and on the unmenu main page i have StatusDiskMountedDeviceModel/SerialTempReadsWritesErrorsSizeUsed%UsedFree OKparity/dev/sddWDC_WD15EADS-00R6B0_WD-WCAVY031710727°C2500 DISK_NP_MISSING/dev/md1WDC_WD15EADS-00R6B0_WD-WCAVY0216212000 DISK_WRONG/dev/md2/dev/sdeST31000340AS_5QJ10E87 <-- was old disk in this slot WDC WD15EADS-00R6B0 _ WD-WCAVY0216212 <-- current disk in this slot29°C2900 OK/dev/md3/dev/sdaST31500341AS_9VS0E6HW30°C2900 DISK_INVALID/dev/md4/dev/sdbST31500341AS_9VS09S4T30°C2900 OK/dev/md5/dev/sdcWDC_WD7500AACS-00ZJB0_WD-WCASN005715826°C3100 ive attached the log. Can you run a reiserfsck /dev/md2 at this point in time? (if yes, then can you put the drive you took out of slot 2 into the slot for disk1. apparently you left it empty) Don't do anything more than a simple reiserfsck... I'm just trying to see if the disk controller is working. If the file-system check can now read the superblock on disk2 (which is the physical disk that was in slot1, then it points to the disk controller being the issue) Joe L.
January 14, 201016 yr Author hi i ran another smartctrl on disk2 (which was the bad drive as disk1) root@Tower:~# smartctl -a -d ata /dev/sdf smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD15EADS-00R6B0 Serial Number: WD-WCAVY0216212 Firmware Version: 01.00A01 User Capacity: 1,500,300,828,160 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 14 19:06:05 2010 GMT-12 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: (36360) 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 - 0 3 Spin_Up_Time 0x0027 152 149 021 Pre-fail Always - 9391 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 159 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 094 094 000 Old_age Always - 4559 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 101 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 7 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 142 194 Temperature_Celsius 0x0022 117 101 000 Old_age Always - 35 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 4553 - 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. heres the reiserfsck result root@Tower:~# reiserfsck /dev/md2 reiserfsck 3.6.19 (2003 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/md2 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Failed to open the device '/dev/md2': No such file or directory and heres disk4, which i havent swapped yet. root@Tower:~# reiserfsck /dev/md4 reiserfsck 3.6.19 (2003 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/md4 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Failed to open the device '/dev/md4': No such file or directory and the smartctrl for disk4 root@Tower:~# smartctl -a -d ata /dev/sdb smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ST31500341AS Serial Number: 9VS09S4T Firmware Version: SD1A User Capacity: 1,500,300,828,160 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Thu Jan 14 19:09:49 2010 GMT-12 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: (0x82) Offline data collection activity was completed without error. 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: ( 609) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103b) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 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 113 099 006 Pre-fail Always - 58707541 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 76 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 2 7 Seek_Error_Rate 0x000f 071 060 030 Pre-fail Always - 14193986 9 Power_On_Hours 0x0032 090 090 000 Old_age Always - 9460 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 548 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 099 000 Old_age Always - 21475164166 189 High_Fly_Writes 0x003a 031 031 000 Old_age Always - 69 190 Airflow_Temperature_Cel 0x0022 063 046 045 Old_age Always - 37 (Lifetime Min/Max 29/37) 194 Temperature_Celsius 0x0022 037 054 000 Old_age Always - 37 (0 19 0 0) 195 Hardware_ECC_Recovered 0x001a 031 020 000 Old_age Always - 58707541 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 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. under the devices list, the drives that list as bad are actually sde (currently sdf, ie disk1 in disk2's bay) and sdb (disk4). im assuming the reiserfsck failed because the array is down, since the drives have been moved. i dont want to start the array without a confirmation that this wont actually break anything and screw up my parity/array. cheers again
January 14, 201016 yr Put the disks back in their original slots before we get too mixed up. Can we read the disks at all? od -x /dev/sde | head -50 od -x /dev/sdf | head -50 If you can read the disks, try a reiserfsck on the raw partition on each disk. reiserfsck /dev/sdf1 and reiserfsck /dev/sde1 note the "1" at the end of the above commands, pointing the file system check to the 1st raw partition on the disk (actually, in our case, the only partition) Joe L.
January 17, 201016 yr Author od -x /dev/sde | head -50 root@Tower:~# od -x /dev/sde | head -50 0000000 0000 0000 0000 0000 0000 0000 0000 0000 * 0000700 0000 0083 0000 003f 0000 72b0 aea8 0000 0000720 0000 0000 0000 0000 0000 0000 0000 0000 * 0000760 0000 0000 0000 0000 0000 0000 0000 aa55 0001000 0000 0000 0000 0000 0000 0000 0000 0000 * 0277000 0e56 15d5 936f 0313 0072 0e5e 0012 0000 0277020 0000 0000 2000 0000 0400 0000 c0f9 7663 0277040 0384 0000 001e 0000 0000 0000 1000 03cc 0277060 0104 0002 6552 7349 7245 4632 0073 0000 0277100 0003 0000 0005 2bab 0002 0000 8bcd 0007 0277120 0001 0000 182d fe76 513d 0747 41bd 7c54 0277140 3b71 5750 0000 0000 0000 0000 0000 0000 0277160 0000 0000 0000 0000 0000 0000 0000 0000 * 0277300 0000 0000 0000 0000 0000 0000 0001 0000 0277320 01e9 0000 01ea 0000 01ef 0000 01f0 0000 0277340 01f5 0000 01f6 0000 01ff 0000 0200 0000 0277360 020c 0000 020d 0000 0447 0000 0448 0000 0277400 07ee 0000 07ef 0000 0804 0000 0805 0000 0277420 0874 0000 0875 0000 0892 0000 0893 0000 0277440 08c6 0000 08c7 0000 0b3a 0000 0b3c 0000 0277460 0cfe 0000 0cff 0000 0d3b 0000 0d42 0000 0277500 0d43 0000 0d47 0000 0d48 0000 0d49 0000 0277520 0d4a 0000 0d4f 0000 0d50 0000 0d51 0000 0277540 0d52 0000 0d6b 0000 0d6d 0000 0d84 0000 0277560 13f3 0000 13f6 0000 13f7 0000 13fb 0000 0277600 1401 0000 1409 0000 140a 0000 140c 0000 0277620 1422 0000 14d7 0000 14d8 0000 152a 0000 0277640 154b 0000 154f 0000 1553 0000 1564 0000 0277660 16b6 0000 16b8 0000 16cf 0000 16d0 0000 0277700 17bc 0000 17bd 0000 17bf 0000 17c0 0000 0277720 17ce 0000 17d3 0000 1892 0000 1893 0000 0277740 18a6 0000 18a7 0000 18a8 0000 18a9 0000 0277760 18aa 0000 18ab 0000 18ac 0000 18b2 0000 0300000 18c0 0000 18c1 0000 18e2 0000 18e5 0000 0300020 18e7 0000 18e9 0000 18ec 0000 18ed 0000 0300040 18f2 0000 1904 0000 1905 0000 1913 0000 0300060 1914 0000 191d 0000 1938 0000 1969 0000 0300100 196b 0000 197c 0000 197d 0000 197e 0000 0300120 198b 0000 1990 0000 19d9 0000 19f4 0000 0300140 1a00 0000 1a35 0000 1a37 0000 1a38 0000 0300160 1a4d 0000 1a4e 0000 1a60 0000 1a62 0000 0300200 1ac6 0000 1ac8 0000 1ace 0000 1ad0 0000 0300220 1ad1 0000 1ad2 0000 1ad3 0000 1b2d 0000 0300240 1b34 0000 1b35 0000 1b36 0000 1b47 0000 0300260 1b73 0000 1b92 0000 1b93 0000 1bde 0000 0300300 1bdf 0000 1be3 0000 1c40 0000 1c41 0000 od -x /dev/sdb | head -50 root@Tower:~# od -x /dev/sdb | head -50 0000000 0000 0000 0000 0000 0000 0000 0000 0000 * 0000700 0000 0083 0000 003f 0000 72b0 aea8 0000 0000720 0000 0000 0000 0000 0000 0000 0000 0000 * 0000760 0000 0000 0000 0000 0000 0000 0000 aa55 0001000 0000 0000 0000 0000 0000 0000 0000 0000 * 0277000 0e56 15d5 408c 0e55 3668 11be 0012 0000 0277020 0000 0000 2000 0000 0400 0000 52fa 39d3 0277040 0384 0000 001e 0000 0000 0000 1000 03cc 0277060 000a 0002 6552 7349 7245 4632 0073 0000 0277100 0003 0000 0005 2bab 0002 0000 0026 0000 0277120 0001 0000 0731 160a acd9 b946 66b0 5352 0277140 6dc9 765a 0000 0000 0000 0000 0000 0000 0277160 0000 0000 0000 0000 0000 0000 0000 0000 * 0277300 0000 0000 0000 0000 0000 0000 0001 0000 0277320 0427 0000 0428 0000 0429 0000 042a 0000 0277340 042b 0000 042c 0000 042d 0000 042e 0000 0277360 0430 0000 0000 0000 0000 0000 0000 0000 0277400 0000 0000 0000 0000 0000 0000 0000 0000 * 0307000 ffff ffff ffff ffff ffff ffff ffff ffff * 0317000 4577 0000 0009 0000 0000 0000 0000 0000 0317020 0000 0000 0000 0000 0000 0000 0000 0000 * 0327000 4578 0000 0009 0000 0016 0000 8000 0601 0327020 0010 0000 b81e 0601 8655 05fe 0002 05fe 0327040 bc1e 0601 ad37 0135 c00a 0601 c407 0601 0327060 0000 0000 0000 0000 0000 0000 0000 0000 * 0336760 0000 0000 6552 7349 7245 424c 0000 0000 0337000 ffff ffff ffff ffff ffff ffff ffff ffff * 0343220 ffff ffff ffff ffff ffff 00ff 0000 0000 0343240 0000 0000 0000 0000 0000 0000 0000 0000 * 0347000 0e56 15d5 10fe 0e58 3668 11be 0012 0000 0347020 0000 0000 2000 0000 0400 0000 52fa 39d3 0347040 0384 0000 001e 0000 0000 0000 1000 03cc 0347060 0008 0002 6552 7349 7245 4632 0073 0000 0347100 0003 0000 0005 2bab 0002 0000 0025 0000 0347120 0001 0000 0731 160a acd9 b946 66b0 5352 0347140 6dc9 765a 0000 0000 0000 0000 0000 0000 0347160 0000 0000 0000 0000 0000 0000 0000 0000 * 0347300 0000 0000 0000 0000 0000 0000 0001 0000 0347320 0427 0000 0428 0000 0429 0000 042a 0000 reiserfsck /dev/sde1 root@Tower:~# reiserfsck /dev/sde1 reiserfsck 3.6.19 (2003 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/sde1 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 Mon Jan 18 06:48:33 2010 ########### Replaying journal.. Trans replayed: mountid 92, transid 6163783, desc 5182, len 1, commit 5184, next trans offset 5167 Trans replayed: mountid 92, transid 6163784, desc 5185, len 1, commit 5187, next trans offset 5170 Trans replayed: mountid 92, transid 6163785, desc 5188, len 10, commit 5199, next trans offset 5182 Trans replayed: mountid 92, transid 6163786, desc 5200, len 13, commit 5214, next trans offset 5197 Trans replayed: mountid 92, transid 6163787, desc 5215, len 1, commit 5217, next trans offset 5200 Trans replayed: mountid 92, transid 6163788, desc 5218, len 1, commit 5220, next trans offset 5203 Trans replayed: mountid 92, transid 6163789, desc 5221, len 5, commit 5227, next trans offset 5210 Trans replayed: mountid 92, transid 6163790, desc 5228, len 1, commit 5230, next trans offset 5213 Trans replayed: mountid 92, transid 6163791, desc 5231, len 4, commit 5236, next trans offset 5219 Trans replayed: mountid 92, transid 6163792, desc 5237, len 4, commit 5242, next trans offset 5225 Trans replayed: mountid 92, transid 6163793, desc 5243, len 4, commit 5248, next trans offset 5231 Trans replayed: mountid 92, transid 6163794, desc 5249, len 4, commit 5254, next trans offset 5237 Trans replayed: mountid 92, transid 6163795, desc 5255, len 1, commit 5257, next trans offset 5240 Trans replayed: mountid 92, transid 6163796, desc 5258, len 4, commit 5263, next trans offset 5246 Trans replayed: mountid 92, transid 6163797, desc 5264, len 9, commit 5274, next trans offset 5257 Trans replayed: mountid 92, transid 6163798, desc 5275, len 8, commit 5284, next trans offset 5267 Trans replayed: mountid 92, transid 6163799, desc 5285, len 1, commit 5287, next trans offset 5270 Trans replayed: mountid 92, transid 6163800, desc 5288, len 4, commit 5293, next trans offset 5276 Trans replayed: mountid 92, transid 6163801, desc 5294, len 11, commit 5306, next trans offset 5289 Trans replayed: mountid 92, transid 6163802, desc 5307, len 5, commit 5313, next trans offset 5296 Trans replayed: mountid 92, transid 6163803, desc 5314, len 1, commit 5316, next trans offset 5299 Trans replayed: mountid 92, transid 6163804, desc 5317, len 1, commit 5319, next trans offset 5302 Trans replayed: mountid 92, transid 6163805, desc 5320, len 4, commit 5325, next trans offset 5308 Trans replayed: mountid 92, transid 6163806, desc 5326, len 1, commit 5328, next trans offset 5311 Trans replayed: mountid 92, transid 6163807, desc 5329, len 1, commit 5331, next trans offset 5314 Trans replayed: mountid 92, transid 6163808, desc 5332, len 4, commit 5337, next trans offset 5320 Trans replayed: mountid 92, transid 6163809, desc 5338, len 1, commit 5340, next trans offset 5323 Trans replayed: mountid 92, transid 6163810, desc 5341, len 2, commit 5344, next trans offset 5327 Trans replayed: mountid 92, transid 6163811, desc 5345, len 5, commit 5351, next trans offset 5334 Trans replayed: mountid 92, transid 6163812, desc 5352, len 9, commit 5362, next trans offset 5345 Trans replayed: mountid 92, transid 6163813, desc 5363, len 5, commit 5369, next trans offset 5352 Trans replayed: mountid 92, transid 6163814, desc 5370, len 7, commit 5378, next trans offset 5361 Trans replayed: mountid 92, transid 6163815, desc 5379, len 9, commit 5389, next trans offset 5372 Trans replayed: mountid 92, transid 6163816, desc 5390, len 5, commit 5396, next trans offset 5379 Trans replayed: mountid 92, transid 6163817, desc 5397, len 5, commit 5403, next trans offset 5386 Trans replayed: mountid 92, transid 6163818, desc 5404, len 11, commit 5416, next trans offset 5399 Trans replayed: mountid 92, transid 6163819, desc 5417, len 5, commit 5423, next trans offset 5406 Trans replayed: mountid 92, transid 6163820, desc 5424, len 7, commit 5432, next trans offset 5415 Trans replayed: mountid 92, transid 6163821, desc 5433, len 7, commit 5441, next trans offset 5424 Trans replayed: mountid 92, transid 6163822, desc 5442, len 9, commit 5452, next trans offset 5435 Trans replayed: mountid 92, transid 6163823, desc 5453, len 5, commit 5459, next trans offset 5442 Trans replayed: mountid 92, transid 6163824, desc 5460, len 7, commit 5468, next trans offset 5451 Trans replayed: mountid 92, transid 6163825, desc 5469, len 7, commit 5477, next trans offset 5460 Trans replayed: mountid 92, transid 6163826, desc 5478, len 5, commit 5484, next trans offset 5467 Trans replayed: mountid 92, transid 6163827, desc 5485, len 7, commit 5493, next trans offset 5476 Trans replayed: mountid 92, transid 6163828, desc 5494, len 9, commit 5504, next trans offset 5487 Trans replayed: mountid 92, transid 6163829, desc 5505, len 4, commit 5510, next trans offset 5493 Trans replayed: mountid 92, transid 6163830, desc 5511, len 5, commit 5517, next trans offset 5500 Trans replayed: mountid 92, transid 6163831, desc 5518, len 1, commit 5520, next trans offset 5503 Trans replayed: mountid 92, transid 6163832, desc 5521, len 7, commit 5529, next trans offset 5512 Trans replayed: mountid 92, transid 6163833, desc 5530, len 5, commit 5536, next trans offset 5519 Trans replayed: mountid 92, transid 6163834, desc 5537, len 4, commit 5542, next trans offset 5525 Trans replayed: mountid 92, transid 6163835, desc 5543, len 4, commit 5548, next trans offset 5531 Trans replayed: mountid 92, transid 6163836, desc 5549, len 7, commit 5557, next trans offset 5540 Trans replayed: mountid 92, transid 6163837, desc 5558, len 7, commit 5566, next trans offset 5549 Trans replayed: mountid 92, transid 6163838, desc 5567, len 4, commit 5572, next trans offset 5555 Trans replayed: mountid 92, transid 6163839, desc 5573, len 6, commit 5580, next trans offset 5563 Trans replayed: mountid 92, transid 6163840, desc 5581, len 20, commit 5602, next trans offset 5585 Trans replayed: mountid 92, transid 6163841, desc 5603, len 4, commit 5608, next trans offset 5591 Trans replayed: mountid 92, transid 6163842, desc 5609, len 5, commit 5615, next trans offset 5598 Trans replayed: mountid 92, transid 6163843, desc 5616, len 6, commit 5623, next trans offset 5606 Trans replayed: mountid 92, transid 6163844, desc 5624, len 1, commit 5626, next trans offset 5609 Trans replayed: mountid 92, transid 6163845, desc 5627, len 4, commit 5632, next trans offset 5615 Trans replayed: mountid 92, transid 6163846, desc 5633, len 6, commit 5640, next trans offset 5623 Trans replayed: mountid 92, transid 6163847, desc 5641, len 6, commit 5648, next trans offset 5631 Trans replayed: mountid 92, transid 6163848, desc 5649, len 4, commit 5654, next trans offset 5637 Trans replayed: mountid 92, transid 6163849, desc 5655, len 7, commit 5663, next trans offset 5646 Trans replayed: mountid 92, transid 6163850, desc 5664, len 1, commit 5666, next trans offset 5649 Trans replayed: mountid 92, transid 6163851, desc 5667, len 4, commit 5672, next trans offset 5655 Trans replayed: mountid 92, transid 6163852, desc 5673, len 4, commit 5678, next trans offset 5661 Trans replayed: mountid 92, transid 6163853, desc 5679, len 2, commit 5682, next trans offset 5665 Trans replayed: mountid 92, transid 6163854, desc 5683, len 1, commit 5685, next trans offset 5668 Trans replayed: mountid 92, transid 6163855, desc 5686, len 15, commit 5702, next trans offset 5685 Trans replayed: mountid 92, transid 6163856, desc 5703, len 8, commit 5712, next trans offset 5695 Trans replayed: mountid 92, transid 6163857, desc 5713, len 7, commit 5721, next trans offset 5704 Trans replayed: mountid 92, transid 6163858, desc 5722, len 2, commit 5725, next trans offset 5708 Trans replayed: mountid 92, transid 6163859, desc 5726, len 7, commit 5734, next trans offset 5717 Reiserfs journal '/dev/sde1' in blocks [18..8211]: 77 transactions replayed reiserfsck /dev/sdb1 root@Tower:~# reiserfsck /dev/sdb1 reiserfsck 3.6.19 (2003 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/sdb1 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 Mon Jan 18 06:56:12 2010 ########### Replaying journal.. Trans replayed: mountid 24, transid 17852, desc 762, len 1, commit 764, next trans offset 747 Trans replayed: mountid 24, transid 17853, desc 765, len 1, commit 767, next trans offset 750 Reiserfs journal '/dev/sdb1' in blocks [18..8211]: 2 transactions replayed Checking internal tree../ 6 (of 6)/ 88 (of 108)/ 1 (of 163)bad_path: The left delimiting key [1007 1026 0x5862001 IND (1)] of the node (20217888) must be equal to the first element's key [1007 1023 0x3945001 IND (1)] within the node. / 89 (of 108)block 30634743: The level of the node (4426) is not correct, (2) expected the problem in the internal node occured (30634743), whole subtree is skipped finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 2 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Mon Jan 18 07:08:44 2010 ###########
January 22, 201016 yr sde1 looked like it had a lot of transactions that needed to be replayed before it could be mounted. It does not look like there is anything wrong with it at all. The second disk on /dev/sdb1 has a corrupt file system that it is suggesting can be repaired by typing reiserfsck --rebuild-tree /dev/sdb1 That is your next step. Then let us know the output. If it does not suggest any other corrective action is needed, reboot the server and let it come back online. It will probably start a parity check. Let it complete. Fixing the file-systems on the raw disks will have invalidated some of the parity so it will find a few errors in parity and it will fix it to be in sync with your data.
January 23, 201016 yr Author ran the rebuild-tree command, heres the result root@Tower:~# reiserfsck --rebuild-tree /dev/sdb1 reiserfsck 3.6.19 (2003 www.namesys.com) ************************************************************* ** Do not run the program with --rebuild-tree unless ** ** something is broken and MAKE A BACKUP before using it. ** ** If you have bad sectors on a drive it is usually a bad ** ** idea to continue using it. Then you probably should get ** ** a working hard drive, copy the file system from the bad ** ** drive to the good one -- dd_rescue is a good tool for ** ** that -- and only then run this program. ** ** 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 rebuild the filesystem (/dev/sdb1) tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Replaying journal.. Reiserfs journal '/dev/sdb1' in blocks [18..8211]: 0 transactions replayed ########### reiserfsck --rebuild-tree started at Sat Jan 23 17:07:05 2010 ########### Pass 0: ####### Pass 0 ####### Loading on-disk bitmap .. ok, 122492108 blocks marked used Skipping 19389 blocks (super block, journal, bitmaps) 122472719 blocks will be read 0%....20%. left 0, 19846 /seccc1042 directory entries were hashed with "r5" hash. "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 122472719 Leaves among those 120995 Objectids found 1044 Pass 1 (will try to insert 120995 leaves): ####### Pass 1 ####### Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....100% left 0, 101 /sec Flushing..finished 120995 leaves read 120995 inserted ####### Pass 2 ####### Flushing..finished Pass 3 (semantic): ####### Pass 3 ######### /TV Shows/Gilmore Girlsrebuild_semantic_pass: The entry [1040 1043] ("Season 1") in directory [64 1040] points to nowhere - is removed rebuild_semantic_pass: The entry [1040 1061] (".DS_Store") in directory [64 1040] points to nowhere - is removed vpf-10650: The directory [64 1040] has the wrong size in the StatData (104) - corrected to (48) /TV Shows/Family Guyrebuild_semantic_pass: The entry [1039 1041] ("Season 8") in directory [64 1039] points to nowhere - is removed vpf-10650: The directory [64 1039] has the wrong size in the StatData (72) - corrected to (48) Flushing..finished Files found: 927 Directories found: 114 Names pointing to nowhere (removed): 3 Pass 3a (looking for lost dir/files): ####### Pass 3a (lost+found pass) ######### Looking for lost directories: Flushing..finished23, 49 /sec Pass 4 - finished done 120496, 39 /sec Flushing..finished Syncing..finished ########### reiserfsck finished at Sat Jan 23 19:42:06 2010 ########### root@Tower:~# but when i reboot the server, the 2 disks still show up as unformatted
January 23, 201016 yr ran the rebuild-tree command, heres the result root@Tower:~# reiserfsck --rebuild-tree /dev/sdb1 reiserfsck 3.6.19 (2003 www.namesys.com) ************************************************************* ** Do not run the program with --rebuild-tree unless ** ** something is broken and MAKE A BACKUP before using it. ** ** If you have bad sectors on a drive it is usually a bad ** ** idea to continue using it. Then you probably should get ** ** a working hard drive, copy the file system from the bad ** ** drive to the good one -- dd_rescue is a good tool for ** ** that -- and only then run this program. ** ** 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 rebuild the filesystem (/dev/sdb1) tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Replaying journal.. Reiserfs journal '/dev/sdb1' in blocks [18..8211]: 0 transactions replayed ########### reiserfsck --rebuild-tree started at Sat Jan 23 17:07:05 2010 ########### Pass 0: ####### Pass 0 ####### Loading on-disk bitmap .. ok, 122492108 blocks marked used Skipping 19389 blocks (super block, journal, bitmaps) 122472719 blocks will be read 0%....20%. left 0, 19846 /seccc1042 directory entries were hashed with "r5" hash. "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 122472719 Leaves among those 120995 Objectids found 1044 Pass 1 (will try to insert 120995 leaves): ####### Pass 1 ####### Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....100% left 0, 101 /sec Flushing..finished 120995 leaves read 120995 inserted ####### Pass 2 ####### Flushing..finished Pass 3 (semantic): ####### Pass 3 ######### /TV Shows/Gilmore Girlsrebuild_semantic_pass: The entry [1040 1043] ("Season 1") in directory [64 1040] points to nowhere - is removed rebuild_semantic_pass: The entry [1040 1061] (".DS_Store") in directory [64 1040] points to nowhere - is removed vpf-10650: The directory [64 1040] has the wrong size in the StatData (104) - corrected to (48) /TV Shows/Family Guyrebuild_semantic_pass: The entry [1039 1041] ("Season 8") in directory [64 1039] points to nowhere - is removed vpf-10650: The directory [64 1039] has the wrong size in the StatData (72) - corrected to (48) Flushing..finished Files found: 927 Directories found: 114 Names pointing to nowhere (removed): 3 Pass 3a (looking for lost dir/files): ####### Pass 3a (lost+found pass) ######### Looking for lost directories: Flushing..finished23, 49 /sec Pass 4 - finished done 120496, 39 /sec Flushing..finished Syncing..finished ########### reiserfsck finished at Sat Jan 23 19:42:06 2010 ########### root@Tower:~# but when i reboot the server, the 2 disks still show up as unformatted The file-system-repair seems to have cleaned up a bunch of stuff. Now... post a new syslog. It is the only way to know what is happening.
January 25, 201016 yr does the log point to anything? It still shows that disk1 and disk4 were unable to be mounted because it did not detect a file-system on them. Jan 24 13:28:56 Tower emhttp: shcmd (13): mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1 >/dev/null 2>&1 Jan 24 13:28:56 Tower kernel: ReiserFS: md1: warning: sh-2006: read_super_block: bread failed (dev md1, block 2, size 4096) Jan 24 13:28:56 Tower kernel: ReiserFS: md1: warning: sh-2006: read_super_block: bread failed (dev md1, block 16, size 4096) Jan 24 13:28:56 Tower kernel: ReiserFS: md1: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on md1 Jan 24 13:28:56 Tower emhttp: shcmd (13): mount -t reiserfs -o noatime,nodiratime /dev/md4 /mnt/disk4 >/dev/null 2>&1 Jan 24 13:28:56 Tower kernel: ReiserFS: md4: warning: sh-2006: read_super_block: bread failed (dev md4, block 2, size 4096) Jan 24 13:28:56 Tower kernel: ReiserFS: md4: warning: sh-2006: read_super_block: bread failed (dev md4, block 16, size 4096) Jan 24 13:28:56 Tower kernel: ReiserFS: md4: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on md4 I'm a bit confused, since if the file-system check was successful, the disks should mount. Can you try the "mount" commands at the command line so we can see any error messages they emit. When unRAID does it, it sends the error messages to /dev/null so we cannot see them. Type mkdir /mnt/disk1 mkdir /mnt/disk4 mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1 mount -t reiserfs -o noatime,nodiratime /dev/md4 /mnt/disk4 Joe L.
January 26, 201016 yr Author heres the output root@Tower:~# mkdir /mnt/disk1 mkdir: cannot create directory `/mnt/disk1': File exists root@Tower:~# mkdir /mnt/disk4 root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1 mount: wrong fs type, bad option, bad superblock on /dev/md1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/md4 /mnt/disk4 mount: wrong fs type, bad option, bad superblock on /dev/md4, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so root@Tower:~#
January 26, 201016 yr Author i noticed there was a mysql dir in disk1, so thought that might have somethign to do with the error creating the disk1 dir, so uninstalled that, rebooted and heres the new output Linux 2.6.27.7-unRAID-Bubba. root@Tower:~# mkdir /mnt/disk1 root@Tower:~# mkdir /mnt/disk4 root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1 mount: wrong fs type, bad option, bad superblock on /dev/md1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/md4 /mnt/disk4 mount: wrong fs type, bad option, bad superblock on /dev/md4, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so root@Tower:~# syslog-2010-01-26.txt
January 26, 201016 yr i noticed there was a mysql dir in disk1, so thought that might have somethign to do with the error creating the disk1 dir, so uninstalled that, rebooted and heres the new output Linux 2.6.27.7-unRAID-Bubba. root@Tower:~# mkdir /mnt/disk1 root@Tower:~# mkdir /mnt/disk4 root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1 mount: wrong fs type, bad option, bad superblock on /dev/md1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so root@Tower:~# mount -t reiserfs -o noatime,nodiratime /dev/md4 /mnt/disk4 mount: wrong fs type, bad option, bad superblock on /dev/md4, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so root@Tower:~# I'm still trying to figure this out. Obviously, when accesed through the "md" device, the two disk partitions do not look like reiserfs file systems. Let's try first checking them once more with reiserfs on the raw disk partitions, then mounting the raw partitions. So once more a quick check. I expect no errors. reiserfsck /dev/sdb1 reiserfsck /dev/sde1 then, if no errors, try mounting them. mount -t reiserfs -o noatime,nodiratime /dev/sdb1 /mnt/disk1 mount -t reiserfs -o noatime,nodiratime /dev/sde1 /mnt/disk4 If they mount as /mnt/sde1, but not as /dev/md4, then we need to send Tom @lime-tech a PM/email to take a look at this thread...
Archived
This topic is now archived and is closed to further replies.