{"id":987,"date":"2010-09-25T00:52:17","date_gmt":"2010-09-25T04:52:17","guid":{"rendered":"http:\/\/cd34.com\/blog\/?p=987"},"modified":"2010-09-25T00:52:17","modified_gmt":"2010-09-25T04:52:17","slug":"adaptec-31205-under-debian","status":"publish","type":"post","link":"https:\/\/cd34.com\/blog\/infrastructure\/adaptec-31205-under-debian\/","title":{"rendered":"Adaptec 31205 under Debian"},"content":{"rendered":"

We have a Storage Server with 11 2tb drives in a Raid5. During a recent visit, we heard the alarm, but, no red light on any drive was visible nor was the light on the front of the chassis lit. Knowing it was a problem waiting to happen, but, without being able to see which drive had caused the array to fail, we scheduled a maintenance window that happened to coincide with a kernel upgrade.<\/p>\n

In the meantime, we attempted to install the RPM and java management system to no avail. So, we weren’t able to read the controller status to find out what the problem was.<\/p>\n

When we rebooted the machine, the array status was degraded and it prompted us to hit enter to accept the configuration or control-A to enter the admin. We entered the admin, Manage array, all drives are present and working. Immediately the array status changes to rebuilding with no indication which drive had failed and was being readded.<\/p>\n

Exiting the admin, saving the config, the client said, pull the machine offline until it is fixed. This started what seemed like an endless process. We figured we would let it rebuild while it was online, but, disable it from the cluster. We installed a new kernel, 2.6.36-rc5, rebooted and this is where the trouble started. On boot, the new kernel got an I\/O error, the channel hung, it forced a reset and then sat there for about 45 seconds. After it continued, it paniced as it was unable to read \/dev\/sda1.<\/p>\n

Rebooting and entering the admin, we’re faced with an array that is marked offline. After identifying each of the drives through disk utils to make sure that they are recognized, we forced the array back online and rebooted into the old kernel. As it turns out, something in our 2.6.36-rc5 disables the array and sets it offline. It takes 18 hours to rebuild the array and return it to optimal status.<\/p>\n

After the machine comes up, we knew we had a problem on one of the directories on the system and this seemed like an opportune time to run xfs_repair. About 40 minutes into it, we run into an I\/O error with a huge block number and bam, the array is offline again.<\/p>\n

In Disk Util in the ROM we start the test on the first drive. It takes 5.5 hours to run through the first disk which puts us at an estimated 60+ hours to check all 11 drives in the array. smartctl doesn’t allow us to independently check the drives, so, we fire up a second machine and mount each of the drives looking for any possible telltale signs in the S.M.A.R.T. data stored on the drives. Two drives show some abnormal numbers and we have an estimated 11 hours to check those disks. 5.5 hours later, the first disk is clean, less than 30 minutes later, we have our culprit. Relocating a number of bad sectors results in the controller hanging again, yet, no red fault light anywhere to be seen, no indication in the Adaptec manager that this drive is bad.<\/p>\n

Replacing the drive and going back into the admin shows us a greyed out drive which immediately starts reconstructing. We reboot the system into the older kernel and start xfs_repair again. After two hours, it has run into a number of errors, but no I\/O Errors.<\/p>\n

It is obvious we’ve had some corruption for quite some time. We had a directory we couldn’t delete because it claimed it had files, however, no files were in the directory. We had 2 directories with files that we couldn’t do anything with and couldn’t even mv them to an area outside our working directories. We figured it was an xfs bug that we had hit due to the 18 terabyte size of the partition, but guessed that an xfs_repair would fix this. It was a minor annoyance to the client until we could get to a maintenance interval so we waited. In reality, this should have been a sign that we had some issues and we should have pushed the client harder to allow us to diagnose this much earlier. There is some data corruption, but, this is the second in a pair of backup servers for their cluster. Resyncing the data to a known good source will fix this without too much difficulty.<\/p>\n

After four hours, xfs_repair is reporting issues like:<\/p>\n

\r\n\r\nbad directory block magic # 0 in block 0 for directory inode 21491241467\r\ncorrupt block 0 in directory inode 21491241467\r\n        will junk block\r\nno . entry for directory 21491241467\r\nno .. entry for directory 21491241467\r\nproblem with directory contents in inode 21491241467\r\ncleared inode 21491241467\r\n        - agno = 6\r\n        - agno = 7\r\n        - agno = 8\r\nbad directory block magic # 0 in block 1947 for directory inode 34377945042\r\ncorrupt block 1947 in directory inode 34377945042\r\n        will junk block\r\nbad directory block magic # 0 in block 1129 for directory inode 34973370147\r\ncorrupt block 1129 in directory inode 34973370147\r\n        will junk block\r\nbad directory block magic # 0 in block 3175 for directory inode 34973370147\r\ncorrupt block 3175 in directory inode 34973370147\r\n        will junk block\r\n<\/pre>\n
It appears that we have quite a bit of data corruption due to a bad drive which is precisely why we use Raid.<\/p>\n
The array failed, why didn’t the Adaptec on-board manager know which drive had failed?  Had we gotten the Java application to run, I’m still not convinced it would have told us which drive was throwing the array into degraded status.  Obviously the card knew something was wrong as the alarm was on.  Each drive has a fault light and an activity light, but, all of the drives allowed the array to be rebuilt and claimed the status was Optimal.  During initialization, the Adaptec does light the fault and activity lights for each drive so it seems reasonable that when the drive encountered errors, it could have lit the fault light so we knew which drive to replace.  When running xfs_repair and receiving the I\/O error where it couldn’t relocate the block, why didn’t the Adaptec controller immediately fail the drive?<\/p>\n
All in all, I’m not too happy with Adaptec right now.  A 2tb hard drive failed which cost us roughly 60 hours to diagnose and put back into service.  The failing drive should have been tagged and removed from the raid set immediately and marked.  As it is right now, even though it was running in degraded mode, we shouldn’t have seen any corruption, however, xfs_repair is finding a considerable number of errors.  <\/p>\n
The drives report roughly 5600 hours online which corresponds to the eight months we’ve had the machine online and based on the number of files xfs_repair is finding are bad, I believe that drive had been failing for quite some time and Adaptec has failed us.  While we have a considerable number of Adaptec controllers, we’ve never seen a failure like this.<\/p>\n
\n
<\/div>\n<\/fb:like>\n<\/div>
<\/div>","protected":false},"excerpt":{"rendered":"
We have a Storage Server with 11 2tb drives in a Raid5. During a recent visit, we heard the alarm, but, no red light on any drive was visible nor was the light on the front of the chassis lit. Knowing it was a problem waiting to happen, but, without being able to see which […]<\/p>\n
\n
<\/div>\n<\/fb:like>\n<\/div>
<\/div>","protected":false},"author":15,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[101,131,100],"class_list":["post-987","post","type-post","status-publish","format-standard","hentry","category-infrastructure","tag-adaptec-31205","tag-debian","tag-linux"],"_links":{"self":[{"href":"https:\/\/cd34.com\/blog\/wp-json\/wp\/v2\/posts\/987","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cd34.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cd34.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cd34.com\/blog\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/cd34.com\/blog\/wp-json\/wp\/v2\/comments?post=987"}],"version-history":[{"count":2,"href":"https:\/\/cd34.com\/blog\/wp-json\/wp\/v2\/posts\/987\/revisions"}],"predecessor-version":[{"id":989,"href":"https:\/\/cd34.com\/blog\/wp-json\/wp\/v2\/posts\/987\/revisions\/989"}],"wp:attachment":[{"href":"https:\/\/cd34.com\/blog\/wp-json\/wp\/v2\/media?parent=987"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cd34.com\/blog\/wp-json\/wp\/v2\/categories?post=987"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cd34.com\/blog\/wp-json\/wp\/v2\/tags?post=987"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}