tag:blogger.com,1999:blog-13777170.post114419445370575907..comments2024-03-11T02:35:50.848-05:00Comments on grand stream dreams: SysAdmin Utilities on a USB-Stick ListUnknownnoreply@blogger.comBlogger4125tag:blogger.com,1999:blog-13777170.post-71181743216317208822009-03-30T14:09:00.000-05:002009-03-30T14:09:00.000-05:00this is a very nice article. many helpful links to...this is a very nice article. many helpful links to a lot of good software. i was a little sceptical but then noticed some programs i use and my scepticism vanished.<BR/>also thanks to DjLizard.<BR/>pastakAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-13777170.post-21666931846856192012008-06-05T09:06:00.000-05:002008-06-05T09:06:00.000-05:00Bart PE has saved my life on several occasions! I...Bart PE has saved my life on several occasions! I love it.<BR/><BR/>OH, another one that I have found VERY useful is the boot sector repair abilities embedded in Norton Ghost 10. This has been my saviour on several occasions and has yet to let me down.<BR/><BR/>Although, I hate the fact that Norton Ghost 10 does not allow you to create an image outside of the Windows environment. Oh, and USB drive support is highly limited. I have yet to find a USB drive that Norton Ghost 10 will load.<BR/><BR/>But, repairing the boot sector is soooooo very easy with Norton Ghost 10.Anonymoushttps://www.blogger.com/profile/15457923352034378962noreply@blogger.comtag:blogger.com,1999:blog-13777170.post-63505984735287870472007-06-07T21:57:00.000-05:002007-06-07T21:57:00.000-05:00thanks a ton, DjLizard.The link has a whole lot of...thanks a ton, DjLizard.<BR/><BR/>The link has a whole lot of great info. I will have to print it out to digest it all.<BR/><BR/>I do carry some different "Live CDs" with me, a customized Bart's PE and some Linux distros as well.<BR/><BR/>I look forward to seeing some more tips on "command-line" Linux tips. <BR/><BR/>Any helpful GUI-based disk repair/recovery utilities as well?<BR/><BR/>Any particular Linux "live cd's" you find more helpful than most for rescue and recovery to recommend?<BR/><BR/>--ClausClaushttps://www.blogger.com/profile/11692921474310162470noreply@blogger.comtag:blogger.com,1999:blog-13777170.post-25835695693617337282007-05-31T19:24:00.000-05:002007-05-31T19:24:00.000-05:00I enjoyed your list a lot, and I'm going to post a...I enjoyed your list a lot, and I'm going to post a few suggestions (tech to tech) that might save you/your clients time/money. Some of this stuff I've made myself.<BR/><BR/>If you don't already know about this, you might want to save the "printer friendly" version of the following page to your USB drive for reference: http://wiki.DjLizard.net/SVI<BR/>I have used this procedure a million times and it has saved a lot of people time and money. You might be surprised at how easy it is to identify where a registry roll-back would fix the problem, and how many times it actually does fix the problem.<BR/><BR/>Re: Linux<BR/>You might want to check out RIPLinux - it has exactly what you need and nothing more. You can do the best tasks from console, so you don't really even need the X version. If you don't get the X version, you could actually partition a larger USB drive to contain the stuff on your list in one partition and RIPLinux for USB drives in the other.<BR/><BR/>Use 'fdisk -l' to identify the detected drives/partitions<BR/>Use 'badblocks -sv /dev/hda' to scan a drive for bad sectors. Replace /dev/hda with the actual device you want to scan (which can be any kind of device, not just hard drives or their partitions). If you include the number then you are scanning just that partition. When using -sv as the parameters, badblocks will sit on one line printing the current sector / the last sector until it hits a bad block, at which point it will print the bad block # and print a carriage return. If you see that, Control+C and...<BR/>Use 'ddrescue' to clone a failing drive (or to be more accurate, a failing device) to a known-good device.<BR/><BR/>Syntax: ddrescue source destination logfile<BR/>Example: ddrescue /dev/hda /dev/hdb /hda.log<BR/>To clone native IDE drive #1 to native IDE drive #2. SATA drives usually show up as /dev/sda (or b, c, etc). You can clone anything to anywhere else (including an image file of the device, which you could then bzip2). I've recovered data from horribly scratched CD-ROMs, USB drives that were shorting out, hard drives (SATA, SCSI, and IDE), floppies, memory cards, and zero-filled writeable devices by using /dev/zero as the source. Pro-tip: use /dev/urandom as the source to do a security random-fill wipe. Don't believe the hype, you only need one wipe.<BR/><BR/>Anyway, I hope some of the above helps, and I am planning on writing more about using RIPLinux (and Linux in general) to fix Windows PCs / perform data recovery in an upcoming wiki article.<BR/><BR/>I hope the formatting of this comment isn't horrible - it's hard to write in this crampled little box. :)Anonymousnoreply@blogger.com