Bugzilla – Bug 15942
Unsupported Disk Format error message seen when attaching external USB hard drive with specific steps
Last modified: 2010-04-08 17:26:46 UTC
Running firmware r8661 and Fab4/TinySC combination. Will get Unsupported Disk Format error message when attaching an external powered USB drive in this sequence: 1. Fab4 powered up and running. TinySC not running. 2. USB drive already powered up. 3. Plug in USB cable for drive into Fab4. 4. Fab4 sees USB drive and displays screen. 5. After about 15 seconds, displays Unsupported Disk Format Will NOT get this error message if I follow this sequence: 1. Fab4 OFF with no power cord plugged into back. 2. USB drive already powered up. 3. Plug in USB cable for drive into Fab4. 4. Plug in power cord into Fab4. In the second case, TinySC will start up OK and scan the drive after Fab4 finishes booting. Seen with these three hard drives: WD Elements 1.5TB Seagate Expansion 2TB Hitachi XL1000 1TB Easily reproducible, so let me know if there are logging switches to enable debugging. Screen shot of error message enclosed.
Created attachment 6684 [details] Photo of error message
What filesystem is formatted on these drives? Do you have the ability to attach a serial console and see what's being shown there? I don't think the kernel messages actually go to syslog, so I think the only way to see them is via a serial console.
You should get the output of dmesg and/or /var/log/messages when this happens.
heh...right, what Andy said. dmesg output will probably be the most telling (and the equivalent of what I was asking for), but both it and /var/log/messages together should do it.
I'll have a look. These are all NTFS formatted.
Created attachment 6685 [details] dmesg output Dmesg file show attached WD drive. Note that it shows itself as 3 drives -- a the drive itself, a virtual CD-ROM and a SES drive enclosure controller. This file generated when Fab4 did NOT successfully see the drive.
Created attachment 6686 [details] Messages file with 2 attempts: first one worked, last one did not Oddly enough, a second attempt to connect the WD 1TB MyBook drive worked fine. That's shown in the first half of the message log. The second half of the message log shows a failed attempt to connect. The failure occurred after I deleted the .Squeezebox and Playlist folders from the drive (plugged into Windows XP). Note that in both attempts, Linux eventually mounts the MyBook drive, even though Fab4 doesn't see it the second time. Not sure what's going on, but one guess is that we're not waiting long enough for Linux to mount the drive. There's some drive-spin up time when first plugging in a external USB drive; I can hear it spinning up immediately when I plug the USB cable into the back of Fab4. Not sure what the deletion of .Squeezebox has to do with this, though.
The mount timer expired after 20 seconds but the NTFS partition took a bit longer to mount: Dec 31 20:34:36 squeezeplay: DEBUG applet.SqueezeCenter - SqueezeCenterApplet.lua:586 mountingDriveTimeout=20 Dec 31 20:34:36 squeezeplay: WARN applet.SqueezeCenter - SqueezeCenterApplet.lua:615 *** Device failed to mount. Dec 31 20:34:37 squeezeplay: DEBUG squeezebox.server - SlimServer.lua:566 SlimServer {Mickey's Work Fab4 #2 (USB)}:free Dec 31 20:34:39 ntfs-3g[2679]: Version 2009.4.4 integrated FUSE 27 Dec 31 20:34:39 ntfs-3g[2679]: Mounted /dev/sda1 (Read-Write, label "My Book", NTFS 3.1) Dec 31 20:34:39 ntfs-3g[2679]: Cmdline options: Dec 31 20:34:39 ntfs-3g[2679]: Mount options: silent,allow_other,nonempty,relatime,fsname=/dev/sda1,blkdev,blksize=4096 Dec 31 20:34:39 squeezeplay: DEBUG applet.SqueezeCenter - SqueezeCenterApplet.lua:354 udevEventHandler() Dec 31 20:34:39 root: mount.sh/automount Auto-mount of [/media/sda1] successful The timer should be 30 seconds, so I'm not sure why it is 20 here. I think the only thing we can do is set a longer timeout.
== Auto-comment from SVN commit #8664 to the jive repo by bklaas == == https://svn.slimdevices.com/jive?view=revision&revision=8664 == Bug: 15942 Description: set mount timeout back to 30 seconds
== Auto-comment from SVN commit #8665 to the jive repo by bklaas == == https://svn.slimdevices.com/jive?view=revision&revision=8665 == Bug: 15942 Description: set timeout to 60 seconds for very slow to mount drives
Finally able to test with r8665. Works great with drives that failed previously: 1. WD MyBook 1TB 2. WDElements 1.5TB Tried it 2-3 times each. Renamed .Squeezebox and Playlists folders on each drive once too.
This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release. If you are still seeing this issue, please let us know!