I have to say first, I have almost zero experience is the use of Terminal, an usually I'm very careful with what command I use.
I have tryed to create a bootable Android x86 usb and it was a success, it booted perfectly on a windows pc. I hope it worked on Mac too, sadly it was not.
But I immidiatly(usually shut the Mac once a week) discovered, by that boot try, I did something wrong. A slow grey loading bar appeared at the start up! Before realizing the bootable android usb (with UNetbooting) I tryed a terminal operation I saw on youtube and in another thread
sudo DiskUtil UnmountDisk disk1s1
sudo dd if=/Users/Me/Desktop/android.iso of=/rdisk1s1
(I get now it was correct
of=/dev/rdisk, right?)and I use it three times, without any results, I thought.So, after the long slow bar, I tryed to verify disk with Disk Utility and found I need to repair.
Booted my install CD and before I opened Disk Utility notice in the choice of partition install Macintosh HD was not appearing, just my Vista partition.
Disk Utility sadly sad me it was beyond repair and needed a backup. I did it twice, one with SuperDuper! (who was even faster than Time Machine, who started even long before I downloaded SD!). But I'm not ok with this. I find here this
sudo fsck_hfs -l /dev/disk0s2
with, again, just the repair advaice.
Even noticed the three tries were placed at Macintosh HD folder with lost+found and DamagedFiles folders, all created at the same time.
So I hoped deleting them the problem could be solved. No, it isn't.
Still I transcripted the 2 damaged files in the folder who are
.DSIsRunning Macintosh HD/Library/Prefences/DirectoryService
utmpx Macintosh HD/private/var/run
Now. My only chance to set everything back, even if my Mac still works without any defect sign (expect the long startup), is just to restore backup or else?