This is a discussion on dd disk image won't boot within the comp.unix.solaris forums, part of the Solaris Operating System category; --> Hello, I have the following problem : I took a dd image from a boot disk on a E4500 ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello, I have the following problem : I took a dd image from a boot disk on a E4500 to another disk on a second diskboard. disk0 (source) = /dev/dsk/c0t10d0s2 disk3 (target) = /dev/dsk/c1t14d0s2 The goal was to have a copy of the boot disk. (I know there are better and faster ways of copying disk, but this is the way it is). As dd takes a bitwise copy, I expect the resulting disk to be bootable. So, I issued the following command (in single user mode) : dd if=/dev/rdsk/c0t10d0s2 of=/dev/rdsk/c1t14d0s2 bs=1048576 When I swap the diskboards, the kernel spits out the following error message : Device not bootable I booted from cdrom, mounted the disk, and verified the contents of it. Looked Ok. Then I made sure the disk to be bootable by a "installboot" command. When I rebooted with "boot disk" on the Ok prompt, I got the same error (Device not bootable). I'm really puzzled here. Could it be that I have to dd the last slice too ? Maybe the blocksize is too big, and a part of the last slice didn't get copied ? The disk I dd'ed was mirrorred too. Could this be a problem ? But I expect that the copied disk only will complain about it mirror not up to date (metastat will issue a Needs maintenance), so that after a "metareplace -e c1t15d0s2" (second disk on the new diskboard), the mirror resyncs itself. DN. |
| |||
| ><foo@unix.org> a écrit dans le message de >> I booted from cdrom, mounted the disk, and verified the contents of it. >> Looked Ok. Then I made sure the disk to be bootable by a "installboot" >> command. When I rebooted with "boot disk" on the Ok prompt, I got the >> same error (Device not bootable). mika wrote: > You must install boot block on the new disk# installboot > /usr/platform/`uname -i`/lib/fs/ufs/pboot > /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t6d0s2"/dev/null" Maybe the original poster wasn't totally clear on that but it seems to me that he already did install the bootblock on the new disk... Kristof |
| ||||
| /dev/null <foo@unix.org> wrote: > Hello, > I have the following problem : > I took a dd image from a boot disk on a E4500 to another disk on a > second diskboard. > disk0 (source) = /dev/dsk/c0t10d0s2 > disk3 (target) = /dev/dsk/c1t14d0s2 > The goal was to have a copy of the boot disk. (I know there are better > and faster ways of copying disk, but this is the way it is). As dd takes > a bitwise copy, I expect the resulting disk to be bootable. Correct. > When I swap the diskboards, the kernel spits out the following error > message : > Device not bootable The "kernel" does? Huh? I've never seen "Device not bootable" from the kernel or from an OBP message. Instead I'd expect "No such device", "can't open device", or "contents don't appear to be bootable". Can you cut & paste the entire contents from "boot disk" to the error message? I can only assume that you're not booting from the disk you think you are. -- Darren Dunham ddunham@taos.com Unix System Administrator Taos - The SysAdmin Company Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. > |