Re: rebuild 240v from scratch


Mike Dundas wrote:

> My plan was to partition mirror boot drive on "server b" to
> match our "server a" and ufsdump/ufsrestore over the network to the
> mounted mirror boot partitions on "server b". Once I had mirror boot
> disk bootable, I would boot from it and dd from one disk to the other.
>
> Once system restore was complete, I modified the vfstab on mounted
> mirror drive, /mnt/etc/vfstab, to point to correct disk and installed
> bootblk. I tried to boot from disk1 and the system failed to boot and
> panicked rebooting from primary boot disk. I have done some
> investigation and I think it has to do with the meta devices.
>
> boot message:
>
> Cannot open mirrored root device, error 19
> Cannot remount root on /pseudo/md@0:0,0,blk fstype ufs
>
> panic[cpu1]/thread=180e000: vfs_mountroot: cannot remount root
>
> Any help appreciated,
>
> Mike Dundas

If your description of what took place is complete I would say
that the failure is due to that you did NOT create a new set
of METADEVICE databases on server b.


There is at least three things that must be present for a successful
volumemanager boot:

/etc/system file must preload the MD devicedrivers and
the pointer to the metadevice rootfilesystem.

/etc/vfstab must reference the metadevices.

A valid and correct metadabase must exist that translates
the metadevice root-referens from /etc/system to a physical
disc/partition number.

The error seems to say that the /etc/system file that you copied
over from server A with its root metadevice pointer could not
find a metadb on server B to resolve it to a physical partition.

//Lars

.

Relevant Pages

  • Re: Backup fails suspect VSS problem
    ... Will reboot and run a backup tonight and see what happens. ... The problem I have now is that the server appears to the customer to ... I don't even try to boot after swapping a motherboard. ... Could not access portions of directory System State\COM+ ...
    (microsoft.public.windows.server.sbs)
  • Re: RIS, same GUID, duplicates, Dell GX60s
    ... My first thought is the boot agent on the nic needs to be updated. ... these nics part of the motherboard or pci devices? ... It has to be run from a server and a floppy is created ... the nic drivers are not entirely correct, update the drivers in your RIS ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Backup fails suspect VSS problem
    ... System State can be backed-up on its own fine! ... Kerry Brown ... The problem I have now is that the server appears to the customer to be ... I don't even try to boot after swapping a motherboard. ...
    (microsoft.public.windows.server.sbs)
  • Re: Backup fails suspect VSS problem
    ... I suspect this has something to do with VSS because after a failed backup ... The problem I have now is that the server appears to the customer to be ... I don't even try to boot after swapping a motherboard. ... Could not access portions of directory System State\COM+ ...
    (microsoft.public.windows.server.sbs)
  • Re: Backup fails suspect VSS problem
    ... Something else I have noticed is that after a backup failure 'VSSAdmin List ... The problem I have now is that the server appears to the customer to be ... I don't even try to boot after swapping a motherboard. ...
    (microsoft.public.windows.server.sbs)