resizing partition

  • Thread starter Thread starter waltraud
  • Start date Start date
W

waltraud

Hi all of you,

I have tried to resize my c partition with partition magic. When the
computer reboots it gives me the "error 1527, bad update sequence
number" and reboots without applying the resize. I have done a chkdsk
on c but this does not repair the bad update sequence number. Does
anybody have an idea how to mend the error?

Thanks for any suggestions

Waltraud
 
Dear Bally,

I am using Partition Magic 8 and this is where it does not want to
cope with the "bad update sequence number".
Waltraud
 
http://www.powerquest.com/support/primus/id4184.cfm
(PartitionMagic 8.0 FAQ)
is now at http://service1.symantec.com/SUPPOR...2004061486839062?OpenDocument&src=hot&seg=hho
[It just says to run "chkdsk /F"]


http://www.powerquest.com/support/primus/id4718.cfm
is gone



http://www.powerquest.com/support/primus/id4540.cfm
is gone



http://www.powerquest.com/support/primus/id3560.cfm
is here:
http://web.archive.org/web/20040214014401/http://www.powerquest.com/support/primus/id3560.cfm
[It just tells how to run "chkdsk /F"]



Other related Symantec pages are:

"PartitionMagic 8.0 error messages and solutions"
http://service1.symantec.com/SUPPORT/powerquest.nsf/docid/2004050712232662?OpenDocument&seg=hm
[but it, too, just says to run "chkdsk /F"]
and
"Checking partitions for errors using PartitionMagic 8.0"
http://service1.symantec.com/SUPPOR...c9ba3b96088256e75007ca29a?OpenDocument&seg=hm



Unfortunately, I'm looking at a machine on which XP's chkdsk
is happy, but Partition Magic 8.0 still fails with error 1527.


-Dave
dave429 at burtonsys dot com but please no spam
 
I got the same error and PM 8.0 has basically robbed me of 10 gigs of HDD and plomped it into a grey area of "unallocated" space with no drive letter.

I cant delete it & I cant make it active. FDISK doesnt seem to like it either.

I cant see it to chdsk it.

Any ideas?

D
 
Use Partition Commander instead of Partition Magic

Hi jediboyuk,

After trying unsuccessfully to reach someone at Symantec who was competent and interested in this problem, I gave up, and tried a different product. (Note: I spent MANY hours, over, gosh, I think at least a week.)

Partition Commander (which came with System Commander) got the job done with no problem. (Go to v-com.com)

Sad to say, Symantec has ruined yet another once-fine product.

Dave Burton
(dave429 at burtonsys dot com but please no spam)
 
Here's one more thing to try.

This page http://service1.symantec.com/support/powerquest.nsf/docid/2004060929274462 (or http://www.webcitation.org/5ZNoov40R) says that if you've recently upgraded your BIOS, and your motherboard uses a VIA chipset, you might encounter the Error 1527 "bad update sequence number" problem. The solution, they claim, is to disable search Indexing on the drive.

I cannot imagine what a BIOS update or the VIA chipset could possibly have to do with this Partition Magic bug, but I supposed that it is worth a try to disable the search indexing for the drive. That would cause a lot of little flags to be reset throughout the NTFS file system structure, which seems like it could possibly be helpful.

BTW, don't bother with contacting Symantec tech support. You'll get someone totally clueless who is reading a script (probably in India), who has probably never used the product, and who won't ever even answer a straightforward question like, "it has been over four years since the current 8.05 version was released, will it EVER be updated?" or "have you ever used this product, yourself?" But in case you are a masochist, here's the link: http://www.symantec.com/norton/support/productdetail/contact_ts.jsp?pvid=npmagic_8

Dave Burton
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top