Lucio Crusca wrote: > The installation starts normally, it leads me through all the steps, it > formats the filesystem, copies files, but in the end GRUB installation > fails. I've tried both UEFI and CSM bios settings with no luck, always same > error: > > [!!] install GRUB boot loader on disk > Installation step failed > > or something like that, I just can't copy and paste. > > Unfortunately even the 4th console does not say anything useful, like the > reason why it failed. Dmesg doesn't say a thing about this. The only time I have ever had this problem was with a previous Debian release (Etch 4.0 or Lenny 5.0, don't remember) and setting up the root filesystem on lvm *without* a separate /boot partition. However I believe that is handled correctly with the current release and later. But this leads me to believe that the problem must be associated with how the disk is partitioned. And since you are setting up raid that will be the most complicated choices made during operating the installer. > I have two SATA disks 1TB each in software RAID, but I've already tried > using only one disk without raid and with only 1 partition and obtained the > same error. That would have been my suggestion. If you didn't select the simplest options then I would double check with a single disk and make sure that there isn't any raid or lvm being used for the "simple" test. My next suggestion would be to use the install media as a rescue system. (I have been suggesting that a lot lately. Sorry for being so repetitive but it seems useful here too.) Here about half way down this previous posting is where I described it in most detail so I won't repeat that part here again. http://lists.debian.org/debian-user/2013/01/msg01127.html After booting the rescue and launching a full bash shell you should be able to have access to the network and to run full commands. That will be useful for debugging. You can run commands and save off the output as needed. I would typically set up remote sshd login capability and log in remotely from another machine and debug from there. Can then cut and paste easily. In either case you should be able to run 'grub-install' manually from the command line at that point and any errors it produces will be immediately available. root@example:~# grub-install /dev/sda If it produces any errors those will now be visible directly without the debian-installer needing to be in the middle of the interface. Bob
Attachment:
signature.asc
Description: Digital signature