REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range

[iarp]

The hard drive SDD is not even in the array, how is it causing my server to crash? This is the 2nd time this week.

 

Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052107 (122096638)
Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052108 (122096638)
Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052109 (122096638)
Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052110 (122096638)
Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052111 (122096638)
Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052112 (122096638)
Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052113 (122096638)
Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052114 (122096638)
Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052115 (122096638)
Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052116 (122096638)
Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052117 (122096638)
Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052118 (122096638)
Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052119 (122096638)
Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052120 (122096638)
Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052121 (122096638)
Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052122 (122096638)
Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052123 (122096638)

 

followed by 946,635 more lines of the same error message but a different block number.

[remotevisitor]

I am wondering why you think the drive sdd is not in the system.

 

How many drives do you have installed?

 

The sd? name allocated to each drive is dynamically allocated when the system boots .... And therefore is not necessarily the same every time the system boots.

 

But on most system it is usually consistent on each boot provided the number and location of the drives have't changed.

 

[iarp]

I didn't say it's not in the system, it's not in the array. Why would a drive outside the array not being used for anything be causing the entire system to go down.

 

I have since powered down and pulled the drive out.

[remotevisitor]

Sorry, missed read your initial post.

 

I don't suppose you had previously used the unassigned devices plugin to mount it outside the array and it was still mounting it.

 

I would have suggested using the 'mount' command to check if it was mounted somewhere for some unknown reason.  But as you have now removed the disk it is no longer relevant ... Although it would have been nice to have solved the mystery.

[iarp]

Timing wise it started just as my nightly rsync script executed, it connects to my web servers using rsync and it mirrors the home directories into a backup share along with copies of the databases.

 

Turns out the cache drive WAS in the array when it first went down, however after forcefully restarting the machine as it just wouldn't respond to anything the cache drive had de-selected itself from the array when the system came back up.

 

That was when I posted here, I had forgotten the cache drive was in the array but had somehow removed itself during the reboot.

 

I have since connected the drive to my main computer to read it and it contains the contents of that partial rsync just before going down. I formatted it and it didn't make it 16 minutes into a stress test sitting in my external case. Another Seagate down the tubes.