In a RAID array I had a have periodically lost a drive here and there over the past several months. Iwas always able to readd and resync without losing data. However at some point it looks like some minor corruption happened and this makes DRBD unhappy. Using fsck did not help either. Dec 19 06:01:45 storageboxtest4 kernel: [19005.945890] EXT3-fs error (device drbd0): ext3_get_inode_loc: unable to read inode block - inode=22184379........

mdadm --manage /dev/md125 -a /dev/sdb4 mdadm: add new device failed for /dev/sdb4 as 3: Invalid argument Dec 19 01:23:48 storageboxtest kernel: [ 2328.854491] md: sdb4 does not have a valid v1.2 superblock, not importing! Dec 19 01:23:48 storageboxtest kernel: [ 2328.854499] md: md_import_device returned -22 #zero the superblock and try again! mdadm --zero-superblock /dev/sdb4 mdadm --ma........

service named status rndc: connect failed: 127.0.0.1#953: connection refused named (pid 10557) is running... This issue is normally caused by a permissions issue where named doesn't have the permissions to read the rndc.key. Check /var/log/messages: Jan 4 17:06:22 storagebox named[10753]: none:0: open: /etc/rndc.key: permission denied Jan 4 17:06:22 storagebox named[10........