Mailinglist Archive: opensuse (4398 mails)
| < Previous | Next > |
Curious RAID effect?
- From: Simon Roberts <thorpflyer@xxxxxxxxx>
- Date: Wed, 31 Aug 2005 20:29:16 -0700 (PDT)
- Message-id: <20050901032916.15118.qmail@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
I think I've worked around this, but I observed what appeared to be a
rather strange (and rather undesireable) effect of RAID 1 in a new
installation I just made.
I started out with a pair of 160G disks, one old with SuSE 9.1 on it,
and one completely new. The new one happened to be the "first" drive in
a RAID 1 pair in the new install of SuSE 9.3 with the older one as the
second drive.
Anyway, the install all went fine, and the new system booted quite
happily even though there was no non-RAID partition. But I noticed a
couple of anomalies, like sound was behaving strangely. Then at the
next reboot, the fun really started. I noticed many error messages
during the boot process. The system complained of many modules that the
kernel couldn't load. The system did manage to come up and run, but
then it started telling me about new hardware--this was hardware that
was already installed and configured in the initial setup.
At the next reboot, the grub splash screen had changed from the green
9.3 screen to the blue 9.1 screen, the system failed to load a bunch of
modules, and several other strange things happened. The network, which
had been working up to that point, totally failed, and several Yast
modules complained of contraditions, duplications, or other errors in
the configurations of both the network and sound devices.
My guess is that the RAID 1 configuration was sucking the contents of
the old 9.1 partition into the new disk. Seems kinda improbable, but
the partitions don't get formatted (according to the partition
settings) only the RAID itself. Certainly the effect of bits of 9.1
appearing in the new system seems highly suggestive. (I did a fresh
install, not an upgrade, and the raid partition itself was formatted,
so "should be blank").
Any thoughts are welcome. Meanwhile, I'm going to do a fake or
temporary install, non-RAID, and make the front of both drives a
formatted swap partition, I'm hoping that by following this up with a
real install over the whole of both disks in RAID-1 mode, I will
prevent RAID from finding anything that it thinks it can recover.
Bizzare, or what?
Cheers,
Simon
"You can tell whether a man is clever by his answers. You can tell whether a man is wise by his questions." Naguib Mahfouz
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
rather strange (and rather undesireable) effect of RAID 1 in a new
installation I just made.
I started out with a pair of 160G disks, one old with SuSE 9.1 on it,
and one completely new. The new one happened to be the "first" drive in
a RAID 1 pair in the new install of SuSE 9.3 with the older one as the
second drive.
Anyway, the install all went fine, and the new system booted quite
happily even though there was no non-RAID partition. But I noticed a
couple of anomalies, like sound was behaving strangely. Then at the
next reboot, the fun really started. I noticed many error messages
during the boot process. The system complained of many modules that the
kernel couldn't load. The system did manage to come up and run, but
then it started telling me about new hardware--this was hardware that
was already installed and configured in the initial setup.
At the next reboot, the grub splash screen had changed from the green
9.3 screen to the blue 9.1 screen, the system failed to load a bunch of
modules, and several other strange things happened. The network, which
had been working up to that point, totally failed, and several Yast
modules complained of contraditions, duplications, or other errors in
the configurations of both the network and sound devices.
My guess is that the RAID 1 configuration was sucking the contents of
the old 9.1 partition into the new disk. Seems kinda improbable, but
the partitions don't get formatted (according to the partition
settings) only the RAID itself. Certainly the effect of bits of 9.1
appearing in the new system seems highly suggestive. (I did a fresh
install, not an upgrade, and the raid partition itself was formatted,
so "should be blank").
Any thoughts are welcome. Meanwhile, I'm going to do a fake or
temporary install, non-RAID, and make the front of both drives a
formatted swap partition, I'm hoping that by following this up with a
real install over the whole of both disks in RAID-1 mode, I will
prevent RAID from finding anything that it thinks it can recover.
Bizzare, or what?
Cheers,
Simon
"You can tell whether a man is clever by his answers. You can tell whether a man is wise by his questions." Naguib Mahfouz
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
| < Previous | Next > |