Hi!
For testing purposes, I've placed a HDD with a number of PVs (assembling
to one VG with one LV) into a test box and installed 2.4.19 with the
dewnloadable DM patch (official release) and installed LVM2. Initially,
this ran quite well, and I added another HDD (this is the third HDD. One
is for the system, the other two large ones to store data).
After playing a bit with DM+LVM2, I shutted the box down to bring it to
another location, but it didn't any longer boot:-( I reinstalled the
base system (the LVs came up again with no problems:-), but rebooting
the box again, it didn't boot up again:-(
This time, I used gpart to try to recover, and it found useful data to
assemble a new partition table. Before writing it, I backed up the first
1.44MB of /dev/hda (guess where I stored it on:-> to do
post-mortem-inspection.
The first 512 byted of mentioned boot HDD where overwritten by some
Samba log! This is followed by some KB of 0x00. However, hda was never
ever itself (or any partition on it) used with LVM or anything else what
could IMHO caused this. The only difference compared to dozends of
machines I installed is DM + LVM2 userland tools (used with LVM1
metadata). Is it possible that the DM version downloadable at sistina
isn't really stable (for basic use)? Should I try some CVS checkout?
MfG, JBG
PS: If you would like to have the floppy's contents for your own
inspection, I can place it somewhere...
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur
fuer einen Freien Staat voll Freier Bürger" | im Internet!
Shell Script APT-Proxy: http://lug-owl.de/~jbglaw/software/ap2/
Attachment:
pgp00458.pgp
Description: PGP signature
