Your message dated Sat, 31 Aug 2013 12:52:13 +0200 with message-id <201308311252.51555.holger@layer-acht.org> and subject line dealing with old installation-reports has caused the Debian Bug report #705187, regarding Installation bug 6.0.7 incorrectly boot to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 705187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705187 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Re: Installation bug 6.0.7 incorrectly boot
- From: "Oleg V. Rukhlov" <rukhlovov@gmail.com>
- Date: Thu, 11 Apr 2013 07:14:22 +0400
- Message-id: <CAJBYBXYF4ozgsMxzmK=EyM1_8EHzW8qvSkPs0Z4y5VwAYbQG4A@mail.gmail.com>
- In-reply-to: <CAJBYBXY3+K0wONgmX8h7okoF3WPS68OnWmgFFJiL4dbjCmYgJQ@mail.gmail.com>
- References: <CAJBYBXY3+K0wONgmX8h7okoF3WPS68OnWmgFFJiL4dbjCmYgJQ@mail.gmail.com>
Package: installVersion: 6.0.7If the disk contains the OS Windows + Windows-recovery on installation Debian is after trying GRUB record makes it impossible to load any of the OS.
This is because it is an bootable partition on which Debian is installed, but the GRUB is written to the not bootable partition. (It was automatic disk partitioning with separate /home).
This happened on two laptops:
Toshiba Satellite A660-157, Windows 7 + section recovery from Acronis
Asus U32U, Windows 7 + serial section recovery
So users are not familiar with Debian is not able to try it when installed together with Windows and generally unable to function laptop.
For further corrections have to use a boot live-image and install GRUB thrugh terminal. Installing Debian is not completed (not created Root password, user, etc.)
Here is image
http://postimg.org/image/e2lzeit7v/
and here details of problem and solution
http://www.linux.org.ru/forum/linux-install/9034841#commentsBest regards, Oleg
--- End Message ---
--- Begin Message ---
- To: control@bugs.debian.org, 686953-done@bugs.debian.org, 706320-done@bugs.debian.org, 705790-done@bugs.debian.org, 705187-done@bugs.debian.org, 702294-done@bugs.debian.org, 701196-done@bugs.debian.org, 700918-done@bugs.debian.org, 700378-done@bugs.debian.org, 700175-done@bugs.debian.org, 699760-done@bugs.debian.org, 699478-done@bugs.debian.org, 699136-done@bugs.debian.org, 698933-done@bugs.debian.org, 698878-done@bugs.debian.org, 698877-done@bugs.debian.org, 698739-done@bugs.debian.org, 697915-done@bugs.debian.org, 697645-done@bugs.debian.org, 697442-done@bugs.debian.org, 697327-done@bugs.debian.org, 696770-done@bugs.debian.org
- Subject: dealing with old installation-reports
- From: Holger Levsen <holger@layer-acht.org>
- Date: Sat, 31 Aug 2013 12:52:13 +0200
- Message-id: <201308311252.51555.holger@layer-acht.org>
reassign 699136 partman retitle 699136 partman hangs with specific mbr/usbsticks tags 696755 +confirmed Hi, thank you for submitting installation reports, much appreciated. I read through all the bugs mentioned here (and I'm sure they were read by several people at the time they were submitted) and am closing them now as/if - they (finally) indicated success and/or - I know from first hand experience that the functionality is working in Wheezy and/or - they only contained very little information and/or - they contained user errors and/or - they were caused by broken hardware and/or - they have been from a development phase where things were not stable and/or - they are quite old (and thus likely fixed today) and/or - moreinfo was asked and not given or - they are wishlist but rather special + exotic and not have been acted on for years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to close wishlist bugs.) If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll do if requested) or just file a new one - thats often better, as the bug log will be clearer and shorter and not contain cruft. cheers, HolgerAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---