I'm not sure what happened, but after upgrading my 320gb drive with a new 2tb apparently another one of my older 2tb drives has issues. I'm pretty sure it is my WD EARX in disk position 1, but I'm not used to how the log is formatted so I want to make sure.

 

Also, I am unable to format the new drive and am not sure if this is the issue or not, but I can't put the working 320GB back in place to replace the possibly failing WD drive because it is an "invalid configuration".

 

Log posted below and any help would be much appreciated.

 

Jan 23 07:59:20 UnRAID kernel: mdcmd (1): import 0 8,144 1953514552 ST2000DM001-1CH164_S1E2YT1C

Jan 23 07:59:20 UnRAID kernel: md: import disk0: [8,144] (sdj) ST2000DM001-1CH164_S1E2YT1C size: 1953514552

Jan 23 07:59:20 UnRAID kernel: mdcmd (2): import 1 8,192 1953514552 WDC_WD20EARX-00PASB0_WD-WMAZA6962916

Jan 23 07:59:20 UnRAID kernel: md: import disk1: [8,192] (sdm) WDC_WD20EARX-00PASB0_WD-WMAZA6962916 size: 1953514552

Jan 23 07:59:20 UnRAID kernel: mdcmd (3): import 2 8,128 1953514552 ST2000DM001-1ER164_W4Z07DP3

Jan 23 07:59:20 UnRAID kernel: md: import disk2: [8,128] (sdi) ST2000DM001-1ER164_W4Z07DP3 size: 1953514552

Jan 23 07:59:20 UnRAID kernel: mdcmd (4): import 3 8,64 312571192 WDC_WD3200AAJS-00RYA0_WD-WMAPZ0108623

Jan 23 07:59:20 UnRAID kernel: md: import disk3: [8,64] (sde) WDC_WD3200AAJS-00RYA0_WD-WMAPZ0108623 size: 312571192

Jan 23 07:59:20 UnRAID kernel: mdcmd (5): import 4 8,16 312571192 WDC_WD3200AAJS-00RYA0_WD-WMAPZ0061103

Jan 23 07:59:20 UnRAID kernel: md: import disk4: [8,16] (sdb) WDC_WD3200AAJS-00RYA0_WD-WMAPZ0061103 size: 312571192

Jan 23 07:59:20 UnRAID kernel: mdcmd (6): import 5 8,48 312570132 WDC_WD3200JS-00PDB0_WD-WCAPD4281351

Jan 23 07:59:20 UnRAID kernel: md: import disk5: [8,48] (sdd) WDC_WD3200JS-00PDB0_WD-WCAPD4281351 size: 312570132

Jan 23 07:59:20 UnRAID kernel: mdcmd (7): import 6 8,32 312571192 WDC_WD3200AAJS-00RYA0_WD-WMAPZ0082789

Jan 23 07:59:20 UnRAID kernel: md: import disk6: [8,32] (sdc) WDC_WD3200AAJS-00RYA0_WD-WMAPZ0082789 size: 312571192

Jan 23 07:59:20 UnRAID kernel: mdcmd (: import 7 8,160 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA3693931

Jan 23 07:59:20 UnRAID kernel: md: import disk7: [8,160] (sdk) WDC_WD20EARS-00MVWB0_WD-WMAZA3693931 size: 1953514552

Jan 23 07:59:20 UnRAID kernel: mdcmd (9): import 8 8,112 1953514552 WDC_WD20EARX-00PASB0_WD-WCAZAE095706

Jan 23 07:59:20 UnRAID kernel: md: import disk8: [8,112] (sdh) WDC_WD20EARX-00PASB0_WD-WCAZAE095706 size: 1953514552

Jan 23 07:59:20 UnRAID kernel: mdcmd (10): import 9 8,80 1953514552 WDC_WD20EARS-00S8B1_WD-WCAVY5673505

Jan 23 07:59:20 UnRAID kernel: md: import disk9: [8,80] (sdf) WDC_WD20EARS-00S8B1_WD-WCAVY5673505 size: 1953514552

Jan 23 07:59:20 UnRAID kernel: mdcmd (11): import 10 8,96 1953514552 WDC_WD20EARS-00J2GB0_WD-WCAYY0111280

Jan 23 07:59:20 UnRAID kernel: md: import disk10: [8,96] (sdg) WDC_WD20EARS-00J2GB0_WD-WCAYY0111280 size: 1953514552

Jan 23 07:59:20 UnRAID kernel: mdcmd (12): import 11 8,176 1953514552 WDC_WD20EARS-60MVWB0_WD-WCAZA7979531

Jan 23 07:59:20 UnRAID kernel: md: import disk11: [8,176] (sdl) WDC_WD20EARS-60MVWB0_WD-WCAZA7979531 size: 1953514552

 

Jan 23 07:59:30 UnRAID kernel: REISERFS warning (device md2): sh-2006 read_super_block: bread failed (dev md2, block 2, size 4096)

Jan 23 07:59:30 UnRAID kernel: REISERFS warning (device md2): sh-2006 read_super_block: bread failed (dev md2, block 16, size 4096)

Jan 23 07:59:30 UnRAID kernel: REISERFS warning (device md2): sh-2021 reiserfs_fill_super: can not find reiserfs on md2

 

Jan 23 07:59:44 UnRAID logger:

Jan 23 07:59:45 UnRAID logger:

Jan 23 07:59:45 UnRAID logger: The problem has occurred looks like a hardware problem. If you have

Jan 23 07:59:45 UnRAID logger: bad blocks, we advise you to get a new hard drive, because once you

Jan 23 07:59:45 UnRAID logger: get one bad block  that the disk  drive internals  cannot hide from

Jan 23 07:59:45 UnRAID logger: your sight,the chances of getting more are generally said to become

Jan 23 07:59:45 UnRAID logger: much higher  (precise statistics are unknown to us), and  this disk

Jan 23 07:59:45 UnRAID logger: drive is probably not expensive enough  for you to you to risk your

Jan 23 07:59:45 UnRAID logger: time and  data on it.  If you don't want to follow that follow that

Jan 23 07:59:45 UnRAID logger: advice then  if you have just a few bad blocks,  try writing to the

Jan 23 07:59:45 UnRAID logger: bad blocks  and see if the drive remaps  the bad blocks (that means

Jan 23 07:59:45 UnRAID logger: it takes a block  it has  in reserve  and allocates  it for use for

Jan 23 07:59:45 UnRAID logger: of that block number).  If it cannot remap the block,  use badblock

Jan 23 07:59:45 UnRAID logger: option (-B) with  reiserfs utils to handle this block correctly.

Jan 23 07:59:45 UnRAID logger:

Jan 23 07:59:45 UnRAID logger: bread: Cannot read the block (0): (Input/output error).

Jan 23 07:59:45 UnRAID logger:

Jan 23 07:59:45 UnRAID kernel: Buffer I/O error on device md2, logical block 0

Jan 23 07:59:45 UnRAID kernel: Buffer I/O error on device md2, logical block 1

Jan 23 07:59:45 UnRAID kernel: Buffer I/O error on device md2, logical block 2

Jan 23 07:59:45 UnRAID kernel: Buffer I/O error on device md2, logical block 3

Jan 23 07:59:45 UnRAID kernel: Buffer I/O error on device md2, logical block 4

Jan 23 07:59:45 UnRAID kernel: Buffer I/O error on device md2, logical block 5

Jan 23 07:59:45 UnRAID kernel: Buffer I/O error on device md2, logical block 6

Jan 23 07:59:45 UnRAID kernel: Buffer I/O error on device md2, logical block 7

Jan 23 07:59:45 UnRAID kernel: Buffer I/O error on device md2, logical block 8

Jan 23 07:59:45 UnRAID kernel: Buffer I/O error on device md2, logical block 9

I would think that the problem is your disk #2 (ST2000DM001-1ER164_W4Z07DP3) hence the md2 error messages.  Since you just replaced a drive, I would double check and reseat your power and sata cables to the drive at both the hard drive and mobo ends.

 

After that if there are still problems, then go here: http://lime-technology.com/wiki/index.php/Check_Disk_Filesystems

Thanks for the reply. Looks like the new drive is the culprit. That is why I put it in my windows box and ran HDtune to zero the drive and verify. I also did a surface scan and multiple smart tests. All were fine. The other strange thing is that the drive was fine when I first put it in. The rebuild started then for some reason my parity drive dropped off. Rebooted and it shows the new drive as unformatted and it won't cooperate.

Ok. So I put the drive in an alternate box and boot into a fresh unraid and I get no errors on that drive. Formats without issue.

 

I backed up my current config and started fresh on my current server with a blank unraid install. No errors.

 

So, could something be corrupt on my current config? How do I start over and preserve my data?

Thanks for the reply. Looks like the new drive is the culprit. That is why I put it in my windows box and ran HDtune to zero the drive and verify. I also did a surface scan and multiple smart tests. All were fine. The other strange thing is that the drive was fine when I first put it in. The rebuild started then for some reason my parity drive dropped off. Rebooted and it shows the new drive as unformatted and it won't cooperate.

 

All sata and power connections are fine. I even changed to alternate sata ports where other drives are working. Same error.

 

I attempted to run reiserfsck --check and get the following:

 

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.

 

This error does not come up if I use a fresh config or move the drive to a different box.

 

I've looked and can't seem to find a straight forward way of just starting my config over as I think something may be corrupt on the flash drive.

 

From what I've found in older how-to guides I just need to put my drives in the same spot and start the array and let parity rebuild. How will that work if I have one drive unformatted? I did a parity check before all this started and had no errors.

 

Please advise.

Ok. I put the drive in my windows box and deleted the partition. I then formatted to NTFS just to see.

 

Now I no longer get block read errors, but the drive still won't format.

 

I've attached the latest log and a smart report.

smart.zip

unraid.zip

The syslog is showing write errors on the first few sectors of the drive.  If this cannot be rectified then the disk will not be able to be formatted by unRAID.  If that drive supports it, then it might be worth running a smartctl conveyance test against the drive in case it was damaged during shipping (as it a new drive it seems to me that is a distinct possibility).

 

One thing to try is to put the disk into a PC and use the manufacturers diagnostic software to test the drive and to write zeroes to the whole drive to see if that helps rectify the problem.  Another possibility is to run the pre-clear script on the unRAID system which will also try to write zeroes to all the drive.

I would agree with you except for the fact that other instances of unraid have no issue with the drive. I've already written zeros to the drive and verified the drive after. No issues.

 

I think there is something wrong with my instance of unraid since a blank config with the exact same hardware has no trouble with the drive.

 

At this point I'm looking for the easiest method to start over and keep my data.

I would agree with you except for the fact that other instances of unraid have no issue with the drive. I've already written zeros to the drive and verified the drive after. No issues.

 

I think there is something wrong with my instance of unraid since a blank config with the exact same hardware has no trouble with the drive.

 

At this point I'm looking for the easiest method to start over and keep my data.

If you are reasonably happy the drive (and its cabling) are OK and simply want to start over then I would:

• With the array stopped, back up the files on your flash to somewhere outside unRAID (e.g.your PC) so that you can revert to the current configuration if necessary.
  
• Make sure you know what the current assignments are (by serial number).  A screen shot may be a good idea
  
• Use the 'new config' option from the Tools menu to clear the current assignments.
  
• Assign your drives as you want them (at this point I would leave off the parity drive).  In a New Config state unRAID will add unRAID formatted data drives with existing data unchanged.
  
• Start the array and check everything looks as you expect.  At this point you can also check that you can format the problem drive
  
• Stop the array and assign the parity drive.  The reason for not doing it initially was in case you made an error assigning the data drives as assigning one incorrectly as parity would lose its contents.  Start the array to rebuild parity.
  
• When the parity build has completed then it is worth doing a parity check to validate that parity can be read back correctly.
  

If you really wanted a completely clean start without any plugins then you could have reformatted the USB drive and put a fresh install on it instead of going the New Config route, but that would mean any add-ins or settings relating to shares would need redoing.  Still might be worth doing to guarantee a completely clean state.

I would agree with you except for the fact that other instances of unraid have no issue with the drive. I've already written zeros to the drive and verified the drive after. No issues.

 

I think there is something wrong with my instance of unraid since a blank config with the exact same hardware has no trouble with the drive.

 

At this point I'm looking for the easiest method to start over and keep my data.

If you are reasonably happy the drive (and its cabling) are OK and simply want to start over then I would:

• With the array stopped, back up the files on your flash to somewhere outside unRAID (e.g.your PC) so that you can revert to the current configuration if necessary.
  
• Make sure you know what the current assignments are (by serial number).  A screen shot may be a good idea
  
• Use the 'new config' option from the Tools menu to clear the current assignments.
  
• Assign your drives as you want them (at this point I would leave off the parity drive).  In a New Config state unRAID will add unRAID formatted data drives with existing data unchanged.
  
• Start the array and check everything looks as you expect.  At this point you can also check that you can format the problem drive
  
• Stop the array and assign the parity drive.  The reason for not doing it initially was in case you made an error assigning the data drives as assigning one incorrectly as parity would lose its contents.  Start the array to rebuild parity.
  
• When the parity build has completed then it is worth doing a parity check to validate that parity can be read back correctly.
  

If you really wanted a completely clean start without any plugins then you could have reformatted the USB drive and put a fresh install on it instead of going the New Config route, but that would mean any add-ins or settings relating to shares would need redoing.  Still might be worth doing to guarantee a completely clean state.

 

Thanks. I do have a question. Since the problem drive is replacing an existing working drive won't I lose data if I start then new config without parity?

Thanks. I do have a question. Since the problem drive is replacing an existing working drive won't I lose data if I start then new config without parity?

After reviewing the thread, this question now after all that has already been done to get to this point is very confusing.

 

Any use of New Config even if you include parity will mean you can't rebuild a drive. In fact, it is not clear if you can get to a state where a rebuild would be possible.

 

If you don't mean you still need to rebuild a disk, then I don't know what you mean by this question. The parity drive does not contain any of your data.

Ok. I put the drive in my windows box and deleted the partition. I then formatted to NTFS just to see.

 

Now I no longer get block read errors, but the drive still won't format.

 

I've attached the latest log and a smart report.

 

The drive should not be formatted. Formatting is included when the partition is rebuilt. Formatting the drive will make recovery much more difficult. Show a screenshot of unRAID main.

Thanks. I do have a question. Since the problem drive is replacing an existing working drive won't I lose data if I start then new config without parity?

After reviewing the thread, this question now after all that has already been done to get to this point is very confusing.

 

Any use of New Config even if you include parity will mean you can't rebuild a drive. In fact, it is not clear if you can get to a state where a rebuild would be possible.

 

If you don't mean you still need to rebuild a disk, then I don't know what you mean by this question. The parity drive does not contain any of your data.

 

Thank you for taking the time too look this over. I bought a new drive just in case and have the same issue.

 

I originally started with 5 320 GB drives and 6 2tb drives. I upgraded one of the 320 GB drives with the 2tb drives in question and it just refuses to format and rebuild. Tried everything. Wrote zeros and verified the drives, nothing of note in the smart report.

 

I have not touched anything on the 320 GB drive that was in the working array just in case. I tried to put it back in but it won't let me because it now has a size discrepancy.

 

Can I start a new config with the drives that were working and not use any of my new 2tb drives and rebuild parity?

 

Basically go back to 5 320 GB drives and 6 2 tb drives that I started with to get things back to a working state? I no longer trust my config.

...it just refuses to format and rebuild...

Formatting a drive is not part of the rebuild process. Maybe that is where you are going wrong. When replacing a drive you should not be trying to format the new drive.

Can I start a new config with the drives that were working and not use any of my new 2tb drives and rebuild parity?

 

Basically go back to 5 320 GB drives and 6 2 tb drives that I started with to get things back to a working state? I no longer trust my config.

Yes. Just make sure you assign the drives correctly and most importantly don't put a data drive in the parity slot or unRAID will overwrite the data with parity.

...it just refuses to format and rebuild...

Formatting a drive is not part of the rebuild process. Maybe that is where you are going wrong. When replacing a drive you should not be trying to format the new drive.

Can I start a new config with the drives that were working and not use any of my new 2tb drives and rebuild parity?

 

Basically go back to 5 320 GB drives and 6 2 tb drives that I started with to get things back to a working state? I no longer trust my config.

Yes. Just make sure you assign the drives correctly and most importantly don't put a data drive in the parity slot or unRAID will overwrite the data with parity.

 

Thanks. I'm actually not trying to format, unraid says "unformatted drive" and then has the option to format. No rebuild option is present. I'll grab a screenshot as asked so you can see what I mean.

Are you trying to assign the new drive into the slot of the old drive? Or are you trying to add it to a new slot?

I tried to put it back in but it won't let me because it now has a size discrepancy.

This is the reason it is recommended to backup your flash drive before any changes are made.  If you had/have done that then you could restore the config folder from the backup and put the old drives back into the array and restarted your array and it shouldn't have any problems with size.

Are you trying to assign the new drive into the slot of the old drive? Or are you trying to add it to a new slot?

 

Yes, that's what I was trying to do. Just upgrade a drive from 320 gb to a 2 tb drive.

I tried to put it back in but it won't let me because it now has a size discrepancy.

This is the reason it is recommended to backup your flash drive before any changes are made.  If you had/have done that then you could restore the config folder from the backup and put the old drives back into the array and restarted your array and it shouldn't have any problems with size.

 

Agreed. That will be standard practice from now on. Thanks.

Thanks everyone for the help. I've resolved the issue by putting the known working disks in a new config and setting everything up again. It was simple since I don't use any plugins at the moment. No loss of data, parity sync went through without issue.

 

Thanks again.