search for: bootinfoscript

Hello, I was looking for a way to detect the installed boot loader of an image and I found this: https://github.com/arvidjaar/bootinfoscript This script will inspection a lot of things on a running system and will output a Report. The most interesting part is that it uses known Master and Volume Boot Record byte-patterns to determine the installed boot loader: https://github.com/arvidjaar/bootinfoscript/blob/master/bootinfoscript#L2983...

On Fri, Jun 19, 2015 at 01:53:13PM +0300, Nikos Skalkotos wrote: > Hello, > > I was looking for a way to detect the installed boot loader of an image > and I found this: https://github.com/arvidjaar/bootinfoscript > This script will inspection a lot of things on a running system and will > output a Report. The most interesting part is that it uses known Master > and Volume Boot Record byte-patterns to determine the installed boot loader: > https://github.com/arvidjaar/bootinfoscript/blob/master/...

Please, download this. http://sourceforge.net/projects/bootinfoscript/ Run it: http://bootinfoscript.sourceforge.net/ Post a URL to the resulting file somewhere. I suggest having the entire computer assembled as it should be in normal use, rather than simulating device failure by removing a device. --- Chris Murphy

On 8/5/2015 1:30 PM, Chris Murphy wrote: > Please, download this. > http://sourceforge.net/projects/bootinfoscript/ > > Run it: > http://bootinfoscript.sourceforge.net/ > > Post a URL to the resulting file somewhere. I suggest having the > entire computer assembled as it should be in normal use, rather than > simulating device failure by removing a device. http://pastebin.com/sgWTYpp4 --...

On 8/5/2015 1:00 PM, Chris Murphy wrote: > On Wed, Aug 5, 2015 at 10:52 AM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: >> How would I go about pointing it at the partition? >> >> What I am currently doing is this: >> device (hd0) /dev/hdg >> root (hd0,0) >> setup (hd0) > > setup (hd1,0) > > It's hd1 if your device map is correct and

- Ahh OK now I see why I was confused. The originally posted partition map uses cylinders as units, not LBA. I missed that. Cylinder 1 is the same as LBA 63. And that is sufficiently large for a GRUB legacy stage 2. - OK this is screwy. Partitions 1 and 3 on both drives have the same number of sectors, but partitions 2 differ: /dev/hde2 401,625 975,691,709 975,290,085 fd Linux