10:47 a.m.
I updated to 2.6.12 kernel without updating something else necessary,
apparently and have hosed my system. The real problem is that it won't
boot of disk. We had 2 64 bit systems have the kernel problem and the
other is back up and running fine. The only disk I can get the second
system to boot is off a 386 iso, which causes problems when I try and do
anything (including chroot /mnt/sysimage) so I can't really rescue the
system. I'd be ok with reinstalling, because I was just doing the
initial system set-up anyway, but I can't figure out how to do that
without being able to boot off a cd. The instructions I've found from
booting from the network start with--boot from an iso cd (not helpful).
Any input would be appreciated.
Thanks
Anne
11:10 a.m.
Am Mo, den 01.08.2005 schrieb Anne Ramey um 17:47:
I updated to 2.6.12 kernel without updating something else necessary,
apparently and have hosed my system. The real problem is that it won't
boot of disk. We had 2 64 bit systems have the kernel problem and the
other is back up and running fine. The only disk I can get the second
system to boot is off a 386 iso, which causes problems when I try and do
anything (including chroot /mnt/sysimage) so I can't really rescue the
system. I'd be ok with reinstalling, because I was just doing the
initial system set-up anyway, but I can't figure out how to do that
without being able to boot off a cd. The instructions I've found from
booting from the network start with--boot from an iso cd (not helpful).
Anne
How did you initially install the machine in question? At that time it
booted from your CD but now after a kernel update it does not any
longer? Please provide hardware information, especially about the
controller (IDE / SCSI) and what else might be important.
Alexander
--
Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773
legal statement: http://www.uni-x.org/legal.html
Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp
Serendipity 18:09:13 up 16 days, 22:41, load average: 0.12, 0.17, 0.23
12:03 p.m.
Alexander Dalloz wrote:
Am Mo, den 01.08.2005 schrieb Anne Ramey um 17:47:
>I updated to 2.6.12 kernel without updating something else necessary,
>apparently and have hosed my system. The real problem is that it won't
>boot of disk. We had 2 64 bit systems have the kernel problem and the
>other is back up and running fine. The only disk I can get the second
>system to boot is off a 386 iso, which causes problems when I try and do
>anything (including chroot /mnt/sysimage) so I can't really rescue the
>system. I'd be ok with reinstalling, because I was just doing the
>initial system set-up anyway, but I can't figure out how to do that
>without being able to boot off a cd. The instructions I've found from
>booting from the network start with--boot from an iso cd (not helpful).
>Anne
How did you initially install the machine in question? At that time it
booted from your CD but now after a kernel update it does not any
longer? Please provide hardware information, especially about the
controller (IDE / SCSI) and what else might be important.
Alexander
The machine came with fedora 3 (kernel 2.6.10) installed, so I guess it
did boot from 64 bit CD at one point, but I never did it.
Hardware RAID: 8-Ch 3Ware SATA 9500S-8 w/ battery
IDE Devices: hda: QSI CD-RW/DVD-ROM SBW242C
SCSI Devices: AMCC 9500S-8 DISK (Direct-Access)
This is the system info for the system that did come back up:
http://daredevil.blast.com/sys/
The only differences between the two are disk size and sw/hw raid.
Daredevil has software raid, the dead one has hw raid.
Anne
12:12 p.m.
Alexander Dalloz wrote:
> Am Mo, den 01.08.2005 schrieb Anne Ramey um 17:47:
>
>
>>I updated to 2.6.12 kernel without updating something else necessary,
>>apparently and have hosed my system. The real problem is that it won't
>>boot of disk. We had 2 64 bit systems have the kernel problem and the
>>other is back up and running fine. The only disk I can get the second
>>system to boot is off a 386 iso, which causes problems when I try and do
>>anything (including chroot /mnt/sysimage) so I can't really rescue the
>>system. I'd be ok with reinstalling, because I was just doing the
>>initial system set-up anyway, but I can't figure out how to do that
>>without being able to boot off a cd. The instructions I've found from
>>booting from the network start with--boot from an iso cd (not helpful).
>
>
>>Anne
>
>
> How did you initially install the machine in question? At that time it
> booted from your CD but now after a kernel update it does not any
> longer? Please provide hardware information, especially about the
> controller (IDE / SCSI) and what else might be important.
>
> Alexander
>
>
>
The machine came with fedora 3 (kernel 2.6.10) installed, so I guess it
did boot from 64 bit CD at one point, but I never did it.
Hardware RAID: 8-Ch 3Ware SATA 9500S-8 w/ battery
IDE Devices: hda: QSI CD-RW/DVD-ROM SBW242C
SCSI Devices: AMCC 9500S-8 DISK (Direct-Access)
This is the system info for the system that did come back up:
http://daredevil.blast.com/sys/
The only differences between the two are disk size and sw/hw raid.
Daredevil has software raid, the dead one has hw raid.
Anne
When you say it 'wont boot off CD', what sort of error msg do
you get? Is your BIOS config'd to boot from CD as the first choice,
or is the box still actually trying to boot from your raid system?
Cheers,
Terry.
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
12:16 p.m.
If you put the cd into another system (regardless of os) do you see only one
file or lots of files and directories? I did this just the other day even
though I knew better. If you only see one file you have made a coaster; you
should see multiple files.
Marc
On 8/1/05, T. Horsnell <tsh(a)mrc-lmb.cam.ac.uk> wrote:
>Alexander Dalloz wrote:
>> Am Mo, den 01.08.2005 schrieb Anne Ramey um 17:47:
>>
>>
>>>I updated to 2.6.12 kernel without updating something else necessary,
>>>apparently and have hosed my system. The real problem is that it won't
>>>boot of disk. We had 2 64 bit systems have the kernel problem and the
>>>other is back up and running fine. The only disk I can get the second
>>>system to boot is off a 386 iso, which causes problems when I try and
do
>>>anything (including chroot /mnt/sysimage) so I can't really rescue the
>>>system. I'd be ok with reinstalling, because I was just doing the
>>>initial system set-up anyway, but I can't figure out how to do that
>>>without being able to boot off a cd. The instructions I've found from
>>>booting from the network start with--boot from an iso cd (not helpful).
>>
>>
>>>Anne
>>
>>
>> How did you initially install the machine in question? At that time it
>> booted from your CD but now after a kernel update it does not any
>> longer? Please provide hardware information, especially about the
>> controller (IDE / SCSI) and what else might be important.
>>
>> Alexander
>>
>>
>>
>The machine came with fedora 3 (kernel 2.6.10) installed, so I guess it
>did boot from 64 bit CD at one point, but I never did it.
>Hardware RAID: 8-Ch 3Ware SATA 9500S-8 w/ battery
>IDE Devices: hda: QSI CD-RW/DVD-ROM SBW242C
>SCSI Devices: AMCC 9500S-8 DISK (Direct-Access)
>
>This is the system info for the system that did come back up:
>http://daredevil.blast.com/sys/
>The only differences between the two are disk size and sw/hw raid.
>Daredevil has software raid, the dead one has hw raid.
>
>Anne
When you say it 'wont boot off CD', what sort of error msg do
you get? Is your BIOS config'd to boot from CD as the first choice,
or is the box still actually trying to boot from your raid system?
Cheers,
Terry.
>
>--
>fedora-list mailing list
>fedora-list(a)redhat.com
>To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
>
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
12:24 p.m.
Marc M wrote:
If you put the cd into another system (regardless of os) do you see
only
one file or lots of files and directories? I did this just the other
day even though I knew better. If you only see one file you have made a
coaster; you should see multiple files.
Marc
I see multiple files when I look at it on my desktop, and it worked fine
in the other machine...
Anne
9:15 a.m.
I realize that this is probably too late, to do any good, but here goes.
When I installed FC1, it came as 3 CDs, and after I realized that it
would load with only 64 Megs of Ram, and upgraded, to 128 Megs, it
installed.
I downloaded FC2, as ISOs.
I made FC3 CDs, from a Linux Format DVD, using Winmkiso, and got ISOs on My CDs.
I downloaded FC4, as ISOs, as the Version was only available, on the Web.
The 1 thing that ALL the ISOs had in common, was that They wouldn't
load, until I Ripped the ISOs, using Media Creator, running on W**dows
X*.
You 'Right Click', on the ISO File, to bring up the Idiot Box, and
click on 'Record to CD'.
When the Option Box, comes up, You have to check the box, that says:
'Write to Text', or 'Write as Text'. This Option, is not normally
Highlighted.
It then records the CDs, as just Files, which then load, without a
problem. In fact, when the Disc is finished, the File Box will 'Pop
Up', and show You all the Folders and Files. That way You know that it
worked.
But Wait, cause it sometimes takes a minute or two, for that to
happen. I think that it depends on how fast Your computer is, that
You're running Media Creator on.
I hope this helps!
Michael
On 8/1/05, Marc M <linuxr(a)gmail.com> wrote:
If you put the cd into another system (regardless of os) do you see
only one
file or lots of files and directories? I did this just the other day even
though I knew better. If you only see one file you have made a coaster; you
should see multiple files.
Marc
On 8/1/05, T. Horsnell <tsh(a)mrc-lmb.cam.ac.uk> wrote:
> >Alexander Dalloz wrote:
> >> Am Mo, den 01.08.2005 schrieb Anne Ramey um 17:47:
> >>
> >>
> >>>I updated to 2.6.12 kernel without updating something else necessary,
> >>>apparently and have hosed my system. The real problem is that it
won't
> >>>boot of disk. We had 2 64 bit systems have the kernel problem and the
> >>>other is back up and running fine. The only disk I can get the second
> >>>system to boot is off a 386 iso, which causes problems when I try and
do
> >>>anything (including chroot /mnt/sysimage) so I can't really rescue
the
> >>>system. I'd be ok with reinstalling, because I was just doing the
> >>>initial system set-up anyway, but I can't figure out how to do that
> >>>without being able to boot off a cd. The instructions I've found
from
> >>>booting from the network start with--boot from an iso cd (not helpful).
> >>
> >>
> >>>Anne
> >>
> >>
> >> How did you initially install the machine in question? At that time it
> >> booted from your CD but now after a kernel update it does not any
> >> longer? Please provide hardware information, especially about the
> >> controller (IDE / SCSI) and what else might be important.
> >>
> >> Alexander
> >>
> >>
> >>
> >The machine came with fedora 3 (kernel 2.6.10) installed, so I guess it
> >did boot from 64 bit CD at one point, but I never did it.
> >Hardware RAID: 8-Ch 3Ware SATA 9500S-8 w/ battery
> >IDE Devices: hda: QSI CD-RW/DVD-ROM SBW242C
> >SCSI Devices: AMCC 9500S-8 DISK (Direct-Access)
> >
> >This is the system info for the system that did come back up:
> >http://daredevil.blast.com/sys/
> >The only differences between the two are disk size and sw/hw raid.
> >Daredevil has software raid, the dead one has hw raid.
> >
> >Anne
>
> When you say it 'wont boot off CD', what sort of error msg do
> you get? Is your BIOS config'd to boot from CD as the first choice,
> or is the box still actually trying to boot from your raid system?
>
> Cheers,
> Terry.
>
> >
> >--
> >fedora-list mailing list
> >fedora-list(a)redhat.com
> >To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-list
> >
>
> --
> fedora-list mailing list
> fedora-list(a)redhat.com
> To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-list
>
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-list
12:27 p.m.
T. Horsnell wrote:
>Alexander Dalloz wrote:
>
>>Am Mo, den 01.08.2005 schrieb Anne Ramey um 17:47:
>>
>>
>>
>>>I updated to 2.6.12 kernel without updating something else necessary,
>>>apparently and have hosed my system. The real problem is that it won't
>>>boot of disk. We had 2 64 bit systems have the kernel problem and the
>>>other is back up and running fine. The only disk I can get the second
>>>system to boot is off a 386 iso, which causes problems when I try and do
>>>anything (including chroot /mnt/sysimage) so I can't really rescue the
>>>system. I'd be ok with reinstalling, because I was just doing the
>>>initial system set-up anyway, but I can't figure out how to do that
>>>without being able to boot off a cd. The instructions I've found from
>>>booting from the network start with--boot from an iso cd (not helpful).
>>
>>
>>>Anne
>>
>>
>>How did you initially install the machine in question? At that time it
>>booted from your CD but now after a kernel update it does not any
>>longer? Please provide hardware information, especially about the
>>controller (IDE / SCSI) and what else might be important.
>>
>>Alexander
>>
>>
>>
>
>The machine came with fedora 3 (kernel 2.6.10) installed, so I guess it
>did boot from 64 bit CD at one point, but I never did it.
>Hardware RAID: 8-Ch 3Ware SATA 9500S-8 w/ battery
>IDE Devices: hda: QSI CD-RW/DVD-ROM SBW242C
>SCSI Devices: AMCC 9500S-8 DISK (Direct-Access)
>
>This is the system info for the system that did come back up:
>http://daredevil.blast.com/sys/
>The only differences between the two are disk size and sw/hw raid.
>Daredevil has software raid, the dead one has hw raid.
>
>Anne
When you say it 'wont boot off CD', what sort of error msg do
you get? Is your BIOS config'd to boot from CD as the first choice,
or is the box still actually trying to boot from your raid system?
Cheers,
Terry.
Yes, BIOS is set to boot of CD. It asks me to choose another boot
method or insert bootable media. As I mentioned, it just doesn't work
for 64 bit iso, a friend's 386 iso boots, but doesn't allow me to rescue
the system because of the incompatibility. This same 64 bit iso disk
rescued my other 64 bit system. I even made another copy, thinking it
had somehow turned into a coaster in between systems. No luck.
Anne
12:33 p.m.
Do you have another 64-bit 'live cd' like Ubuntu Hoary or something like
that? If so, maybe you can boot to it and copy a 64 bit kernel and get it to
work.
Marc
On 8/1/05, Anne Ramey <anner(a)blast.com> wrote:
T. Horsnell wrote:
>>Alexander Dalloz wrote:
>>
>>>Am Mo, den 01.08.2005 schrieb Anne Ramey um 17:47:
>>>
>>>
>>>
>>>>I updated to 2.6.12 kernel without updating something else necessary,
>>>>apparently and have hosed my system. The real problem is that it
won't
>>>>boot of disk. We had 2 64 bit systems have the kernel problem and the
>>>>other is back up and running fine. The only disk I can get the second
>>>>system to boot is off a 386 iso, which causes problems when I try and
do
>>>>anything (including chroot /mnt/sysimage) so I can't really rescue
the
>>>>system. I'd be ok with reinstalling, because I was just doing the
>>>>initial system set-up anyway, but I can't figure out how to do that
>>>>without being able to boot off a cd. The instructions I've found
from
>>>>booting from the network start with--boot from an iso cd (not
helpful).
>>>
>>>
>>>>Anne
>>>
>>>
>>>How did you initially install the machine in question? At that time it
>>>booted from your CD but now after a kernel update it does not any
>>>longer? Please provide hardware information, especially about the
>>>controller (IDE / SCSI) and what else might be important.
>>>
>>>Alexander
>>>
>>>
>>>
>>
>>The machine came with fedora 3 (kernel 2.6.10) installed, so I guess it
>>did boot from 64 bit CD at one point, but I never did it.
>>Hardware RAID: 8-Ch 3Ware SATA 9500S-8 w/ battery
>>IDE Devices: hda: QSI CD-RW/DVD-ROM SBW242C
>>SCSI Devices: AMCC 9500S-8 DISK (Direct-Access)
>>
>>This is the system info for the system that did come back up:
>>http://daredevil.blast.com/sys/
>>The only differences between the two are disk size and sw/hw raid.
>>Daredevil has software raid, the dead one has hw raid.
>>
>>Anne
>
>
> When you say it 'wont boot off CD', what sort of error msg do
> you get? Is your BIOS config'd to boot from CD as the first choice,
> or is the box still actually trying to boot from your raid system?
>
> Cheers,
> Terry.
>
Yes, BIOS is set to boot of CD. It asks me to choose another boot
method or insert bootable media. As I mentioned, it just doesn't work
for 64 bit iso, a friend's 386 iso boots, but doesn't allow me to rescue
the system because of the incompatibility. This same 64 bit iso disk
rescued my other 64 bit system. I even made another copy, thinking it
had somehow turned into a coaster in between systems. No luck.
Anne
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
12:37 p.m.
Anne Ramey wrote:
Yes, BIOS is set to boot of CD. It asks me to choose another boot
method or insert bootable media. As I mentioned, it just doesn't work
for 64 bit iso, a friend's 386 iso boots, but doesn't allow me to rescue
the system because of the incompatibility. This same 64 bit iso disk
rescued my other 64 bit system. I even made another copy, thinking it
had somehow turned into a coaster in between systems. No luck.
Anne
When you say you made another copy, do you mean you duplicated
the disc? If so, and it has a problem, then so will the duplicate.
If you started from another ISO image and burnt a new CD from
that, then that would be an entirely different matter.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
12:58 p.m.
Mike McCarty wrote:
Anne Ramey wrote:
> Yes, BIOS is set to boot of CD. It asks me to choose another boot
> method or insert bootable media. As I mentioned, it just doesn't work
> for 64 bit iso, a friend's 386 iso boots, but doesn't allow me to
> rescue the system because of the incompatibility. This same 64 bit
> iso disk rescued my other 64 bit system. I even made another copy,
> thinking it had somehow turned into a coaster in between systems. No
> luck.
>
> Anne
>
When you say you made another copy, do you mean you duplicated
the disc? If so, and it has a problem, then so will the duplicate.
If you started from another ISO image and burnt a new CD from
that, then that would be an entirely different matter.
Mike
I mean I downloaded another copy of the iso and burned a new disk of
the same thing.
Anne
2:43 p.m.
Anne Ramey wrote:
Mike McCarty wrote:
> Anne Ramey wrote:
>
>> Yes, BIOS is set to boot of CD. It asks me to choose another boot
>> method or insert bootable media. As I mentioned, it just doesn't
>> work for 64 bit iso, a friend's 386 iso boots, but doesn't allow me
>> to rescue the system because of the incompatibility. This same 64
>> bit iso disk rescued my other 64 bit system. I even made another
>> copy, thinking it had somehow turned into a coaster in between
>> systems. No luck.
>>
>> Anne
>>
> When you say you made another copy, do you mean you duplicated
> the disc? If so, and it has a problem, then so will the duplicate.
> If you started from another ISO image and burnt a new CD from
> that, then that would be an entirely different matter.
>
> Mike
I mean I downloaded another copy of the iso and burned a new disk of
the same thing.
Anne
Then you have some problem with either:
BIOS settings (but you say you've checked)
BIOS ROM (old version, corrupted FLASH, etc.)
CDROM drive (have you tried swapping it out?)
cables
kernel can't recognize it's on a 64 bit machine
something else
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
2:04 a.m.
Mike McCarty wrote:
Anne Ramey wrote:
>
> Mike McCarty wrote:
>
>> Anne Ramey wrote:
>>
>>> Yes, BIOS is set to boot of CD. It asks me to choose another boot
>>> method or insert bootable media. As I mentioned, it just doesn't
>>> work for 64 bit iso, a friend's 386 iso boots, but doesn't allow me
>>> to rescue the system because of the incompatibility. This same 64
>>> bit iso disk rescued my other 64 bit system. I even made another
>>> copy, thinking it had somehow turned into a coaster in between
>>> systems. No luck.
>>>
>>> Anne
>>>
>> When you say you made another copy, do you mean you duplicated
>> the disc? If so, and it has a problem, then so will the duplicate.
>> If you started from another ISO image and burnt a new CD from
>> that, then that would be an entirely different matter.
>>
>> Mike
>
>
>
> I mean I downloaded another copy of the iso and burned a new disk of
> the same thing.
>
> Anne
>
Then you have some problem with either:
BIOS settings (but you say you've checked)
BIOS ROM (old version, corrupted FLASH, etc.)
CDROM drive (have you tried swapping it out?)
cables
kernel can't recognize it's on a 64 bit machine
something else
Mike
Just to chime in here...maybe running a bootmanager floppy might work? I
know I've had to do this in the past. I don't have the URL on hand, but
it's a sourceforge project...google should turn it up.
Regards,
Ed.
6848
days inactive
6857
days old
12 comments
7 participants
participants (7)
-
Alexander Dalloz -
Anne Ramey -
Edward Dekkers -
Marc M -
Michael -
Mike McCarty -
Terry Horsnell