On Sat, Aug 29, 2015 at 11:47 PM, Marc Skinner <marc at e-skinner.net> wrote: > So what is the problem ... it won't mount? > > > Did you do an fsck on it? Assuming you had a filesystem that worked on it > prior to your issue. > > > > # fsck /dev/md0 fsck from util-linux 2.26.2 e2fsck 1.42.13 (17-May-2015) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/md0 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device> Did some reading on fsck and there are warnings of data loss in using it to repair. As this is a data raid (with business data on it) data loss and corruption is not an option I want to pursue. Any ideas on how to re-mount the array? TIA Dee -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20150830/dfe92464/attachment.html>