|
|
This problem was caused by hardware error (confirmed by Michael Kuhn) so i'm closing it. |
|
|
|
Mistake ... hardware error is about issue 4174. |
|
|
|
We're both (me and Jiri) tried to reproduce or find where the problem was, but without success. So closing it as unable to reproduce. |
|
|
|
I'm also unable to reproduce issue. |
|
|
|
Re-opening because I've just received another MM 3.0.1 db that will hopefully shed light on the problem. The db associated with Randall at http://www.mediamonkey.com/forum/viewtopic.php?t=23499 has been uploaded to the ftp server. |
|
|
|
It's different bug and i've made new issue for it (4209). |
|
|
rusty
2007-12-21 16:35
administrator
~0012704
Last edited: 2007-12-21 16:36
|
Petr, I just tested out the MM 2.5 DB from the user and build 1121 doesn'n seem to be able to perform a GUI upgrade on it. If that's not working, isn't it indicative of a problem with the upgrade process (which could in turn cause other problems such as the duplicates observed by the user)? Or is a failed GUI upgrade expected in some cases?
EDIT: it just took a REALLY long time...not sure why...but it did finally work. Re-resolving.
|
|
|
|
Closing as dup. |
|
|
|
Apparently, this issue isn't resolved with RC-6 :(
Here's the email from bob:
Good news and still bad news.....
Good News....The new version fixes problem with the location node
bug - it doesn't fix the problem with duplicates.
Base News... I converted over the DB2.5 to 3.0 - then did a rescan
of my external drive, all files were duplicated. I did a second scan
and file were not in triplicate. Each rescan caused the files to be
treated as new and added to the total. The new build doesn't fix the
duplicate files issue.
I installed RC6 today, then did a conversion of the 2.5DB. Noted same as mentioned above - still doesn't fix problem with duplicate entries after rescan of my LACIE drive (FAT32). No problem with my Maxtor (NTFS) external drive. |
|
|
|
Setting this as resolved, since we tried many things and weren't able to reproduce. Also, it happened to just one user, so it probably isn't a big issue anyway. Let's reopen in case it appears again... |
|
|
|
note from Bob:
Figuring that there is an issue with how MM3 was handling the FAT32 drive, I converted it to NTFS. Good news in a way, this now confirms my hunch as I can now scan my test directory without any problems. Bad news, it doesn't recognize the drive as it was originally scanned. This does though kind of show why this may be occurring. Before a did a rescan of my drive MM3 was not showing any files in my test directory (Test_Ext) on my H drive (all titles were grayed out). Had me concerned until I then noticed that MM3 actually created a new location for the drive. You'll notice that the original drive is listed as "HD:Lacie" whereas the drive now converted to NTFS and rescanned shows as "HD:Lacie(H:)".
Here is the location of the originally scanned drive - all songs are grayed out as MM3 doesn't recognize them: <missing image>
Here is the "new" location - notice that the songs are not grayed out and listed once: <missing image>
I noticed that MM2.5 does the same thing, it has created a new location as well - and the original location doesn't find the songs:
<missing image>
And here's the new location:
<missing image>
Hope this helps. Now that I've converted my drive I won't be able to verify any fixes but at least this should point you in the direction as to the root cause of the problem. |
|
