search for: mdamd

...1 out of 2 mirrors Jan 17 12:22:15 zion kernel: md: ... autorun DONE. ... This computer is really old, Celeron 800MHz, 256MB of RAM and IDE disk too. I know that I have to suffer the consequences but if you know some way to recover some data, help me please. These days I have been reading about: mdamd, and some way to recover but no success: I tried to boot from rescue mode with CentOS 5 first CD and do an fsck to /dev/hda3 and /dev/hdd2. After this something about superblock was told to me and that use the command e2fsck -b 8123 <device> (I don't remember the number exactly) but no s...

...mirrors Jan 17 12:22:15 zion kernel: md: ... autorun DONE. ... This computer is old, Celeron 800MHz, 256MB of RAM and IDE disk too. I know that I have to suffer the consequences but if you know some way to recover some data, I'll appreciate it very much. These days I have been reading about: mdamd, and some way to recover but no success. I tried to boot from rescue mode with CentOS 5 first CD and do an fsck to /dev/hda3 and /dev/hdd2. After this something about superblock was told to me and that use the command e2fsck -b 8123 <device> (I don't remember the number exactly) but no s...

...f the file systems. It reported several errors and I let it fix them. The thing that's bothering me is I can't find any reason for the EXT3 error. Nothing seems to be wrong with the array or the hardware. I also noticed a few worrying messages while booting up and shutting down. On boot-up mdamd complains that super-minor should only be declared once and then there's a message that File descriptor 21 is open. On shutdown there are messages that md0 and md1 are in immediate safe mode and that md1 is till in use. Is my system totally hosed or can I ignore these warnings? Thanks, Rasmus