state = Dirty reported for Clean W10 filesystems
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| lshw (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
W10/Mint latest - on GPT disk with 9 partitions, both MS and GNU/Linux (multi-boot C855D laptop).
Microsoft tool "fsutil" reports NO dirty bit in p1 (ntfs), p3 (MS Reserved), p5 (ntfs) filesystems.
Scandisk, and chkdsk ops done in both online and offline W10 admin command windows, report NO issues.
W10 OS is in d0p4 (ntfs); seperate DATA storage is in d0p6 (ntfs); seperate EXTRA storage d0p7 (ntfs).
>>> Both latest ubuntu / Mint Tessa (run in UEFI Mode) and pmagic-2017 (run in CSM) command "sudo lshw" in terminal, report false "state=dirty"... for volume 0,2,and 4 ... which are equivalent to sda1 (d0p1), sda3 (d0p3), sda5 (d0p5). All other W10 partitions' filesystems, and (unmounted) Mint partitions' filesystems, are reported correctly, by both versions of lshw.
*NOTES: latest "lshw" version for Mint Tessa, and older "lshw" used in pmagic-2017 have exact-same Issue. Also observed "clonezilla" tool, in pmagic-2017, reports NO dirty bits (correctly).
*Possible causes: legacy Toshiba Satellite C855D UEFI / Digital Signatures / unusual GPT layout.
Priority = Low - [we Thank! the Package Maintainers for the fact our Legacy hardware works at-all!]
| owner-1 (ldcjmd) wrote | #1 |
