On Wed, 17 May 2017 18:18:38 -0000 "William Mattison" <mattison.computer@xxxxxxxxx> wrote: > 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. It isn't home you want to mount, it's /, the root filesystem. One of my earlier emails had instructions on how to create symlink to that partition, and then exit from dracut shell to reboot. Given the rest of your information, it seems you have a corrupted root filesystem on the hard drive, so it probably wouldn't have worked. [snip] > 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. We could be wrong, but when it matters like this it is certainly better to have more sets of eyes look at things. >From rescue mode, you need to run e2fsck (I'm assuming that the filesystems are one of ext[2, 3, 4]. If that isn't what lsblk shows, then you will have to use the appropriate tool for the filesystem you have. I think you want to use the -c and -v options to do a non destructive check first to see if there is anything wrong. You could look at the -k option, and the -c -c option, the -b option, and when you are ready to fix the filesystem, the -p option and possibly -y option. e.g. e2fsck -c -v /dev/sda6 from the rescue boot to check for errors. e2fsck -p -y /dev/sda6 to automatically fix any errors on the device. It's possible that the drive is bad, and this should tell you that. The time problem suggests that the little pancake battery on the MB that maintains the clock might be out of juice. I think these are 2032 style for PCs. It would be a good idea to replace it. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
