[clug] Repairing bootloader
BAXTER,Adam
adam.baxter at deewr.gov.au
Wed Sep 30 16:34:13 MDT 2009
Should probably let the list know I fixed the bootloader. Ended up using "AutoSuperGrubDisk", which modifies the *windows* bootloader to launch GRUB, then uninstalls itself at next Windows boot.
It uses a modified version of Unetbootin, which is a program to create LiveUSBs from LiveCD/ISOLinux CDs.
I've made a note of the other methods for next time I mess up my bootloaders.
Thanks all!
--Adam
-----Original Message-----
From: linux-bounces at lists.samba.org [mailto:linux-bounces at lists.samba.org] On Behalf Of linux-request at lists.samba.org
Sent: Wednesday, 30 September 2009 21:40
To: linux at lists.samba.org
Subject: linux Digest, Vol 81, Issue 83
Send linux mailing list submissions to
linux at lists.samba.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.samba.org/mailman/listinfo/linux
or, via email, send a message with subject or body 'help' to
linux-request at lists.samba.org
You can reach the person managing the list at
linux-owner at lists.samba.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of linux digest..."
Today's Topics:
1. Swear count per kernel version (jm)
2. Re: EXT4 Reliability [SEC=PERSONAL] (Carlo Hamalainen)
3. Re: EXT4 Reliability [SEC=PERSONAL] (Mike Carden)
4. Re: EXT4 Reliability (Hugh Fisher)
5. Re: EXT4 Reliability [SEC=PERSONAL] (Sam Couter)
6. really customisable system monitor (David Schoen)
7. Re: Non-Job - CLUG monthly meeting organiser person required
(Paul Wayper)
8. Re: Repairing bootloader (David Schoen)
9. Re: Repairing bootloader (David Schoen)
----------------------------------------------------------------------
Message: 1
Date: Wed, 30 Sep 2009 13:03:59 +1000
From: jm <jeffm at ghostgun.com>
To: CLUG List <linux at lists.samba.org>
Subject: [clug] Swear count per kernel version
Message-ID: <4AC2CA9F.3070505 at ghostgun.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Graph of occurance of swear words by kernel version.
http://www.vidarholen.net/contents/wordcount/
Jeff.
------------------------------
Message: 2
Date: Wed, 30 Sep 2009 08:26:16 +0200
From: Carlo Hamalainen <carlo.hamalainen at gmail.com>
To: CLUG List <linux at lists.samba.org>
Subject: Re: [clug] EXT4 Reliability [SEC=PERSONAL]
Message-ID:
<46ba3d380909292326w67dfc1e3oe03f82b9fd0e08d2 at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
On Wed, Sep 30, 2009 at 2:23 AM, Alex Satrapa <alexsatrapa at mac.com> wrote:
> Longevity of the information can be assured by copying the files from the
> old file system to the new file system (along with assumptions that you'll
> *always* have Data and Resource forks, right? they're sacred and Apple will
> *never* take them away).
I'm just curious about what you mean by Data and Resource forks?
--
Carlo Hamalainen
http://carlo-hamalainen.net
------------------------------
Message: 3
Date: Wed, 30 Sep 2009 16:38:14 +1000
From: Mike Carden <mike.carden at gmail.com>
To: CLUG List <linux at lists.samba.org>
Subject: Re: [clug] EXT4 Reliability [SEC=PERSONAL]
Message-ID:
<24dc89620909292338w6a2fb691g4bd75e3a6c15921b at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
On Wed, Sep 30, 2009 at 4:26 PM, Carlo Hamalainen
<carlo.hamalainen at gmail.com> wrote:
> I'm just curious about what you mean by Data and Resource forks?
They were a feature of one of Apple's old file systems:
http://en.wikipedia.org/wiki/Resource_fork
I think Alex was suggesting that if you were a pre-OSX Apple user, you
might never imagine that the eminently sensible practice of having a
dedicated metadata spot in your file system might ever go away.
--
MC
------------------------------
Message: 4
Date: Wed, 30 Sep 2009 17:01:05 +1000
From: Hugh Fisher <hugh.fisher at anu.edu.au>
To: CLUG List <linux at lists.samba.org>
Subject: Re: [clug] EXT4 Reliability
Message-ID: <4AC30231.8090105 at anu.edu.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Mike Carden wrote:
>
> I think Alex was suggesting that if you were a pre-OSX Apple user, you
> might never imagine that the eminently sensible practice of having a
> dedicated metadata spot in your file system might ever go away.
And they haven't. Apple have deprecated the original resource
fork API, but the resource forks are kept around as extended
attributes in MacOS X. (If they weren't, MacOS 9 and earlier
apps couldn't run.)
Even in the Classic MacOS days, not many people liked resource
forks for document/data files, because they invariably got lost
when transferring files to other computers, and the Internet
more or less killed them off altogether. (A fair number of apps
would still store stuff like window size or current selection
when last opened in the resource fork, but absolutely nothing
that users might miss.)
cheers,
Hugh
------------------------------
Message: 5
Date: Wed, 30 Sep 2009 18:49:13 +1000
From: Sam Couter <sam at couter.id.au>
To: linux at lists.samba.org
Subject: Re: [clug] EXT4 Reliability [SEC=PERSONAL]
Message-ID: <20090930084913.GA1339 at tekno.house>
Content-Type: text/plain; charset="us-ascii"
jm <jeffm at ghostgun.com> wrote:
> Of course, as we're talking about archiving the question is "What
> will be readable in X years?". I'm guessing that ISO9660 will be the
> best bet as it's formalised and written down somewhere.
That formalised standard isn't meaningful when it describes an ideal
that nobody really meets.
I'll take an actual, working reference implementation (eg, ext3) over a
theoretical standard any day.
I think Alex has it right though: Keep your data online and alive and
migrate it to new devices periodically. Don't archive data on a shelf or
you'll never see it again. Unless it's printed on paper with inert inks
or chiselled in stone, it's going to die soon.
--
Sam Couter | mailto:sam at couter.id.au
OpenPGP fingerprint: A46B 9BB5 3148 7BEA 1F05 5BD5 8530 03AE DE89 C75C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.samba.org/pipermail/linux/attachments/20090930/3ff22e6e/attachment-0001.pgp>
------------------------------
Message: 6
Date: Wed, 30 Sep 2009 19:44:37 +1000
From: David Schoen <dave at lyte.id.au>
To: CLUG List <linux at lists.samba.org>
Subject: [clug] really customisable system monitor
Message-ID:
<224ff23a0909300244q50a833b5uc0e9d69ca6ef30e2 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi,
Does anyone know of anything that sits in either the system tray or
that I can insert on to a gnome-panel that will let me write custom
scripts and have it run them at custom intervals and will notify me
appropriately depending on values that I define?
Even something close would be good, lots of what I want to do will
essentially reuse nagios check_${stuff} scripts so if it has
compatibility with that, that'd be a bonus.
I'm looking for something that will let me:
* Watch many remote nagios instances without having to start firefox
(nagios-checker)
* Check custom "success" values for lots of scripts that run on my
machine (backups, synchronisations between desktops/laptops,
republishing of calendars in to public_html/*.ics files, pushing of
html org-mode files, the list goes on...)
* Being able to graph anything numerical and provide history of
states on anything that's not would get huge bonus points
I've looked high and low and can't find anything. I was about to start
writing something when I figured I would ask if someone already had
something.
Cheers,
Dave
------------------------------
Message: 7
Date: Wed, 30 Sep 2009 21:04:15 +1000
From: Paul Wayper <paulway at mabula.net>
To: CLUG List <linux at lists.samba.org>
Subject: Re: [clug] Non-Job - CLUG monthly meeting organiser person
required
Message-ID: <4AC33B2F.5090208 at mabula.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 30/09/09 08:34, Robert Brockway wrote:
> Hi all. This seems like quite a lot for one volunteer position.
>
> In the LUGs I've been involved with these tasks are seperated:
>
> Talks Coordinator: Organises talks and makes sure equipment will be at
> the meeting. The talks coordinator is explicitely not required to attend
> meetings. Even if present they don't have any responsibilities at the
> meeting.
>
> MC: Makes announcements, greets & introduces the speaker and deals with
> any last minute issues.
>
> We have never had a position to deal with food but this would seem to a
> suitable 3rd position.
Those are good ideas and I'd be willing to have people volunteer for any or
all of those three. I do think that the talks coordinator should also be the
MC - the person that's started the process with the speakers should be there
to finish it - but that's just my own way of doing things.
I hope this spurs someone on to help out, because right now there's still no
volunteers.
Have fun,
Paul
------------------------------
Message: 8
Date: Wed, 30 Sep 2009 21:25:56 +1000
From: David Schoen <neerolyte at gmail.com>
To: Boyd <boydwilding at gmail.com>
Cc: "linux at lists.samba.org" <linux at lists.samba.org>, "BAXTER, Adam"
<adam.baxter at deewr.gov.au>
Subject: Re: [clug] Repairing bootloader
Message-ID:
<224ff23a0909300425g770c0f3aw90f2891a6672b0b8 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
The process I follow that's loosely described below is this (from
memory, please forgive mistakes):
Boot off live cd, find a root prompt on a terminal somewhere
Mount root partition at something like /mnt/ubuntu , e.g:
# mkdir -p /mnt/ubuntu; mount /dev/sda1 /mnt/ubuntu
Mount proc (out of habit, not sure if it's needed):
# mount -t proc NONE /mnt/ubuntu/proc
Mount /boot, /usr and /var if they are separate partitions (or any
others that seem important that you may have).
chroot in to the ubuntu (non-live cd) environment:
# chroot /mnt/ubuntu
run grub to enter the grub prompt:
# grub
Tell grub where /boot is (or / if you have no /boot):
grub> root (hd0,0)
Tell grub to install itself on to the MBR of my first drive:
grub> setup (hd0)
Then quit everything back to the livecd, umount all the mounted stuff,
reboot, hope.
The above commands need to be tailored to your exact configuration but
hopefully the example helps.
Also once you're in the chroot terminal most people report more
success with grub-install:
# grub-install /dev/sda
but grub-install seems to hates me passionately.
Have fun,
Dave
2009/9/30 Boyd <boydwilding at gmail.com>:
> A quick search of the ubuntu forums has a few solutions.
>
> As far as windows 7 goes, I haven't touched that yet, however I've fixed
> vista and debian/ubuntu dual-boot installs before without problems.
>
> The basic process is: you boot off the ubuntu CD and just reinstall grub to
> /dev/sda (with specific command-lines found somewhere in the aforementioned
> forums) and it should load GRUB first on boot, giving you the boot menu
> showing the linux and windows boot options. If you choose windows, it then
> loads the vista boot loader for you and everything that that contains. (some
> people install vista and XP side by side, so this menu may contain vista as
> well as xp as a windows OS choice).
>
> There is also the sledgehammer solution, to just reinstall debian/ubuntu,
> which then reinstalls grub at the end of the process, detecting any other
> OS's, and everything usually works well once doing that.
>
> YMMV.
>
> On Thu, Sep 24, 2009 at 10:18 AM, BAXTER,Adam <adam.baxter at deewr.gov.au>wrote:
>
>> Hi guys,
>> I know I've left this til the last minute, but I'd like to have my
>> dual-boot machine back up and running before the LUG so I can SSH into it
>> for some troubleshooting by the gurus.
>>
>> I recently installed Windows 7 (yeah yeah, I know), and of course the
>> installer clobbered GRUB. Is there an easy way to fix this from a
>> LiveCD/USB? Every time I try I seem to destroy Windows' bootloader too.
>>
>> My setup is this:
>> Sda1 is Windows
>> Sda2 is Ubuntu
>>
>> I'm assuming the MBR is on /dev/sda, Windows bootloader (bootmgr/ntldr) is
>> on /dev/sda1 and GRUB needs to be installed on /dev/sda.
>>
>> What's the best way to do this?
>>
>> --Adam
>> Notice:
>>
>> The information contained in this email message and any attached files may
>> be confidential information, and may also be the subject of legal
>> professional privilege. If you are not the intended recipient any use,
>> disclosure or copying of this email is unauthorised. If you received this
>> email in error, please notify the DEEWR Service Desk by calling (02) 6240
>> 9999 and delete all copies of this transmission together with any
>> attachments.
>>
>> --
>> linux mailing list
>> linux at lists.samba.org
>> https://lists.samba.org/mailman/listinfo/linux
>>
> --
> linux mailing list
> linux at lists.samba.org
> https://lists.samba.org/mailman/listinfo/linux
>
------------------------------
Message: 9
Date: Wed, 30 Sep 2009 21:40:09 +1000
From: David Schoen <neerolyte at gmail.com>
To: Boyd <boydwilding at gmail.com>
Cc: "linux at lists.samba.org" <linux at lists.samba.org>, "BAXTER, Adam"
<adam.baxter at deewr.gov.au>
Subject: Re: [clug] Repairing bootloader
Message-ID:
<224ff23a0909300440k55aa66b3mb05497f9aee3b427 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Whoops left out getting back in to windows...
What I wrote will get grub reinstalled but not give you access to the
windows boot menu.
Windows XP looks like so (as far as I'm aware Vista/7 work the same
also, but I haven't yet tried either) in your /boot/grub/menu.list
file:
title Microsoft Windows XP Professional
# my windows install is on the first partition on my first hard drive,
or /dev/sda1
rootnoverify (hd0,0)
savedefault
makeactive
chainloader +1
If you get to a grub menu during your boot sequence you can press
something "c" to enter a grub console from which you should be able to
enter:
grub> rootnoverify (hd0,0) # windows partition
grub> makeactive
grub> chainload +1
and try different drives/partitions until you find your windows one
(note that they tab complete at the boot console).
This way if you're not sure which one is the windows install you can
figure it out (although there's probably a better way).
Once you know the right sequence you can put it back in /boot/grub/menu.lst
Have fun,
Dave
2009/9/30 David Schoen <neerolyte at gmail.com>:
> The process I follow that's loosely described below is this (from
> memory, please forgive mistakes):
>
> Boot off live cd, find a root prompt on a terminal somewhere
>
> Mount root partition at something like /mnt/ubuntu , e.g:
> # mkdir -p /mnt/ubuntu; mount /dev/sda1 /mnt/ubuntu
>
> Mount proc (out of habit, not sure if it's needed):
> # mount -t proc NONE /mnt/ubuntu/proc
>
> Mount /boot, /usr and /var if they are separate partitions (or any
> others that seem important that you may have).
>
> chroot in to the ubuntu (non-live cd) environment:
> # chroot /mnt/ubuntu
>
> run grub to enter the grub prompt:
> # grub
>
> Tell grub where /boot is (or / if you have no /boot):
> grub> root (hd0,0)
>
> Tell grub to install itself on to the MBR of my first drive:
> grub> setup (hd0)
>
> Then quit everything back to the livecd, umount all the mounted stuff,
> reboot, hope.
>
> The above commands need to be tailored to your exact configuration but
> hopefully the example helps.
>
> Also once you're in the chroot terminal most people report more
> success with grub-install:
> # grub-install /dev/sda
> but grub-install seems to hates me passionately.
>
>
> Have fun,
> Dave
>
> 2009/9/30 Boyd <boydwilding at gmail.com>:
>> A quick search of the ubuntu forums has a few solutions.
>>
>> As far as windows 7 goes, I haven't touched that yet, however I've fixed
>> vista and debian/ubuntu dual-boot installs before without problems.
>>
>> The basic process is: you boot off the ubuntu CD and just reinstall grub to
>> /dev/sda (with specific command-lines found somewhere in the aforementioned
>> forums) and it should load GRUB first on boot, giving you the boot menu
>> showing the linux and windows boot options. If you choose windows, it then
>> loads the vista boot loader for you and everything that that contains. (some
>> people install vista and XP side by side, so this menu may contain vista as
>> well as xp as a windows OS choice).
>>
>> There is also the sledgehammer solution, to just reinstall debian/ubuntu,
>> which then reinstalls grub at the end of the process, detecting any other
>> OS's, and everything usually works well once doing that.
>>
>> YMMV.
>>
>> On Thu, Sep 24, 2009 at 10:18 AM, BAXTER,Adam <adam.baxter at deewr.gov.au>wrote:
>>
>>> Hi guys,
>>> I know I've left this til the last minute, but I'd like to have my
>>> dual-boot machine back up and running before the LUG so I can SSH into it
>>> for some troubleshooting by the gurus.
>>>
>>> I recently installed Windows 7 (yeah yeah, I know), and of course the
>>> installer clobbered GRUB. Is there an easy way to fix this from a
>>> LiveCD/USB? Every time I try I seem to destroy Windows' bootloader too.
>>>
>>> My setup is this:
>>> Sda1 is Windows
>>> Sda2 is Ubuntu
>>>
>>> I'm assuming the MBR is on /dev/sda, Windows bootloader (bootmgr/ntldr) is
>>> on /dev/sda1 and GRUB needs to be installed on /dev/sda.
>>>
>>> What's the best way to do this?
>>>
>>> --Adam
>>> Notice:
>>>
>>> The information contained in this email message and any attached files may
>>> be confidential information, and may also be the subject of legal
>>> professional privilege. If you are not the intended recipient any use,
>>> disclosure or copying of this email is unauthorised. If you received this
>>> email in error, please notify the DEEWR Service Desk by calling (02) 6240
>>> 9999 and delete all copies of this transmission together with any
>>> attachments.
>>>
>>> --
>>> linux mailing list
>>> linux at lists.samba.org
>>> https://lists.samba.org/mailman/listinfo/linux
>>>
>> --
>> linux mailing list
>> linux at lists.samba.org
>> https://lists.samba.org/mailman/listinfo/linux
>>
>
------------------------------
_______________________________________________
linux mailing list
linux at lists.samba.org
https://lists.samba.org/mailman/listinfo/linux
End of linux Digest, Vol 81, Issue 83
*************************************
Notice:
The information contained in this email message and any attached files may be confidential information, and may also be the subject of legal professional privilege. If you are not the intended recipient any use, disclosure or copying of this email is unauthorised. If you received this email in error, please notify the DEEWR Service Desk by calling (02) 6240 9999 and delete all copies of this transmission together with any attachments.
More information about the linux
mailing list