Maxtor drive lost all partitons

Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

I bought a brand new Maxtor Diamond Plus 8 160Gb Hard disk last week,
partitioned it up into about 5 partitions, put various files and
downloaded stuff on them, then all at once like today, none of the
partitions were available!
Win2k reported that folders were not available and were corrupt.
So, I rebooted and the HD was found ok on bootup; fdisk reported only
25Gb available, but maybe that was just fdisk. I booted back into
Windows and all the partitions on that disk had disappeared.
I then ran PM8 and re partitioned the said disk again, but I am loathe
to put anything on it in case the same thing happens.

One thing I did notice tho' was when I was burning some files, 350mb
approx, to a CDR, I heard some ticking noise, and at first I thoght it
was coming from my CDRwriter, coz after the burning stopped so did the
ticking.

Any ideas as to what may have caused it? I did NOT do anything out of
the ordainary on this machine at all. It just happened??

Thanks
16 answers Last reply
More about maxtor drive lost partitons
  1. Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

    If you had used Disk Manager instead, it would likely show only 128GB.

    If so, you cannot use the rest of the disk, because your BIOS or old IDE driver
    do not support larger disks. Instead it overwrites at the beginning.

    "Bob H" <bobg4uyi@despammer.com> wrote in message
    news:41f2df37$0$16572$cc9e4d1f@news-text.dial.pipex.com...
    > I bought a brand new Maxtor Diamond Plus 8 160Gb Hard disk last week,
    > partitioned it up into about 5 partitions, put various files and
    > downloaded stuff on them, then all at once like today, none of the
    > partitions were available!
    > Win2k reported that folders were not available and were corrupt.
  2. Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

    Bob H wrote:
    > I bought a brand new Maxtor Diamond Plus 8 160Gb Hard disk last week,

    Is that old stock or something? They've been doing Diamond Plus _9_
    drives for some time now.

    > partitioned it up into about 5 partitions, put various files and
    > downloaded stuff on them, then all at once like today, none of the
    > partitions were available!
    > Win2k reported that folders were not available and were corrupt.
    > So, I rebooted and the HD was found ok on bootup; fdisk reported only
    > 25Gb available, but maybe that was just fdisk. I booted back into
    > Windows and all the partitions on that disk had disappeared.
    > I then ran PM8 and re partitioned the said disk again, but I am loathe
    > to put anything on it in case the same thing happens.
    >
    > One thing I did notice tho' was when I was burning some files, 350mb
    > approx, to a CDR, I heard some ticking noise, and at first I thoght it
    > was coming from my CDRwriter, coz after the burning stopped so did the
    > ticking.
    >
    > Any ideas as to what may have caused it? I did NOT do anything out of
    > the ordainary on this machine at all. It just happened??
    >
    > Thanks

    I doubt it's the drive's fault -- more likely software, IMHO.


    --
    The e-mail address in our reply-to line is reversed in an attempt to
    minimize spam. Our true address is of the form che...@prodigy.net.
  3. Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

    Eric Gisin wrote:
    > If you had used Disk Manager instead, it would likely show only
    128GB.
    >
    > If so, you cannot use the rest of the disk, because your BIOS or old
    IDE driver
    > do not support larger disks. Instead it overwrites at the beginning.
    >
    > "Bob H" <bobg4uyi@despammer.com> wrote in message
    > news:41f2df37$0$16572$cc9e4d1f@news-text.dial.pipex.com...
    > > I bought a brand new Maxtor Diamond Plus 8 160Gb Hard disk last
    week,
    > > partitioned it up into about 5 partitions, put various files and
    > > downloaded stuff on them, then all at once like today, none of the
    > > partitions were available!
    > > Win2k reported that folders were not available and were corrupt.
  4. Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

    Eric Gisin wrote:
    > If you had used Disk Manager instead, it would likely show only
    128GB.
    >
    > If so, you cannot use the rest of the disk, because your BIOS or old
    IDE driver
    > do not support larger disks. Instead it overwrites at the beginning.
    >
    > "Bob H" <bobg4uyi@despammer.com> wrote in message
    > news:41f2df37$0$16572$cc9e4d1f@news-text.dial.pipex.com...
    > > I bought a brand new Maxtor Diamond Plus 8 160Gb Hard disk last
    week,
    > > partitioned it up into about 5 partitions, put various files and
    > > downloaded stuff on them, then all at once like today, none of the
    > > partitions were available!
    > > Win2k reported that folders were not available and were corrupt.
  5. Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

    CJT wrote:
    > Bob H wrote:
    >
    >> I bought a brand new Maxtor Diamond Plus 8 160Gb Hard disk last week,
    >
    >
    > Is that old stock or something? They've been doing Diamond Plus _9_
    > drives for some time now.

    Ooops, I misread, Its a 7200rpm with 8mb cache, so I suppose that would
    be a _9_ now

    >
    >> partitioned it up into about 5 partitions, put various files and
    >> downloaded stuff on them, then all at once like today, none of the
    >> partitions were available!
    >> Win2k reported that folders were not available and were corrupt.
    >> So, I rebooted and the HD was found ok on bootup; fdisk reported only
    >> 25Gb available, but maybe that was just fdisk. I booted back into
    >> Windows and all the partitions on that disk had disappeared.
    >> I then ran PM8 and re partitioned the said disk again, but I am loathe
    >> to put anything on it in case the same thing happens.
    >>
    >> One thing I did notice tho' was when I was burning some files, 350mb
    >> approx, to a CDR, I heard some ticking noise, and at first I thoght it
    >> was coming from my CDRwriter, coz after the burning stopped so did the
    >> ticking.
    >>
    >> Any ideas as to what may have caused it? I did NOT do anything out of
    >> the ordainary on this machine at all. It just happened??
    >>
    >> Thanks
    >
    >
    > I doubt it's the drive's fault -- more likely software, IMHO.
    >
    >
  6. Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

    Eric Gisin wrote:
    > If you had used Disk Manager instead, it would likely show only 128GB.
    >
    > If so, you cannot use the rest of the disk, because your BIOS or old IDE driver
    > do not support larger disks. Instead it overwrites at the beginning.

    Do you mean Disk Management in Win2k?
    It showed that the drive was all free space

    >
    > "Bob H" <bobg4uyi@despammer.com> wrote in message
    > news:41f2df37$0$16572$cc9e4d1f@news-text.dial.pipex.com...
    >
    >>I bought a brand new Maxtor Diamond Plus 8 160Gb Hard disk last week,
    >>partitioned it up into about 5 partitions, put various files and
    >>downloaded stuff on them, then all at once like today, none of the
    >>partitions were available!
    >>Win2k reported that folders were not available and were corrupt.
    >
    >
  7. Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

    "Bob H" <bobg4uyi@despammer.com> wrote in message
    news:41f37a6a$0$16586$cc9e4d1f@news-text.dial.pipex.com...
    > Eric Gisin wrote:
    > > If you had used Disk Manager instead, it would likely show only 128GB.
    > >
    > > If so, you cannot use the rest of the disk, because your BIOS or old IDE
    driver
    > > do not support larger disks. Instead it overwrites at the beginning.
    >
    > Do you mean Disk Management in Win2k?
    > It showed that the drive was all free space
    >
    That happens when the MBR is overwritten. It can be recreated with findpart.

    Does it show 128GB or 150GB?
  8. Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

    Eric Gisin wrote:
    > If you had used Disk Manager instead, it would likely show only 128GB.
    >
    > If so, you cannot use the rest of the disk, because your BIOS or old IDE driver
    > do not support larger disks. Instead it overwrites at the beginning.

    I think that's a pretty good guess of what happened. The disk
    addressing "wrapped around" and over-wrote the start of the disk where
    some important stuff like partitioning info resides.

    >
    > "Bob H" <bobg4uyi@despammer.com> wrote in message
    > news:41f2df37$0$16572$cc9e4d1f@news-text.dial.pipex.com...
    >
    >>I bought a brand new Maxtor Diamond Plus 8 160Gb Hard disk last week,
    >>partitioned it up into about 5 partitions, put various files and
    >>downloaded stuff on them, then all at once like today, none of the
    >>partitions were available!
    >>Win2k reported that folders were not available and were corrupt.
    >
    >


    --
    The e-mail address in our reply-to line is reversed in an attempt to
    minimize spam. Our true address is of the form che...@prodigy.net.
  9. Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

    Eric Gisin wrote:
    > "Bob H" <bobg4uyi@despammer.com> wrote in message
    > news:41f37a6a$0$16586$cc9e4d1f@news-text.dial.pipex.com...
    >
    >>Eric Gisin wrote:
    >>
    >>>If you had used Disk Manager instead, it would likely show only 128GB.
    >>>
    >>>If so, you cannot use the rest of the disk, because your BIOS or old IDE
    >
    > driver
    >
    >>>do not support larger disks. Instead it overwrites at the beginning.
    >>
    >>Do you mean Disk Management in Win2k?
    >>It showed that the drive was all free space
    >>
    >
    > That happens when the MBR is overwritten. It can be recreated with findpart.
    >
    > Does it show 128GB or 150GB?
    >
    Well, it showed 157Gb of freespace, but as I said I have re partitioned now
  10. Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

    CJT wrote:
    > Eric Gisin wrote:
    >
    >> If you had used Disk Manager instead, it would likely show only 128GB.
    >>
    >> If so, you cannot use the rest of the disk, because your BIOS or old
    >> IDE driver
    >> do not support larger disks. Instead it overwrites at the beginning.
    >
    >
    > I think that's a pretty good guess of what happened. The disk
    > addressing "wrapped around" and over-wrote the start of the disk where
    > some important stuff like partitioning info resides.

    Ok, I think someone else said that, so what would cause that then?
    Is it something to do with 48bit lba?

    Thanks
    >

    >
  11. Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

    Bob H wrote:
    > CJT wrote:
    >
    >> Eric Gisin wrote:
    >>
    >>> If you had used Disk Manager instead, it would likely show only 128GB.
    >>>
    >>> If so, you cannot use the rest of the disk, because your BIOS or old
    >>> IDE driver
    >>> do not support larger disks. Instead it overwrites at the beginning.
    >>
    >>
    >>
    >> I think that's a pretty good guess of what happened. The disk
    >> addressing "wrapped around" and over-wrote the start of the disk where
    >> some important stuff like partitioning info resides.
    >
    >
    > Ok, I think someone else said that, so what would cause that then?
    > Is it something to do with 48bit lba?

    Yes. It's everything to do with 48 bit lba.
    >
    > Thanks
    >
    >>
    >
    >>


    --
    The e-mail address in our reply-to line is reversed in an attempt to
    minimize spam. Our true address is of the form che...@prodigy.net.
  12. Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

    CJT wrote:
    > Bob H wrote:
    >
    >> CJT wrote:
    >>
    >>> Eric Gisin wrote:
    >>>
    >>>> If you had used Disk Manager instead, it would likely show only 128GB.
    >>>>
    >>>> If so, you cannot use the rest of the disk, because your BIOS or old
    >>>> IDE driver
    >>>> do not support larger disks. Instead it overwrites at the beginning.
    >>>
    >>>
    >>>
    >>>
    >>> I think that's a pretty good guess of what happened. The disk
    >>> addressing "wrapped around" and over-wrote the start of the disk where
    >>> some important stuff like partitioning info resides.
    >>
    >>
    >>
    >> Ok, I think someone else said that, so what would cause that then?
    >> Is it something to do with 48bit lba?
    >
    >
    > Yes. It's everything to do with 48 bit lba.
    >
    >>
    >> Thanks
    >>
    >>>
    >>
    >>>
    >
    >
    I thought so. Too b****y late tho! I lost a few media files I had
    downloaded, and a lot of music files as well. Oh well, lesson learned
    I have EnableBigLba = 1 now in my registry
    'Oh bugger' said Bungle
    At least the disk is not kaput or going that way then.

    Thanks
  13. Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

    On Sat, 22 Jan 2005 16:37:21 -0800, "Eric Gisin"
    <ericgisin@hotmail.com> wrote:

    >If you had used Disk Manager instead, it would likely show only 128GB.
    >
    >If so, you cannot use the rest of the disk, because your BIOS or old IDE driver
    >do not support larger disks. Instead it overwrites at the beginning.

    It should be noticed that Disk Manager is not reliable. If the disk is
    partitioned for more than 128 GB, Windows 2000 Disk Manager will show
    the partitioned size. It will not show the size that Windows can
    access, or give any warnings.
    --
    Svend Olaf
  14. Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

    On Sun, 23 Jan 2005 20:17:25 GMT, svolaf@partitionsupport.com (Svend
    Olaf Mikkelsen) wrote:

    >On Sat, 22 Jan 2005 16:37:21 -0800, "Eric Gisin"
    ><ericgisin@hotmail.com> wrote:
    >
    >>If you had used Disk Manager instead, it would likely show only 128GB.
    >>
    >>If so, you cannot use the rest of the disk, because your BIOS or old IDE driver
    >>do not support larger disks. Instead it overwrites at the beginning.
    >
    >It should be noticed that Disk Manager is not reliable. If the disk is
    >partitioned for more than 128 GB, Windows 2000 Disk Manager will show
    >the partitioned size. It will not show the size that Windows can
    >access, or give any warnings.

    Some additional information is available here:

    http://www.partitionsupport.com/win2000/

    For the 2000 and 2000a pictures, the BIOS supports the disk size,
    which is 160 GB.

    The only tool which reliable can tell the disk size that Windows 2000
    recognizes is Findpart. As far as I know :-)

    --
    Svend Olaf
  15. Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

    "Svend Olaf Mikkelsen" <svolaf@partitionsupport.com> wrote in message
    news:41f4e5bd.17094170@News.Individual.NET...

    > >It should be noticed that Disk Manager is not reliable. If the disk is
    > >partitioned for more than 128 GB, Windows 2000 Disk Manager will show
    > >the partitioned size. It will not show the size that Windows can
    > >access, or give any warnings.
    >
    > Some additional information is available here:
    >
    > http://www.partitionsupport.com/win2000/
    >
    > For the 2000 and 2000a pictures, the BIOS supports the disk size,
    > which is 160 GB.
    >
    > The only tool which reliable can tell the disk size that Windows 2000
    > recognizes is Findpart. As far as I know :-)

    I assume you use IOCTL_DISK_GET_DRIVE_GEOMETRY, and Disk Managment uses LDM
    service. Dskprobe's Volume Information should also work, and mbrwiz /list
    (mbr.bigr.net).
  16. Archived from groups: comp.sys.ibm.pc.hardware.storage (More info?)

    On Mon, 24 Jan 2005 09:06:46 -0800, "Eric Gisin"
    <ericgisin@hotmail.com> wrote:

    >> The only tool which reliable can tell the disk size that Windows 2000
    >> recognizes is Findpart. As far as I know :-)
    >
    >I assume you use IOCTL_DISK_GET_DRIVE_GEOMETRY, and Disk Managment uses LDM
    >service. Dskprobe's Volume Information should also work, and mbrwiz /list
    >(mbr.bigr.net).

    Yes, I use that method.

    I found the correct information in Windows 2000 too, in "Computer
    Management, System Tools, System Information, Components, Storage,
    Drives".
    --
    Svend Olaf
Ask a new question

Read More

Maxtor Storage