Which disk would I download to get into rescue mode on F14 x86_64?
All I need to do is reinstall grub, after (hopefully) repairing a broken Windows XP that I have not been able to boot for a year because of having gotten a new motherboard a year ago.
I do not have a floppy drive or any type of usb drive. All I have are my hard drives and a CD/DVD drive.
On Wed, 2011-01-26 at 10:57 -0700, Petrus de Calguarium wrote:
Which disk would I download to get into rescue mode on F14 x86_64?
All I need to do is reinstall grub, after (hopefully) repairing a broken Windows XP that I have not been able to boot for a year because of having gotten a new motherboard a year ago.
I do not have a floppy drive or any type of usb drive. All I have are my hard drives and a CD/DVD drive.
Petrus,
You can boot your system using the F14 x86_64 installation DVD (or first CD image). At the install menu select the Rescue option.
--Doc Savage Fairview Heights, IL
OK. Thanks to both of you. Yes, I had feared that this might be the only way.
I didn't want to have to download 700MB just to be able to reinstall grub, but I guess that is the only way.
I don't have an installation disk, since I did a system upgrade from f13 to f14. I no longer have the f13 installation disk and I imagine that it wouldn't work, now that I am using f14.
On 01/26/2011 02:22 PM, Petrus de Calguarium wrote:
OK. Thanks to both of you. Yes, I had feared that this might be the only way.
I didn't want to have to download 700MB just to be able to reinstall grub, but I guess that is the only way.
I don't have an installation disk, since I did a system upgrade from f13 to f14. I no longer have the f13 installation disk and I imagine that it wouldn't work, now that I am using f14.
maybe http://boot.fedoraproject.org/index can be useful
Gabriel
On Wed, 2011-01-26 at 13:22 -0700, Petrus de Calguarium wrote:
OK. Thanks to both of you. Yes, I had feared that this might be the only way.
I didn't want to have to download 700MB just to be able to reinstall grub, but I guess that is the only way.
I don't have an installation disk, since I did a system upgrade from f13 to f14. I no longer have the f13 installation disk and I imagine that it wouldn't work, now that I am using f14.
Petrus,
You can also use the much smaller (220 MB) boot.iso CD image. You can find it on a mirror site at:
.../releases/14/Fedora/x86_64/os/images/boot.iso
--Doc Savage Fairview Heights, IL
Robert G. (Doc) Savage wrote:
You can also use the much smaller (220 MB) boot.iso CD image. You can find it on a mirror site at:
.../releases/14/Fedora/x86_64/os/images/boot.iso
I already tried that. It didn't work. A black screen appeared with a grub menu and it was not able to detect that I already had grub installed to the MBR of the first hard drive. It did not give me the normal option of a rescue disk, where you hit the ESC or TAB or whatever in order to type 'linux rescue'. As a result, I fumbled around with grub commands, telling it which was root and kernel and initrd, but with the new fedora kernel boot line that sets up the keyboard and all that other stuff, which is impossible to remember in its entirety, the boot failed, hanging even before plymouth. And booting the system was not what I wanted, I wanted rescue.
Gabriel Ramirez wrote:
maybe http://boot.fedoraproject.org/index can be useful
Thank you. I had downloaded it about a year ago when I first heard about it, but never tried it. I decided to get a new version, in case it changed, and burnt it to disk. It must have taken 15-20 minutes for it to load and download the image and whatever it needs, despite a high-speed internet connection, but it works like a charm. It is good to know that I feel comfortable with BFO as a failsafe.
Unfortunately, Windows refused to repair the installed system and a blue screen appeared telling me to remove the new hardware and try again. How stupid. I cannot remove the motherboard! I guess if I want Windows, I will have to wipe that partition and reinstall it, which is exactly what I had hoped never to need to do again when I installed it to that partition in the first place. Then, despite not being able to repair itself, Windows changed the system clock from UTC to local time, so fedora needed to do a complete relabelling before I could finally boot up again. Man alive! Fortunately, I do have a working version of Windows installed to a qemu image file, so I can still access some of those pesky services that refuse to work without Windows (Adobe Digital Editions, Overdrive DRM-encumbered audiobooks, Mobibook reader, etc. -- stuff from the public library that I need to access).
Thanks for all of the suggestions. My system is intact and Windows is still broken, but after a year of it being broken, I guess I don't need it anyhow.
On Wed, 2011-01-26 at 21:25 -0700, Petrus de Calguarium wrote:
Windows changed the system clock from UTC to local time, so fedora needed to do a complete relabelling before I could finally boot up again.
I can't see why that was necessary.
Tim wrote:
On Wed, 2011-01-26 at 21:25 -0700, Petrus de Calguarium wrote:
Windows changed the system clock from UTC to local time, so fedora needed to do a complete relabelling before I could finally boot up again.
I can't see why that was necessary.
I've experienced it before. It says something like the last disk access is in the future, or something like that.
On 01/27/2011 10:14 AM, Petrus de Calguarium wrote:
Tim wrote:
On Wed, 2011-01-26 at 21:25 -0700, Petrus de Calguarium wrote:
Windows changed the system clock from UTC to local time, so fedora needed to do a complete relabelling before I could finally boot up again.
I can't see why that was necessary.
I've experienced it before. It says something like the last disk access is in the future, or something like that.
IIRC, Windows forces the hardware clock to the local time. If you intend to dual-boot between Winblows and Linux, uncheck the "System clock uses UTC" button in system-config-date "Time Zone" tab and adjust your clock again to make sure it's right.
---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, C2 Hosting ricks@nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - All generalizations are false. - ----------------------------------------------------------------------
Rick Stevens <ricks <at> nerd.com> writes:
IIRC, Windows forces the hardware clock to the local time. If you intend to dual-boot between Winblows and Linux, uncheck the "System clock uses UTC" button in system-config-date "Time Zone" tab and adjust your clock again to make sure it's right.
There's a registry hack, which I use on both XP and Vista, and should work on Windows 7 as well, that will make Windows interpret the hardware clock as UTC (search for "registry UTC"). It works fine for me, though I've heard there may be issues with suspend/hibernate (which I don't normally do).
Andre Robatino <robatino <at> fedoraproject.org> writes:
There's a registry hack, which I use on both XP and Vista, and should work on Windows 7 as well, that will make Windows interpret the hardware clock as UTC (search for "registry UTC"). It works fine for me, though I've heard there may be issues with suspend/hibernate (which I don't normally do).
Probably a better search is for "RealTimeIsUniversal" which is the registry key that needs to be set (to 1). When using this on a dual-boot system, I make sure that only the more frequently used OS (Linux in my case) has NTP enabled, since they aren't aware of each other.
Petrus de Calguarium:
Windows changed the system clock from UTC to local time, so fedora needed to do a complete relabelling before I could finally boot up again.
Tim:
I can't see why that was necessary.
Petrus de Calguarium:
I've experienced it before. It says something like the last disk access is in the future, or something like that.
I've had that error before, and it only entailed a short correction of a small amount of data on the drive (automatically). Probably only about five seconds. Certainly not going through the entire drive.
What filing system are you using?
On 01/27/2011 07:58 PM, Rick Stevens wrote:
IIRC, Windows forces the hardware clock to the local time. If you intend to dual-boot between Winblows and Linux, uncheck the "System clock uses UTC" button in system-config-date "Time Zone" tab and adjust your clock again to make sure it's right.
IIRC, if you do that the clock you will have problems at next daylight saving time change. Linux will assume the hw clock is local time, but the hw clock does not know about DST. If you boot Windows, it will detect that there has been a change of DST between last boot and this one and do the correction to the hw clock. Then you boot Linux and it is OK.
There are a big number of failure scenarios: - what if you do not boot windows for some time? - what if you boot many windows instances from different partitions? - if you make the correction in Linux and than you boot Windows, it overcorrects, so you have to undo the second correction manually
Basically timezone management in Windows is a total mess.
Try the registry switch to let Windows run the hw clock in UTC mode, as suggested by someone else. Never tried if it really works. But at least it will leave your hw clock alone and Linux will never be affected.
In this case the usual failure scenario is that someone sees a wrong time in the BIOS (UTC) and "corrects" it to the local time. :-)
On Fri, Jan 28, 2011 at 3:47 PM, Roberto Ragusa mail@robertoragusa.it wrote:
Try the registry switch to let Windows run the hw clock in UTC mode, as suggested by someone else. Never tried if it really works. But at least it will leave your hw clock alone and Linux will never be affected.
I have used it with XP and it works very well. However I don't have the hack handy at this moment. But I do recall I got it from a thread on this list about 2 years ago. I think that Mikkel mentioned it in a response to one of my posts. As far as I recall I helped someone with the same issue sometime last year and all of the information was posted again. Hope this helps with the archive search.
On 01/28/2011 06:47 AM, Roberto Ragusa wrote:
In this case the usual failure scenario is that someone sees a wrong time in the BIOS (UTC) and "corrects" it to the local time.
BTDTGTTS.
My desktop has Win98 on it, although I only boot into it once a year or so. (There are one or two programs that SELinux won't let work right under Wine that I need once in a blue moon or two.) I've always kept the hw clock on local time for simplicity, as it's not exactly hard to adjust for Daylight Wasting Time.
When I bought a new laptop, I blew away Winderz iCandy and put Fedora on it as the sole OS. Naturally, I set it to UTC. There was a problem with Fedora 11 that hung the laptop in a way that made it look like it was overheating, meaning I had to diddle with the BIOS trying to figure it out. (The fix was Fedora 12.) Naturally, I forgot I'd set it to UTC, causing great confusion until I remembered what I'd done.
Robert G. (Doc) Savage wrote:
You can also use the much smaller (220 MB) boot.iso CD image.
I guess I could just have gone to the command shell and run the install command, eh? Just get to the grub shell and run root and setup commands. I never thought of that until now. I thought I had to run the grub package that is installed on my partition.
-
Andre Robatino -
Gabriel Ramirez -
Joe Zeff -
Peter G. -
Rick Stevens -
Robert G. (Doc) Savage -
Roberto Ragusa -
Suvayu Ali -
Tim