On Sat, 26 Aug 2017 13:06:43 -0500
D&R wrote:
> On Mon, 21 Aug 2017 22:19:05 -0500
> D&R wrote:
>
> > On Sat, 19 Aug 2017 17:18:53 -0500
> > dwoody5...@gmail.com wrote:
> >
> > > On Wed, 9 Aug 2017 14:27:07 -0700
> > > Rick Stevens wrote:
> > >
> > > > On 08/09/2017 12:08 PM, D&R wrote
On Mon, 21 Aug 2017 22:19:05 -0500
D&R wrote:
> On Sat, 19 Aug 2017 17:18:53 -0500
> dwoody5...@gmail.com wrote:
>
> > On Wed, 9 Aug 2017 14:27:07 -0700
> > Rick Stevens wrote:
> >
> > > On 08/09/2017 12:08 PM, D&R wrote:
> > > > On Wed, 9 Aug 2017 12:00:00 -0700
> > > > Rick Stevens wr
On Sat, 19 Aug 2017 17:18:53 -0500
dwoody5...@gmail.com wrote:
> On Wed, 9 Aug 2017 14:27:07 -0700
> Rick Stevens wrote:
>
> > On 08/09/2017 12:08 PM, D&R wrote:
> > > On Wed, 9 Aug 2017 12:00:00 -0700
> > > Rick Stevens wrote:
> > >
> > >> On 08/09/2017 11:52 AM, D&R wrote:
> > >>>
On Wed, 9 Aug 2017 14:27:07 -0700
Rick Stevens wrote:
> On 08/09/2017 12:08 PM, D&R wrote:
> > On Wed, 9 Aug 2017 12:00:00 -0700
> > Rick Stevens wrote:
> >
> >> On 08/09/2017 11:52 AM, D&R wrote:
> >>> When I boot into the install there is an error in the destination
> >>> section.
> >>>
>
On Thu, 10 Aug 2017 14:03:46 -0700
Gordon Messmer wrote:
> On 08/10/2017 01:36 PM, D&R wrote:
> > /dev/md:
> > total 0
> > lrwxrwxrwx 1 root root 8 Aug 10 19:04 home -> ../md127
> > lrwxrwxrwx 1 root root 8 Aug 10 19:04 root -> ../md126
>
>
> Good. Try removing the "ignoredisk", "clearpart",
On 08/10/2017 01:36 PM, D&R wrote:
/dev/md:
total 0
lrwxrwxrwx 1 root root 8 Aug 10 19:04 home -> ../md127
lrwxrwxrwx 1 root root 8 Aug 10 19:04 root -> ../md126
Good. Try removing the "ignoredisk", "clearpart", and "part" lines from
your kickstart file.
On Wed, 9 Aug 2017 14:27:07 -0700
Rick Stevens wrote:
> On 08/09/2017 12:08 PM, D&R wrote:
> > On Wed, 9 Aug 2017 12:00:00 -0700
> > Rick Stevens wrote:
> >
> >> On 08/09/2017 11:52 AM, D&R wrote:
> >>> When I boot into the install there is an error in the destination
> >>> section.
> >>>
>
On 08/09/2017 06:14 PM, Rick Stevens wrote:
You have to have at least two "part raid.somenumber" lines to create a
RAID1, and a "raid" line to define the type of RAID, filesystem type
and mountpoint.
I did. I used a kickstart that was as close to D&R's snippet as possible.
Have a look at:
On 08/09/2017 04:02 PM, Gordon Messmer wrote:
> On 08/09/2017 02:27 PM, Rick Stevens wrote:
>> Right below those "part" definitions, you see "raid" definitions where
>> those labels are normally used. In your case,
>>
>> raid / --device=root --fstype=ext4 --level=raid1 --useexisting
>>
>> tells
On 08/09/2017 02:27 PM, Rick Stevens wrote:
Right below those "part" definitions, you see "raid" definitions where
those labels are normally used. In your case,
raid / --device=root --fstype=ext4 --level=raid1 --useexisting
tells the system to use the first two devices in the "part" sec
On 08/09/2017 12:08 PM, D&R wrote:
> On Wed, 9 Aug 2017 12:00:00 -0700
> Rick Stevens wrote:
>
>> 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 abou
On 08/09/2017 11:52 AM, D&R wrote:
I looked at the debug info in the storage.log and there was an
error about sdb1 did not exist. But...
Switch to VT2 (where I assume you examined storage.log) and run "ls -l
/dev/sd* /dev/md" or "lsblk" to see what block devices *do* exist.
You want to make
On Wed, 9 Aug 2017 12:00:00 -0700
Rick Stevens wrote:
> 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...
> >
> > Whe
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 r
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 [
15 matches
Mail list logo