06-18-2013
You haven't told us which OS you use, but from the log i guess it is some Linux. (We shouldn't have to guess at all, so please describe always your environment.)
If so, the part probing your hardware is called "udev" and it is rule-based. Basically it scans the system permanently for (new) hardware and then executes some rule-based methods to create "devices" (=respective entries in the "/dev" hierarchy) for newly found hardware. This thing not only managed your harddisks, but also, if you are to put in (or remove) an USB stick, for instance. I suggest you read carefully the man page for "udev" to understand how it works and how certain devices (disks among them) can be "blacklisted" from probing.
If this still leaves questions feel free to ask again.
I hope this helps.
bakunin
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
:confused: ........I have a new hard drive and I need to copy ALL info from the old to the new. I would like to use the dd command. I know the command is as follows......
dd if=/dev/rdsk/c1t1d0s0 of=/dev/rdsk/????????
Where I have the question marks is the problem.
How do I find out what the... (4 Replies)
Discussion started by: shorty
4 Replies
2. Filesystems, Disks and Memory
Hi
I have 2 75GB SCSI hard drives and 2 250GB SATA hard drives which are using RAID Level 1 respectively. I wana have both FTP and Apache installed on them as services. I'm wondering what's the best partitioning schem? I wana use FC3 as my OS, so, I thought I can use the 75GB hard drive as the /... (0 Replies)
Discussion started by: sirbijan
0 Replies
3. Solaris
I have a hard drive that we are trying to jumpstart in a sunblad 1500. we keep getting errors. I placed the drive in my 1500. I want to wipe the drive clean because for some reason it has a partition table. and when i go to format and try to format the drive it says it can not use a program. is... (5 Replies)
Discussion started by: deaconf19
5 Replies
4. SCO
I have a USB hard drive attached to my SCO OSR6 machine I accidently powered it off while it was mounted and now the OS complains when you try to re-mount it and it appears that it is complaining because it has a new device number so it isn't at the original device location anymore. does anyone... (1 Reply)
Discussion started by: garycrow
1 Replies
5. Solaris
Need to replace hard drive on Ultra 10 running Solaris 2.6.
Bought new drive about the same size.
Partitioned it differently to solve a space problem.
After newfs used tar commands to copy most of the files to the new drive.
Installboot took care of the boot file.
ufsdump copied /dev and... (3 Replies)
Discussion started by: snorkack59
3 Replies
6. Filesystems, Disks and Memory
How do I check for physical damage on red hat linux hard disks? I tried smartctl /dev/sdb but it came back so fast saying it was ok. Is there a better linux command to check for bad sectors or physical disks in linux? Is there a good way such as with parted or something else? I normally in HP... (4 Replies)
Discussion started by: taekwondo
4 Replies
7. SCO
I have tried to (unsuccessfully) add an old drive to get drivers (for the 3Com network card) onto a Sco Openserver 5.1 server. Now it wont boot:
I used Sco Admin to do this.
It have 3 scuzzi drives
I added an IDE
I think what I did wrong was add the IDE to existing space, and I should not have... (6 Replies)
Discussion started by: lappies67
6 Replies
8. Filesystems, Disks and Memory
Hello
I am having a problem with being able to use my 2nd hard drive as my new os doesn't recognize it. it is /dev/hdb2 and it shows as It is still in my system. it is a 73 gb hard drive and it is useless to me now. I used to have windows XP and had no problem with it,I have since changed to... (2 Replies)
Discussion started by: Donald Spauldin
2 Replies
9. UNIX for Beginners Questions & Answers
Hello all,
I am EXTREMELY new to using bash and I have a bit of a problem: I'm trying to set up a shell script that can
1.) take one of several giant files off of an external hard drive
2.) use it as input for scripts on my laptop's hard drive
... (3 Replies)
Discussion started by: machine_spirit
3 Replies
LEARN ABOUT DEBIAN
bup-damage
bup-damage(1) General Commands Manual bup-damage(1)
NAME
bup-damage - randomly destroy blocks of a file
SYNOPSIS
bup damage [-n count] [-s maxsize] [--percent pct] [-S seed] [--equal]
DESCRIPTION
Use bup damage to deliberately destroy blocks in a .pack or .idx file (from .bup/objects/pack) to test the recovery features of bup-fsck(1)
or other programs.
THIS PROGRAM IS EXTREMELY DANGEROUS AND WILL DESTROY YOUR DATA
bup damage is primarily useful for automated or manual tests of data recovery tools, to reassure yourself that the tools actually work.
OPTIONS
-n, --num=numblocks
the number of separate blocks to damage in each file (default 10). Note that it's possible for more than one damaged segment to
fall in the same bup-fsck(1) recovery block, so you might not damage as many recovery blocks as you expect. If this is a problem,
use --equal.
-s, --size=maxblocksize
the maximum size, in bytes, of each damaged block (default 1 unless --percent is specified). Note that because of the way bup-
fsck(1) works, a multi-byte block could fall on the boundary between two recovery blocks, and thus damaging two separate recovery
blocks. In small files, it's also possible for a damaged block to be larger than a recovery block. If these issues might be a
problem, you should use the default damage size of one byte.
--percent=maxblockpercent
the maximum size, in percent of the original file, of each damaged block. If both --size and --percent are given, the maximum block
size is the minimum of the two restrictions. You can use this to ensure that a given block will never damage more than one or two
git-fsck(1) recovery blocks.
-S, --seed=randomseed
seed the random number generator with the given value. If you use this option, your tests will be repeatable, since the damaged
block offsets, sizes, and contents will be the same every time. By default, the random numbers are different every time (so you can
run tests in a loop and repeatedly test with different damage each time).
--equal
instead of choosing random offsets for each damaged block, space the blocks equally throughout the file, starting at offset 0. If
you also choose a correct maximum block size, this can guarantee that any given damage block never damages more than one git-fsck(1)
recovery block. (This is also guaranteed if you use -s 1.)
EXAMPLE
# make a backup in case things go horribly wrong
cp -a ~/.bup/objects/pack ~/bup-packs.bak
# generate recovery blocks for all packs
bup fsck -g
# deliberately damage the packs
bup damage -n 10 -s 1 -S 0 ~/.bup/objects/pack/*.{pack,idx}
# recover from the damage
bup fsck -r
SEE ALSO
bup-fsck(1), par2(1)
BUP
Part of the bup(1) suite.
AUTHORS
Avery Pennarun <apenwarr@gmail.com>.
Bup unknown- bup-damage(1)