05-21-2015
dd if=/dev/sda of=/mnt/USBDrive/dd/partition-restore bs=1 count=2047 will give you 2047 bytes, not blocks, because you have set the block size to 1. Use bs=512, or just leave out bs entirely, since dd will assume 512 when you don't tell it otherwise. I think you want 2048, not 2047, as well.
There is no 'sector', 'cylinder', 'head', 'track', etc, etc, etc. None of that has been relevant for going on 20 years. Hard drives do have a block size though, of 512 bytes (and even the very newest drives, which use 4K blocks internally, still act like they have 512 byte blocks.)
34612341692783461 lines of script aren't going to help you when you don't know how to do it by hand.
This User Gave Thanks to Corona688 For This Post:
9 More Discussions You Might Find Interesting
1. Solaris
Please help urgently.
I need to setup up some sort of service on a solaris server on a port.
I dont need it do anything special, anything that is sent to this port from an external server should be dump to /dev/null or a flat file..
Can you help urgently? (1 Reply)
Discussion started by: frustrated1
1 Replies
2. Solaris
Hi, Anyone can help
My solaris 8 system has the following
/dev/null , /dev/tty and /dev/console
All permission are lrwxrwxrwx
Can this be change to a non-world write ??
any impact ?? (12 Replies)
Discussion started by: civic2005
12 Replies
3. UNIX for Dummies Questions & Answers
Hello,
i am using finch (unix commandline instant messaging client using libgnt) which is running connected to /dev/pts/1
Now I would like to "remote control" the program by sending the key combinations normally typed on the keyboard from a programm in another shell. So I tried:... (0 Replies)
Discussion started by: mentos
0 Replies
4. Slackware
Hello,
Ive got an HP LaserJet 2100 / parallel interface.
I had some troubles getting going due to non-working cups drivers. Updated cups and also used a .ppd.gz file from something HP provided. found the files here...
www.linuxprinting.org/show_printer.cgi?recnum=HP-LaserJet_2100
Anyways.... (1 Reply)
Discussion started by: agentrnge
1 Replies
5. Solaris
So, we removed a LUN from the SAN and the system is refusing to remove the references to it in the /dev folder. I've done the following:
devfsadm -Cv
powermt -q
luxadm -e offline <drive path>
luxadm probe
All those commands failed to remove the path. The drive stills shows up as <drive... (13 Replies)
Discussion started by: DustinT
13 Replies
6. AIX
Hi,
How can i check that i am using RAW devices for storage in my AIX machine...
Also after adding a LUN from storage to a aix host, when i check /dev in the host, i can see both rhdisk and hdisk with same number
eg:
dcback1(root):/dev>ls -lrt | grep disk12
crw------- 1 root ... (4 Replies)
Discussion started by: jibujacob
4 Replies
7. AIX
Hello AIXians,
I can't boot my AIX, it hangs and stops at the code error: 0518
After searching google, I knew the problem is due to problems in File Systems.
So the solution is booting from any bootable media, then run these commands in maintenance mode:
#fsck -y /dev/hd4
#fsck -y... (3 Replies)
Discussion started by: Mohannad
3 Replies
8. Red Hat
Hi,
Please suggest steps to change grub from /dev/sda to /dev/sdb, (1 Reply)
Discussion started by: manoj.solaris
1 Replies
9. HP-UX
Hi,
In our HP-UX B.11.11. I could not find dev/urandom and dev/random
Are all pseudo-devices implemented as device drivers, or in need to run /configure some package to install the package to have dev/urandom.
Please help (4 Replies)
Discussion started by: rashi
4 Replies
HP(4) Kernel Interfaces Manual HP(4)
NAME
hp - RH-11/RP04, RP05, RP06 moving-head disk
DESCRIPTION
The octal representation of the minor device number is encoded idp, where i is an interleave flag, d is a physical drive number, and p is a
pseudodrive (subsection) within a physical unit. If i is 0, the origins and sizes of the pseudodisks on each drive, counted in cylinders
of 418 512-byte blocks, are:
disk start length
0 0 23
1 23 21
2 0 0
3 0 0
4 44 386
5 430 385
6 44 367
7 44 771
If i is 1, the minor device consists of the specified pseudodisk on drives numbered 0 through the designated drive number. Successively
numbered blocks are distributed across the drives in rotation.
Systems distributed for these devices use disk 0 for the root, disk 1 for swapping, and disk 4 (RP04/5) or disk 7 (RP06) for a mounted user
file system.
The block files access the disk via the system's normal buffering mechanism and may be read and written without regard to physical disk
records.
A `raw' interface provides for direct transmission between the disk and the user's read or write buffer. A single read or write call
results in exactly one I/O operation and therefore raw I/O is considerably more efficient when many words are transmitted. The names of
the raw files conventionally begin with an extra `r.' In raw I/O the buffer must begin on a word boundary, and raw I/O to an interleaved
device is likely to have disappointing results.
FILES
/dev/rp?, /dev/rrp?
SEE ALSO
rp(4)
BUGS
In raw I/O read and write(2) truncate file offsets to 512-byte block boundaries, and write scribbles on the tail of incomplete blocks.
Thus, in programs that are likely to access raw devices, read, write and lseek(2) should always deal in 512-byte multiples.
Raw device drivers don't work on interleaved devices.
HP(4)