Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Simultaneus file system corruption of three drives in JBOD array


  • Please log in to reply
3 replies to this topic

#1 L2ZP

L2ZP

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:01:37 PM

Posted 03 August 2016 - 03:38 PM

So I recently experienced simultaneous file system corruption in three hard drives of a JBOD array, and I am wondering if anyone here might have insight into this problem? Fortunately, data was almost all backed up and I recovered the rest, so that is not the issue, but I would like to identify the root cause so it can be addressed.

 

I run Windows 10 on an HP 251 a123wb and use this system as a home NAS server with a JBOD array of seven 4 to 5 Tb external hard drives. They are housed within a Mediasonic H82-SU3S2 8-bay enclosure.

 

Here is the sequence of events leading to the corruption. I removed drive 4 for a couple of hours with the system and enclosure powered down and then replaced it.

 

When I powered the system back on, drives 5, 6, and 7 had been corrupted. The first thing that I noticed was that the names of the drives had changed.

 

The drive named 5 had been renamed to 3Y. 3Y is the name of another drive in the enclosure that was still also named 3Y and functioning properly. The drive previously named 5 was accessible and all of the files and folders appeared to be there, however two of the folders from the drive named 6 were now there as well, and those folders were inaccessible and presumably corrupted.

 

The drive named 6 had been renamed to 7 and was completely inaccessible.

 

The drive named 7 was still named 7 but also completely inaccessible.

 

7 was the only drive with some files that weren't backed up, so I ran chkdsk on it and identified multiple corrupt attribute records. This error is described here: https://support.microsoft.com/en-us/kb/169404 and in short, "Multiple attributes associated with a given file have the same attribute instance tag value. This is only likely to happen in directories where many files are repeatedly added and deleted in an "unbalanced" way." I was able to correct the file system, retake ownership of the drive with ACLs, and recover all of the files.

 

My question is what would cause an error like this? In my opinion, the enclosure should be suspect for creating simultaneous file system corruption spanning multiple drives. However, the renaming of drives seems to point to the OS. Do any of you have any ideas?



BC AdBot (Login to Remove)

 


#2 FreeBooter

FreeBooter

  • Members
  • 3,137 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Turkey - Adana
  • Local time:08:37 PM

Posted 04 August 2016 - 04:49 AM

When combined into a single logical volume, JBOD configurations are also called "linear", as separate hard drives are concatenated in a linear manner to form a logical volume. Due to its nature, no redundancy is provided with this configuration, meaning that failure of a single hard drive destroys the logical volume as a whole.

The JBOD known as Non-RAID drive architectures.


Posted Image


#3 L2ZP

L2ZP
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:01:37 PM

Posted 04 August 2016 - 03:19 PM

I should have specified, while they were JBOD, each one was a separate volume. I did not combine them into a single logical volume.



#4 Kilroy

Kilroy

  • BC Advisor
  • 3,378 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Launderdale, MN
  • Local time:12:37 PM

Posted 05 August 2016 - 08:38 AM

I should have specified, while they were JBOD, each one was a separate volume. I did not combine them into a single logical volume.

 

Then it isn't JBOD.  Odds are it is an issue with the enclosure and how it reacts when you remove a drive.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users