July 24, 201411 yr I am sometimes confused by some of the terminology since it is often used very inconsistently by many users. For example, I said parity sync earlier because in my mind, a correcting parity check, which is what you get if you have an unsafe shutdown, is functionally equivalent to a parity rebuild. So, is it a sync or a check? I also wonder if there are not additional undiagnosed problems since the array may have had some neglect. Additional undiagnosed problems might or might not affect recovery depending on the method. A syslog would perhaps put that to rest somewhat, but we haven't got one yet. ColonialRaptor, the syslog is just a text file. You can open it in a text editor and manually break it into smaller pieces, zip them separately, and then attach them to one or more posts.
July 24, 201411 yr I am sometimes confused by some of the terminology since it is often used very inconsistently by many users. For example, I said parity sync earlier because in my mind, a correcting parity check, which is what you get if you have an unsafe shutdown, is functionally equivalent to a parity rebuild. So, is it a sync or a check? A parity rebuild is functionally the same as a parity sync (A.K.A parity build). The difference is that a parity rebuild is triggered differently (by replacing the parity disk), and when you are doing a parity rebuild, you cannot make other array composition changes (e.g., add or remove disks to the array). If you want to rebuild (upsize) parity AND add the old parity disk as a data disk without preclearing it, you can do the new config, reassign all the disks in the array including the new parity and the old parity in the next data slot, DO NOT select trust parity, and start the array. Parity will rebuild onto the new parity disk with the configured disks. This is explained in more detail in my sig link about replacing parity.
July 24, 201411 yr OT for the OP ... If you want to rebuild (upsize) parity AND add the old parity disk as a data disk without preclearing it, you can do the new config, reassign all the disks in the array including the new parity and the old parity in the next data slot, DO NOT select trust parity, and start the array. Parity will rebuild onto the new parity disk with the configured disks. This is explained in more detail in my sig link about replacing parity. I understand why this would work, but I have never done it that way. I have done another preclear of the old parity before adding it as data. At what point in your process does the formatting of the old parity (new data) disk to ReiserFS happen? I assume unRAID would tell you the new data (old parity) disk was unformatted and you would wait until after the new parity build was complete to format it. Is that right?
July 24, 201411 yr OT for the OP ... If you want to rebuild (upsize) parity AND add the old parity disk as a data disk without preclearing it, you can do the new config, reassign all the disks in the array including the new parity and the old parity in the next data slot, DO NOT select trust parity, and start the array. Parity will rebuild onto the new parity disk with the configured disks. This is explained in more detail in my sig link about replacing parity. I understand why this would work, but I have never done it that way. I have done another preclear of the old parity before adding it as data. At what point in your process does the formatting of the old parity (new data) disk to ReiserFS happen? I assume unRAID would tell you the new data (old parity) disk was unformatted and you would wait until after the new parity build was complete to format it. Is that right? Exactly right. And if for some reason a drive fails during the new parity build, you can restore the old disk config files and effectively recover. All this is laid out in my "how to" post linked in my sig.
July 25, 201411 yr Author Thanks for the replies guys. I'm sorry I reacted the way I did bjp I just felt like I was being told "yep you screwed up" over and over again instead of receiving any meaningful help (not directed towards you trurl you've been trying to help so thanks). Okay.. I've managed to get my current syslog to zip to an acceptable size and I attached it here. It seems there are a lot of error's regarding disk 3. It looks nasty and I'm thinking there is not a lot of chance than I'm going to be able to recover it. With regards to the temperature of the drives I imagine that has something to do with them all being crammed into the small area inside the case and heating each other up? Is there anything I can try and do to cool them down other than moving them apart from one another? I don't know if I have the space to move them around at the moment but I'll see whether I can put it together in a better way. I was meaning to ask about the heat as well. I hadn't noticed it being so hot before. bjp you asked about my parity drive. What happened was this: 1. I was having problems with my server on version 4.9 the unmenu was crashing, but everything else was working fine. Happened out of no where, had been running fine for a long time. 2. I upgraded the server from 4.9 to the most recent stable version. 3. I couldn't access all my files because I hadn't created a user share, but stupidly I thought it was a file tree problem so I ran reiserfsck --rebuild-tree on disk 3 because it told me too. I believe this drive is dying. 4. At this point I had a valid parity drive syncs and checked. 5. I realised that the reason I was having trouble creating a user was because I had spaces in the "description area" which was causing the user share not to create. I created a user and restarted the server using the webgui option. At this point drive 3 was showing "unformatted". 6. When the server restarted it started a parity sync which is promply cancelled because I thought this would remove the parities ability to restore any data from drive 3 because it was syncing the array with an unformatted drive (and hence removing that data from the parity) so it was cancelled and I now have an invalid parity. I haven't re-mounted my parity drive yet as I am waiting to figure out what to do with drive 3. That is basically where I am at. I have notice the possibility of spinrite but I would need someone to tell me what I need to do in order to use this properly. I have done a surface search of the server and I can't tell exactly what I am missing at the moment, but I don't think I have lost anything crucial but I would like to have it all back IF possible. I do not believe I can restore from parity because the parity is currently "invalid". When I go to the 'stats' page on the webgui it shows that drive 3 is full up... Basically I need to know this information: What will happen if I run a full parity sync now while the drive is showing unformatted but contains data? Will the parity drive keep that data? If so can I rebuild that drive with my new 2tb? Is there something more wrong with my array / server that I'm not aware of (syslog?)... Is there anything I can do to save disk 3? Is there a way to restory the parity sync back to the previous sync it had before the one that I cancelled? Should I be doing anything to my array to re-allocate the files so that it's not so "full up"... syslog-2014-07-25.zip
July 25, 201411 yr Thanks for the replies guys. I'm sorry I reacted the way I did bjp I just felt like I was being told "yep you screwed up" over and over again instead of receiving any meaningful help (not directed towards you trurl you've been trying to help so thanks). I know, but to help you recover people need info. You may think saying - "I followed these instructions and it was a mistake" tells people something and that asking about it is rubbing your nose in it. But the truth is rebuilding the stick would not have caused you to lose data. As unpleasant as it may seem, you have to relive it over and over and tell every ugly little detail of what you did that got you to a certain point. Dgaschk is very adept with these kinds of issues. If anyone can get help, he can. Suggest you follow his suggestions. Do what he says - no more no less. If you have to go to the bathroom, ask first. (In other words, don't to anything additional even if you think it is common sense without confirming).
July 26, 201411 yr Author Thanks for the replies guys. I'm sorry I reacted the way I did bjp I just felt like I was being told "yep you screwed up" over and over again instead of receiving any meaningful help (not directed towards you trurl you've been trying to help so thanks). I know, but to help you recover people need info. You may think saying - "I followed these instructions and it was a mistake" tells people something and that asking about it is rubbing your nose in it. But the truth is rebuilding the stick would not have caused you to lose data. As unpleasant as it may seem, you have to relive it over and over and tell every ugly little detail of what you did that got you to a certain point. Dgaschk is very adept with these kinds of issues. If anyone can get help, he can. Suggest you follow his suggestions. Do what he says - no more no less. If you have to go to the bathroom, ask first. (In other words, don't to anything additional even if you think it is common sense without confirming). Oh I don't disagree that there is something wrong with disk 3 that is outside all of this. It has bad blocks or something and that is what made the reiserfsck command fail and got me to the point where I am at the moment. What I want to try and do is get it to be part of the array again and get it's data into the parity (if I'm lucky) then I've got another 2TB drive ready to replace it with. I know it's gone, it's the oldest drive I've got I've had it for about 5 years and it had been cropping up with numbers in the "errors" column for a little while now. Extended SMART Self Test is under way - it's 60% completed. I will post the results when it is done. I will not do anything without being told to do it first and absolutely no more outbursts. By the way. I bought one of these: It's got a fan directly on the drives so it would be okay to move three drives there yes? Then I should try and leave a space between all of the other drives so that they are not radiating heat directly at the other drives amiright? I think I have some other fans lying around. Would you suggest putting them in the case blowing over the other drives as well? Noise isn't an issue so there is probably no reason not too...
July 26, 201411 yr Extended SMART Self Test is under way - it's 60% completed. I will post the results when it is done.You probably don't want to hear this, especially not from me, since I set you off to begin with, but that is not what you were asked to do. Paste a SMART report for disk 3. A smart report checks what is currently in the drive's memory that pertains to health and other statistics. A smart test tells the drive to exercise itself to check for errors, and record the results of the test in the smart data. There is no need to do a test to get the report, it's a different but related function.
July 26, 201411 yr Author Extended SMART Self Test is under way - it's 60% completed. I will post the results when it is done.You probably don't want to hear this, especially not from me, since I set you off to begin with, but that is not what you were asked to do. Paste a SMART report for disk 3. A smart report checks what is currently in the drive's memory that pertains to health and other statistics. A smart test tells the drive to exercise itself to check for errors, and record the results of the test in the smart data. There is no need to do a test to get the report, it's a different but related function. Heh... Nah it's alright dude I was probably too touchy the other day. I'm sorry for lashing out. So should I have not run a SMART Test? I didn't think there was any way to get any other details other than to actually run the test - there was no other useful information that I could see. Was it the Disk Self Test Log or the Disk error log that I was supposed to have supplied? Where do I get a simply "SMART report" from if it's not the test I had no idea they were different things... The test has been sitting at 90% for a couple of hours now... should I allow it to keep going or cancel that test?
July 26, 201411 yr Where do I get a simply "SMART report" from if it's not the test I had no idea they were different things...Read this and post back what you think you should type to get the desired results. Don't actually do it yet, I don't want you to jump to more conclusions. http://lime-technology.com/wiki/index.php/Troubleshooting#Obtaining_a_SMART_report As to cancelling the self test, I'm not aware of a way to cancel it, it's just a request made to the drive to do the test internally. Can you post a screen shot of what you are talking about?
July 27, 201411 yr Author Okay so the SMART test completed "without error". In terms of the SMART Report, I didn't have to run anything to get this, but I believe this might be what you're looking for.. ATA Error Count: 3818 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 3818 occurred at disk power-on lifetime: 37271 hours (1552 days + 23 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 78 e0 18 e0 Error: UNC at LBA = 0x0018e078 = 1630328 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 78 e0 18 00 08 7d+04:13:49.583 READ DMA EXT ec 00 01 00 00 00 00 08 7d+04:13:49.583 IDENTIFY DEVICE 25 00 00 78 dc 18 00 08 7d+04:13:49.497 READ DMA EXT e5 00 00 00 00 00 00 08 7d+04:13:49.497 CHECK POWER MODE 25 00 00 78 d8 18 00 08 7d+04:13:48.393 READ DMA EXT Error 3817 occurred at disk power-on lifetime: 37269 hours (1552 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 78 20 2d e0 Error: UNC at LBA = 0x002d2078 = 2957432 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 78 20 2d 00 08 7d+02:56:10.588 READ DMA EXT 25 00 00 78 1c 2d 00 08 7d+02:56:05.815 READ DMA EXT ec 00 01 00 00 00 00 08 7d+02:56:05.814 IDENTIFY DEVICE 25 00 00 78 18 2d 00 08 7d+02:56:05.664 READ DMA EXT 25 00 00 78 14 2d 00 08 7d+02:56:05.481 READ DMA EXT Error 3816 occurred at disk power-on lifetime: 37222 hours (1550 days + 22 hours) When the command that caused the error occurred, the device was doing SMART Offline or Self-test. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 78 0c 2d e0 Error: UNC at LBA = 0x002d0c78 = 2952312 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 78 0c 2d 00 08 5d+03:28:40.346 READ DMA EXT ec 00 01 00 00 00 00 08 5d+03:28:40.346 IDENTIFY DEVICE 25 00 00 78 08 2d 00 08 5d+03:28:39.962 READ DMA EXT 25 00 00 78 04 2d 00 08 5d+03:28:35.622 READ DMA EXT 25 00 00 78 00 2d 00 08 5d+03:28:33.728 READ DMA EXT Error 3815 occurred at disk power-on lifetime: 37221 hours (1550 days + 21 hours) When the command that caused the error occurred, the device was doing SMART Offline or Self-test. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 78 80 19 e0 Error: UNC at LBA = 0x00198078 = 1671288 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 78 80 19 00 08 5d+02:59:22.860 READ DMA EXT ec 00 01 00 00 00 00 08 5d+02:59:22.859 IDENTIFY DEVICE 25 00 00 78 7c 19 00 08 5d+02:59:22.697 READ DMA EXT e5 00 00 00 00 00 00 08 5d+02:59:22.697 CHECK POWER MODE 25 00 00 78 78 19 00 08 5d+02:59:22.579 READ DMA EXT Error 3814 occurred at disk power-on lifetime: 37220 hours (1550 days + 20 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 40 f8 2d e0 Error: UNC at LBA = 0x002df840 = 3012672 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 40 f8 2d 00 08 5d+01:59:55.005 READ DMA EXT 25 00 00 40 f4 2d 00 08 5d+01:59:54.858 READ DMA EXT b0 d1 01 01 4f c2 00 08 5d+01:59:54.854 SMART READ ATTRIBUTE THRESHOLDS [OBS-4] 25 00 00 40 f0 2d 00 08 5d+01:59:50.102 READ DMA EXT 25 00 00 40 ec 2d 00 08 5d+01:59:49.119 READ DMA EXT
July 27, 201411 yr Okay so the SMART test completed "without error". In terms of the SMART Report, I didn't have to run anything to get this, but I believe this might be what you're looking for.. ATA Error Count: 3818 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 3818 occurred at disk power-on lifetime: 37271 hours (1552 days + 23 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 78 e0 18 e0 Error: UNC at LBA = 0x0018e078 = 1630328 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 78 e0 18 00 08 7d+04:13:49.583 READ DMA EXT ec 00 01 00 00 00 00 08 7d+04:13:49.583 IDENTIFY DEVICE 25 00 00 78 dc 18 00 08 7d+04:13:49.497 READ DMA EXT e5 00 00 00 00 00 00 08 7d+04:13:49.497 CHECK POWER MODE 25 00 00 78 d8 18 00 08 7d+04:13:48.393 READ DMA EXT Error 3817 occurred at disk power-on lifetime: 37269 hours (1552 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 78 20 2d e0 Error: UNC at LBA = 0x002d2078 = 2957432 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 78 20 2d 00 08 7d+02:56:10.588 READ DMA EXT 25 00 00 78 1c 2d 00 08 7d+02:56:05.815 READ DMA EXT ec 00 01 00 00 00 00 08 7d+02:56:05.814 IDENTIFY DEVICE 25 00 00 78 18 2d 00 08 7d+02:56:05.664 READ DMA EXT 25 00 00 78 14 2d 00 08 7d+02:56:05.481 READ DMA EXT Error 3816 occurred at disk power-on lifetime: 37222 hours (1550 days + 22 hours) When the command that caused the error occurred, the device was doing SMART Offline or Self-test. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 78 0c 2d e0 Error: UNC at LBA = 0x002d0c78 = 2952312 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 78 0c 2d 00 08 5d+03:28:40.346 READ DMA EXT ec 00 01 00 00 00 00 08 5d+03:28:40.346 IDENTIFY DEVICE 25 00 00 78 08 2d 00 08 5d+03:28:39.962 READ DMA EXT 25 00 00 78 04 2d 00 08 5d+03:28:35.622 READ DMA EXT 25 00 00 78 00 2d 00 08 5d+03:28:33.728 READ DMA EXT Error 3815 occurred at disk power-on lifetime: 37221 hours (1550 days + 21 hours) When the command that caused the error occurred, the device was doing SMART Offline or Self-test. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 78 80 19 e0 Error: UNC at LBA = 0x00198078 = 1671288 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 78 80 19 00 08 5d+02:59:22.860 READ DMA EXT ec 00 01 00 00 00 00 08 5d+02:59:22.859 IDENTIFY DEVICE 25 00 00 78 7c 19 00 08 5d+02:59:22.697 READ DMA EXT e5 00 00 00 00 00 00 08 5d+02:59:22.697 CHECK POWER MODE 25 00 00 78 78 19 00 08 5d+02:59:22.579 READ DMA EXT Error 3814 occurred at disk power-on lifetime: 37220 hours (1550 days + 20 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 40 f8 2d e0 Error: UNC at LBA = 0x002df840 = 3012672 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 40 f8 2d 00 08 5d+01:59:55.005 READ DMA EXT 25 00 00 40 f4 2d 00 08 5d+01:59:54.858 READ DMA EXT b0 d1 01 01 4f c2 00 08 5d+01:59:54.854 SMART READ ATTRIBUTE THRESHOLDS [OBS-4] 25 00 00 40 f0 2d 00 08 5d+01:59:50.102 READ DMA EXT 25 00 00 40 ec 2d 00 08 5d+01:59:49.119 READ DMA EXT These types of errors indicate a cabling problem. And these errors will NEVER clear. You will see them for the life of the drive. Note that the most recent happened at 37271 powered on hours. You can compare that the current powered on hours to see how recent the error occurred. And if you see a more recent one pop up, you know the issue isn't fixed.
July 28, 201411 yr Author Okay... So if I replace the cable will that help? Can you tell me any advice about what to do with the drive to try and get it functioning again long enough to get the data into the parity so I can replace the drive?
July 28, 201411 yr Only the bottom half of the SMART report has been posted. Need the entire report to advise. The command "smartctl -a /dev/sdd" should work; but first verify that the disk 3 device label is still "sdd". These labels may change when rebooting.
July 28, 201411 yr Okay... So if I replace the cable will that help? Can you tell me any advice about what to do with the drive to try and get it functioning again long enough to get the data into the parity so I can replace the drive? This question doesn't compute. You can't get a drive's data into parity. Parity is computed based on a set of drives. Then. If one of them dies, it's contents can be rebuilt onto a replacement drive using parity +.every other drive that was in the array. Parity alone is worthless.
July 29, 201411 yr Author Here is the other part I assume? Sorry bjp... What I mean is that I want to get the drive accessible so I can put the parity drive back into the array, run a parity sync so that when I remove this drive I can restore it's data back onto the new drive.
July 29, 201411 yr See here: http://lime-technology.com/wiki/index.php/Troubleshooting#Resolving_a_Pending_Sector
July 29, 201411 yr This drive has 604 pending sectors. That means 604 sectors that the drive has detected as unreadable or badly damaged. The other errors ATA errors in your prior post indicate cabling problems, but cabling problems cannot cause pending sectors. So it is likely you have both problems simultaneously. My guess is the drive is failing or has failed. When an array disk fails (detected by a write failure), the array can still be used. The failed or missing disk will be simulated using all of the other disks + parity. You can then remove the failed disk, replace it with a fresh disk, and rebuild it. That is the way it is supposed to work. To be of any help I need to understand the state of your array. I suggest you boot into safe mode (boot from the memory stick and select the safe mode boot option from the boot menu). Then open the Web GUI, and take a screen shot. Sorry bjp... What I mean is that I want to get the drive accessible so I can put the parity drive back into the array, run a parity sync so that when I remove this drive I can restore it's data back onto the new drive. This makes no sense to me. Is parity not in the array? I am totally confused and unless I understand precisely the situation I cannot help.
July 29, 201411 yr He removed parity earlier to "preserve" it, but he had already done rebuild-tree on the md device.
July 30, 201411 yr Author I don't have a valid parity at the moment... I removed it from the array after it automatically tried to update and I cancelled the sync... so I have a currently "invalid" parity and can't use that to restore the drive... This is why I want to try and access the data on drive 3 which has been messed up with --rebuild-tree, that isn't what the problem is but it is the reason it is showing "unformatted" to me because it didn't complete the rebuild tree. Does that make more sense? I don't know how else to explain it.
July 30, 201411 yr The array operates as a unit. If you lose one drive it can be rebuilt with the other drives (all of them, including parity). But if you removed parity and wrote to a drive you will never get the drives synced again so that they can restore the missing drive. Sorry.
July 31, 201411 yr Author I know. What I'm trying to do is get the missing drive running to a point where it won't say "unformatted" any more so I can rebuild it as a whole (with the almost dead drive). I'm hoping it could have enough left in it to do this just so I can get a parity sync done and then replace the drive. So, that's why I'm asking about what to do when a drive is showing "unformatted" after --rebuild-tree failed to run because there are damaged blocks. From what I've read it seems like Spinrite might be my only chance / solution but I have no idea how to use that program to try and fix (I don't know if fix is the right word) those damaged blocks.
July 31, 201411 yr I know. What I'm trying to do is get the missing drive running to a point where it won't say "unformatted" any more so I can rebuild it as a whole (with the almost dead drive). I'm hoping it could have enough left in it to do this just so I can get a parity sync done and then replace the drive. So, that's why I'm asking about what to do when a drive is showing "unformatted" after --rebuild-tree failed to run because there are damaged blocks. From what I've read it seems like Spinrite might be my only chance / solution but I have no idea how to use that program to try and fix (I don't know if fix is the right word) those damaged blocks. Ok - I think you may just be saying it wrong. You are trying to repair your bad secter so that you can re-run reiserfsck and access the data off of the drive. That is not a rebuild. A rebuild it when you use parity and the other disks to reconstruct a bad disk. Read about a tool called badblocks.
August 2, 201411 yr Author I know. What I'm trying to do is get the missing drive running to a point where it won't say "unformatted" any more so I can rebuild it as a whole (with the almost dead drive). I'm hoping it could have enough left in it to do this just so I can get a parity sync done and then replace the drive. So, that's why I'm asking about what to do when a drive is showing "unformatted" after --rebuild-tree failed to run because there are damaged blocks. From what I've read it seems like Spinrite might be my only chance / solution but I have no idea how to use that program to try and fix (I don't know if fix is the right word) those damaged blocks. Ok - I think you may just be saying it wrong. You are trying to repair your bad secter so that you can re-run reiserfsck and access the data off of the drive. That is not a rebuild. A rebuild it when you use parity and the other disks to reconstruct a bad disk. Read about a tool called badblocks. That's exactly right... repair! Okay, I've read up about badblocks... but I can't seem to find anywhere any information on where to place the file to install it on my flash drive in order to run the program? I downloaded it and have the "badblocks-1.42" file but that's about as far as I can seem to get. All of the threads seem to indicate a pre-understainding of the usage I'm sorry I'm so useless without instruction. All of the info refers to the program for Linux and unfortunately... I just don't know how to use linux (the only linux I use is Un-Raid) and the only reason I know how to use that is because of this forum. I know that's not such a good thing but I'm not a power user and until now it's been fine for my purposes. I just don't know how to go from here.
Archived
This topic is now archived and is closed to further replies.