This generally happens when you miss the dasd_configure step which adds it into
/etc/udev/rules.d/
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Michael
Weiner
Sent: Wednesday, November 16, 2016 3:55 PM
To: LINUX-390@VM.MARIST.EDU
Subject:
Hi group!
I have created an LVM on root root and about a month ago I expanded / resized
it using yast.
I formatted the DASD
CreAted the partition
Added the volume to vgroot
Expanded the LVM and finished.
Today I went to bring up the machine and it was complaining about lvroot that
it was
Thank you Mark.
I am able to get to the site via a web browser at which point I am
prompted for credentials. I'll follow up with support to see if it is
account related. Good to know you are able to access the service.
Thanks,
Duane
Duane Beyer
Marist College
(845) 575-3216 - Office
(845)
>>> On 11/16/2016 at 12:09 PM, Duane Beyer wrote:
> Mark,
>
> The formatting may get a little messy, here is the results of the zypper
> lr -u.
-snip-
Those look like what I expected, so I checked my /etc/zypp/services.d/ files,
and in there I see the
We point most of our stuff at SMT or SUSE Manager, but I have seen this.
We opened a ticket once and SUSE said they had an outage - please try again.
Perhaps that is what happened?
(although I just tried it and all is well from here).
Also check that you've not had a firewall or proxy server
Mark,
The formatting may get a little messy, here is the results of the zypper
lr -u.
zypper lr -u
# | Alias | Name |
Enabled | GPG Check | Refresh | URI
>>> On 11/16/2016 at 10:24 AM, Duane Beyer wrote:
> Is anyone else having a problem applying service to SLES 12 SP1.
>
> We started getting the following error on all of our SLES 12 SP1 systems
> when trying to apply service. Same error with zypper and Yast. Just
>
Is anyone else having a problem applying service to SLES 12 SP1.
We started getting the following error on all of our SLES 12 SP1 systems
when trying to apply service. Same error with zypper and Yast. Just
want to verify it is a SLES issue and not our issue. The systems are
registered with