Sussed! (*Hopefully*!!!) - Re: Techie help required pls

"Old Grizzly" <me@xxxxxxxxxxx> wrote in message
news:40ecviF18jfpfU1@xxxxxxxxxxxxxxxxx
> "Old Grizzly" <me@xxxxxxxxxxx> wrote in message
> news:40ech0F1a7dt6U1@xxxxxxxxxxxxxxxxx
>> "pmj" <post@xxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:Ynlof.9475$iz3.2521@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
<snip>
>> > OK...
>> >
>> > Let's take a step (or 2!) back...
>> >
>> > & see if we can suss out what's what & what Options you have
>> > available, to make it Fixted...
>> >
>> > It *was* Booting off the Hard Disk OK, until very recently?
>> >
>> > Have you got any other Hard Disks in the Machine?
>> > What Make & Model (& Size) of Hard Disk(s) are they?
>> > What Partitions do you have Set up on them?
>> > What Filing Systems? - Fat32 &/or NTFS?
>> > & what Operating System(s) do you have Installed on them?
>>
>> Ok
>> Fdisk says
>> Partitions on 1st harddisk (8024.6, 1023 cylinders)
>> No 1 Start=0 end=1023 MB=57239.3 Staus = N TYpe Fat 32 LBA

Right...
I *think* we may well be getting somewherE?...

That "Staus = N" (on the Single (Primary) Partition on the Hard Disk)
is I presume actually "Status = N" ?

If so, then it *should* be "Status = A" !!!

It needs to be marked as what FDisk (& windoze) calls "Active"
(or "Startable/Bootable") - that's if it *is* actually s'posed to
be the Hard Disk that is the Bootable Hard Disk in the system (but if
you have 3 or 4 *other* Hard Disks, then one of *those* should be the
Bootable Disk.

So, try going back into FDisk & Setting that Partition as "Active"?

>> HTH Len

Yes!
I think it does!!!

> Ok PTEDIT

Ah great!!!
PTEdit as well!?

Good stuff!
:-)

> says 1 partition
> type= oc
> boot 00

Yep!!!
That should be 80 (Hex)

That's the "Boot Flag" & is 00 for a Partition that *isn't* Marked
as Active/Startable/Bootable & should be 80 (Hex) for a Startable
Primary Partition.

So...
Either Set that partition as Active (using FDisk) or Edit that Byte
(using PTEdit) so that it says "80"

Then try doing a ReBoot
(& maybe another FIXMBR &/or a FIXBOOT, from within the Recovery Console
- though you may find you need one & not the other.

> cyl 0
> head 1
> sector 1
> Cyl 1023
> Head 254
> Sector 63
> Before 63 Sectors 117226242
> And partition info FAT32X 57239 MB
>
> HTH Len

Try the above?
& Post back with what happens, OK?

& if it *doesn't* work, then that means that there's some *other*
(3rd Party) Disk Management Utility (or even some MalWare been
involved in screwing up the Hard Disk.

HTH

--
pmj


.

Relevant Pages

  • fdisk problem
    ... the slice with fdisk but not write the settings. ... Figures below won't work with BIOS for partitions not in cyl 1 ... BIOS sector numbering starts with sector 1 ... The data for partition 1 is: ...
    (freebsd-questions)
  • Re: hard drive?????
    ... Important Considerations Before You Use the Fdisk and Format Tools ... If not, view the second question. ... Is this hard disk the only hard disk on your computer or is ... 118335 Maximum Partition Size Using FAT16 File System ...
    (microsoft.public.windowsxp.general)
  • system boot taking more time, unable to mount vfat, linux partitions,
    ... I use my second hard disk as a backup to store data, ... Figures below won't work with BIOS for partitions not in cyl 1 ... BIOS sector numbering starts with sector 1 ... The data for partition 1 is: ...
    (freebsd-questions)
  • Problem with fdisk -i
    ... I have a problem with fdisk -i on one of my FreeBSD server: ... Figures below won't work with BIOS for partitions not in cyl 1 ... BIOS sector numbering starts with sector 1 ... The data for partition 1 is: ...
    (freebsd-questions)
  • Adding a slice using sysinstall
    ... I tried to attach the unused portion of the hard disk in my FBSD ... Figures below won't work with BIOS for partitions not in cyl 1 ... BIOS sector numbering starts with sector 1 ... The data for partition 1 is: ...
    (comp.unix.bsd.freebsd.misc)