need help with ccrashed suse 10 raid1 system
I had a failure on /sev/sdb2. I tried backing up using tar to a USB drive, but something happened and if filled up the disk. There was about 27 GB on the 148 GB disk when I started. After it ran out of disk space, it locked up. on rebooting, it will not boot. Get the splash screen, then when booting, it hangs. Tried the rescue system, I can mount /dev/md0 /mnt and view the directories and files. Tried the suse installation, automatic recovery, it errors out on the hard disks. tried the fsck on sda2, but it fails with error 0x10. tried reiser.fsck, but it does nothing. I li /mnt/home I also get nothing listed. Also, If is start the installation, it recognizes the processor as AMD Hammer 64-bit, however, the processor is a Semperon 32-bit. Any suggestions on how I can fix this? Art
Art Fore wrote:
I had a failure on /sev/sdb2. I tried backing up using tar to a USB drive, but something happened and if filled up the disk. There was about 27 GB on the 148 GB disk when I started. After it ran out of disk space, it locked up. on rebooting, it will not boot. Get the splash screen, then when booting, it hangs.
tried the fsck on sda2, but it fails with error 0x10. tried reiser.fsck, but it does nothing.
If sda2 is part of your RAID1 setup, there's no point in checking it separately. When you boot the rescue system, I would expect your RAID1 array to be running degraded, but that's not a problem.
Any suggestions on how I can fix this?
Have you fscked /dev/md0? /Per Jessen, Zürich -- http://www.spamchek.ch/ - professionelle Emailsicherheitslösung. Jetzt für 30 Tage ausprobieren - kostenlos und unverbindlich!
Yes, but got same results as mentioned earlier. Art On Mon, 2005-12-19 at 20:02 +0100, Per Jessen wrote:
Art Fore wrote:
I had a failure on /sev/sdb2. I tried backing up using tar to a USB drive, but something happened and if filled up the disk. There was about 27 GB on the 148 GB disk when I started. After it ran out of disk space, it locked up. on rebooting, it will not boot. Get the splash screen, then when booting, it hangs.
tried the fsck on sda2, but it fails with error 0x10. tried reiser.fsck, but it does nothing.
If sda2 is part of your RAID1 setup, there's no point in checking it separately. When you boot the rescue system, I would expect your RAID1 array to be running degraded, but that's not a problem.
Any suggestions on how I can fix this?
Have you fscked /dev/md0?
/Per Jessen, Zürich
-- http://www.spamchek.ch/ - professionelle Emailsicherheitslösung. Jetzt für 30 Tage ausprobieren - kostenlos und unverbindlich!
Art Fore wrote:
Yes, but got same results as mentioned earlier.
Could you perhaps post the output, error message, maybe snippets from /var/log/messages and/or dmesg. Also, what does 'cat /proc/mdstat' say? The normal procedure when a disk in a RAID1 fails, is something along these lines: replace failed drive (with or without shutting the box, depending on whether the drive is hot-pluggable). partition replaced drive in the same way as the old drive raidhotadd /dev/mdx /dev/sdx I think the newer package mdadm does this slightly different, but the principle is the same. /Per Jessen, Zürich -- http://www.spamchek.ch/ - professionelle Emailsicherheitslösung. Jetzt für 30 Tage ausprobieren - kostenlos und unverbindlich!
participants (2)
-
Art Fore -
Per Jessen