From: <wangmin@phytium.com.cn>
To: "'OpenBMC Maillist'" <openbmc@lists.ozlabs.org>
Cc: '刘勇鹏' <liuyongpeng@phytium.com.cn>, shuyiqi@phytium.com.cn
Subject: [OpenBMC]: root is rejected to login an aarch64 openBmc system
Date: Tue, 23 Mar 2021 17:13:14 +0800 [thread overview]
Message-ID: <!&!AAAAAAAAAAAuAAAAAAAAAO4CP8j4rjtAsuu29GjYeJQBAMO2jhD3dRHOtM0AqgC7tuYAAAAAAA4AABAAAADosvXoMjmFTaNtUZ21y/cCAQAAAAA=@phytium.com.cn> (raw)
[-- Attachment #1: Type: text/plain, Size: 10982 bytes --]
Hi all,
At present, an aarch64 root file system was build and run on an aarch64 soc. However, root is rejected to login. It is skeptical that there are some wrong configurations in the file “/etc/fstab”. Anyone have ideas on the issue, please give your comments. Thanks in advance.
The following text snippets are the contents of the file “/etc/fstab”.
# stock fstab - you probably want to override this with a machine specific one
/dev/root / auto defaults 1 1
proc /proc proc defaults 0 0
devpts /dev/pts devpts mode=0620,ptmxmode=0666,gid=5 0 0
tmpfs /run tmpfs mode=0755,nodev,nosuid,strictatime 0 0
tmpfs /var/volatile tmpfs defaults 0 0
# uncomment this if your device has a SD/MMC/Transflash slot
#/dev/mmcblk0p1 /media/card auto defaults,sync,noauto 0 0
Sincerely,
wangmin
The startup log is shown the below text lines.
[ 1.949186][ 3] done.
[ 2.044027][ 3] VFS: Mounted root (squashfs filesystem) readonly on device 1:0.
[ 2.051540][ 3] devtmpfs: mounted
[ 2.055297][ 3] Freeing unused kernel memory: 1344K
[ 2.060279][ 3] Run /sbin/init as init process
[ 2.126531][ 3] systemd[1]: systemd 244.3+ running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPAR)
[ 2.148585][ 3] systemd[1]: Detected architecture arm64.
Welcome to Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 0.1.0!
[ 2.170085][ 3] systemd[1]: Set hostname to <phytium>.
[ 2.177862][ 3] random: systemd: uninitialized urandom read (16 bytes read)
[ 2.184835][ 3] systemd[1]: Initializing machine ID from random generator.
[ 2.191748][ 3] systemd[1]: Installed transient /etc/machine-id file.
[ 2.250899][ 3] random: systemd: uninitialized urandom read (16 bytes read)
[ 2.257923][ 3] systemd[1]: system-getty.slice: unit configures an IP firewall, but the local system.
[ 2.270618][ 3] systemd[1]: (This warning is only shown for the first unit using IP firewalling.)
[ 2.280218][ 3] systemd[1]: Created slice system-getty.slice.
[ OK ] Created slice system-getty.slice.
[ 2.302077][ 3] random: systemd: uninitialized urandom read (16 bytes read)
[ 2.309286][ 3] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ OK ] Created slice system-serial\x2dgetty.slice.
[ 2.330128][ 3] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ OK ] Started Dispatch Password âÀ¦ts to Console Directory Watch.
[ 2.354103][ 3] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ OK ] Started Forward Password R uests to Wall Directory Watch.
[ 2.378081][ 3] systemd[1]: Reached target Paths.
[ OK ] Reached target Paths.
[ 2.394068][ 3] systemd[1]: Reached target Remote File Systems.
[ OK ] Reached target Remote File Systems.
[ 2.414068][ 3] systemd[1]: Reached target Slices.
[ OK ] Reached target Slices.
[ 2.430071][ 3] systemd[1]: Reached target Swap.
[ OK ] Reached target Swap.
[ 2.446293][ 3] systemd[1]: Listening on Syslog Socket.
[ OK ] Listening on Syslog Socket.
[ 2.467220][ 3] systemd[1]: Listening on Process Core Dump Socket.
[ OK ] Listening on Process Core Dump Socket.
[ 2.486120][ 3] systemd[1]: Listening on initctl Compatibility Named Pipe.
[ OK ] Listening on initctl[ 2.494822][ 0] usb 2-2: new SuperSpeed Gen 1 USB device number 2 usingd
Compatibility Named Pipe.
[ 2.514215][ 3] systemd[1]: Listening on Journal Audit Socket.
[ OK ] Listening on Journal Audit Socket.
[ 2.532382][ 0] usb-storage 2-2:1.0: USB Mass Storage device detected
[ 2.538920][ 0] scsi host4: usb-storage 2-2:1.0
[ 2.546153][ 3] systemd[1]: Listening on Journal Socket (/dev/log).
[ OK ] Listening on Journal Socket (/dev/log).
[ 2.566158][ 3] systemd[1]: Listening on Journal Socket.
[ OK ] Listening on Journal Socket.
[ 2.590185][ 3] systemd[1]: Listening on Network Service Netlink Socket.
[ OK ] Listening on Network Service Netlink Socket.
[ 2.610172][ 3] systemd[1]: Listening on udev Control Socket.
[ OK ] Listening on udev Control Socket.
[ 2.630125][ 3] systemd[1]: Listening on udev Kernel Socket.
[ OK ] Listening on udev Kernel Socket.
[ 2.651160][ 3] systemd[1]: Mounting Huge Pages File System...
Mounting Huge Pages File System...
[ 2.671120][ 3] systemd[1]: Mounting POSIX Message Queue File System...
Mounting POSIX Message Queue File System...
[ 2.691112][ 1] systemd[1]: Mounting Kernel Debug File System...
Mounting Kernel Debug File System...
[ 2.714920][ 1] systemd[1]: Mounting Temporary Directory (/tmp)...
Mounting Temporary Directory (/tmp)...
[ 2.738097][ 1] systemd[1]: Condition check resulted in Create list of static device nodes for the c.
[ 2.750575][ 1] systemd[1]: Starting File System Check on Root Device...
Starting File System Check on Root Device...
[ 2.771480][ 2] systemd[1]: Starting Journal Service...
Starting Journa[ 2.777184][ 2] systemd[1]: Condition check resulted in Load Kernel Modules .
l Service...
[ 2.788090][ 2] systemd[1]: Condition check resulted in FUSE Control File System being skipped.
[ 2.799386][ 2] systemd[1]: Mounting Kernel Configuration File System...
Mounting Kernel Configuration File System...
[ 2.823495][ 2] systemd[1]: Starting Apply Kernel Variables...
Starting Apply Kernel Variables...
[ 2.843199][ 2] systemd[1]: Starting udev Coldplug all Devices...
Starting udev Coldplug all Devices...
[ 2.866823][ 2] systemd[1]: Started Journal Service.
[ OK ] Started Journal Service.
[FAILED] Failed to mount Huge Pages File System.
See 'systemctl status dev-hugepages.mount' for details.
[FAILED] Failed to mount POSIX Message Queue File System.
See 'systemctl status dev-mqueue.mount' for details.
[FAILED] Failed to mount Kernel Debug File System.
See 'systemctl status sys-kernel-debug.mount' for details.
[FAILED] Failed to mount Temporary Directory (/tmp).
See 'systemctl status tmp.mount' for details.
[DEPEND] Dependency failed for Network Name Resolution.
[DEPEND] Dependency failed for D-Bus System Message Bus.
[DEPEND] Dependency failed for Network Time Synchronization.
[ OK ] Started File System Check on Root Device.
[FAILED] Failed to mount Kernel Configuration File System.
See 'systemctl status sys-kernel-config.mount' for details.
[ OK ] Started Apply Kernel Variables.
[ OK ] Reached target Host and Network Name Lookups.
[ OK ] Reached target System Time Set.
[ OK ] Reached target System Time Synchronized.
Starting Remount Root and Kernel File Systems...
[ OK ] Started udev Coldplug all Devices.
[FAILED] Failed to start Remount Root and Kernel File Systems.
See 'systemctl status systemd-remount-fs.service' for details.
Starting Flush Journal to Persistent Storage...
[ 3.227668][ 3] systemd-journald[1452]: Received client request to flush runtime journal.
Starting Create Static Device Nodes in /dev...
[ OK ] Started Flush Journal to Persistent Storage.
[ OK ] Started Create Static Device Nodes in /dev.
[ OK ] Reached target Local File Systems (Pre).
Mounting /var/volatile...
Starting udev Kernel Device Manager...
[FAILED] Failed to mount /var/volatile.
See 'systemctl status var-volatile.mount' for details.
[DEPEND] Dependency failed for Bind mount volatile /var/cache.
[DEPEND] Dependency failed for Local File Systems.
[DEPEND] Dependency failed for Bind mount volatile /srv.
[DEPEND] Dependency failed for Bind mount volatile /var/lib.
[DEPEND] Dependency failed for Bind mount volatile /var/spool.
[ OK ] Started udev Kernel Device Manager.
[ 3.460610][ 0] random: fast init done
[ OK ] Stopped Dispatch Password  ts to Console Directory Watch.
[ OK ] Stopped Forward Password R uests to Wall Directory Watch.
[ OK ] Reached target Timers.
[ 3.548046][ 0] scsi 4:0:0:0: Direct-Access USB SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6
[ 3.556938][ 0] sd 4:0:0:0: [sdb] 240353280 512-byte logical blocks: (123 GB/115 GiB)
[ 3.565978][ 1] sd 4:0:0:0: [sdb] Write Protect is off
[ OK ] Closed 3.572198][ 0] sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn'tA
39mSyslog Socket.
[ OK ] Reached targe[ 3.595391][ 1] sdb: sdb1
t Login Prompts.
[ 3.603064][ 1] sd 4:0:0:0: [sdb] Attached SCSI removable disk
Starting Network Service...
Starting Load/Save Random Seed...
[ OK ] Reached target Sockets.
Mounting Kernel Configuration File System...
[ OK ] Started Emergency Shell.
[ OK ] Reached target Emergency Mode.
Starting Create Volatile Files and Directories...
[ OK ] Started Network Service.
[ OK ] Started Load/Save Random Seed.
[FAILED] Failed to mount Kernel Configuration File System.
See 'systemctl status sys-kernel-config.mount' for details.
[ OK ] Started Create Volatile Files and Directories.
[ OK ] Reached target Network.
Starting Run pending postinsts...
[FAILED] Failed to start Run pending postinsts.
See 'systemctl status run-postinsts.service' for details.
You are in emergency mode. After logging in, type "journalctl -xb" to view
systeGive root password for maintenance
(or press Control-D to continue):
Login incorrect
Give root password for maintenance
(or press Control-D to continue):
Login incorrect
Give root password for maintenance
(or press Control-D to continue):
Login incorrect
Give root password for maintenance
(or press Control-D to continue):
Login incorrect
Give root password for maintenance
(or press Control-D to continue):
Reloading system manager configuration
Starting default target
You are in emergency mode. After Give root password for maintenance
(or press Control-D to continue):
Login incorrect
Give root password for maintenance
(or press Control-D to continue):
Login incorrect
Give root password for maintenance
(or press Control-D to continue):
Reloading system manager configuration
Starting default target
You are in emergency mode. After Give root password for maintenance
(or press Control-D to continue):
[-- Attachment #2: Type: text/html, Size: 24539 bytes --]
next reply other threads:[~2021-03-23 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 9:13 wangmin [this message]
2021-03-23 9:52 [OpenBMC]: root is rejected to login an aarch64 openBmc system wangmin
2021-03-23 15:14 ` Joseph Reynolds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=''\!'&'\!'AAAAAAAAAAAuAAAAAAAAAO4CP8j4rjtAsuu29GjYeJQBAMO2jhD3dRHOtM0AqgC7tuYAAAAAAA4AABAAAADosvXoMjmFTaNtUZ21y/cCAQAAAAA=@phytium.com.cn' \
--to=wangmin@phytium.com.cn \
--cc=liuyongpeng@phytium.com.cn \
--cc=openbmc@lists.ozlabs.org \
--cc=shuyiqi@phytium.com.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).