raid0 crash
Hi all, i just had a crash with software raid 1, the power of 1 of the 2 raid hd's came loose during bootup. It resulted in me having to reboot. Then it checked the hd, found that an inode was not connected. Had to drop into a shell and run fcsk. Which put a single inode in the lost+found dir. But when it try to read it it gives a read-error. My question is, is there any way to find out what data was on the inode? and any way to retrieve it? Surge
Re: raid0 crash
Loose my head next time... really... offcourse i meant with raid0 At 13:51 24/10/99 +0200, Kelina wrote: Hi all, i just had a crash with software raid 1, the power of 1 of the 2 raid hd's came loose during bootup. It resulted in me having to reboot. Then it checked the hd, found that an inode was not connected. Had to drop into a shell and run fcsk. Which put a single inode in the lost+found dir. But when it try to read it it gives a read-error. My question is, is there any way to find out what data was on the inode? and any way to retrieve it? Surge
Re: raid0 crash
On Sun, Oct 24, 1999 at 03:11:53PM +0200, Kelina wrote:
Loose my head next time... really...
Deal :)Ok, you had me wondering there...
offcourse i meant with raid0
No, if you have a bad block that the disk can't read, no software in the
world is going to make the data come back.
(if it's sound data you could extrapolate in the Fourier domain of course,
or if it's sales material add some ``enterprise'' ``internet'' etc. to
fill in the blanks ;)
Hard drives crash, that's why you take frequent backups and run raid1/5
: [EMAIL PROTECTED] : And I see the elder races, :
:.: putrid forms of man:
: Jakob Østergaard : See him rise and claim the earth, :
:OZ9ABN : his downfall is at hand. :
:.:{Konkhra}...:
