On Mar 18, 2014, at 12:53 PM, pgaltieri . <pgalti...@gmail.com> wrote: > Please unplug everything from this laptop, except power. You need to get the > basic setup working reliably first. No external hard drives. No mouse. > Nothing, except power.
You haven't done this like I asked. [ 0.860472] scsi 0:0:0:0: Direct-Access ATA WDC WD10JPVX-75J 01.0 PQ: 0 ANSI: 5 [ 0.861762] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 2.901151] scsi 5:0:0:0: Direct-Access SanDisk Cruzer 2.01 PQ: 0 ANSI: 6 [ 2.909355] sd 5:0:0:0: [sdb] 31266816 512-byte logical blocks: (16.0 GB/14.9 GiB) [ 3.012954] scsi 6:0:0:0: Direct-Access Seagate Backup+ BL 0409 PQ: 0 ANSI: 6 [ 3.014683] sd 6:0:0:0: [sdc] 1953525167 512-byte logical blocks: (1.00 TB/931 GiB) [ 703.081242] systemd[1]: Timed out waiting for device ST1000LM024_HN-M101MBB. Your logs indicate problems with sdc. That needs to be disconnected, and comment out its fstab entry if there is one. And ideally don't have the SanDisk connecting during boot or reboot/poweroff, only on-demand when you need to save out a log file. Thanks. > > I tried the poweroff and it worked. I rebooted tried it again and it worked. > I rebooted again and tried the So I think you either have a race condition that is mitigated by one or more of the debug boot parameters; or maybe more likely you've got an selinux issue that's alleviated by enforcing=0. For now, keep enforcing=0 as a boot parameter. > > and this time the system did not power off, it reset and now I'm back in > rescue mode. Here's the link to the shutdown-log.txt file for this event. > > https://www.amazon.com/clouddrive/share?s=4LDATpk0T3IoK1jb-pKshY Yeah you forgot to include enforcing=0 in this boot, so I think you might have an SELinux issue, possibly the result of the interrupted labeling. *sigh* LOTS of problems with sdc that even the kernel doesn't like. Remove this device and troubleshoot that separately. [ 634.006871] EXT4-fs error (device sdc1): ext4_find_entry:1309: inode #2: comm sagan: reading directory lblock 0 [ 754.896528] EXT4-fs error (device sdc1): __ext4_get_inode_loc:3909: inode #2: block 1057: comm broctl: unable to read itable block [ 760.478899] quiet_error: 24 callbacks suppressed [ 760.478905] Buffer I/O error on device sdc1, logical block 121667584 [ 760.478907] lost page write due to I/O error on sdc1 [ 760.478910] JBD2: Error -5 detected when updating journal superblock for sdc1-8. [ 760.478937] Aborting journal on device sdc1-8. [ 760.478940] Buffer I/O error on device sdc1, logical block 121667584 [ 760.478941] lost page write due to I/O error on sdc1 [ 760.478943] JBD2: Error -5 detected when updating journal superblock for sdc1-8. [ 1053.600851] EXT4-fs error (device sdc1): ext4_journal_check_start:56: Detected aborted journal [ 1053.600858] EXT4-fs (sdc1): Remounting filesystem read-only [ 1365.490135] EXT4-fs error (device sdc1): ext4_put_super:791: Couldn't clean up the journal [ 1365.491999] ------------[ cut here ]------------ [ 1365.492897] WARNING: CPU: 2 PID: 3751 at fs/sysfs/group.c:214 sysfs_remove_group+0xc6/0xd0() [ 1365.493824] sysfs group ffffffff81cb05c0 not found for kobject 'target6:0:0' [ 1365.494823] Modules linked in: vfat fat usb_storage i915 i2c_algo_bit drm_kms_helper drm i2c_core video [ 1365.495802] CPU: 2 PID: 3751 Comm: umount Not tainted 3.13.5-103.fc19.x86_64 #1 [ 1365.496750] Hardware name: Dell Inc. Inspiron 7537/0F5R3Y, BIOS A05 10/31/2013 [ 1365.497700] 0000000000000009 ffff8802089b9b70 ffffffff81680604 ffff8802089b9bb8 [ 1365.498649] ffff8802089b9ba8 ffffffff8106d35d 0000000000000000 ffffffff81cb05c0 [ 1365.499599] ffff8800afd47c38 ffff8802315ce188 ffff8800afc7f100 ffff8802089b9c08 [ 1365.500546] Call Trace: [ 1365.501510] [<ffffffff81680604>] dump_stack+0x45/0x56 [ 1365.502432] [<ffffffff8106d35d>] warn_slowpath_common+0x7d/0xa0 [ 1365.503352] [<ffffffff8106d3cc>] warn_slowpath_fmt+0x4c/0x50 [ 1365.504236] [<ffffffff8123004e>] ? sysfs_get_dirent_ns+0x4e/0x70 [ 1365.505101] [<ffffffff81231316>] sysfs_remove_group+0xc6/0xd0 [ 1365.505920] [<ffffffff8141cb63>] dpm_sysfs_remove+0x43/0x50 [ 1365.506730] [<ffffffff814128b5>] device_del+0x45/0x1c0 [ 1365.507549] [<ffffffff8143cb77>] scsi_target_reap_usercontext+0x27/0x40 [ 1365.508349] [<ffffffff81086147>] execute_in_process_context+0x67/0x70 [ 1365.509177] [<ffffffff8143dff4>] scsi_target_reap+0xc4/0xf0 [ 1365.509991] [<ffffffff8143ffc6>] scsi_device_dev_release_usercontext+0xe6/0x120 [ 1365.510783] [<ffffffff81086147>] execute_in_process_context+0x67/0x70 [ 1365.511592] [<ffffffff8143fedc>] scsi_device_dev_release+0x1c/0x20 [ 1365.512458] [<ffffffff81411f02>] device_release+0x32/0xa0 [ 1365.513320] [<ffffffff813156b7>] kobject_cleanup+0x77/0x1b0 [ 1365.514154] [<ffffffff81315570>] kobject_put+0x30/0x60 [ 1365.515035] [<ffffffff814121f7>] put_device+0x17/0x20 [ 1365.515865] [<ffffffff814326db>] scsi_device_put+0x3b/0x50 [ 1365.516711] [<ffffffff81444b70>] scsi_disk_put+0x30/0x50 [ 1365.517610] [<ffffffff81444ea2>] sd_release+0x42/0xd0 [ 1365.518495] [<ffffffff811f09fc>] __blkdev_put+0x16c/0x1a0 [ 1365.519384] [<ffffffff811f099e>] __blkdev_put+0x10e/0x1a0 [ 1365.520245] [<ffffffff811f133c>] blkdev_put+0x4c/0x120 [ 1365.521118] [<ffffffff811ba474>] kill_block_super+0x44/0x70 [ 1365.521962] [<ffffffff811ba73d>] deactivate_locked_super+0x3d/0x60 [ 1365.522814] [<ffffffff811bace6>] deactivate_super+0x46/0x60 [ 1365.523686] [<ffffffff811d69fc>] mntput_no_expire+0xac/0x140 [ 1365.524568] [<ffffffff811d7e6e>] SyS_umount+0x8e/0x100 [ 1365.525458] [<ffffffff8168f5e9>] system_call_fastpath+0x16/0x1b [ 1365.526316] ---[ end trace 16e36edf7920cc51 ]--- This might be relevant, I'm not sure yet. It may be due to the failed relabel. [ 1657.518736] systemd[1]: Failed to load configuration for poweroff.service: No such file or directory [ 1657.534026] systemd[1]: SELinux access check scon=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcon=system_u:object_r:power_unit_file_t:s0 tclass=service perm=start path=/usr/lib/systemd/system/poweroff.target cmdline=poweroff: 0 What do you get for: ausearch -m AVC OK and this looks to me like the poweroff did get communicated by systemd to the kernel, so I don't know why it reset/rebooted this time instead of powering down. [ 1660.559953] systemd[4182]: Executing: /usr/bin/systemctl --force poweroff [ 1660.559958] systemd[1]: systemd-update-utmp-shutdown.service: cgroup is empty [ 1660.559985] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local [ 1660.561009] systemd[1]: Accepted connection on private bus. [ 1660.561140] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.PowerOff() on /org/freedesktop/systemd1 [ 1660.561287] systemd[1]: SELinux access check scon=system_u:system_r:init_t:s0 tcon=system_u:system_r:init_t:s0 tclass=system perm=halt path=(null) cmdline=(null): 0 [ 1660.561302] systemd[1]: Shutting down. [ 1660.718362] systemd-journald[680]: Received SIGTERM [ 1661.711545] EXT4-fs (dm-1): re-mounted. Opts: (null) [ 1661.743821] EXT4-fs (dm-1): re-mounted. Opts: (null) [ 1661.744809] EXT4-fs (dm-1): re-mounted. Opts: (null) [ 1661.981516] EXT4-fs (dm-1): re-mounted. Opts: (null) And last check these: [ 7.752011] systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway. [ 10.940037] systemd[1]: media-NEWDATA2.mount: Directory /media/NEWDATA2 to mount over is not empty, mounting anyway. In order: 1. Remove the Seagate and the USB Flash drive. 2. /etc/fstab changes: comment out entries for any disconnected devices like the Seagate. Also comment out the /boot/efi line. You don't need /boot/efi mounted right now anyway, and we're not having any luck with all these other problems in figuring out why it won't mount unless you manually insmod fat and vfat. 3. edit grub.cfg, first kernel entry boot parameter is currently: vmlinuz-3.13.5-103.fc19.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap rd.md=0 rd.dm=0 vconsole.keymap=us rd.luks=0 vconsole.font=latarcyrheb-sun16 rd.lvm.lv=fedora/root systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M Change it to this: vmlinuz-3.13.5-103.fc19.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap rd.md=0 rd.dm=0 vconsole.keymap=us rd.luks=0 vconsole.font=latarcyrheb-sun16 rd.lvm.lv=fedora/root systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 1 4. reboot 5. Report the result for these ausearch -m AVC rpm -q selinux-policy 6. Run this, just report if it completes (you get a prompt) or if you get a system reset/reboot in the middle of it. restorecon -Rv / 7. reboot 8. poweroff Does that work? If it does, edit grub.cfg and remove the 1 at the end. See if you can power off from within Mate, consistently. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
