On 05/22/2013 04:45 PM, Sebastian Canagaratna wrote:
Thank uou Frank and Klaus. As you surmised, it was a typo : I meant to
say /dev/sda to be sure I repeated the grub-install
and the version given by bootinfoscript if 1.99 though AI have
2.00-14. When I use grub rescue and type set
prefixs=(hd1,msdos1)/boot/grub and then root=(hd1,msdos1) and insmod
normal it gives unknown file system error.
Sebastian
On Wed, May 22, 2013 at 7:19 PM, Frank McCormick
<debianl...@videotron.ca <mailto:debianl...@videotron.ca>> wrote:
On 05/22/2013 05:21 PM, Sebastian Canagaratna wrote:
Further to the questions I raised, I downloaded supergrub2 and
I was
able to access the system.However, after starting 3.9.3.slh-1 and
running update-grub and grub-install /dev/sda0 ( the installation
finished. No error reported) still, on rebooting, come to the
same error
I think you should be installing grub in /dev/sda, the MBR not
a partition.
--
Cheers
Frank
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
<mailto:debian-user-requ...@lists.debian.org> with a subject of
"unsubscribe". Trouble? Contact listmas...@lists.debian.org
<mailto:listmas...@lists.debian.org>
Archive: http://lists.debian.org/519d5267.1070...@videotron.ca
Hi all
Actully fdisk -l shows the Master Boot Record (MBR) on /dev/sda1. This
is the standard place for it for ext type formats. It and the partition
table are in the first 512 bytes of first partition. I formatted both
systems months ago and have had no trouble until now. All test show that
there is nothing wrong with the partitioning. Further, I did nothing to
the disk partitions during the update. As I said earlier, my other
identical system works fine and the bad system only started giving
trouble after a fairly massive update.
Sebastian, Your root="(hd0,msdos1)" should be 'set root="(hd0,msdos1)".'
I don't know whether that is a typo or whether leaving off set would
make a difference but my information says it should be "set root".
Gary R.
