Sdimgr not writing partitions as expected

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an image that is stored as an sdi file, this sdi was captured from a
post fba image, using the commands
sdimgr /new c:\image.sdi
and
sdimgr c:\image.sdi /readpart:e:
so far so good.
I then have a script which drops all partitions on the target drive, creates
the partitions as I need than, assigns then drive letters and then formats
the new drives. I then issue the command
Sdimgr c:\image.sdi /writepart:e:
I then activate the disk and reboot the terminal, however, when I reboot the
terminal I get the message “disk read errorâ€. I’ve taken the disk out of the
unit and inspected it on my desktop, it seems to be set up correctly and all
the files appear to be in the right place, but I still get the error, am I
missing something about the sdimgr? I’ve been digging through the postings,
but have not been able to find anything that helps particually.
 
Rob,

IIRC, you have manually "fix" the partition to mark it as active (use diskpart, e.g.) after you expand SDI file onto it using
SDIMgr.
 
I already do that, I create the partitions, write the disk partition using
/writepart and then run a script in diskpart that selects the partition and
activates it. It's all a bit strange.
 
Rob,

I meant you should do that AFTER you issue /writepart command. Even more, reboot the machine after the /writepart command and then
mark the partition active.

Also, you better capturing the SDI file on the target machine (so that all boot sectors are target specific).

If you can figure this out. I'd suggest you to explore the MBR and PBR and compare them with states BEFORE and AFTER the /writepart
command.
IIRC, in the PBR, some values (like the number of heads) may be getting set wrong.
 
I re-captured the sdi, on the target machine and it all seems to be working
fine now, thanks for your help.
 
Back
Top