 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Forum / Windows XP / Setup and Deployment / June 2006ADS - Capturing OEM partitions
I've been trying to use ADS 1.1, installed on a W2k3 Enterprise, to capture a OEM partition from a Dell Poweredge 2850 server. I can capture other partitions from the same server (System and Data), but I can't capture the OEM partition. This is the disk geometry I have on the PE2850: Disk Geometry for [\Device\Harddisk0] : Cylinders ............: 17834 Media Type ...........: 12 Tracks Per Cylinder ..: 255 Sectors Per Track ....: 63 Bytes Per Sector .....: 512 Signature ............: 1570243347 Partition Style ......: MBR Partition Information for [\Device\Harddisk0\Partition1] : Hidden Sectors .......: 63 Starting Offset ......: 32256 Partition Length .....: 32868864 (31 MB) Partition Type .......: 222 (Unknown partition type) Partition Bootable ...: FALSE Recognized Partition .: TRUE Partition Information has not changed. Partition Information for [\Device\Harddisk0\Partition2] : Hidden Sectors .......: 64260 Starting Offset ......: 32901120 Partition Length .....: 5765921280 (5498 MB) Partition Type .......: 7 (PARTITION_IFS) Partition Bootable ...: TRUE Recognized Partition .: TRUE Partition Information has not changed. Partition Information for [\Device\Harddisk0\Partition3] : Hidden Sectors .......: 11325825 Starting Offset ......: 5798822400 Partition Length .....: 3150282240 (3004 MB) Partition Type .......: 7 (PARTITION_IFS) Partition Bootable ...: FALSE Recognized Partition .: TRUE Partition Information has not changed. This is the sequence I'm using (the target has already booted to DA, so I only want to capture the partition): <?xml version="1.0" encoding="utf-16"?> <sequence version="1" description="Capture OEM partition" command="Capture_OEM_partition.xml" xmlns="http://schemas.microsoft.com/ads/2003/sequence"> <task description="Capture OEM partition" doesReboot="false"> <command>/IMAGING/imgbmdeploy.exe</command> <parameters> <parameter>"Dell_PE2850_OEM_part"</parameter> <parameter>\device\harddisk0\partition1</parameter> <parameter>"Dell PowerEdge 2850 - particao OEM"</parameter> <parameter>/c</parameter> <parameter>/p</parameter> <parameter>/client</parameter> <parameter>/nonetencrypt</parameter> </parameters> </task> </sequence> And this is the error I get on ADS, with an Exit Code of "-1056960493": "The boot sector data in the image file is corrupted." Has anyone ever seen this, or has any idea of how I can solve this? Thanks in advance! Regards, Tiago Carvalho You are lucky, I am getting this: Windows could not start due to an error while booting the RAMDISK. Windows failed to build a bootable RAMDISK image. System will reboot in 5 seconds > I've been trying to use ADS 1.1, installed on a W2k3 Enterprise, to capture a > OEM partition from a Dell Poweredge 2850 server. [quoted text clipped - 71 lines] > Regards, > Tiago Carvalho I had that one too... I'll try to hekp you on that. What version of ADS are you using? If it's 1.0, I'd consider upgrading to 1.1. It comes with several fixes, one of them related to that error message you're getting. That message is typical when the necessary network drivers for the target/device are not loaded in the PreSystem folder. Re-check that you're using the correct W2k3 network drivers for the machine you're trying to capture/deploy. While you're at it, check also the storage controller drivers. Also, activate tracing (logging) for the ADS Builder Service. All this is discussed in the article KB841550. I hope that helps! > You are lucky, I am getting this: > Windows could not start due to an error while booting the RAMDISK. Windows [quoted text clipped - 75 lines] > > Regards, > > Tiago Carvalho Thanks, I will check into it, it sems like a driver problem for sure, most likely the PERC driver. I am also using PE2850. But the only article I could find about this message was 899343 and I am using ADS 1.1 with newer files so it led me nowhere. About your problem - Are you sure that ADS can capture anything else besides NTFS partitions? I think you need to capture the whole disk. > I had that one too... I'll try to hekp you on that. > [quoted text clipped - 91 lines] > > > Regards, > > > Tiago Carvalho Once you turn the tracing on, it'll tell you what drivers/files are missing. ADS can be used to capture the OEM partition, yes. KB article #875418 refers that, but doesn't show any example of the capture sequence to use (so, I'm assuming it's just like any other partition). I'll continue to have a look on this problem, because it would simplify even more the deployment of new server hardware. > Thanks, > I will check into it, it sems like a driver problem for sure, most likely [quoted text clipped - 100 lines] > > > > Regards, > > > > Tiago Carvalho Success! It was the NIC driver. I also tried to capture the OEM partition and had the same error message. It may be because of the RAID, but unfortunately I don't have time to install W on a single disk and play with it. > Once you turn the tracing on, it'll tell you what drivers/files are missing. > [quoted text clipped - 109 lines] > > > > > Regards, > > > > > Tiago Carvalho That's good news! In a few days, I hope to have a few other servers (Dell PE 6850) captured/deployed. I don't expect any problems with them. For ADS, the RAID should be transparent, it shouldn't make any difference. Anyway, I'll do a few more tests, at least until someone can tell me exactly what I'm doing wrong... > Success! It was the NIC driver. > I also tried to capture the OEM partition and had the same error message. [quoted text clipped - 114 lines] > > > > > > Regards, > > > > > > Tiago Carvalho Change partition type 222 to 'c' (FAT32) and try again. > I've been trying to use ADS 1.1, installed on a W2k3 Enterprise, to > capture a [quoted text clipped - 73 lines] > Regards, > Tiago Carvalho How can I change the type of the partition, without loosing it's data? If I do that, on the deployment stage, I'll have to change from FAT32 to "222" again... Is that possible? > Change partition type 222 to 'c' (FAT32) and try again. > [quoted text clipped - 75 lines] > > Regards, > > Tiago Carvalho Just to let everyone know that this issue no longer exists. I've tried on new servers (PE1850, 2850 and 6850) that came with a newer BIOS version, and everything worked as expected. Thanks to everyone, and especially to Alexander Ortha, who gave me the hint about the BIOS version. Regards, Tiago Carvalho > How can I change the type of the partition, without loosing it's data? If I > do that, on the deployment stage, I'll have to change from FAT32 to "222" [quoted text clipped - 79 lines] > > > Regards, > > > Tiago Carvalho |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.