On 10 April 2011 16:02, Edward Siefker <hatta00@xxxxxxxxxxx> wrote: > >> >> Doesn't look good.. >> What version of mdadm? ÂWhat kernel? >> >> NeilBrown >> > > > > root@iblis:~# mdadm --version > mdadm - v3.1.4 - 31st August 2010 > root@iblis:~# uname -a > Linux iblis 2.6.38-2-amd64 #1 SMP Tue Mar 29 16:45:36 UTC 2011 x86_64 > GNU/Linux > > Did you see the other post I made? ÂThe array still > reports as clean, but I haven't tried to mount it yet. > This array started out as a RAID1, which I changed to > RAID5, added a disk, reshaped, and added a spare to. > This worked great and I used it for a couple weeks > before deciding to go to RAID6. > > > Looking at the output of 'mdadm -E' and 'mdadm -D' > (again in the other post), it looks like there's > some inconsistency in the raid device for /dev/sde1. > -E reports it as number 4 and raid device 4. But, > -D says /dev/sde1 is number 4 and raid device 3. > Don't know if that means anything, but it's the > only thing I see that looks unusual. > > Since the array is clean, is it safe to mount it? > It's actually a luks volume, fwiw. ÂThanks > -- > > Âhatta00@xxxxxxxxxxx > > -- > http://www.fastmail.fm - mmm... Fastmail... > > -- > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at Âhttp://vger.kernel.org/majordomo-info.html > Just try a fsck -n ? // Mathias -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
