Public bug reported:
== Comment: #0 - Kenneth Null <kn...@us.ibm.com> - 2015-07-15 13:39:01 ==
---Problem Description---
I was not able to get logs due to the nature of this fail.
Problem: After successfully installing Ubuntu 14.04.2 on both LPARs using SAN
disks, we were able to log in as the user created (in this case
lte/don2rry) and create the root login. (root/don2rry)
At this point, we were able to exit from the lte login, and log back in as
root. The next step we took was to reboot the LPARs
using the 'reboot' command.
When the partitions restarted, we saw some errors posted during the IPL from
the File System. Now when we see the login prompt,
we enter root, press enter, and the LPAR clears the screen and comes right back
the UID prompt. We can't log in again. This happens every time, and only after
the LPAR is rebooted after install.
These are the errors we see on the login screen:
pole2lp1 login: [ 29.047665] blk_update_request: critical target error, dev
dm-4, sector 46160256
[ 29.047713] dm-6: WRITE SAME failed. Manually zeroing.
[ 58.248887] EXT4-fs error (device dm-6): ext4_mb_generate_buddy:757: group
0, block bitmap and bg descriptor inconsistent: 32768 vs 22668 free clusters
[ 58.248923] Aborting journal on device dm-6-8.
[ 58.251649] EXT4-fs (dm-6): Remounting filesystem read-only
[ 58.251663] EXT4-fs error (device dm-6): ext4_mb_generate_buddy:757: group
1, block bitmap and bg descriptor inconsistent: 32768 vs 20210 free clusters
[ 58.251703] EXT4-fs error (device dm-6): ext4_mb_generate_buddy:757: group
3, block bitmap and bg descriptor inconsistent: 32768 vs 9004 free clusters
[ 58.251725] EXT4-fs error (device dm-6): ext4_mb_generate_buddy:757: group
4, block bitmap and bg descriptor inconsistent: 32768 vs 6131 free clusters
[ 58.251809] EXT4-fs error (device dm-6): ext4_mb_generate_buddy:757: group
6, block bitmap and bg descriptor inconsistent: 32768 vs 15379 free clusters
[ 58.251831] EXT4-fs error (device dm-6): ext4_mb_generate_buddy:757: group
7, block bitmap and bg descriptor inconsistent: 32768 vs 21972 free clusters
[ 58.261066] EXT4-fs error (device dm-6): ext4_journal_check_start:56:
Detected aborted journal
At this point, press enter and the screen clears, and offers us the
login prompt again, but never gets to the password prompt.
I am going to attempt a reinstall on pole2lp1, and if successful again,
I will leave it there for someone to try to get some data. To recreate
this fail, after logging in as either the user that we create during
install, or as root after it is created, just reboot the LPAR.
I will provide the uname -a data if I am successful at reinstall.
Ken.
Contact Information = Kenneth Null/kn...@us.ibm.com, Mikhail
Afanasiev/afana...@us.ibm.com
---uname output---
I have uname -r output: uname -r 3.16.0-43-generic
Machine Type = 8247-22L
---System Hang---
The system boots the LPARs to runtime, but does not allow login.
We have tried changing SAN devices, as we suspected that maybe the old drives
may have been corrupted. These new drives were just allocated to us yesterday.
Storage (160G total of type 'pLinux') and host connection 'pole2lp1' created on
MSAN8
Alias existed and re-zoned to 'pole2_to_MSAN8', and enabled.
Old storage on XIVLS deleted.
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Restart the LPAR, or use the HMC to Shutdown/Restart.
Stack trace output:
no
Oops output:
no
System Dump Info:
The system is not configured to capture a system dump.
*Additional Instructions for Kenneth Null/kn...@us.ibm.com, Mikhail
Afanasiev/afana...@us.ibm.com:
-Post a private note with access information to the machine that the bug is
occuring on.
-Attach sysctl -a output output to the bug.
== Comment: #3 - MIKHAIL AFANASIEV <afana...@us.ibm.com> - 2015-07-16 13:20:04
==
I have left pole2lp2 at the recovery shell after this problem was encountered
(accessible through advanced options via the boot loader). Logs are accessible
here and networking is functional.
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: architecture-ppc64le bugnameltc-127704 severity-critical
targetmilestone-inin14043
** Tags added: architecture-ppc64le bugnameltc-127704 severity-critical
targetmilestone-inin14043
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475471
Title:
ISST-LTE: Ubuntu 14.04.2 does not allow user login after rebooting
LPAR after successful install.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1475471/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
