Re: 10.3 repair options abort
- From: David Bolt <blacklist-me@xxxxxxxxxx>
- Date: Fri, 12 Oct 2007 04:41:28 +0100
On Thu, 11 Oct 2007, John Bowling wrote:-
Selecting either the repair on the grub menu from the DVD or repair after
selecting install > other > repair shut the system down immediately and
rebooted.
Not seen that, but only tried the repair option once. It didn't do the
repair[0] but it still didn't shut the system down.
This is with an installed 10.3 system (not beta or RC) that works for the
most part. My original DVD had a checksum error I didn't catch and it
installed except for qt3.
You didn't check the MD5SUM when you downloaded it, did you? And I bet
you didn't do a media check either? They are supplied/there for a
reason.
Update didn't fix it even though it warned me
about it.
You tried to do an upgrade install over the top of the existing install
and it wouldn't do it?
This should not prevent it from doing a repair from a good DVD.
If a package failed to install, a repair won't do anything about it.
Just go into the package management and force it to install the
package(s) that were broken.
I made a new DVD with valid checksum
You checked it this time?
and first installed it onto a Compaq
Evo N400c laptop and it works very well [700M Pentium III, 256M RAM, 20G
HD]. Then I attempted the repair options to see if it would replace the
missing files.
What makes you think it would add the missing files? Package management
would if they were required to satisfy dependencies. If not, and they
aren't required by an installed pattern, they won't be added. Then you
just need to install them yourself.
I am doing a full reinstall currently.
WTF for? Use the package management system. Tell it to either install
the packages that it missed or, if it thinks they're there but the
aren't, tell it to upgrade them. Either way would be a lot quicker than
doing a full reinstall.
[0] 10.3 on an iMac. For some reason the system refuses to boot from
anything but the Mac OS partition. Repeated repairs/rewrites of the boot
loader have done absolutely nothing so my present method on starting it
is to boot the DVD, select install and then use the "boot installed
system" option. And, I know it's not a SUSE issue, as I've also tried
the PPC version of Debian and that fails in exactly the same way. I
think it's related to the partitioning of the drive/drive size but can't
test that until I get my hands on a much smaller drive (80GB or less).
Regards,
David Bolt
--
Member of Team Acorn checking nodes at 100 Mnodes/s: www.distributed.net
SUSE 10.0 32bit | SUSE 10.1 32bit | openSUSE 10.2 32bit | openSUSE 10.3 32bit
SUSE 10.0 64bit | SUSE 10.1 64bit | openSUSE 10.2 64bit |
RISC OS 3.11 | RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC
.
- Follow-Ups:
- Re: 10.3 repair options abort
- From: John Bowling
- Re: 10.3 repair options abort
- References:
- 10.3 repair options abort
- From: John Bowling
- 10.3 repair options abort
- Prev by Date: Re: Something blocking Java in 10.3?
- Next by Date: Re: 10.3 repair options abort
- Previous by thread: 10.3 repair options abort
- Next by thread: Re: 10.3 repair options abort
- Index(es):
Relevant Pages
|
