OK, now for a switch: a DD question. I was able to read the entire drive (cat /dev/rdisk0 > /dev/null) without error. So, I want to try a "write each sector back in place", to see if the drive is still alive or dying.
My thinking was simple: dd if=/dev/rdisk0 of=/dev/rdisk0 bs=2560 thinking that would would read 10 sectors, write those same 10 sectors, and then continue. My concern? With the same file for input and output, would it write starting at block 0, or would it read 0-9, and then write 10-19? Also: Is there a better way to re-write the contents of a hard drive? On 2016-03-26, at 7:14 PM, Carl Hoefs <[email protected]> wrote: > I believe it would use an Ultra ATA/100 hard drive (60GB?). Not sure about > availability of those anymore... > -Carl > >> On Mar 26, 2016, at 7:10 PM, Michael <[email protected]> wrote: >> >> Hmm ... what kind of drive do I put in this laptop? >> >> iBook G4, 15 inch ... 1 GB memory. >> >> (I use it primarily for a second screen, and playing dos games in QEMU). >> >> On 2016-03-26, at 7:08 PM, Carl Hoefs <[email protected]> wrote: >> >>> Disk Warrior can work wonders, but you'd probably be better off getting a >>> new drive for that $120, and reloading your Time Machine backup onto it. >>> When you start getting file system corruption, it's usually the fault of >>> the disk (as I learned the hard way :O) >>> -Carl >>> >>> >>>> On Mar 26, 2016, at 6:30 PM, Michael <[email protected]> wrote: >>>> >>>> At $120, it's not worth that much :-). >>>> >>>> I'm wondering if I could get a reinstall from the genius bar. >>>> >>>> On 2016-03-26, at 4:33 PM, Macs R We <[email protected]> wrote: >>>> >>>>> If you have disk warrior, boot from it and try to repair the drive. If >>>>> you don't have it, it's really, really worth getting. >>>>> >>>>>> On Mar 26, 2016, at 3:59 PM, Michael <[email protected]> wrote: >>>>>> >>>>>> I have an iBook G4, running 10.5.8. Today, it rebooted on me, at >>>>>> "random". >>>>>> >>>>>> During startup, it complained about problems with the root file system, >>>>>> and said that an fsck would be forced at next startup. So, I forced a >>>>>> reboot from the login screen. >>>>>> >>>>>> Naturally, it did not do the fsck. So, a reboot into single user mode. >>>>>> >>>>>> Fsck -f tells me the following: >>>>>> >>>>>> Checking Journaled HFS plus volume >>>>>> Checking extents overflow file >>>>>> Checking catalog file >>>>>> Keys out of order (4, 704) >>>>>> Rebuilding catalog B-tree >>>>>> The volume could not be repaired >>>>>> Exited with signal 8 >>>>>> >>>>>> What do I do at this point to recover? I have a full time machine backup. >>>>>> >>>>>> --- >>>>>> Entertaining minecraft videos >>>>>> http://YouTube.com/keybounce >>>>>> >>>>>> _______________________________________________ >>>>>> MacOSX-talk mailing list >>>>>> [email protected] >>>>>> http://www.omnigroup.com/mailman/listinfo/macosx-talk >>>>> >>>> >>>> --- >>>> Entertaining minecraft videos >>>> http://YouTube.com/keybounce >>>> >>>> _______________________________________________ >>>> MacOSX-talk mailing list >>>> [email protected] >>>> http://www.omnigroup.com/mailman/listinfo/macosx-talk >>> >> >> --- >> Entertaining minecraft videos >> http://YouTube.com/keybounce >> > --- Entertaining minecraft videos http://YouTube.com/keybounce _______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
