- #PARTITION FIND AND MOUNT NO PARTITION FOUND UPDATE#
- #PARTITION FIND AND MOUNT NO PARTITION FOUND FULL#
- #PARTITION FIND AND MOUNT NO PARTITION FOUND WINDOWS#
#PARTITION FIND AND MOUNT NO PARTITION FOUND WINDOWS#
And when I installed Windows to the SAN drive, I did not have the local drives connected. When I first installed Windows to the local drive, I did not have the SAN drive connected. I can't use a normal Ghost boot disk since that disk is based on WinPE and WinPE can't support a 32bit application such as Ghost. The point of the SAN drive is so I can boot off a drive that is different from the local drive so I can run Ghost to image it. Perhaps my mentioning of the SAN is complicating things. Load of Win2003ent, Local failed: Not Found
#PARTITION FIND AND MOUNT NO PARTITION FOUND FULL#
I should have just restored the Windows partition, but I wanted to test a full restore so I restored the entire disk, including the EFI partition. If you don't see it type 'attrib' since it The local disks and do the installation on
![partition find and mount no partition found partition find and mount no partition found](https://i.stack.imgur.com/sniF7.png)
Those partition GUID's (since they are the Partition GUID's and as such it is normal What most likely occured is that, when you can you boot from the SAN drive when the can you post the exact error message that ? or did you only restored the Windows partition from the GHOST image ? You mentioned some issues with the array, so was the local array config erased and re-created i.e. So any idea how I can fix this? Is there some sort of fix-efi tool? If I boot off the Smart Setup CD and go to Create Partition option, it does show that it detects an EFI partition on the local disk. I can even mount it and look at the contents, which looks to still be intact. If I boot to the SAN drive Windows again, I can see the efi partition on the local drive. Using 'dh -p diskio' and 'map', I map fs0 to the first partition and fs1 to the second partition.īut when I go to the new fs0 and do a 'ls', it says:
![partition find and mount no partition found partition find and mount no partition found](https://i.stack.imgur.com/gJg4o.png)
#PARTITION FIND AND MOUNT NO PARTITION FOUND UPDATE#
The GUIDs for the partitions have changed so I figured I need update the boot menu entry by mapping the efi partitions to fsX, find the wiindows boot options file, and use nvrboot.efi to add a boot menu entry to it.
![partition find and mount no partition found partition find and mount no partition found](https://img-16.ccm2.net/L4xuCqaAoqG0MBmd8dKUS-YOxHI=/120x/c824c518a5cb457890afbd08d8c76270/ccm-download/11532-4c6ab8f6.jpg)
Running 'map -r' didn't make a difference. Scanning the BLKx entries, I do see the local array drive and the two partitions in it (efi + windows). I jump into the built-in EFI shell, run 'map', and see that the only filesystem (fs0) mounted is the cd-rom, which has a Smart Setup CD. I do that, detach the SAN drive, and try to boot off the local array, but it complains that the requested boot item is not found. Things happened to the OS on the local array and I needed to re-apply the Ghost image to the local array to start over. This was accomplished by booting the server from a SAN drive with another copy of Windows. On a rx2620 running Windows, I took a Symantec Ghost image of the local disk array.