SCIENTIFIC-LINUX-USERS Archives

April 2013

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Yasha Karant <[log in to unmask]>
Reply To:
Yasha Karant <[log in to unmask]>
Date:
Tue, 9 Apr 2013 19:04:01 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (16 lines)
Based on observations of the failure mode of anaconda for an in-place 
upgrade to 6.4, I used a heuristic method and solved the problem.

I made a backup copy of /etc/fstab, and then edited fstab to remove all 
references to any physical hard drive (e.g., sdb, sdc) that did not 
contain the images that needed upgrading.  For upgrade, anaconda 
evidently depends upon the contents of fstab; this change made anaconda 
ignore the disks with which it found issue.  After the upgrade and 
reboot, I then copied the saved fstab over the edited fstab, issued the 
appropriate mount command, and everything seems to be working.

I presume that this will not work when we migrate to SL 7 and must only 
have the target hard drive physically connected.

Yasha Karant

ATOM RSS1 RSS2