Hi all,
Please let me know if this message is inappropriate for this list. I
think I have a superblock problem on my RAID device, but I could be
wrong.
Also, much of the screen output recorded here was retyped, so might
contain minor errors, which are mine and not Debian's.
I'm trying to put toget
Hi Alvin,
Thanks for taking the time to reply.
First of all, I should have clarified that I am booting from hda, which is
another drive that is not in the RAID system at all. Booting is fine apart
from stopping for the fsck failure - the system comes up and appears to
work.
>> e2fsck 1.37 (21-Mar-
Hi Alvin,
I had a chance to think over the problem, and it looks much closer to
solution now. I had tried to mount the array on /home after boot, but the
complaints suggested to me that the array didn't exist as far as the
mounter was concerned. So I ran mdadm --assemble (with --scan, IIRC), left
i
Hey Alvin,
> if files/directories disappeared..
>
> a) your raid is corrupt in one or more ways
> b) you do have backups before the corruptions started to show
I think what happened was that, because I didn't have a /home entry on
fstab, files I created in /home/cjb were actually on the / partiti
>> you can get around all of the above by simply using your own custom
>> kernel with built in drivers for that sata controller
>> - modules is for job security for those that want to
>> build up hours to help corps debug systems that wont boot :-)
>
> So I just need to make myself a new
5 matches
Mail list logo
