Ditto. I am doing a fresh install of 20.04 from a USB drive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641078
Title:
System cannot be booted up when root filesystem is on an LVM on two
disks
I have this same issue on Ubuntu Focal today fresh install from
netinstall. On upgraded host from 18.04 to 20.04 i havent this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641078
Title:
Sys
Edit, i havent upgrade jet ubuntu 18.04 to 20.04, so i dont know if this
work on upgraded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641078
Title:
System cannot be booted up when root filesyste
--- Comment From heinz-werner_se...@de.ibm.com 2017-10-20 07:42 EDT---
An enhancement wihtin this area might be addresssed by a future announcement
--- Comment From heinz-werner_se...@de.ibm.com 2017-10-20 07:42 EDT---
IBM bugzilla status _> closed, might by fixed by future enhance
This issues was rejected by Canonical, and closed as invalid on
2017-01-18.
This bug is incorrectly filed against src:linux, I will move it to
src:s390-tools shortly.
Further discussion is about upstream features. Canonical does not
participate in s390-tools upstream development.
It is absolutel
Installed lpar onto 154d dasd drive, using LVM automatic partitioning recipe.
After installation and reipl, I did the following:
$ sudo chzdev -e 254d
ECKD DASD 0.0.254d configured
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.4.0-60-generic
W: mdadm: /etc/mdadm/mdadm
** Changed in: ubuntu-z-systems
Status: New => Triaged
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
On 11 November 2016 at 13:29, bugproxy wrote:
> --- Comment From ma...@de.ibm.com 2016-11-11 08:24 EDT---
> (In reply to comment #2)
>> (In reply to comment #1)
> I don't know how much automatic dependency tracking Ubuntu does for the user,
> especially regarding additional z-specific dev
** Tags added: bugnameltc-148452 severity-critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641078
Title:
System cannot be booted up when root filesystem is on an LVM on two
disks
To manage
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Tags added: s390x
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
--- Comment From ma...@de.ibm.com 2016-11-11 08:24 EDT---
(In reply to comment #2)
> (In reply to comment #1)
> The installation was on a FCP SCSI SAN volumes each with two active paths.
> Multipath was involved. The system IPLed fine up to the point that we
> expanded the /root filesystem
11 matches
Mail list logo
