When I was trying to find man for mkfs.jfs I discovered that jfsutils was suddenly not installed. I installed it and then could man mkfs.jfs . I rebooted so I could plug in the second drive, and then md0 was getting mounted on /home as it should. Indeed I have all my data again. I don't understand what happened. --- On Thu, 10/22/09, Majed B. <majedb@xxxxxxxxx> wrote: > From: Majed B. <majedb@xxxxxxxxx> > Subject: Re: Is My Data DESTROYED?! > To: "adfas asd" <chimera_god@xxxxxxxxx> > Cc: linux-raid@xxxxxxxxxxxxxxx > Date: Thursday, October 22, 2009, 7:43 PM > I don't know exactly what went wrong > with your setup, so I can't tell > why it's not mounting. > > Did you check the output of dmesg | tail after a failed > mount? > > I'd suggest that you don't touch the disks, cables, nor the > array. > > Try running sudo fsck /dev/md0 > > On Fri, Oct 23, 2009 at 5:18 AM, adfas asd <chimera_god@xxxxxxxxx> > wrote: > > > > I don't understand exactly what it is to be done. If > I can mount using a different superblock, do I then remove > one of the drives from the array so I can put that drive > away with my data until I can buy another drive to back up > the data to? If so, how? > > > > How is it that the superblock on -both- drives got > destroyed? Isn't RAID10 supposed to be mirrored? > > > > --- On Thu, 10/22/09, Majed B. <majedb@xxxxxxxxx> > wrote: > > > > > From: Majed B. <majedb@xxxxxxxxx> > > > Subject: Re: Is My Data DESTROYED?! > > > To: "adfas asd" <chimera_god@xxxxxxxxx> > > > Cc: linux-raid@xxxxxxxxxxxxxxx > > > Date: Thursday, October 22, 2009, 7:12 PM > > > If you have bad sectors here > > > & there, and you didn't read the areas where > the bad > > > sectors are, you won't get read errors. > > > > > > That's why you should always have smartd running > along > > > with periodic sync_action -> check to force > mdadm to > > > check the array. > > > > > > > > > > > > There's still hope in recovering your data. > Don't > > > despair. > > > > > > On Fri, Oct 23, 2009 at 5:04 AM, > > > adfas asd <chimera_god@xxxxxxxxx> > > > wrote: > > > > > > > > > How could this possibly have > > > happened? The whole idea of RAID is so > something like this > > > won't happen. > > > > > > > > > > > > > > > > > > I was using JFS. > > > > > > > > > > > > I've lost confidence now in mdadm. I have too > much > > > data to back up practically, and am now at a > loss. > > > > > > > > > > > > > > > > > > --- On Thu, 10/22/09, Majed B. <majedb@xxxxxxxxx> > > > wrote: > > > > > > > > > > > > > From: Majed B. <majedb@xxxxxxxxx> > > > > > > > Subject: Re: Is My Data > > > DESTROYED?! > > > > > > > To: "adfas asd" <chimera_god@xxxxxxxxx> > > > > > > > Cc: linux-raid@xxxxxxxxxxxxxxx > > > > > > > Date: Thursday, October 22, 2009, 6:40 PM > > > > > > > Seems like your > > > filesystem is > > > > > > > corrupted. Some filesystems have > alternative > > > superblocks. > > > > > > > > > > > > > > you can mount your filesystem using an > alternative > > > > > > > superblock using: mount -o > sb=<offset> > > > > > > > You find the offset value by running a > dry-run (test) > > > of > > > > > > > mkfs on your drives. It will print multiple > offsets > > > for > > > > > > > superblocks. > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Oct 23, 2009 at 4:36 AM, > > > > > > > adfas asd <chimera_god@xxxxxxxxx> > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > Today I went in to my HTPC, to find it was > hung and > > > the > > > > > > > drive light was stuck on. After all > attempts to > > > revive it > > > > > > > or switch to terminal 2 or 3 had failed I > reset the > > > system. > > > > > > > > > > > > > > > > > > > > > > > > > > > > It rebooted to tell me that it cannot mount > /home, > > > the > > > > > > > RAID10offset2 device. > > > > > > > > > > > > > > > > > > > > > > > > > > > > When I reboot in recovery mode and try to > mount > > > /dev/md0 > > > > > > > manually it informs me there is an invalid > superblock! > > > I > > > > > > > shut down and unplugged each drive in turn, > and > > > /proc/mdstat > > > > > > > shows the appropriate volume gone, but still > can't > > > mount > > > > > > > the array. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > What has happened here? Is all my data > destroyed? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Majed B. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > 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 > > > > > > > > > > > > > > > -- > > > Majed B. > > > > > > > > > > > > > > > > > -- > > 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 > > > > -- > Majed B. > -- > 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 > -- 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
