Arch Linux

romeluc

Member

Registered: 2014-12-03

Posts: 12

Boot errors on new install

Hello,

I am preparing to migrate to arch and I am installing it first on an external hard drive to make sure everything works.

My output for journalctl -b -p err is as follows:

[me@Qosmio ~]$ journalctl -b -p err 
-- Logs begin at Mon 2015-03-02 22:52:00 GST, end at Sat 2015-03-07 17:02:34 GST. --
Mar 07 14:23:56 Qosmio kernel: ACPI: Invalid _PSD:coord_type
Mar 07 14:23:56 Qosmio kernel: ACPI: Invalid _PSD:coord_type
Mar 07 14:23:56 Qosmio kernel: ACPI: Invalid _PSD:coord_type
Mar 07 14:23:56 Qosmio kernel: ACPI: Invalid _PSD:coord_type
Mar 07 14:24:00 Qosmio kernel: sdb2: WRITE SAME failed. Manually zeroing.
Mar 07 14:24:48 Qosmio pulseaudio[521]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed 
Mar 07 15:53:51 Qosmio kcheckpass[1184]: pam_tally(kde:auth): Error opening /var/log/faillog for update
Mar 07 15:53:51 Qosmio kcheckpass[1184]: pam_tally(kde:auth): Error opening /var/log/faillog for read
Mar 07 15:53:51 Qosmio kcheckpass[1184]: pam_tally(kde:setcred): Error opening /var/log/faillog for update
Mar 07 15:53:51 Qosmio kcheckpass[1184]: pam_tally(kde:setcred): Error opening /var/log/faillog for update
Mar 07 16:26:54 Qosmio sudo[1585]: me : a password is required ; TTY=pts/2 ; PWD=/home/me ; USER=root ; COMMAND=list /usr/bin/pacman --color auto -Sy
Mar 07 16:26:58 Qosmio sudo[1587]: pam_unix(sudo:auth): conversation failed
Mar 07 16:26:58 Qosmio sudo[1587]: pam_unix(sudo:auth): auth could not identify password for [me]
Mar 07 16:27:04 Qosmio sudo[1617]: me : a password is required ; TTY=pts/2 ; PWD=/home/me ; USER=root ; COMMAND=list /usr/bin/pacman --color auto -Sy
Mar 07 16:33:02 Qosmio sudo[1823]: me : a password is required ; TTY=pts/2 ; PWD=/home/me ; USER=root ; COMMAND=list /usr/bin/pacman --color auto -S extra/audacity
lines 1-16/16 (END)

I would appreciate any information about how to troubleshoot this. sdb2 is the partition where arch is installed. I have kde plasma 5 with sddm login manager configured for auto login. I installed gnome also but disabled it's login service.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,662

Re: Boot errors on new install

Please post the output of  mount

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

romeluc

Member

Registered: 2014-12-03

Posts: 12

Re: Boot errors on new install

Here is the output of mount:

[me@Qosmio ~]$ mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=4014144k,nr_inodes=1003536,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sdb2 on / type ext4 (rw,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=31,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
configfs on /sys/kernel/config type configfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sdb1 on /run/media/me/BACKUP type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=803380k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

Also, this time when I booted arch, some of the errors went away. The new journalctl output is now:

[me@Qosmio ~]$ journalctl -b -p err 
-- Logs begin at Mon 2015-03-02 22:52:00 GST, end at Sat 2015-03-07 20:24:13 GST. --
Mar 07 20:17:44 Qosmio kernel: ACPI: Invalid _PSD:coord_type
Mar 07 20:17:44 Qosmio kernel: ACPI: Invalid _PSD:coord_type
Mar 07 20:17:44 Qosmio kernel: ACPI: Invalid _PSD:coord_type
Mar 07 20:17:44 Qosmio kernel: ACPI: Invalid _PSD:coord_type
Mar 07 20:18:17 Qosmio kernel: sdb2: WRITE SAME failed. Manually zeroing.
Mar 07 20:18:39 Qosmio pulseaudio[523]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed 
lines 1-7/7 (END)

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,662

Re: Boot errors on new install

I take it that the primary concern is the WRITE SAME issue.  Try turning off WRITE SAME as discussed here
It looks like your hardware does not support a bulk erase mode where you re-write the same block automatically.

Further discussion here

How old is your kernel?  Try a system upgrade and see if the issue goes away.  In any event, it is not really a problem.
I cannot help with the ACPI errors, but they don't look serious.  The pulseaudio error has to do with bluetooth.  Did you install the bluetooth stuff?  Do you need bluetooth audio?

Again, a full system update might help.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

romeluc

Member

Registered: 2014-12-03

Posts: 12

Re: Boot errors on new install

Thank you for your suggestions.

Regarding the WRITE SAME error, the link asks to to add a file in /etc/tmpfiles.d/ and modify the code given:

 w       /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:1:0/0:1:0:0/scsi_disk/0:1:0:0/max_write_same_blocks     -       -       -       -   

I am not quiet sure how to modify this as I don't have a target0:1:0 file. I am also curious whether using udev rules is a proper solution to this problem. I am not very knowledgeable about this topic.

For the pulseaudio error, I now installed bluez and the error went away. Also, I upgraded my system.

sudo pacman -S bluez bluez-utils
sudo modprobe btusb
sudo systemctl start bluetooth.service
sudo systemctl enable bluetooth.service
sudo usermod -a -G lp me

However, I'm getting new errors now:

[me@Qosmio ~]$ journalctl -b -p err
-- Logs begin at Mon 2015-03-02 22:52:00 GST, end at Sun 2015-03-08 21:49:55 GST. --
Mar 08 21:42:55 Qosmio kernel: ACPI: Invalid _PSD:coord_type
Mar 08 21:42:56 Qosmio kernel: ACPI: Invalid _PSD:coord_type
Mar 08 21:42:56 Qosmio kernel: ACPI: Invalid _PSD:coord_type
Mar 08 21:42:56 Qosmio kernel: ACPI: Invalid _PSD:coord_type
Mar 08 21:42:59 Qosmio kernel: sdb2: WRITE SAME failed. Manually zeroing.
Mar 08 21:43:03 Qosmio bluetoothd[298]: Sap driver initialization failed.
Mar 08 21:43:03 Qosmio bluetoothd[298]: sap-server: Operation not permitted (1)
Mar 08 21:43:54 Qosmio kernel: sound hdaudioC1D3: hda-codec: out of range cmd 3:5:707:ffffffff

[me@Qosmio ~]$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2015-03-08 21:43:03 GST; 8min ago
     Docs: man:bluetoothd(8)
 Main PID: 298 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─298 /usr/lib/bluetooth/bluetoothd

Mar 08 21:43:03 Qosmio bluetoothd[298]: Bluetooth daemon 5.28
Mar 08 21:43:03 Qosmio bluetoothd[298]: Starting SDP server
Mar 08 21:43:03 Qosmio bluetoothd[298]: Bluetooth management interface 1.7 initialized
Mar 08 21:43:03 Qosmio bluetoothd[298]: Sap driver initialization failed.
Mar 08 21:43:03 Qosmio bluetoothd[298]: sap-server: Operation not permitted (1)
Mar 08 21:43:56 Qosmio bluetoothd[298]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSource
Mar 08 21:43:56 Qosmio bluetoothd[298]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSink

I saw a thread that says installing bluez4 from AUR solves the problem, but aside from the error, my bluetooth seems to work fine. Also, my audio works fine despite the other error.

Are these errors not important?

romeluc

Member

Registered: 2014-12-03

Posts: 12

Re: Boot errors on new install

Hello, it's me again.

I had two crashes so far, after arch has booted, and the log files show some of the same errors I posted before.

[me@Qosmio ~]$ sudo journalctl -x -p err
.
.
.
Mar 14 16:23:27 Qosmio kernel: sd 7:0:0:0: [sdc] Assuming drive cache: write through
Mar 14 19:50:06 Qosmio kcheckpass[1798]: pam_tally(kde:auth): Error opening /var/log/faillog for update
Mar 14 19:50:06 Qosmio kcheckpass[1798]: pam_tally(kde:auth): Error opening /var/log/faillog for read
Mar 14 19:50:06 Qosmio kcheckpass[1798]: pam_tally(kde:setcred): Error opening /var/log/faillog for update
Mar 14 19:50:06 Qosmio kcheckpass[1798]: pam_tally(kde:setcred): Error opening /var/log/faillog for update
Mar 14 21:02:41 Qosmio kcheckpass[3575]: pam_tally(kde:auth): Error opening /var/log/faillog for update
Mar 14 21:02:41 Qosmio kcheckpass[3575]: pam_tally(kde:auth): Error opening /var/log/faillog for read
Mar 14 21:02:41 Qosmio kcheckpass[3575]: pam_tally(kde:setcred): Error opening /var/log/faillog for update
Mar 14 21:02:41 Qosmio kcheckpass[3575]: pam_tally(kde:setcred): Error opening /var/log/faillog for update
-- Reboot --

In both cases, I had a VMware virtual machine running when the arch desktop stopped responding. Opening another tty with ctr+alt+f2 shows a black screen with only:

starting version 218

Last edited by romeluc (2015-03-14 18:01:03)