t "upgrading a RAID system was
beyond the scope of installation support" (of course, what I was doing
was upgrading the non-RAID part). In any event, I had to physically unplug
the IDE disks to get RH 6.1 to update.
--
Stephen Walton, Professor of Physics and Astronomy,
California State University, Northridge
[EMAIL PROTECTED]
rger than the RAID created by
mkraid. This causes bootup mount of the RAID to fail, since "/sbin/e2fsck
-p /dev/md0" exits with an error status.
What happened? Can it be fixed without re-creating the array? If not,
how do I do the re-creation so that this doesn't happen again
I had _exactly_ the same problem. The only way I found around it was to
go into the BIOS and manually set both disks to NORMAL instead of LBA.
Attempting to set both to LBA didn't work. This is with RedHat 6.0 with
the 2.2.5-22 kernel. Perhaps this is fixed in a later kernel?
--
St
workaround? RedHat 6.0 (I have 6.1 but haven't installed it yet).
--
Stephen Walton, Professor of Physics and Astronomy,
California State University, Northridge
[EMAIL PROTECTED]
file system is not an
integer multiple of 504 blocks (the size of one 'cylinder').
--
Stephen Walton, Professor of Physics and Astronomy,
California State University, Northridge
[EMAIL PROTECTED]
s 20039544 blocks (40079708
for two). None of these values match up. Did I do something
un-recoverable? Can I just go ahead and run fsck anyway? Why the
discrepancies anyway?
Thanks in advance.
--
Stephen Walton, Professor, Dept. of Physics & Astronomy, Cal State Northridge
[EMAIL PROTECTED]
