Created attachment 3231 [details]
No disk error

*** Bug 7827 has been marked as a duplicate of this bug. ***

One reason for this I could imagine is some file path pointing to a no longer existing drive (external HD unplugged) or a drive with removable media (CD, floppy - yes, they still exist). I remember having seen similar messages when trying to pick a music folder and the list of drives was displayed, including the aforementioned cases. Might be helpful to have the customer's server.prefs file and a description of his system, what drives, external or internal etc.

SlimServer 6.5.4 was re-installed on this system after SlimCenter was removed. SlimServer installed without any errors and the music system was restored. My Squeezebox is now working with Slimserver 6.5.4.

*** Bug 7843 has been marked as a duplicate of this bug. ***

Gordy - would you mind giving me your system details anyway? We won't be able to fix this unless we know what causes the error. Thanks!

David - could you please give the latest build another try? I wonder whether we're dealing with a broken build here. We've not had this issue for months and now two within a day without changing anything in the build process.

Also - could you please answer my earlier questions about removable media on your system? And you don't by chance have a playlist or shortcut pointing to some inexisting drive? 

I had running version 6.5.4 and had trouble with it reading some playlists.  I decided to upgrade to 7.0.

I downloaded 7.0 and installed it.  I had this same error with 7.0.  So I decided to upgrade to the 7.01 beta.  I originally had the 7.0.1-17976.  The problem was still there and the problem with the playlists was worse.

Last week I installed the 7.0.1-18767 beta and still got the error.  However it looks like my playlist issue is fixed.

I am running Windows XP Home SP2.  I have a USB floppy disk installed and my kids use several different USB MP3 players.

All of my music is in My Documents\My Music and that is the directory that the SqueezeCenter is pointed to.

I do know that my son has installed LimeWire.  It has been uninstalled.  I do not know if this would cause the problem.

Please let me know if you need any more information.

Another comment.

As I watch the system scan, it is scanning music files not playlists.  The scan for playlists is later.  When the dialog comes up it is on a music file that does exist on my computer.

Does the log file tell you what files it is having problems with?

Could there be something wrong with the file?

Is there an easy way to search for shortcuts?  I am pretty sure that I do not have any short cuts, but with over 500 different directories I could have missed one.

> I am running Windows XP Home SP2.  I have a USB floppy disk installed and my

Is it plugged in when you see this error? If so, please unplug it and try again.

> Does the log file tell you what files it is having problems with?

It might help. Please set logging for scan.* to debug and try again. You could also narrow down the music path to where you suspect the issue.

> Could there be something wrong with the file?

I wonder whether a disk check might help.

> Is there an easy way to search for shortcuts?

Search for *.lnk

After looking at the scan log, I do remember that more than 5 years ago on another computer I did have a drive I:.

There are lots of playlists on this computer so it will take some time to search them all for references to other drives.

Does SqueezeCenter read .cue files?  The reference in the log points to files that I created from my Vinyl Albums and when those tracks were created I used .cue files to hold song titles.  These could be pointing to the old drive.  I will have to check this out as well.

> After looking at the scan log, I do remember that more than 5 years ago on
> another computer I did have a drive I:.

Do you have a drive I: on your current machine?

> There are lots of playlists on this computer so it will take some time to
> search them all for references to other drives.

Let Windows search do this job ;-)

> Does SqueezeCenter read .cue files?

Yes, it does. Look at these first. As you mentioned earlier playlists are done in a further step.

I just received this from a customer who was suffering the No Disk error:

"I fixed the problem.  Here is the internet site that helped me...  

http://www.consumingexperience.com/2007/11/windows-no-disk-exception-processing.html

Go to the second [part] and I followed the instructions: How to change drive letter assignments in Windows XP to fix the "Windows-no disk" etc error message."

I have looked over these instructions and they detail how you can change the assigned drive letters for removable media.  I've written him back for some clarification on what exactly he changed.  Waiting to hear back, but I thought this might be relevant.

I reviewed the .cue files and there were some that pointed to a non existing drive.  These files were created on an old computer that had an external drive.

Thanks for the help and the great product.

David Bell

David - is the issue gone with the cleanup?

Gordy - any comments? 

We can't think of a good solution for this bug.  Ideas are welcome.

Dan, your team knows now what this bug is about?

No, I can't say we understand the cause of this bug yet.  We certainly don't have a reliable solution.  If there's information outside of this bug log, I'd be interested to hear.  

There's no solution on our side. It's not SC issueing the error message, but Windows: whenever anything tries to access a medium which is not inserted into its drive or ready to be read (floppy, flash card in a card reader, new or empty CD/DVD), Windows will complain about it.

In our case there were cue sheets, which once pointed to an external drive I:. This external drive isn't on I: any more. But instead there's now a flash card reader. As SC tried to follow the link in the cue sheet, Windows got unhappy.

What support has to know: if this error arises, then there's very likely a file pointing to an empty flash card reader (floppies are dieing, CD/DVD writer do not often change drive letter). Ask the client to unplug the card reader (if possible) and try again. If this solves the issue, he should do a search for any playlist/cuesheet etc. with that drive letter in it and clean them up.

why has this come up suddenly with 7.0 and not previously with 6.5.4?

Yes, I agree the OS is issuing the error. But it is perfectly clear that it is caused by a software call from SC 7.0.  I have also removed all my play lists from SC 7.0 with no change.  This error occurs before play lists are scanned when SC 7.0 is initializing/loading. SC halts in loading (rendered INOP) until it passes the system OS error.  To me it seems SC looking for a drive it cannot find in the OS?

> when SC 7.0 is initializing/loading. SC halts in loading (rendered INOP) until
> it passes the system OS error.  To me it seems SC looking for a drive it cannot
> find in the OS?

Could you please upload your server.prefs file (or verify there's nothing in there)?

Would you be able to start SC if you removed all removable drives (unplug USB drives, card reader etc.)?

> why has this come up suddenly with 7.0 and not previously with 6.5.4?

It's neither a sudden appearance nor is it very often. But the common factor here might be time? As time goes by more and more users are updating to 7.0 and buying card readers, offereing new causes for so far unknown issues?

Tech Support has asked me describe a different but perhaps related problem I'm experiencing to the one above.

I've recently moved, and am having trouble getting the latest version of SqueezeCenter to run on my Vista PC. I'm unable to access my ripped music files that are stored on an external PC hard drive. The previous version of SlimServer was also non-functioning. SqueezeNetwork works fine. 

I've done a clean install of the latest version of SqueezeCenter, but just prior to the Install Wizard finishing up, I get an error msg that reads. . ."'X' Not able to write to:". I can close that window and click the finish button on the Wizard, but SqueezeCenter tries but is unable to start. The icon on the task bar just flashes away in a loop.

Anyone else seen this behavior? 

> I've done a clean install of the latest version of SqueezeCenter, but just
> prior to the Install Wizard finishing up, I get an error msg that reads. .
> ."'X' Not able to write to:".

Ken - I think you rather hit https://bugs-archive.lyrion.org/show_bug.cgi?id=8265 than this issue. 

Having recently reported this "Windows No Disk Error" problem to Logitech customer support, I was told it's a "known bug" and that I should visit this page and add my name to the "cc" list. That was and so far is the full extent of Logitech's "support". Which is to say they have offered no support whatsover, with respect to an issue that's been experienced by other users and which Logitech has known about for months now. This is a textbook example of worthless customer support.

What is causing this pop-up message? Why do scans stall? Why is the scanner software incapable of doing its job? These are basic questions. Logitech customer support personnel: you are welcome to visit my home to witness the phenomenon of this "known bug" for which you have no fix and which you evidently have chosen to ignore. What a colossal waste of my time, trying to fix something that you guys can't be bothered to address. I think I'll go look for some audio forums where I can spread the news about the Squeezebox and the squeezecenter software, according to my personal experience. I certainly don't want others making the same mistake that I did, buying this product and using this DEFECTIVE SOFTWARE. Yes, that's right, you're marketing software that you know for a fact is defective and you aren't disclosing that fact to customers before they buy.  Sounds like fraud to me.

If you detect frustration in this message it means you are a reasonably perceptive reader. 

> If you detect frustration in this message it means you are a reasonably
> perceptive reader. 

Please read this bug report and you'll learn that this is not a _but_ in _our_ software, but Windows' response to accessing drives which are not in their slot. I'm sorry we can't detect this before Windows is telling us (and you) so. And I'm sorry you couldn't give us any more information which would help us help you.

Feel free to give the workarounds described here a try. But please don't use support ticketing or bug reporting systems to vent your anger. I do understand the frustration. But you also have to understand the limitations we have to work with. And no frustration does legitimate for insulting behaviour. Thanks for your understanding.

> this is not a _but_ 

I'm sorry, I meant to write _bug_.

(In reply to comment #27)
> > this is not a _but_ 
> 
> I'm sorry, I meant to write _bug_.
> 

Logitech customer support said in an email to me -- and I quote -- "This is actually a known bug." So please let's not start out with an attempt to rewrite history.

You say, "I'm sorry you couldn't give us any more information which would help
us help you."

I have already provided a full report of what I have been experiencing while
using your software -- in two separate reports to Logitech customer support. I
was not asked for more information. What would you like to know?  It's notable
that so far I have received no substantive help whatsoever from customer
support, but you are very quick to imply that I am at fault for not providing
"more information" when none was requested. I repeat: what would you like to
know, beyond the information I have already provided in two detailed messages
to customer support? If you need "more information", beyond what I
have already provided in messages sent to customer support, what is it? I was sent to this page by Logitech customer support. Am I to assume that you are not in communication with the people who sent me here, and that you have none of the information previously provided? Reference: Incident: 080702-002548.

I was the one who sent him to this bug. 

I mainly sent him here to give him a better understanding on what the issue is about. 

I have also sent him a follow up email asking him more questions about the issue at hand. 

I am writting here to clearify things. 

I have been asked to add this info here, so I'm doing so.

The issue is the windows "no disk" pop-up message that is associated with running the squeezecenter software (to say the error message is not attributable to the squeezecenter and associated scanner software is plainly and demonstrably wrong, but there's no point in beating that dead horse any more). So here is my additional info:

In an effort of self-help, I uninstalled and re-installed the
squeezecenter software (ver. 7.0.1). I directed the software to my music library located on an external usb drive (Drive "J"). I then monitored the scanning process. The scanner (scanner.exe) stalled as it had before the reinstall, and the pop-up "no disk" message appeared, during the scan of the iTunes library (which is separate from the music library itself but evidently is scanned as part of the same scanning process). It did this repeatedly, always stalling around the same place (after scanning approximately 20,000 files out of 27,000, according to the displayed file counts).

I noticed that after re-installing the software none of the iTunes
playlists were loaded into the squeezecenter software. This told me that
the scan process did not get that far before stalling. No playlists
loaded, even though they exist in iTunes.

I kept closing scanner.exe (using Windows Task Manager, the only way to shut down scanner.exe) while leaving the squeezecenter software
running. This would allow me to clear the pop-up message. But evidently
scanner.exe gets automatically launched, as the pop-up message kept
reappearing, and I'd find scanner.exe running again. I went through this
process half a dozen times or more -- shutting down scanner.exe in order
to clear the pop-up message.

Now here's the thing: I did nothing differently, but for some reason after
multiple cycles of what I've described above the iTunes library was
successfully scanned, and all the playlists loaded in squeezecenter, and
are now displayed. As of this writing the software had been running for more than 48 hours with no issue. But this has happened before and I therefore have every reason to believe it will happen again. 
  
If the issue were the location of my files, or a change in their location,
or the existence of some other removable media, or the fact that I am using an external drive, I do not believe the problem would "self correct" this way. I believe it would perpetually repeat. But it does not perpetually repeat (although it does repeat enough times to cause any reasonable person to suffer a high degree of frustration). Since the "no disk" error message is not attributable to any user-related action, file location, file movement, use of other external media, etc., I conclude that the problem must be with the software itself. Yet nobody seems to know how to correct it. Has anyone looked at how the scanner.exe software is handling the data in the iTunes database? I'm no software expert, but that seems to be where the problem lies. By the way, FWIW, my music library is actually much larger than what's loaded into iTunes. 

Thanks for the additional information. And sorry for the delay. I've been off for a few days.

> scanning process. The scanner (scanner.exe) stalled as it had before the
> reinstall, and the pop-up "no disk" message appeared, during the scan of the

Would the scanning continue if you closed that message? (It might show up several times - just close it again)

> iTunes library (which is separate from the music library itself but evidently

Did it always stop during the iTunes import? This might explain the change in behaviour:

> If the issue were the location of my files, or a change in their location,
> or the existence of some other removable media, or the fact that I am using an
> external drive, I do not believe the problem would "self correct" this way. I

iTunes doesn't always and immediately update the .xml file. Most notably it does not immediately remove stale items (the .xml file is only a copy or backup of iTunes actual database). Thus it might be there were still tracks in there referenced with a path name which no longer exists. And iTunes might at some point have decided to clean up its file. 

To give some more information about what's happening here:

- the scanner is reading the iTunes .xml file (and playlists, cue sheets etc.) for file names of songs

- scanner is then asking the operating system (Windows) for information about that file, eg. x:\some\path\and\filename.mp3

- if x: doesn't exist any more or is empty (in the case of a removable medium), Windows will show an error, as some application tried to access that drive from which it can't read

- all this time the scanner will wait for Windows to return the information it can't deliver

So what we might try to do is check a drive's availability before Windows does so due to our request for file information. 

Trying to reproduce this with playlists and an iTunes XML file pointing to non-existing drives, card reader and floppy drive without medium, and a CD drive with a blank disc inserted or open: can't get the message to appear :-(.

Dan - are you (or anybody else in QA/support) able to reproduce this easily?

I cannot seem to reproduce this issue at all. 

re-marking bug as monitor for now.  If anyone can come up with a 100% reproducible method please post here so we can track down the issue.

However IMH I still think this is a Microsoft issue, see comment #13

I corrected this problem on my own. Perhaps you can figure out where the error in your software is based on the information that follows. Please refer to my last post dated July 9, 2008 for background.

At the outset let me note that I never experienced this error when using the original squeezebox software. It began only after I installed the squeezecenter 7.0.1 software.

I should also note that I did not have listed in my iTunes library any songs on "non-existent" drives. All songs were present and accounted for. No songs in the library had come from thumb drives or other temporary media. If they were in the iTunes library, they existed on an external drive that was connected and running. I say this with 100% certainty.
 
After I finally got the music library fully scanned (see my July 9 post), I did in fact get the "no disk" error message again. So I decided to take a shot in the dark and start from a completely clean slate. In the following order, I (1) uninstalled the squeezecenter software (2)deleted the entire iTunes library (3) loaded my music library back into iTunes and (4) installed the squeezecenter software. I thereafter encountered no "no disk" error and have not seen the error since. 

What was different this time around? Only one variable: the location of the music files loaded into the iTunes library.

I have 2 external drives storing duplicate (redundant) music files. Over time,  as new music was added into the iTunes library, sometimes I had used files located one of those drives, and at other times I had used files located on the other drive. In other words, some of the songs in the iTunes library were located on drive "I" while others were stored on drive "J" (for any single album, however, all of the songs were located on the same drive). iTunes had no problem keeping track of where the music files were. The original squeezebox software didn't have any trouble with it either. But the new squeezecenter software evidently did. 

When I decided to start with a "clean slate", I loaded the entire iTunes library from a single external hard drive. So all of the songs in the iTunes library were located on the same drive. This was the only difference from before. 

Based upon the foregoing, I conclude that whereas the iTunes software is perfectly capable of loading into a single iTunes library music files that are located on different external hard drives, something about your own squeezecenter software makes it incapable of doing the same thing. Consequently everthing runs fine in iTunes, but when your software tries to load the iTunes library and playlist information, it sputters and stalls. I don't know why this happens, I can only tell you that it happened to me repeatedly and that I was able to correct it through the process described here. 

I still have two external drives storing duplicate/redundant music files, but now I am careful to load new music into the iTunes library from only one of those drives, the same one each time. I have not experienced a "no disk" error since doing this approximately 2 months ago. 

I'm new to this bug group...

I have Windows XP and do not have itunes installed on my PC.  My music is on a removable USB drive.

The pop up 'Windows No Disk Error' occurs only when using SC.  I'm using Winamp for ipod functionality, and Winamp is running fine.

I've tried changing all of the drive paths, I've uninstalled SC and reinstalled - nothing seems to work.  SC won't load at all - the error window pops up and SC won't run.

The only way to get rid of the pop up is to close SC in the task manager.

So I have no music and my system is redundant until a fix is found....

I may have solved the problem.  I'm not a technical person, so bear with me!

It seems that I had one or two redundant drive paths showing on my computer - for example 'G' which was an old USB drive path, also 'F'.  I'm using 6 separate USB drives (ipod, printer, 2 flash drives, card reader, mobile phone)...  My music used to be on G, but it's now on 'M'.

Anyhoo, I unmounted drive G by going to HKLM, System, Mounted Devices in the reg edit.  I then deleted drive G by going into disk management.

The problems now seems resolved and SC is running again with no pop up message.

So it seems to be SC (or perhaps even windows) searching for a previous path that no longer exists.

Hope this helps someone.

Neil - what exact SC version have you been using when you saw this issue?

It was an earlier version - however, I removed that and have installed the very latest version.  The problem occurred on both versions (new and old).  Perhaps somewhere, deep in the software, SC looks for previous drives where the library was - and that causes the problem.  Remove those old drives and it seems (for me at least) to cure it.

I'm having problems with this duet/squeezebox software as well.

> I'm having problems with this duet/squeezebox software as well.

Could you please elaborate a bit? What problems? What software (version, OS etc.)?

I've installed and uninstalled the squeezecenter software 3x on my computer.  It's a HP Pavilion, P-4.  It runs XP Home Edition, Version 2002, Service Pack 2.

Every time I get to the point where it tries to scan my music it gets through the first stage of scanning; then I get the error message "Exception processing message c0000013 Parameters 75b6bf9c 4 75b6bf9c 75b6bf9c ... Cancel, Try again, Continue".  When I try to hit Cancel, Try Again, or Continue, absolutely nothing happens and I have to shut down my computer to get the message to go away.

Your first chair support told me to also remove the Squeeze Center folder in my Program Files folder, as well as the Squeeze Center data folder which is in the Application Data folder.  This didn't help matters at all.

My wife also has an HP computer and it works like a dream on hers.  The Duet was given to me as a birthday gift back in October and I've yet to be able to use it on my own machine.

Did you try to follow any of the instruction like eg. in comment #37? This usually is related to some drive letter reserved somewhere in Windows which isn't available any more.

I haven't tried resolving the issue as recommended in comment #37 because I didn't know that the drive could even be renamed, or that it might be a problem at all.  The external drive that has all of my music on it is "L" and when I'm loading the software and it asks where to look for music I just hit "L:\My Music".  It also asks for playlists, but I have no idea where those would be so I just type "L".  

Michael:

I walked Mark through the instructions in post # 37, but he is still recieving the "No disk" error message. Are there any log settings we can try with SqueezeCenter that can help us assess why he is still receiving this error?

The only log option I'd see are the scan.* options. Then upload the scanner.log file. Maybe we'll be seeing what it tried to read when the window popped up.

Mark - Another reason for this might be playlists pointing to inexisting drives. Couldy you please make sure you don't have any stale playlists in the music folder? Or all of the existing point to a path which is available?

Got this problem also. 

It's in the scanning of the playlists. If i empty this setting, and only scan the musicfolders, then there is no problem. If Squeezecenter try to scan the playlists, then i got this error.

Please see my previous comment #46 and comment #7

Ohkee got it. I think, this rows in the logfile makes the error:

Slim::Formats::Playlists::Base::playlistEntryIsValid (120) Warning: file:///M:/album/679%20Billy%20Ocean%20-%20Ultimate%20Collection/Billy%20Ocean%20-%20Ultimate%20Collection%20-%2003%20-%20There%27ll%20Be%20Sad%20Songs%20(To%20Make%20You%20Cry).mp3 found in playlist:
	file:///M:/album/679%20Billy%20Ocean%20-%20Ultimate%20Collection/Billy%20Ocean%20-%20Ultimate%20Collection.m3u doesn't exist on disk - skipping!

(In reply to comment #49)
> Ohkee got it. I think, this rows in the logfile makes the error:
> Slim::Formats::Playlists::Base::playlistEntryIsValid (120) Warning:
> file:///M:/album/679%20Billy%20Ocean%20-%20Ultimate%20Collection/Billy%20Ocean%20-%20Ultimate%20Collection%20-%2003%20-%20There%27ll%20Be%20Sad%20Songs%20(To%20Make%20You%20Cry).mp3
> found in playlist:
>        
> file:///M:/album/679%20Billy%20Ocean%20-%20Ultimate%20Collection/Billy%20Ocean%20-%20Ultimate%20Collection.m3u
> doesn't exist on disk - skipping!

I'm sorry it wasn't. But scanned my whole m: drive now and got the error on .m3u file i think. I attach the screenshot and the scanner.log file.

Created attachment 4522 [details]
Scanner.log

This is the scanner.log file

Created attachment 4523 [details]
Screenshot of error 

This is a screenshot of the error, and the moment in squeesecenter when it happened.

Got it! That file: U2-18singles.m3u links to 

I:\U2 - 2006 - 18 Singles(320kbps)\01 - U2 - Beautiful Day.Mp3 

But the i: doesn't exist. Ohkee, that should be the solution.

(In reply to comment #52)
> Created an attachment (id=4523) [details]
> Screenshot of error 
> This is a screenshot of the error, and the moment in squeesecenter when it
> happened.

081222-000143

WINDOWS-NO DISK ERROR Message  AGAIN!

This happened before and I restored the software to Slimserver 6.5.4 which worked fine.

I've just bought a Boom Box and this forces the installation of Squeeze Center and the uninstallation of Slimserver so now have two players on my network.

Once instance of this occurring is when the music library is rescanned after addition of new mp3s in 'My Music' 

It is necessary to 'furiously' click 'Cancel' to get rid of the error message. The media library does get updated

My system runs XP Professional with 4gb of RAM although being 32 bit I don't think it can address all the RAM. Some future proofing was built in when it was made just over a year ago.

****
Customer has already performed clean install, and has looked at this bug string and tried suggestions, and it still does not work.

Advised customer to direct information to this bug.


 

> Advised customer to direct information to this bug.

LaRon - Please don't. This is a bug tracker, not a support system.

The issue is known. The real solution is not. But there's a well known manual fix (clean up your playlists and cuesheets - see comment #18) which seems to have helped in all cases. Please help the customer do this cleanup. If this still doesn't work around the problem, come back here. Thanks.

*** Bug 10596 has been marked as a duplicate of this bug. ***