-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

There is an html version of this mail, that also has emerge --info and
my kernel config, at:
http://browniehive.net/tmp/hp-problems.html

I've come to a dead end in troubleshooting this issue and turn to you
for help in how to continue. The following is what I've discovered
during troubleshooting.

# FS's not Mounted After Boot

After login I need to remount `/` with rw. I always then mount `/boot`,
`/mnt/hdd`, `/home/thomas/hdd` manually; that is --- with the `fixmnt`
script I made pasted below.

before doing the above `mount` command tells me that the FS's are
mounted as they should be, but they contain no files.

## `~/bin/fixmnt`

~~~~~~~~~~~~
#!/bin/bash

sudo ip link set lo up
sudo dhclient enp0s25

cp /etc/mtab /home/thomas/mtab-$(date -Iminutes)
wgp=$(wgetpaste /etc/mtab)

sudo mount -o remount,rw /
echo $wgp >> /home/thomas/wgp-$(date -Iminutes)
sudo mount /boot
sudo mount /mnt/hdd
sudo mount /home/thomas/hdd
sudo swapon /dev/sdb2
#ip link set lo up
#sudo ip link set lo up
~~~~~~~~~~~~

As I can't put a copy of `/etc/mtab` anywhere on a read only FS you
won't see what it looks like before running the `fixmnt ` script. The
script gives off an error for the call to cp that I've just ignored for
now (also the wgetpaste doesn't work as it requires creating files in
`/tmp/`, which at that point in time is not writable).

# Daemons Won't Start

You can see from the above that `net.lo` does not get started and there
are some daemons that haven't started and won't start when called. Some
I can start through calling their commands directly (I do this with
`privoxy` and `tor` at the moment in a `tmux` session for browsing).
Other daemons won't start no matter what I try, like `dbus`.

## `/etc/init.d/dbus start`

~~~~~~~~~~~~
* Checking local filesystems  .../dev/sda1 is mounted.
e2fsck: Cannot continue, aborting.


fsck.xfs: invalid option -- 'p'
Usage: fsck.xfs [options] device

Options:
  -f           The device is a file
  -L           Force log zeroing. Do this as a last resort.
  -l logdev    Specifies the device where the external log resides.
  -m maxmem    Maximum amount of memory to be used in megabytes.
  -n           No modify mode, just checks the filesystem for damage.
  -P           Disables prefetching.
  -r rtdev     Specifies the device where the realtime section resides.
  -v           Verbose output.
  -c subopts   Change filesystem parameters - use xfs_admin.
  -o subopts   Override default behaviour, refer to man page.
  -t interval  Reporting interval in seconds.
  -d           Repair dangerously.
  -V           Reports version and exits.
open: No such file or directory
fsck.fat 3.0.28 (2015-05-16)

 * Filesystems couldn't be fixed
                                         [ !! ]
 * ERROR: fsck failed to start
 * Checking local filesystems  .../dev/sda1 is mounted.
e2fsck: Cannot continue, aborting.

.... snip ....

 * Filesystems couldn't be fixed
                                         [ !! ]
 * ERROR: fsck failed to start
 * ERROR: cannot start root as fsck would not start
 * ERROR: cannot start mtab as fsck would not start
 * ERROR: cannot start localmount as fsck would not start
 * ERROR: cannot start dbus as fsck would not start
~~~~~~~~~~~~

Because of the above output I wonder if this is because of some FS or
disk error (crossing fingers for software/config and not hardware) the
culprit could be `fsck.xfs`.

I have run fsck (including `xfs_repair` on the xfs partitions) on all
partitions, with no problems reported from a trisquell livedisk. I also
tried running fsck on `/dev/sda1` from the installed Gentoo instance;
got no errors and didn't change any behaviour as far as I have noticed.

# Overview of System

Sometime in the beginning of October I installed an ssd in this laptop
and migrated to it. The problems started after this, but I am unsure
precisely when as I didn't reboot much in between the migration; for all
I remember now these problems might have started a while after the
migration. `sdb` is the "new" ssd while `sda` is the old hdd.

As you can see from `fstab` I tried putting `/dev/sdb3` as the boot
partition when I installed the ssd.

## `/etc/fstab`

~~~~~~~~~~~~
#/dev/sdb3      /boot                   ext2            noatime         1 2
/dev/sda1       /boot                   ext2            noatime         1 2
/dev/sdb1       /                       ext4            noatime,discard 0 1
/dev/sdb2       none                    swap            sw              0 0
## Old harddisk
/dev/sda4       /mnt/hdd                xfs             noatime         0 2
/mnt/hdd/home/thomas /home/thomas/hdd   none            bind            0 0
~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWayVxAAoJEMUjE08Xv1s5rcoH/3Lz6J7FKByC7xWmkB4iwxx+
oApXUhVfG1+ZJbD6V/EWiPo47aXaen1vOMKadcyw2svpWzZlLpLTQDpOiiGGq9Wj
CCR9VuWlAxJMJZkTm0xEkp7GUAXOR6ln/MJvhbGqnrr1AENj7+QaOVr7rHDziH8M
Ew8oZIQctCFAD8m8dIKkF3E4Jqlu9G7Hyi0MrCuqDJxGrPAXObHKDM2Rlpw1ulb7
bcjekq4Zs0F4VuTpkhM7+6a2jvTCuP1EVdQVGr/J3Czz2P1X6sZr9Wbd9o9TvQO/
LWmYT2KaYXPcWcx3LfWw7U51pv6b5Qf0MS87eEMtcnXjNaIDGt3ADzjMpYJ5ES0=
=FlkE
-----END PGP SIGNATURE-----

Reply via email to