I'm sorry I didn't respond to your first email, but I've had a busy week, and really didn't have any ideas how to help.
On Fri, 2006-03-31 at 17:09 -0700, Mike Garfias wrote: > It was set to /dev/md0. > > We got it fixed. For some reason the original fsck used the wrong > journal. When we replayed against the previous journal all of the > data came back. I'm confused. I'm not sure what you mean by the wrong journal. Unless you use an external journal, there is only one journal per file system. Going back and reading your first email again. You said it wouldn't get past grub. Is it possible that /boot was modified right before your power problem? If very recent changes in /boot or /boot/grub weren't committed to disk, grub may have been unable to read the config and/or kernel until after fsck had run against /. I'm surprised running fsck from the rescue disk didn't help. I may never figure out what happened, but I'm glad you were able to recover it. > > I'd rather like to know why the wrong journal was used. I don't understand what you mean by the wrong journal. What exactly did you do to fix it? -- David Kleikamp IBM Linux Technology Center ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
