I have occasionally had to run an fsck on a filesystem multiple times before it fixed everything. You might want to try the same. But, really, at this point, you're going to need to replace the drive anyway, and the original data is corrupted, so you'll need a new install, too. There's probably not a lot of point.

Also, I should have told you to run it against /dev/rdisk0s3. It's possible that that's relevant, too.