SCIENTIFIC-LINUX-USERS Archives

August 2018

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:
off line upgrade to 7.5 from 7 previous [3]
From:
Yasha Karant <[log in to unmask]>
Reply To:
Yasha Karant <[log in to unmask]>
Date:
Thu, 23 Aug 2018 23:13:04 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (90 lines) 
The pre SL 7.5 machine for which yum crashed during an upgrade does 
boot.  I ran parted as root on the hard drive with the following output:

Model: ATA TOSHIBA DT01ACA2 (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:

Number  Start   End     Size    Type      File system     Flags
  1      32.3kB  41.1MB  41.1MB  primary   fat16           diag
  2      41.9MB  11.1GB  11.1GB  primary   ntfs            boot, diag
  3      11.1GB  51.1GB  40.0GB  primary   xfs
  4      51.1GB  2000GB  1949GB  extended
  5      51.1GB  1051GB  1000GB  logical   xfs
  6      1051GB  1251GB  200GB   logical   xfs
  7      1251GB  1451GB  200GB   logical   xfs
  8      1451GB  1651GB  200GB   logical   xfs
  9      1651GB  1751GB  100GB   logical   xfs
10      1751GB  1791GB  40.0GB  logical   linux-swap(v1)
11      1791GB  1941GB  150GB   logical   xfs


Model: ATA TOSHIBA DT01ACA2 (scsi)
Disk /dev/sdb: 2000GB
Sector size (logical/physical): 512B/4096B

Partition Table: msdos
Disk Flags:

Number  Start   End     Size    Type      File system     Flags
  1      32.3kB  41.1MB  41.1MB  primary   fat16           diag
  2      41.9MB  11.1GB  11.1GB  primary   ntfs            boot, diag
  3      11.1GB  51.1GB  40.0GB  primary   xfs
  4      51.1GB  2000GB  1949GB  extended
  5      51.1GB  1051GB  1000GB  logical   xfs
  6      1051GB  1251GB  200GB   logical   xfs
  7      1251GB  1451GB  200GB   logical   xfs
  8      1451GB  1651GB  200GB   logical   xfs
  9      1651GB  1751GB  100GB   logical   xfs
10      1751GB  1791GB  40.0GB  logical   linux-swap(v1)
11      1791GB  1941GB  150GB   logical   xfs


Model: Linux Software RAID Array (md)
Disk /dev/md126: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:

Number  Start   End     Size    Type      File system     Flags
  1      32.3kB  41.1MB  41.1MB  primary   fat16           diag
  2      41.9MB  11.1GB  11.1GB  primary   ntfs            boot, diag
  3      11.1GB  51.1GB  40.0GB  primary   xfs
  4      51.1GB  2000GB  1949GB  extended
  5      51.1GB  1051GB  1000GB  logical   xfs
  6      1051GB  1251GB  200GB   logical   xfs
  7      1251GB  1451GB  200GB   logical   xfs
  8      1451GB  1651GB  200GB   logical   xfs
  9      1651GB  1751GB  100GB   logical   xfs
10      1751GB  1791GB  40.0GB  logical   linux-swap(v1)
11      1791GB  1941GB  150GB   logical   xfs

End output.

An external  USB 2 Tbyte drive is mounted by this system as /dev/sdg

Is there any reason that as root

dd if=/dev/sda of=/dev/sdg

would not image the mirrored "RAID" drives from one of the mirror set?  
By this means, all of /home , /opt  and the like should be recoverable?  
There may be minor discrepancies but as the system was not being used 
other than for root to run yum, the image should have all vital 
configuration files as
well as all end-user home directories.

Also, as the system does boot, is there anyway to start yum "fresh" and 
force an upgrade at this point?  Only the Xwindows system fails under 
the old system.  During the boot sequence, one can choose the SL7.5 
image, but this one fails with a panic due to the yum upgrade failure.  
However, the older system image does boot as the above output serves to 
verify.  My guess is there are one or more yum bookkeeping files that 
need modification for a "fresh" yum update to be enabled.

Any further assistance would be appreciated.

Yasha Karant

ATOM RSS1 RSS2