[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#417407: debian-installer: d-i destroyed existing raid device



On Monday 02 April 2007 18:33, Peter Nuttall wrote:
> D-I questions: I just pressed enter at the prompt, and set my keyboard
> and location to enGB. On reaching the disk stage, I asked it to set up
> hda as a LVM with / /home /tmp and /var on seperate paritions. On
> checking the result seemed to suggest no changes to /dev/sda or
> /dev/sdb. I have attached syslog and partman from /var/log/installer.

I have tried to reproduce this issue in vmware, but so far have been 
unable to do so.

- started with clean system with 1 IDE and 2 SCSI disks
- installed Etch with /home on RAID1 as only filesystem on SCSI disks
- copied /usr/share/doc into $HOME

I then rebooted the system cleanly and did another install; this did not 
reproduce the os-prober messages. After that install there were no 
problems: installing mdadm made the RAID available without any problems.

I then did a forced shut down the system so that the file systems would 
not be marked clean. This did reproduce the messages during a new install 
while os-prober was run (same for both partitions):
os-prober: debug: running /usr/lib/os-probes/50mounted-tests 
on /dev/discs/disc1/part1
kernel: EXT2-fs: sda1: couldn't mount because of unsupported optional 
features (4).
kernel: EXT3-fs: INFO: recovery required on readonly filesystem.
kernel: EXT3-fs: write access will be enabled during recovery.
kernel: kjournald starting.  Commit interval 5 seconds
kernel: EXT3-fs: recovery complete.
kernel: EXT3-fs: mounted filesystem with ordered data mode.
50mounted-tests: debug: mounted as ext3 filesystem
[...]
os-prober: debug: running /usr/lib/os-probes/50mounted-tests 
on /dev/discs/disc1/part1
kernel: EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 
filesystem as ext2
50mounted-tests: debug: mounted as ext2 filesystem

After the reboot I again installed mdadm. However, I could not reproduce 
any problems during this: the RAID was not out of sync, was assembled 
normally and after mounting it all data was there.

My conclusion is that by itself the fact that os-prober mounts the 
partitions that make up a RAID1 does not damage anything, even if they 
were not unmounted cleanly before.

The real question here seems to be: why were the partitions unclean before 
the installation was started.

Attachment: pgppi5pSvNsdS.pgp
Description: PGP signature


Reply to: