Possible disk problem with backup

I just came up with something that MAY impact this, however since I am not sure WHY this came up it may be a ligitimate reason for this occurance.

After receiving the original error message I again attempted to Repair the disk. This is the first occurance since the original posting last July. The first attempt was on the entire machine (verify only) which gave the following almost immediately:

Verifying and repairing partition map for “Seagate Expansion Desk Media”

Checking prerequisites

Checking the partition list

Problems were encountered during repair of the partition map

Error: Partition map check failed because no slices were found.

Just for confirmation, I ran this again with exact same results.

I then checked and the machine shows one partition.

I then ran the "Repair" on the disk which took about 30+ minutes (I let it run in background while doing other work) and it came up with the following:

Verifying volume “BateStar Backup 03”

Checking file systemChecking Journaled HFS Plus volume.

Checking extents overflow file.

Checking catalog file.

Checking multi-linked files.

Checking catalog hierarchy.

Checking extended attributes file.

Checking multi-linked directories.

Checking volume bitmap.

Checking volume information.

The volume BateStar Backup 03 appears to be OK.

To my knowledge, when I set up this 3T drive as a backup, I did not formally initiate partitioning but left it as default so this may be the cause of the above error message.

I have not done anything to concerning the replies previously given since afterwards there were no more errors and all backups (daily plus hourly) have been clean until today.

IDEAS?

Because of my own reluctance to totally TRASH all my backups I had decided to wait until the next day to see what would happen, especially since this was a second or third occurrance of this identical situation. When the error message did not show the rest of that day and seemed to have returned to normal, I just let it go.

Everything recorded yesterday had happened within 30 minutes of the post itself and YES there has been absolute no error messages since July until yesterday.

I will, however, have to apologize because for some abject reason, AGED MEMORY, I misread the intent of the post you aleud to above and I have no explination as to why unless I was carrying something onward from something else, resetting the HD.

I just wish there would sometimes be something that would occur where there would be indications that would show the problem was fixed. In this case, will probably have to wait at least three months before resetting TimeMachine App would show whether or not it is a reset problem and not something else. Will go ahead and do this then hope I remember around Christmas to watch for the adverse condition while hoping not to see anything through new years.

Tks for bearing with me and I apologize again for mixing thing up mentally

p.s. Not sure what happened to this reply but for some reason it did not get posted back when it was typed. Since this has been resolved in the meantime, will just close this out at this time and give you a helpful.