After Google I got the following:
Text of fix provided by Pogoplug support:
The symptoms you are describing could be caused by a corrupted index file on your Pogoplug's drive. The good news is that this file is automatically regenerated if it isn't present, but the data corruption is not currently detected by the software. Your files are intact but please do the following to resolve this:
- Log in to http://my.pogoplug.com and safely notify the software you wish to eject your drive using the eject icon next to your drive on the left pane.
- Remove you hard drive from the USB on your pogoplug.
- Attach your hard drive to your computer and allow it to be discovered.
- Open the drive in windows explorer, and delete file named "cedb" in the folder named ".cedata"
- Safely remove your drive by clicking the Safely Remove Hardware option from the toolbar in the lower right of the screen.
- Power cycle your Pogoplug, wait for SOLID green led's
- reattach your hard drive to your Pogoplug.
What I did is some different than above:
- ssh into pogoplug, remove the index file in /tmp/.cemnt/mnt_sdb2/.cedata
However I got another problem: "cannot stat '.cedata/cedata_journal': Input/Output error"
It looks like a file system corruption. Ran 'fsck' got some error... And searched online got the following:
fsck applet is only a driver. Real checking is done by executing fsck.binary. Currently, busybox does not build fsck.ext2 (although code is still around in e2fsprogs/old_e2fsprogs/e2fsck.c).
So install e2fsprogs.
ipkg update
ipkg install e2fsprogs
Now, Open a browser, logged in mypogoplug.com and eject the drive.
Back to ssh window:
- check 'mount' to make sure the drive is umounted
- run 'e2fsck /dev/sdb2'. Errors on file system fixed.
- reboot. The drive is usable now.
