Hi Paul, I managed to move pretty much all data from the 'hosed' machine to another place. (there are a few things that I would like to salvage but couldn't)
I would like to make an attempt to fix the filesystem and see if I can get some more of it. So if I issue: "e2fsck -f -b 32768 /dev/mapper/VolGroup00-LogVol01" because that is the one with the bad superblock? that I found a bit ago with: > e2label /dev/mapper/VolGroup00-LogVol01 : bad magic number in > Group-LogVol01. couldn't find valid filesystem superblock (although Jefferson mentioned that might be swap) there is also: /dev/mapper/VolGroup00-LogVol00 but I thought that was /boot ? sorry about all the questions, but I am a bit of a rookie with fixing crashed filesystems. thanks, Ron Paul M. Dyer wrote: > fine. In rescue mode, you can do debugfs or "e2fsck -f -b 32768.." on the > /dev/mapper/volume and try to get a good superblock and correct the > filesystem. > > Paul > > ----- Original Message ----- > From: "Ron Croonenberg" <[email protected]> > To: "Bond Masuda" <[email protected]> > Cc: "linux-poweredge" <[email protected]> > Sent: Friday, June 4, 2010 12:11:53 PM > Subject: Re: dell 2850 initrd problem. > > right, > > > I am actually thinking about moving the date to another machine and/or > put it on another device. > (the rescue cd gives me the option to activate the network interfaces, > that way I could scp or ftp it to another machine and inspect the > retrieved data before anything else.) > > > > Bond Masuda wrote: > >> On Fri, 2010-06-04 at 12:47 -0400, Ron Croonenberg wrote: >> >> >>> Well here is the thing. We had a 'standby' server that basically >>> would copy everything every night and in case something bad ever >>> would happen to the main server we could run it off that one. >>> However that one got fried during that same power outage. >>> We also made backups on tape, and guess what.. the server that made >>> those backups also got fried.. >>> >>> >>> So yes, it is pretty important data, it's pretty much the last >>> accessible data source we have, so I want to be really careful with >>> it. >>> >>> I do have a few other machines that I can use to store data, etc.. >>> >>> Ron >>> >>> >> Wow, sorry to hear about your situation. >> >> If this is critically important, and your absolute last resort to >> recover the data, the first thing I would do is get an image of the >> entire drive, and also an image of each partition (you can get the >> partitions from the full image, but i find it easier to have >> individual partition images for convenience). By image, I'm talking >> about doing a >> dd if=/dev/sda ... >> >> if you don't have a place to store the images, just run down to the >> store and buy a 500GB, 1TB, or 2TB external drive of some sort... USB >> will be rather slow for anything on the order of 100GB's or more, but >> it still works; just takes time. >> >> you can then later make copies of those images to mess with without >> the worry that you're messing around with your only source of the >> data. Without the worry, you'll have more options for recovery... >> >> -Bond >> >> >> > > > > > _______________________________________________ Linux-PowerEdge mailing > list [email protected] > https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read > the FAQ at http://lists.us.dell.com/faq > _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
