Hi Rob, A couple of things. I'd probably make sure that the disk is fully readable first to see if there are any physical errors on it. A quick one-liner is the following:
sudo dd if=/dev/sdX of=/dev/null where /dev/sdX is the name of the device. This basically reads all the raw blocks from the device and writes them into the null device. One can find the name of the device by the df command which shows the device name and the mount point. Either do the entire disk, e.g. /dev/sda (for a full disk check) or the partition that is showing the problem (which may be quicker if you have several partitions) e.g. /dev/sda1. It will take some time... I suggest typing dmesg when the dd command has finished just to see if the kernel has reported any device read errors. If this looks OK, I suggest doing an fsck from the Linux side of things. ..and let me know the results. Cheers, Colin. -- hfsplus oops, corrupted file system https://bugs.launchpad.net/bugs/202595 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs