Processed: Re: Bug#445148: S390: Build w/ /boot partition succeeds, but re-boot fails in fsck

Processing commands for [EMAIL PROTECTED]: > severity 445148 serious Bug#445148: S390: Build w/ /boot partition succeeds, but re-boot fails in fsck Severity set to `serious' from `important' > reassign 445148 debian-installer 20070308 Bug#445148: S390: Build w/ /boot partition

Re: Bug#445148: S390: Build w/ /boot partition succeeds, but re-boot fails in fsck

severity 445148 serious reassign 445148 debian-installer 20070308 thanks On Monday 08 October 2007, Frans Pop wrote: > This does not seem to be an installation problem. Instead it looks like > either the boot loader or the kernel is not releasing the partition > holding /boot after the kernel and/

Bug#445148: S390: Build w/ /boot partition succeeds, but re-boot fails in fsck

tags 445148 confirmed reassign 445148 s390-tools thanks > Install boot went as expected, up until the first re-boot. After > rebooting, system fails in fsck because one of the partitions is > "already mounted". > > Configuration is a 125 cylinder /dev/dasda1, which is to be mounted > as /boot, and

Processed: Bug#445148: S390: Build w/ /boot partition succeeds, but re-boot fails in fsck

Processing commands for [EMAIL PROTECTED]: > tags 445148 confirmed Bug#445148: S390: Build w/ /boot partition succeeds, but re-boot fails in fsck There were no tags set. Tags added: confirmed > reassign 445148 s390-tools Bug#445148: S390: Build w/ /boot partition succeeds, but re-boot fa

Bug#445148: S390: Build w/ /boot partition succeeds, but re-boot fails in fsck

Paste your message below (end with ^D) or cancel with ^C: Sorry, my previous reply is obviously incorrect. The kernel parameter needs to point to the boot partition. I'm not sure what the correct configuration should beto boot with a separate /boot partition on S/390. The manpage for zipl.conf doe

Bug#445148: S390: Build w/ /boot partition succeeds, but re-boot fails in fsck

severity 445148 important reassign 445148 zipl-installer thanks > Configuration is a 125 cylinder /dev/dasda1, which is to be mounted > as /boot, and a large /dev/dasdb1 which is to be mounted as /. > > fsck fails for dasda1, but I don't see anywhere that dasda1 is mounted. > mount /boot says that

Processed: Re: Bug#445148: S390: Build w/ /boot partition succeeds, but re-boot fails in fsck

Processing commands for [EMAIL PROTECTED]: > severity 445148 important Bug#445148: S390: Build w/ /boot partition succeeds, but re-boot fails in fsck Severity set to `important' from `normal' > reassign 445148 zipl-installer Bug#445148: S390: Build w/ /boot partition succeeds, b