Treytor Posted June 2, 2011 Author Share Posted June 2, 2011 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 (204341248): (Input/output error). Aborted Hmm... Should I re-run HDD regenerator? Or does resiserfsck have something that will do the trick? Thanks again for your input, guys. Link to comment
Treytor Posted June 3, 2011 Author Share Posted June 3, 2011 === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green family Device Model: WDC WD15EADS-00S2B0 Serial Number: WD-WCAVY0907597 Firmware Version: 04.05G04 User Capacity: 1,500,301,910,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Thu Jun 2 18:51:27 2011 PDT 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 Error Recovery Control 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 193 193 051 Pre-fail Always - 774399 3 Spin_Up_Time 0x0027 179 139 021 Pre-fail Always - 8016 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1403 5 Reallocated_Sector_Ct 0x0033 159 159 140 Pre-fail Always - 326 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 083 083 000 Old_age Always - 12834 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 - 139 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 61 193 Load_Cycle_Count 0x0032 180 180 000 Old_age Always - 62798 194 Temperature_Celsius 0x0022 124 074 000 Old_age Always - 28 196 Reallocated_Event_Count 0x0032 001 001 000 Old_age Always - 292 197 Current_Pending_Sector 0x0032 197 195 000 Old_age Always - 939 198 Offline_Uncorrectable 0x0030 200 195 000 Old_age Offline - 30 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 - 105358 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. === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green family Device Model: WDC WD15EADS-00S2B0 Serial Number: WD-WCAVY0907597 Firmware Version: 04.05G04 User Capacity: 1,500,301,910,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Thu Jun 2 18:51:27 2011 PDT 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 Error Recovery Control 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 193 193 051 Pre-fail Always - 774399 3 Spin_Up_Time 0x0027 179 139 021 Pre-fail Always - 8016 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1403 5 Reallocated_Sector_Ct 0x0033 159 159 140 Pre-fail Always - 326 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 083 083 000 Old_age Always - 12834 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 - 139 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 61 193 Load_Cycle_Count 0x0032 180 180 000 Old_age Always - 62798 194 Temperature_Celsius 0x0022 124 074 000 Old_age Always - 28 196 Reallocated_Event_Count 0x0032 001 001 000 Old_age Always - 292 197 Current_Pending_Sector 0x0032 197 195 000 Old_age Always - 939 198 Offline_Uncorrectable 0x0030 200 195 000 Old_age Offline - 30 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 - 105358 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. Link to comment
dgaschk Posted June 3, 2011 Share Posted June 3, 2011 5 Reallocated_Sector_Ct 0x0033 159 159 140 Pre-fail Always - 326 197 Current_Pending_Sector 0x0032 197 195 000 Old_age Always - 939 The drive is dead. You can put it in a Windows machine with a reiserfs driver installed and see if you can save some data. When you pull this drive put the original disk19 back in and reset the config. Link to comment
Joe L. Posted June 3, 2011 Share Posted June 3, 2011 5 Reallocated_Sector_Ct 0x0033 159 159 140 Pre-fail Always - 326 197 Current_Pending_Sector 0x0032 197 195 000 Old_age Always - 939 The drive is dead. You can put it in a Windows machine with a reiserfs driver installed and see if you can save some data. When you pull this drive put the original disk19 back in and reset the config. There are 939 unreadable sectors... Very likely one (or more) or those is the reason the reiserfsck is aborting. One possibility, since you have a spare drive of the same size (or bigger), is to make a identical copy of the file system on the bad drive onto a good spare drive. The file system will still be corrupted, but all the sectors on it will be readable, so you might be able to run reiserfsck on the copy on the readable drive without it aborting. The command to perform the copy is dd if=/dev/sda1 of=/dev/md19 conv=noerror bs=1M This will copy from the raw device representing partition 1 of your failing disk to the "md" device of your spare drive. It will copy the 1.5TB file system as best it can onto the 2TB drive. (later, if you can recover your files, we can expand it to use the full 2TB of the drive, as initially it will be only using 1.5TB of the capacity as it is a image of the file-system from the smaller failing drive.) Once the "dd" command completes (and it will probably take 4 or 5 hours or more to copy the drive) you can then run reiserfsck on /dev/md19. Since the sectors are readable, it should be able to complete. Link to comment
Treytor Posted June 3, 2011 Author Share Posted June 3, 2011 YAReG doesn't recognize the drive in windows. The command to perform the copy is dd if=/dev/sda1 of=/dev/md19 conv=noerror bs=1M Trying this now. Thanks! Should I be worried that I am seeing activity on all the drives while this is happening? I stopped the data-rebuild after putting the bad drive back into its slot and putting the new 2 TB drive back into slot 19 (it recognizes this as a new drive.) I also don't completely understand how /dev/sda1 translates to the bad drive9? Wouldn't it be sda9? EDIT: I notice in the stats there are a lot of reads on drive 9, and writes on drive 19. So I guess we're good. Still don't understand why it's reading from all the other drives, however... Link to comment
Joe L. Posted June 3, 2011 Share Posted June 3, 2011 YAReG doesn't recognize the drive in windows. The command to perform the copy is dd if=/dev/sda1 of=/dev/md19 conv=noerror bs=1M Trying this now. Thanks! Should I be worried that I am seeing activity on all the drives while this is happening? I stopped the data-rebuild after putting the bad drive back into its slot and putting the new 2 TB drive back into slot 19 (it recognizes this as a new drive.) I also don't completely understand how /dev/sda1 translates to the bad drive9? Wouldn't it be sda9? EDIT: I notice in the stats there are a lot of reads on drive 9, and writes on drive 19. So I guess we're good. Still don't understand why it's reading from all the other drives, however... sda1 is the first partition on drive /dev/sda It is normally attached through the "md" drivers to /dev/md9, ans we probably could have read from /dev/md9, but I wanted to eliminate any additional overhead or any attempt from the "md" driver to deal with the read failures, therefore, it is reading from the raw drive. On the other hand, we are writing to drive /dev/md19 and to write to it the array has to calculate parity. That forces a read and write of at least the parity drive in addition to the drive assigned as disk19. As far as your question, /dev/sda9 would represent the 9th partition on disk "sda" unRAID only defines one partition per drive and no drive will have 9 partitions. I'm basing my suggested commands on the screen print you posted a few posts back. It showed disk19 as /dev/sdv. It showed disk9 as /dev/sda. We are NOT writing to the raw drive "sdv" since I want to attempt to keep parity correct, therefore, the "writes" are to the "md19" device. (of=/dev/md19) You will need to leave the telnet session open while the copy proceeds. When it is done, you'll get a final status report stating the number of bytes copies and the time it took. Joe L. Link to comment
Treytor Posted June 3, 2011 Author Share Posted June 3, 2011 Ah, okay I gotcha. I honestly think the parity is shot after all this that has been going down, and I'm okay with that at this point. The telnet session is still open and nothing has come up, but HDD activity is still going strong so I'll leave it until I see otherwise. Thanks again! Link to comment
Joe L. Posted June 3, 2011 Share Posted June 3, 2011 As I said, it will take a while. It should be getting close though about now. When it finishes doing the copy you can attempt the same "reiserfsck" commands, but this time using /dev/md19 instead of md9. I would start with a reiserfsck --check /dev/md19 and it will probably complain about either the bitmap, or superblock, or tree nodes being bad. Use its output to guide you as to what to run next. The commands will be working on the cloned copy of the defective disk, so there is nothing you can hurt unless you give the wrong drive as the argument to the command. Link to comment
Treytor Posted June 3, 2011 Author Share Posted June 3, 2011 I was going to post a status update of the progress, but like an idiot I highlighted the progress / errors and pressed CTRL+C in putty, which stopped the copy at 1.1 TB in. Remember kids, don't press CTRL+C to copy text from Putty. The more you know! Aaargh! Starting again Link to comment
Joe L. Posted June 3, 2011 Share Posted June 3, 2011 I was going to post a status update of the progress, but like an idiot I highlighted the progress / errors and pressed CTRL+C in putty, which stopped the copy at 1.1 TB in. Remember kids, don't press CTRL+C to copy text from Putty. The more you know! Aaargh! Starting again In "putty" highlighting text automatically copies it to the clipboard. No need to press ctl-C at all. In putty, the right mouse button pastes the copied content. Link to comment
Treytor Posted June 3, 2011 Author Share Posted June 3, 2011 Yeah, I know this but did it anyway. Force of habit Link to comment
Treytor Posted June 5, 2011 Author Share Posted June 5, 2011 I did reiserfsck --check /dev/md9 To repair any damage, and recover whatever is recoverable you'll need to do the following on /dev/md9 reiserfsck --fix-fixable /dev/md9 If it complains about a missing superblock, then reiserfsck --rebuild-sb /dev/md9 Then, you can try the --fix-fixable once more. Apparently you had one occasion where a --rebuild-tree did not complete. The --fix-fixable may just suggest you run --rebuild-tree as the next step, assuming it can find a valid superblock. reiserfsck will probably not let you run if is the disk is currently mounted, so before you do anything you'll probably need to do umount /mnt/disk9 All this needs to be done with the array "started" so do not stop it before the reiserfsck commands are run. After they are run, and after reiserfsck repairs any damage, then you can stop the array and re-start it and the disk should then mount. When you run the reiserfsck --rebuild-sb /dev/md9 command there will be a series of prompts. Answer as follows: 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 (b0894fe9-3850-4d57-b70b-a41 9cbf3823e) 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 Joe L. So I've managed to copy the contents of the bad drive 9 to 19. I started a reiserfsck --rebuild-sb /dev/md19, and it went for about 10 hours, but then it stopped complaining about another i/o error. Can I do that without it trying to maintain parity? (The parity is wrong anyway at this point). I notice because the array was running, it was reading all the disks as it was doing the scan, which includes the bad disk. I tried removing the bad drive and stopping the array and doing a reiserfsck --rebuild-sb /dev/md19, but it says there is no such file or directory. Thanks! Link to comment
Joe L. Posted June 5, 2011 Share Posted June 5, 2011 Since you don't think parity is good anyways, you can stop the array but then you'll need to run the reiserfsck on the first partition on the new drive. reiserfsck --rebuild-sb /dev/sdv1 parity will not be kept in sync, so expect to have many parity errors when you finally re-calculate it. Link to comment
Treytor Posted June 6, 2011 Author Share Posted June 6, 2011 reiserfsck --rebuild-sb /dev/sdv1 No such file or directory. Should it be sda1? Sorry I still don't understand how these drive / partitions and everything works. Link to comment
Treytor Posted June 6, 2011 Author Share Posted June 6, 2011 Okay, I did that and now it is asking me if I used resizer. I've never seen this question before, and not sure what I should answer. Link to comment
Treytor Posted June 6, 2011 Author Share Posted June 6, 2011 Yeah, but it's asking me if I used resizer, not what version of resizerfs... root@Cooper:~# reiserfsck --rebuild-sb /dev/sda1 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 Did you use resizer(y/n)[n]: Am I missing something really obvious here? Link to comment
Joe L. Posted June 6, 2011 Share Posted June 6, 2011 Yeah, but it's asking me if I used resizer, not what version of resizerfs... root@Cooper:~# reiserfsck --rebuild-sb /dev/sda1 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 Did you use resizer(y/n)[n]: Am I missing something really obvious here? Look at the example answers in my previous post. It showed the responses for all the questions, even for the "resizer" question. As far as it not asking the other questions, perhaps it fixed enough from your prior use where it did not need to ask those questions. Link to comment
Treytor Posted June 6, 2011 Author Share Posted June 6, 2011 I'm an idiot, sorry you're right it's late. Thank you for being patient with me! Now I'm not sure what this means... rebuild-sb: wrong block count occured (488378638), fixed (488378624) Reiserfs super block in block 16 on 0x801 of format 3.6 with standard journal Count of blocks on the device: 488378624 Number of bitmaps: 14905 Blocksize: 4096 Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 95211996 Root block: 39598604 Filesystem is clean Tree height: 5 Hash function used to sort names: "r5" Objectid map size 2, max 972 Journal parameters: Device [0x0] Magic [0x798af978] 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: 30063 UUID: 254bad47-7577-41b4-8aca-184b3dc82489 LABEL: Set flags in SB: ATTRIBUTES CLEAN Mount count: 160 Maximum mount count: Disabled. Run fsck.reiserfs( or use tunefs.reiserfs( to enable. Last fsck run: Never with a version that supports this feature. Check interval in days: Disabled. Run fsck.reiserfs( or use tunefs.reiserfs( to enable. Is this ok ? (y/n)[n]: Link to comment
Joe L. Posted June 6, 2011 Share Posted June 6, 2011 I'm an idiot, sorry you're right it's late. Thank you for being patient with me! Now I'm not sure what this means... rebuild-sb: wrong block count occured (488378638), fixed (488378624) Reiserfs super block in block 16 on 0x801 of format 3.6 with standard journal Count of blocks on the device: 488378624 Number of bitmaps: 14905 Blocksize: 4096 Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 95211996 Root block: 39598604 Filesystem is clean Tree height: 5 Hash function used to sort names: "r5" Objectid map size 2, max 972 Journal parameters: Device [0x0] Magic [0x798af978] 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: 30063 UUID: 254bad47-7577-41b4-8aca-184b3dc82489 LABEL: Set flags in SB: ATTRIBUTES CLEAN Mount count: 160 Maximum mount count: Disabled. Run fsck.reiserfs( or use tunefs.reiserfs( to enable. Last fsck run: Never with a version that supports this feature. Check interval in days: Disabled. Run fsck.reiserfs( or use tunefs.reiserfs( to enable. Is this ok ? (y/n)[n]: never seen it either, but then you probably have run the reiserfsck program many times more than me. I'd just answer no to both of those. They are internal counters to force a file-system check at periodic intervals. unRAID does not use that feature as far as I have ever seen It is encouraging though, as it seems you might be really close now. Joe L. Link to comment
Joe L. Posted June 6, 2011 Share Posted June 6, 2011 A quick question... Can you post the output of: ls -l /dev/disk/by-id Link to comment
Treytor Posted June 6, 2011 Author Share Posted June 6, 2011 When I say no, it says "Super block was not written" and quits. Here is the output of ls -l /dev/disk/by-id: root@Cooper:~# ls -l /dev/disk/by-id total 0 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 ata-Hitachi_HDT721010SLA360_STF604MR2903TP -> ../../sdq lrwxrwxrwx 1 root root 10 2011-06-05 09:48 ata-Hitachi_HDT721010SLA360_STF604MR2903TP-part1 -> ../../sdq1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 ata-Hitachi_HDT721010SLA360_STF604MR2B34XP -> ../../sdg lrwxrwxrwx 1 root root 10 2011-06-05 09:48 ata-Hitachi_HDT721010SLA360_STF604MR2B34XP-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 ata-Maxtor_6H500F0_H808PWZH -> ../../sdr lrwxrwxrwx 1 root root 10 2011-06-05 09:48 ata-Maxtor_6H500F0_H808PWZH-part1 -> ../../sdr1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 ata-SAMSUNG_HD204UI_S2H7J9BB116575 -> ../../sdu lrwxrwxrwx 1 root root 10 2011-06-05 09:48 ata-SAMSUNG_HD204UI_S2H7J9BB116575-part1 -> ../../sdu1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 ata-ST31000528AS_6VP25KSJ -> ../../sdf lrwxrwxrwx 1 root root 10 2011-06-05 09:48 ata-ST31000528AS_6VP25KSJ-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 2011-06-05 09:47 ata-ST32000542AS_5XW16QBX -> ../../sdd lrwxrwxrwx 1 root root 10 2011-06-05 09:47 ata-ST32000542AS_5XW16QBX-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2011-06-05 09:47 ata-ST32000542AS_5XW1XKYR -> ../../sdb lrwxrwxrwx 1 root root 10 2011-06-05 09:47 ata-ST32000542AS_5XW1XKYR-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2011-06-05 09:47 ata-ST32000542AS_5XW1XP9F -> ../../sda lrwxrwxrwx 1 root root 10 2011-06-06 10:34 ata-ST32000542AS_5XW1XP9F-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 ata-ST3750640AS_3QD0Q9TR -> ../../sdj lrwxrwxrwx 1 root root 10 2011-06-05 09:48 ata-ST3750640AS_3QD0Q9TR-part1 -> ../../sdj1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 ata-ST3750640AS_3QD0QBLC -> ../../sdi lrwxrwxrwx 1 root root 10 2011-06-05 09:48 ata-ST3750640AS_3QD0QBLC-part1 -> ../../sdi1 lrwxrwxrwx 1 root root 9 2011-06-05 09:47 ata-ST9160314AS_5VCJZTJC -> ../../sde lrwxrwxrwx 1 root root 10 2011-06-05 09:47 ata-ST9160314AS_5VCJZTJC-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 ata-WDC_WD10EACS-00D6B1_WD-WCAU45550258 -> ../../sdh lrwxrwxrwx 1 root root 10 2011-06-05 09:48 ata-WDC_WD10EACS-00D6B1_WD-WCAU45550258-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 ata-WDC_WD15EADS-00S2B0_WD-WCAVY0776356 -> ../../sdo lrwxrwxrwx 1 root root 10 2011-06-05 09:48 ata-WDC_WD15EADS-00S2B0_WD-WCAVY0776356-part1 -> ../../sdo1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 ata-WDC_WD15EARS-00Z5B1_WD-WCAVU0452333 -> ../../sdn lrwxrwxrwx 1 root root 10 2011-06-05 09:48 ata-WDC_WD15EARS-00Z5B1_WD-WCAVU0452333-part1 -> ../../sdn1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 ata-WDC_WD15EARS-00Z5B1_WD-WMAVU3012356 -> ../../sdp lrwxrwxrwx 1 root root 10 2011-06-05 09:48 ata-WDC_WD15EARS-00Z5B1_WD-WMAVU3012356-part1 -> ../../sdp1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1817430 -> ../../sdt lrwxrwxrwx 1 root root 10 2011-06-05 09:48 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1817430-part1 -> ../../sdt1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 ata-WDC_WD5000AAJS-22TKA0_WD-WCAPW5449900 -> ../../sds lrwxrwxrwx 1 root root 10 2011-06-05 09:48 ata-WDC_WD5000AAJS-22TKA0_WD-WCAPW5449900-part1 -> ../../sds1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 ata-WDC_WD5000AAJS-22TKA0_WD-WCAPW5639136 -> ../../sdm lrwxrwxrwx 1 root root 10 2011-06-05 09:48 ata-WDC_WD5000AAJS-22TKA0_WD-WCAPW5639136-part1 -> ../../sdm1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 ata-WDC_WD5000AAKS-00A7B0_WD-WCASY0208552 -> ../../sdk lrwxrwxrwx 1 root root 10 2011-06-05 09:48 ata-WDC_WD5000AAKS-00A7B0_WD-WCASY0208552-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 ata-WDC_WD5000KS-00MNB0_WD-WCANU1255870 -> ../../sdl lrwxrwxrwx 1 root root 10 2011-06-05 09:48 ata-WDC_WD5000KS-00MNB0_WD-WCANU1255870-part1 -> ../../sdl1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 scsi-SATA_Hitachi_HDT7210_STF604MR2903TP -> ../../sdq lrwxrwxrwx 1 root root 10 2011-06-05 09:48 scsi-SATA_Hitachi_HDT7210_STF604MR2903TP-part1 -> ../../sdq1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 scsi-SATA_Hitachi_HDT7210_STF604MR2B34XP -> ../../sdg lrwxrwxrwx 1 root root 10 2011-06-05 09:48 scsi-SATA_Hitachi_HDT7210_STF604MR2B34XP-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 scsi-SATA_Maxtor_6H500F0_H808PWZH -> ../../sdr lrwxrwxrwx 1 root root 10 2011-06-05 09:48 scsi-SATA_Maxtor_6H500F0_H808PWZH-part1 -> ../../sdr1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 scsi-SATA_SAMSUNG_HD204UIS2H7J9BB116575 -> ../../sdu lrwxrwxrwx 1 root root 10 2011-06-05 09:48 scsi-SATA_SAMSUNG_HD204UIS2H7J9BB116575-part1 -> ../../sdu1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 scsi-SATA_ST31000528AS_6VP25KSJ -> ../../sdf lrwxrwxrwx 1 root root 10 2011-06-05 09:48 scsi-SATA_ST31000528AS_6VP25KSJ-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 2011-06-05 09:47 scsi-SATA_ST32000542AS_5XW16QBX -> ../../sdd lrwxrwxrwx 1 root root 10 2011-06-05 09:47 scsi-SATA_ST32000542AS_5XW16QBX-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2011-06-05 09:47 scsi-SATA_ST32000542AS_5XW1XKYR -> ../../sdb lrwxrwxrwx 1 root root 10 2011-06-05 09:47 scsi-SATA_ST32000542AS_5XW1XKYR-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2011-06-05 09:47 scsi-SATA_ST32000542AS_5XW1XP9F -> ../../sda lrwxrwxrwx 1 root root 10 2011-06-06 10:34 scsi-SATA_ST32000542AS_5XW1XP9F-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 scsi-SATA_ST3750640AS_3QD0Q9TR -> ../../sdj lrwxrwxrwx 1 root root 10 2011-06-05 09:48 scsi-SATA_ST3750640AS_3QD0Q9TR-part1 -> ../../sdj1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 scsi-SATA_ST3750640AS_3QD0QBLC -> ../../sdi lrwxrwxrwx 1 root root 10 2011-06-05 09:48 scsi-SATA_ST3750640AS_3QD0QBLC-part1 -> ../../sdi1 lrwxrwxrwx 1 root root 9 2011-06-05 09:47 scsi-SATA_ST9160314AS_5VCJZTJC -> ../../sde lrwxrwxrwx 1 root root 10 2011-06-05 09:47 scsi-SATA_ST9160314AS_5VCJZTJC-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 scsi-SATA_WDC_WD10EACS-00_WD-WCAU45550258 -> ../../sdh lrwxrwxrwx 1 root root 10 2011-06-05 09:48 scsi-SATA_WDC_WD10EACS-00_WD-WCAU45550258-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 scsi-SATA_WDC_WD15EADS-00_WD-WCAVY0776356 -> ../../sdo lrwxrwxrwx 1 root root 10 2011-06-05 09:48 scsi-SATA_WDC_WD15EADS-00_WD-WCAVY0776356-part1 -> ../../sdo1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 scsi-SATA_WDC_WD15EARS-00_WD-WCAVU0452333 -> ../../sdn lrwxrwxrwx 1 root root 10 2011-06-05 09:48 scsi-SATA_WDC_WD15EARS-00_WD-WCAVU0452333-part1 -> ../../sdn1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 scsi-SATA_WDC_WD15EARS-00_WD-WMAVU3012356 -> ../../sdp lrwxrwxrwx 1 root root 10 2011-06-05 09:48 scsi-SATA_WDC_WD15EARS-00_WD-WMAVU3012356-part1 -> ../../sdp1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1817430 -> ../../sdt lrwxrwxrwx 1 root root 10 2011-06-05 09:48 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1817430-part1 -> ../../sdt1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 scsi-SATA_WDC_WD5000AAJS-_WD-WCAPW5449900 -> ../../sds lrwxrwxrwx 1 root root 10 2011-06-05 09:48 scsi-SATA_WDC_WD5000AAJS-_WD-WCAPW5449900-part1 -> ../../sds1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 scsi-SATA_WDC_WD5000AAJS-_WD-WCAPW5639136 -> ../../sdm lrwxrwxrwx 1 root root 10 2011-06-05 09:48 scsi-SATA_WDC_WD5000AAJS-_WD-WCAPW5639136-part1 -> ../../sdm1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 scsi-SATA_WDC_WD5000AAKS-_WD-WCASY0208552 -> ../../sdk lrwxrwxrwx 1 root root 10 2011-06-05 09:48 scsi-SATA_WDC_WD5000AAKS-_WD-WCASY0208552-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 scsi-SATA_WDC_WD5000KS-00_WD-WCANU1255870 -> ../../sdl lrwxrwxrwx 1 root root 10 2011-06-05 09:48 scsi-SATA_WDC_WD5000KS-00_WD-WCANU1255870-part1 -> ../../sdl1 lrwxrwxrwx 1 root root 9 2011-06-05 09:47 usb-Generic_Flash_Disk_12345678-0:0 -> ../../sdc lrwxrwxrwx 1 root root 10 2011-06-05 09:47 usb-Generic_Flash_Disk_12345678-0:0-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 wwn-0x5000c5001b8ee506 -> ../../sdf lrwxrwxrwx 1 root root 10 2011-06-05 09:48 wwn-0x5000c5001b8ee506-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 2011-06-05 09:47 wwn-0x5000c5002823985e -> ../../sde lrwxrwxrwx 1 root root 10 2011-06-05 09:47 wwn-0x5000c5002823985e-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2011-06-05 09:47 wwn-0x5000c5002a5fac63 -> ../../sdd lrwxrwxrwx 1 root root 10 2011-06-05 09:47 wwn-0x5000c5002a5fac63-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2011-06-05 09:47 wwn-0x5000c5002e95a9fa -> ../../sda lrwxrwxrwx 1 root root 10 2011-06-06 10:34 wwn-0x5000c5002e95a9fa-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 2011-06-05 09:47 wwn-0x5000c5002e96899f -> ../../sdb lrwxrwxrwx 1 root root 10 2011-06-05 09:47 wwn-0x5000c5002e96899f-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 wwn-0x5000cca349e046ce -> ../../sdq lrwxrwxrwx 1 root root 10 2011-06-05 09:48 wwn-0x5000cca349e046ce-part1 -> ../../sdq1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 wwn-0x5000cca349e13af2 -> ../../sdg lrwxrwxrwx 1 root root 10 2011-06-05 09:48 wwn-0x5000cca349e13af2-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 wwn-0x50014ee0ad28bceb -> ../../sdt lrwxrwxrwx 1 root root 10 2011-06-05 09:48 wwn-0x50014ee0ad28bceb-part1 -> ../../sdt1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 wwn-0x50014ee2036f3b10 -> ../../sdo lrwxrwxrwx 1 root root 10 2011-06-05 09:48 wwn-0x50014ee2036f3b10-part1 -> ../../sdo1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 wwn-0x50014ee256073bfe -> ../../sdm lrwxrwxrwx 1 root root 10 2011-06-05 09:48 wwn-0x50014ee256073bfe-part1 -> ../../sdm1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 wwn-0x50014ee256074866 -> ../../sds lrwxrwxrwx 1 root root 10 2011-06-05 09:48 wwn-0x50014ee256074866-part1 -> ../../sds1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 wwn-0x50014ee2aab30590 -> ../../sdl lrwxrwxrwx 1 root root 10 2011-06-05 09:48 wwn-0x50014ee2aab30590-part1 -> ../../sdl1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 wwn-0x50014ee2ac0c87f7 -> ../../sdk lrwxrwxrwx 1 root root 10 2011-06-05 09:48 wwn-0x50014ee2ac0c87f7-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 wwn-0x50014ee2ad02481a -> ../../sdh lrwxrwxrwx 1 root root 10 2011-06-05 09:48 wwn-0x50014ee2ad02481a-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 wwn-0x50014ee2aeef39f1 -> ../../sdn lrwxrwxrwx 1 root root 10 2011-06-05 09:48 wwn-0x50014ee2aeef39f1-part1 -> ../../sdn1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 wwn-0x50014ee6555d2ea8 -> ../../sdp lrwxrwxrwx 1 root root 10 2011-06-05 09:48 wwn-0x50014ee6555d2ea8-part1 -> ../../sdp1 lrwxrwxrwx 1 root root 9 2011-06-05 09:48 wwn-0x50024e92044a57e3 -> ../../sdu lrwxrwxrwx 1 root root 10 2011-06-05 09:48 wwn-0x50024e92044a57e3-part1 -> ../../sdu1 Link to comment
Joe L. Posted June 6, 2011 Share Posted June 6, 2011 When I say no, it says "Super block was not written" and quits. I guess you need to answer "y" then. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.