| 1 |
Hello list, |
| 2 |
|
| 3 |
On my most recent update, I had some build failures that led me to |
| 4 |
find that some files on my root partition have been corrupted. This |
| 5 |
is a new Asus N550JK laptop, a mostly-stable amd64 install with |
| 6 |
gentoo-sources-4.0.5 and ext4-root-in-LVM-in-LUKS-on-HDD, and Debian |
| 7 |
lives in there too (no problems showed up verifying Debian's packages; |
| 8 |
I installed Debian on Jul 1 and used it for a week before getting time |
| 9 |
to set up Gentoo). |
| 10 |
|
| 11 |
These are the package merge times, package names, and files that I |
| 12 |
found to be corrupted via qcheck (there were also a couple Python |
| 13 |
headers that I fixed by rebuilding). They appear to be filled with |
| 14 |
random data. The binpkg contents in /usr/portage/packages are okay, |
| 15 |
so I don't know when the files were corrupted; their mtimes haven't |
| 16 |
been updated since the packages were installed. |
| 17 |
|
| 18 |
Thu-Jul-30-22:40:23-2015 app-arch/p7zip-9.20.1-r5 /usr/lib64/p7zip/Lang/va.txt |
| 19 |
Thu-Jul-30-22:40:23-2015 app-arch/p7zip-9.20.1-r5 /usr/lib64/p7zip/help/cmdline/switches/large_pages.htm |
| 20 |
Sun-Jul-19-22:34:30-2015 dev-libs/libzip-1.0.1 /usr/share/man/man3/zip_error_get_sys_type.3.bz2 |
| 21 |
Sun-Jul-26-22:35:28-2015 dev-python/pygments-2.0.1-r1 /usr/lib64/python2.7/site-packages/pygments/styles/pastie.pyc |
| 22 |
Wed-Jul-08-23:34:56-2015 media-libs/tiff-4.0.3-r6 /usr/share/man/man3/TIFFGetField.3tiff.bz2 |
| 23 |
Thu-Jul-30-10:05:31-2015 sci-mathematics/scilab-5.5.2 /usr/share/scilab/modules/compatibility_functions/macros/%b_l_s.bin |
| 24 |
-(from-stage3-on-Jul-8)- sys-apps/acl-2.2.52-r1 /usr/share/man/man3/acl_set_file.3.bz2 |
| 25 |
|
| 26 |
I haven't had any unclean shutdowns, it looks like OpenRC is |
| 27 |
unmounting things cleanly on shutdown, and suspend appears to work |
| 28 |
fine. |
| 29 |
|
| 30 |
After I make a fresh backup of my files, how would you recommend |
| 31 |
troubleshooting this? Run memtest or a hard drive tester? Since the |
| 32 |
files seemingly corrupted themselves after install without being |
| 33 |
touched, I'm highly suspicious of the hard drive, but would like to |
| 34 |
rule other things out (if say for example that CONFIG_X86_INTEL_PSTATE |
| 35 |
CPU clock booster is dangerous, or nvidia-drivers, or ...). Haven't |
| 36 |
checked for corruption on /home yet. |
| 37 |
|
| 38 |
This is the disk: |
| 39 |
|
| 40 |
*-disk |
| 41 |
description: ATA Disk |
| 42 |
product: ST1000LM024 HN-M |
| 43 |
vendor: Seagate |
| 44 |
physical id: 0.0.0 |
| 45 |
bus info: scsi@4:0.0.0 |
| 46 |
logical name: /dev/sda |
| 47 |
version: 0001 |
| 48 |
size: 931GiB (1TB) |
| 49 |
capabilities: gpt-1.00 partitioned partitioned:gpt |
| 50 |
configuration: ansiversion=5 |
| 51 |
guid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx sectorsize=4096 |
| 52 |
|
| 53 |
Thanks for any help you can provide, |
| 54 |
Bryan |
Archives