On 08/09/2017 11:52 AM, D&R wrote:
When I boot into the install there is an error in the destination
section.
I looked at the debug info in the storage.log and there was an
error about sdb1 did not exist. But...
When I reboot to F24 then ...
cat /proc/mdstat
md126 : active raid1 sda2[2] sdb2[1]
961261568 blocks super 1.2 [2/2] [UU]
bitmap: 2/8 pages [8KB], 65536KB chunk
md127 : active raid1 sdb1[1] sda1[2]
15368064 blocks super 1.0 [2/2] [UU]
bitmap: 1/1 pages [4KB], 65536KB chunk
The section of ks.cfg for hard drive setup is as follows:
ignoredisk --only-use=sda,sdb
bootloader --location=mbr --boot-drive=sda
# Partition clearing information
clearpart --none --initlabel
# Disk partitioning information
part raid.6 --fstype=mdmember --noformat --onpart=sda1
part raid.27 --fstype=mdmember --noformat --onpart=sdb1
part raid.14 --fstype=mdmember --noformat --onpart=sda2
part raid.32 --fstype=mdmember --noformat --onpart=sdb2
raid / --device=root --fstype=ext4 --level=raid1 --useexisting
raid /home --device=home --fstype=ext4 --level=raid1 --noformat --useexisting
I currently have a raid1 setup with 2 drives sda and sdb
Since I am using the option --useexisting do I still need to use the part
commands?
The last time I did an upgrade was to F24 I have not found anything that says
the syntax has changed.
Any Ideas?
Uhm, when you're booting the install, is it possible that the CD/DVD
you're booting from becomes /dev/sda? If so, then your first hard drive
is /dev/sdb and the second is /dev/sdc and the
ignoredisk --only-use=sda,sdb
would block using the second hard drive, since it's /dev/sdc at this
time. This is just a wild guess.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- If your broker is so damned smart...why is he still working? -
----------------------------------------------------------------------