Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Deleting a SYS volume that was extended to a SAN drive

Status
Not open for further replies.

Provogeek

MIS
Sep 4, 2002
1,412
US
Need a sanity check here.

I just recently completed a migration for a customer from 4.11 to 5.1sp5. The migration went with out issue, but after the migration was complete I am getting segment errors on my SYS volume when I go into volume options.

Warning: Volume SYS is missing segment 0. Check to be sure all disk drivers are loaded and configured properly. (nwconfig-5-192)

<enter>

The first segment of volume SYS, segment 1, does not start at block 0. Check to be sure all disk drivers are loaded and configured properly, and that there are not multiple volumes with the same name. (nwconfig-1-194)

<enter>

The definition for syn (or instance) 2 of volume SYS was removed. (nwconfig-5-198)

<enter>

Updating definition of volume SYS

<enter>



Write volume changes to disk? choosing NO

Delete the invalid volume segments? choosing NO



I have chosen not to do anything at this point because the server is running fine, my SYS volume on my new server mounts with out issue. What I have found is that for some reason no one at my client site remembers, the SYS volume was extended to a drive on the SAN when the old server was in operation. The only volume that was actually migrated was the SYS volume. The volumes hosted on the SAN were left alone, and only moved the SCSI cable from the old server to the new server to migrate those.

So now there is a segment of a SYS volume that is being detected. When I boot the old server I am unable to mount SYS due to missing segments (this is what brought me to the conclusion that someone had extended the SYS volume to the SAN).

What I plan to due is during the next down time window, I will down the new server. Move the SAN SCSI cable to the old server and boot it. The SYS volume should mount now that it has the SAN attached to it. DS is locked on the old server and it will never be attached to the network. Once I have the old server up, I plan to just delete the SYS volume.

Since I am not in the habit of deleteing SYS volumes, I am unsure if I will be able to do this. Will the system allow me to delete a SYS volume with out deleteing any other the other volumes it will detetect, even if those volumes are not monted?

 
Hi Provo,

I saw this once before after a ServerMagic migration. Is this what you used? Did you resize the volume or partition using ServerMagic? If so, PowerQuest will have you download a few utilities to correct this. It's been a while so I don't remember the details.

Your statement above &quot;the SYS volume was extended to a drive on the SAN&quot;, even if that were the case, when you migrated, SYS should have migrated whole. So I don't know what to make of that.

Since you mentioned that you moved the SCSI cable, I did find an old TID on Novell's site that mentioned the cable could be the problem....nothing to lose by checking it.

I have deleted SYS and believe me it will allow it. Not sure what you mean about being able to delete the volume with deleting the others. One volume should have nothing to do with the others. But whatever you do, I sure hope you have a backout/contingency plan.

Good Luck
Lou

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top