User:Adamwill/Draft testcase reboot

Associated release criterion
This test case is associated with the Basic_Release_Criteria#shutdown release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.

Description

This test case ensures that disk drive(s) are properly unmounted during a power down or a restart.

Setup

1. Install or deploy the Fedora release media you wish to test. Follow all defaults, except that you can use any file system supported by the installer for the system partitions (ideally, this test should be run at least once with each of them).
2. Reboot to the installed system.

How to test

1. On the installed system, run a console and become root with sudo su - or su -.
2. Run the following command: journalctl -b | grep -E "dirty bit|data may be corrupt|recovery|unmounted|recovering" and see whether there is any output.
3. If there was output from the grep command, run the command journalctl -b > journal.log. If the grep output does not show clearly that the output resulted from a disk unmount problem, open the journal.log file and search for matches to the grep output to verify that the output was related to a disk unmount problem.
4. If the grep output is for a disk unmount problem, please file a bug report (the kernel is most likely the correct package to file the report against) and attach the journal.log file to the bug report.
5. Restart the test system using the command reboot on the virtual console.
6. Repeat steps 1 to 4 above.

Manual error checking
This test relies on specific expected text in error messages. It's possible these messages may change in the future and there may be an error that is not caught by the grep command. Optionally you can examine the journalctl -b output manually for error messages that might indicate a filesystem not being cleanly unmounted at shutdown, and file a bug report if you find any.

Sample Errors

 -- Logs begin at Tue 2019-08-27 09:26:40 CEST, end at Tue 2019-11-26 14:50:14 CET. --
Nov 25 10:25:20 phoenix systemd-fsck[684]: root: recovering journal
Nov 25 10:25:20 phoenix systemd-fsck[684]: root: Clearing orphaned inode
12325283 (uid=1000, gid=1000, mode=0100644, size=641092)
Nov 25 10:25:20 phoenix systemd-fsck[684]: root: Clearing orphaned inode
12331101 (uid=1000, gid=1000, mode=0100644, size=641092)
Nov 25 10:25:20 phoenix systemd-fsck[684]: root: clean, 1023215/26869760
files, 46957728/107451392 blocks
Nov 25 09:25:22 phoenix systemd-fsck[877]: boot: recovering journal
Nov 25 09:25:22 phoenix systemd-fsck[878]: fsck.fat 4.1 (2017-01-24)
Nov 25 09:25:22 phoenix systemd-fsck[878]: 0x25: Dirty bit is set. Fs was
not properly unmounted and some data may be corrupt
Nov 25 09:25:22 phoenix systemd-fsck[878]:  Automatically removing dirty
bit.
Nov 25 09:25:22 phoenix systemd-fsck[878]: Performing changes.
Nov 25 09:25:22 phoenix systemd-fsck[878]: /dev/nvme0n1p1: 34 files,
6897/51145 clusters
Nov 25 09:25:22 phoenix systemd-fsck[877]: boot: clean, 103/65536 files,
67833/262144 blocks

.

Expected Results

1. Each grep command should produce no output.
2. Running reboot should cause an orderly shutdown and restart of the system.