Finally, I hope, a few useful clues. Rescue mode gave me enough information to make a
lucky guess as to how to mount "/home" from within the dracut shell. With that,
I could try the boot again (which of course failed and dropped me into the dracut shell),
and then mount "/home", and then copy logs to a good place within
"/home". I further did a "cat -n [file].txt > [file]_catn.txt" on
each log file to make navigation and discussion easier. I then booted into the windows
box, and used some tool that lets me look at some of the Fedora directories, including
"/home". Using that, I got the files into a windows folder. I have the
following files:
* "dmesg" output;
* dnf.log;
* dnf.rpm.log;
* "fdisk -l" output (from rescue mode);
* "journalctl" output;
* "journalctl -x" output;
* "mount" output; and
* rdsosreport.txt.
I also, from grub, copied (the old fashioned way - paper and pencil) the script that is
running when I try to boot. I then typed that script into a text file within rescue mode.
So if someone wants to see any of these, please sent me the e-mail address, and I'll
send the full file. They're too long to put here.
From the rdsosreport.txt, I've extracted 2 sets of lines that look to me to be likely
causes. Here is the first (with line numbers):
-----
862 [ 1.218683] coyote kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
863 [ 1.218927] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure,
AE_NOT_FOUND (20160930/psargs-359)
864 [ 1.219196] coyote kernel: ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff92ef8e0db488), AE_NOT_FOUND (20160930/psparse-543)
865 [ 1.219856] coyote kernel: ata2.00: ATA-8: ST2000DM001-1CH164, CC24, max
UDMA/133
866 [ 1.220017] coyote kernel: ata2.00: 3907029168 sectors, multi 16: LBA48 NCQ
(depth 31/32), AA
867 [ 1.220812] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure,
AE_NOT_FOUND (20160930/psargs-359)
868 [ 1.221100] coyote kernel: ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff92ef8e0db488), AE_NOT_FOUND (20160930/psparse-543)
869 [ 1.221620] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure,
AE_NOT_FOUND (20160930/psargs-359)
870 [ 1.221909] coyote kernel: ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff92ef8e0dbac8), AE_NOT_FOUND (20160930/psparse-543)
871 [ 1.222200] coyote kernel: ata6.00: ATAPI: HL-DT-ST BD-RE BH14NS40, 1.00, max
UDMA/100
872 [ 1.222374] coyote kernel: ata2.00: configured for UDMA/133
873 [ 1.222582] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure,
AE_NOT_FOUND (20160930/psargs-359)
874 [ 1.222908] coyote kernel: ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff92ef8e0db348), AE_NOT_FOUND (20160930/psparse-543)
875 [ 1.222919] coyote kernel: scsi 1:0:0:0: Direct-Access ATA
ST2000DM001-1CH1 CC24 PQ: 0 ANSI: 5
876 [ 1.223466] coyote kernel: ata4.00: ATAPI: PIONEER BD-RW BDR-208M, 1.10, max
UDMA/100
877 [ 1.226360] coyote kernel: ata7: SATA link down (SStatus 0 SControl 300)
878 [ 1.226407] coyote kernel: ata9: SATA link down (SStatus 0 SControl 300)
879 [ 1.226501] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure,
AE_NOT_FOUND (20160930/psargs-359)
880 [ 1.226507] coyote kernel: ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff92ef8e0dbac8), AE_NOT_FOUND (20160930/psparse-543)
881 [ 1.226519] coyote kernel: ata6.00: configured for UDMA/100
882 [ 1.227197] coyote kernel: ACPI Error: [DSSP] Namespace lookup failure,
AE_NOT_FOUND (20160930/psargs-359)
883 [ 1.227204] coyote kernel: ACPI Error: Method parse/execution failed
[\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff92ef8e0db348), AE_NOT_FOUND (20160930/psparse-543)
884 [ 1.227217] coyote kernel: ata4.00: configured for UDMA/100
-----
and here is the bottom of the file (with line numbers):
-----
1530 [ 2.651202] coyote systemd[1]: Reached target Basic System.
1531 [ 2.933094] coyote kernel: clocksource: Switched to clocksource tsc
1532 [ 2.968658] coyote kernel: random: crng init done
1533 [ 4.022605] coyote systemd-fsck[428]: /dev/sda6: Superblock last mount time is
in the future.
1534 [ 4.022745] coyote systemd-fsck[428]: (by less than a day, probably due to the
hardware clock being incorrectly set)
1535 [ 4.022878] coyote systemd-fsck[428]: /dev/sda6 contains a file system with
errors, check forced.
1536 [ 6.881352] coyote systemd-fsck[428]: /dev/sda6: Deleted inode 1704549 has zero
dtime. FIXED.
1537 [ 13.814145] coyote systemd-fsck[428]: /dev/sda6: Duplicate or bad block in use!
1538 [ 13.855820] coyote systemd-fsck[428]: /dev/sda6: Multiply-claimed block(s) in
inode 674527: 2703102 2703103
1539 [ 13.855918] coyote systemd-fsck[428]: /dev/sda6: Multiply-claimed block(s) in
inode 674586: 2703102 2703103
1540 [ 15.075286] coyote systemd-fsck[428]: /dev/sda6: (There are 2 inodes containing
multiply-claimed blocks.)
1541 [ 15.100918] coyote systemd-fsck[428]: /dev/sda6: File
/usr/share/javadoc/java-1.8.0-openjdk-1.8.0.131-1.b12.fc24/api/java/util/class-use/IllegalFormatCodePointException.html
(inode #674527, mod time Sat Apr 22 17:29:37 2017)
1542 [ 15.101045] coyote systemd-fsck[428]: has 2 multiply-claimed block(s), shared
with 1 file(s):
1543 [ 15.101262] coyote systemd-fsck[428]: /dev/sda6:
/usr/share/javadoc/java-1.8.0-openjdk-1.8.0.131-1.b12.fc24/api/java/util/class-use/SortedMap.html
(inode #674586, mod time Sat Apr 22 17:29:19 2017)
1544 [ 15.101388] coyote systemd-fsck[428]: /dev/sda6:
1545 [ 15.101510] coyote systemd-fsck[428]: /dev/sda6: UNEXPECTED INCONSISTENCY; RUN
fsck MANUALLY.
1546 [ 15.101693] coyote systemd-fsck[428]: (i.e., without -a or -p options)
1547 [ 15.177238] coyote systemd-fsck[428]: fsck failed with error code 4.
1548 [ 15.177386] coyote systemd-fsck[428]: Running request
emergency.target/start/replace
1549 [ 15.179277] coyote systemd[1]: systemd-fsck-root.service: Main process exited,
code=exited, status=1/FAILURE
1550 [ 15.179508] coyote systemd[1]: Failed to start File System Check on
/dev/disk/by-uuid/45e553d2-fa0c-4eae-95f6-7bf9086ab74c.
1551 [ 15.179725] coyote systemd[1]: Dependency failed for /sysroot.
1552 [ 15.179937] coyote systemd[1]: Dependency failed for Initrd Root File System.
1553 [ 15.180040] coyote audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 subj=kernel msg='unit=systemd-fsck-root comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
1554 [ 15.180292] coyote systemd[1]: Dependency failed for Reload Configuration from
the Real Root.
1555 [ 15.180482] coyote systemd[1]: initrd-parse-etc.service: Job
initrd-parse-etc.service/start failed with result 'dependency'.
1556 [ 15.180636] coyote systemd[1]: initrd-parse-etc.service: Triggering OnFailure=
dependencies.
1557 [ 15.180776] coyote systemd[1]: initrd-root-fs.target: Job
initrd-root-fs.target/start failed with result 'dependency'.
1558 [ 15.180915] coyote systemd[1]: initrd-root-fs.target: Triggering OnFailure=
dependencies.
1559 [ 15.181066] coyote systemd[1]: sysroot.mount: Job sysroot.mount/start failed
with result 'dependency'.
1560 [ 15.264980] coyote kernel: kauditd_printk_skb: 2 callbacks suppressed
1561 [ 15.264982] coyote kernel: audit: type=1130 audit(1495014556.700:13): pid=1
uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-fsck-root
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=failed'
1562 [ 15.181237] coyote systemd[1]: systemd-fsck-root.service: Unit entered failed
state.
1563 [ 15.181367] coyote systemd[1]: systemd-fsck-root.service: Failed with result
'exit-code'.
1564 [ 15.181481] coyote systemd[1]: Stopped dracut pre-pivot and cleanup hook.
1565 [ 15.181596] coyote systemd[1]: Stopped target Initrd Default Target.
1566 [ 15.181704] coyote systemd[1]: Reached target Initrd File Systems.
1567 [ 15.181815] coyote systemd[1]: Stopped dracut mount hook.
1568 [ 15.181927] coyote systemd[1]: Stopped target Basic System.
1569 [ 15.182049] coyote systemd[1]: Stopped target System Initialization.
1570 [ 15.182166] coyote systemd[1]: Starting Emergency Shell...
1571 [ 15.203226] coyote systemd[1]: Received SIGRTMIN+21 from PID 395 (plymouthd).
1572 [ 15.213983] coyote audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 subj=kernel msg='unit=plymouth-start comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
1573 [ 15.299101] coyote kernel: audit: type=1131 audit(1495014556.734:14): pid=1
uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=plymouth-start
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
-----
If it helps, here is the "fdisk -l" output from within the rescue shell:
-----
Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xfde8da65
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 206848 1859026943 1858820096 886.4G 7 HPFS/NTFS/exFAT
/dev/sda3 1859026944 1860050943 1024000 500M 83 Linux
/dev/sda4 1860050944 3907029167 2046978224 976.1G 5 Extended
/dev/sda5 1860052992 1876436991 16384000 7.8G 82 Linux swap / Solaris
/dev/sda6 1876439040 1981296639 104857600 50G 83 Linux
/dev/sda7 1981298688 3907028991 1925730304 918.3G 83 Linux
-----
I will re-study what everyone has posted. My non-sys.admin. gut tells me to not try any
real fixes without first getting confirmation here. Otherwise, I could easily make things
worse.
Thank-you for your help so far.
Bill.