Console fseventd error - Disk not readable

Discussion in 'macOS' started by XFire, May 23, 2011.

  1. XFire macrumors newbie

    May 23, 2011
    Just today when plugging in my U3 ClvrStuff USB Flash Drive i received the error "The Disk you inserted is not readable by this computer", i pressed Initialize and from then onwards it gradually went downhill. Both Data Rescue 3 and DiskWarrior 4 were unable to save my USB flashdisk and unfortunately i was left with having to completely reformat, a few times also on Zero Out Data.

    Currently operating a MacBook Pro version 10.6.7, the problem has not gone away. One of the intermediate steps i carried out was to reformat into MacOS Extended (Journaled) and then rebuild the USB by using DiskWarrior. The Graph has reported 28/108 errors with the blue graph underneath showing an "un-optimized" disk. This was then reformatted again into FAT32 using Disk Utility. Upon ejecting and remounting the USB i always get the error:

    "The disk you inserted is not readable by this computer" with the options only to Ignore and Eject.

    I have checked Console and this is what comes up around the time of the error.

    23/05/2011 18:52:42 fseventsd[46] could not open <</Volumes/DISKNAME/.fseventsd/fseventsd-uuid>> (No such file or directory)
    23/05/2011 18:52:42 fseventsd[46] log dir: /Volumes/DISKNAME/.fseventsd getting new uuid: 4193C981-354D-4FB3-AA6B-CF7DC87D8E16
    23/05/2011 18:52:42 mds[40] (Normal) DiskStore: Creating index for /Volumes/DISKNAME

    23/05/2011 18:53:18 kernel USBMSC Identifier (non-unique): 0B604B615222995B 0x8ec 0x20 0x200

    23/05/2011 18:53:19 fseventsd[46] check_vol_last_mod_time:XXX failed to get mount time (25; &mount_time == 0x10037f8b8)
    23/05/2011 18:53:19 fseventsd[46] log dir: /Volumes/DISKNAME/.fseventsd getting new uuid: 0E213259-9297-40F3-A6E0-876696996E23

    23/05/2011 18:53:22 kernel SAM Multimedia: READ or WRITE failed, SENSE_KEY = 0x00, ASC = 0x00, ASCQ = 0x00
    23/05/2011 18:53:22 kernel SAM Multimedia: READ or WRITE failed, SENSE_KEY = 0x00, ASC = 0x00, ASCQ = 0x00
    23/05/2011 18:53:22 kernel SAM Multimedia: READ or WRITE failed, SENSE_KEY = 0x00, ASC = 0x00, ASCQ = 0x00

    The SAM Multimedia errors continue and repeat for a little while until this then comes up

    23/05/2011 18:53:22 kernel disk2s0: I/O error.

    I am unsure what to do to prevent these errors from showing up anymore, or is there no such method to repair my USB. I am not interested in the restoring of any files or anything as i've lost them all anyway, but simply a method of stopping the problem.

    Any help is appreciated, thank you.
  2. taylortm macrumors member

    Mar 11, 2011
    California, USA
    Flash drive shot?

    I'm pretty sure your flash drive is done. When you say it's the "first time" you plugged it in... do you mean EVER (as in you just took it out of the box)? Or do you mean you've used it with other machines for a long time and it worked fine and it just starting behaving like this with this particular Mac?

    The .fsevents errors are related to the fact that Mac OS leaves "breadcrumbs" on every volume it ever sees/touches. You can google to see exactly what it's used for. But, basically, it's one of the first things it does when mounting a volume: look for that directory (and its files) and then create it, if it's not there. Those console log entries just show that process happening.

    The other entries that repeat a lot and just end in "I/O error" are the repeated attempts of your USB to try to write to the USB drive. There are low-level ACKs (confirmations that data is properly being stored on the USB drive) that get exchanged and are not normally seen by "regular users." All of those repeated error lines are repeated failures to confirm that data is properly being written to your USB drive. After so many of those, it "gives up" and reports the I/O error to the OS (and logs it in the Console). Of course, at the user level, you probably get some much less informative summary, like "This drive cannot be used... Retry or Eject."

    As I said, my best guess is that the USB drive is literally bad and unable to read/write data. I suggest trying it with other computers and seeing if you have better luck. If it works with other computers, I'm totally wrong and you should pretend you never saw this post. (And then you might suspect the specific USB port you are using. I assume you're not using a cable. And, after that, you might start watching your Console for other USB-related issues.)

    Good luck.

Share This Page