From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Goryachev Subject: Re: raid10 recovery assistance requested Date: Mon, 23 Sep 2013 15:19:51 +1000 Message-ID: <523FCF77.9080707@websitemanagers.com.au> References: <523A7DB9.9070600@hardwarefreak.com> <523F6692.9090407@turmel.org> <523F7C62.4040305@turmel.org> <523FAD81.9070005@turmel.org> <523FB511.5070001@turmel.org> <523FBAB2.7070506@turmel.org> <523FBFAA.3050705@turmel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-raid-owner@vger.kernel.org To: Dave Gomboc Cc: linux-raid@vger.kernel.org List-Id: linux-raid.ids On 23/09/13 14:55, Dave Gomboc wrote: > root@sysresccd /mnt % mount -o ro /dev/mapper/teramooch-srv /mnt/srv > NTFS signature is missing. > Failed to mount '/dev/mapper/teramooch-srv': Invalid argument > The device '/dev/mapper/teramooch-srv' doesn't seem to have a valid NTFS. > Maybe the wrong device is used? Or the whole disk instead of a > partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around? > > It should be ext3, not NTFS. Try: mount -o ro -t ext3 /dev/mapper/teramooch-srv /mnt/srv This just specifies it is ext3 format, but will probably still fail... check dmesg for details, but hopefully the next step will fix it. If that fails, take a look at: fsck.ext3 -n /dev/mapper/teramooch-srv (Which should do a read-only check, if there are not too many changes, re-run with -y). Worst case, if the fsck destroys the data, you can re-copy the entire array from the original and try again. Hope that helps... Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au