Storage HD can’t be mounted at booting

Ubuntu 16.04 desktop


I have 2 WD HDs solely for storage.



About 1 day before both of them could be mounted automatically at booting and their icons appeared on the left vertical menu. I just found that only WD HD2-2TH could be mounted at booting and WD HD1-4TB unable to be mounted for unknown reason.

⟫ sudo fdisk -l

Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 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: gpt Disk identifier: 75CD82BD-3AF3-44B0-A04D-B4C97B6A381C

Device Start End Sectors Size Type /dev/sdc1 34
1987 1954 977K Linux filesystem /dev/sdc2 1988 7814037118 7814035131 3.7T Linux LVM

Partition 1 does not start on physical sector boundary. (in red color) Partition 2 does not start on physical sector boundary. (in red color)

Please advise how to fix the problem. Thanks in advance.

16.04 not booting. Mounted it on 18.04, data seems fine. Repaired Grub

Been raked over the coals with this one.

16.04 crashed while running. Could not even get grub to come up. It is not a dual boot system. Only 16.04. Just screen flashing. No command line access with no ability to read log files. No ability to go back to run level 3 (systemctl in ubuntu). Nothing.

At first, I reinstalled grub from an 18.04 trial install. After that I Was able to select “ubuntu recovery” on boot but with no effect. Same flashing of the screen with no command line access.

I’m sure that it is not a physical problem with the disk. A few weeks ago this same thing happened on another drive. I cloned the drive with DDrescue to another drive. Data was ok. The problem followed the new drive, implying that the problem was in the operating system. Somehow, not sure how, I was able to boot the new drive.

Now I am “in” the new drive and the same thing happened.

Loaded 18.04 on top of 16.04 and I can mount 16.04 and see programs, data.

Is there a way back from this? I don’t want to have to download 300G on another drive at this point (downloading that much data is expensive).

Thank You Tom

USB stick mounted as read-only CD-ROM

I have a kingston encryptable USB stick, that when plugged into my laptop gets mounted as read-only.

I have followed the advice given here, but it does not work for me.

I have tried the following:

df -Th /dev/sr0                    iso9660    13M   13M     0 100% /media/user/DTVP 

(note that the drive is actually 4GB)

sudo chown user /dev/sr0 sudo chgrp user /dev/sr0 

do not yield any output, same if I apply them to /media/user/DTVP

dosfsck /dev/sr0 fsck.fat 4.1 (2017-01-24) open: Read-only file system 

I also tried

getfacl /media/user getfacl: Removing leading '/' from absolute path names # file: media/user # owner: root # group: root user::rwx user:user:r-x group::--- mask::r-x other::--- 

and then try to correct in

sudo setfacl -m u:user:rwx /media/user 

but still, the stick stays read-only. Curiously, on Nautilus it appears as a CD rom rather than a USB stick, and, I guess for the same reason, on GParted is not listed and cannot be reformatted.

Any pointers?

MariaDB docker “Can’t init tc log” on start up when using mounted storage

I am initializing a new MariaDB database. Running docker with a volume to my home directory allows MariaDB to start up just fine:

docker run -it --rm --name mymaria \   -e MYSQL_RANDOM_ROOT_PASSWORD=yes \   -e MYSQL_PASSWORD=p@$  $  w0rd \   -e MYSQL_DATABASE=myapp \   -e MYSQL_USER=myapp \   -v /home/myuser/mysql:/var/lib/mysql \   mariadb:10.2 

However, running the mariadb container with a volume via a mounted directory like so:

docker run -it --rm --name mymaria \   -e MYSQL_RANDOM_ROOT_PASSWORD=yes \   -e MYSQL_PASSWORD=p@$  $  w0rd \   -e MYSQL_DATABASE=myapp \   -e MYSQL_USER=myapp \   -v /mnt/storage/mysql:/var/lib/mysql \   mariadb:10.2 

This configuration returns this from the docker logs output:

Initializing database 2019-09-23  5:12:13 139724696503616 [ERROR] Can't init tc log 2019-09-23  5:12:13 139724696503616 [ERROR] Aborting   Installation of system tables failed! ... 

Simply removing tc.log as some folks have suggested does not work. Restarting mariadb will rewrite tc.log back into the volume /var/lib/mysql.

Perhaps this is a permissions issue? I feel like I’ve tried every combination of chown with each directory. I do notice that docker appears to change the mounted volume /mnt/storage/mysql to drwxr-xr-x 2 systemd-coredump root 176 Sep 22 23:11 mysql which I find odd.

I encounter this issue only with the 10.2 tag and not the latest. However, for an orchestration I’m working on, it suggests mariadb:10.2.

Rules for being stealthy while mounted

Are there official rules or rulings for attempting to use stealth while mounted?

My research on the internet has found a number of opinions on the matter, but none of them seem to be backed by a reference to a book or a ruling. Is using stealth allowed while riding a mount?

For example, I do not see how a horse could be commanded to be stealthy. If you tried, then would that be an animal handling roll? Lets say that you could give the command, then how would a less stealthy mount like a horse even move stealthily?

I am playing in a 5e campaign. My ranger on horseback will move through a forest, outside of combat, and I want to be stealthy while scouting out possible enemy locations for the rest of the party to strike. I could do it without my horse, but if I get spotted, I really will want to get out of there fast.

How does the Mounted Combatant feat interact with Infernal War Machines?

The new Baldur’s Gate – Descent into Avernus hardcover features a brand new mechanic : Infernal War Machines ! A few things caught my eye – first off, that they have a stat block :

An infernal war machine’s statistics function like those for creatures

Then, that their opportunity attack mechanics function a lot like those of mounts :

Infernal war machines provoke opportunity attacks as normal. When an infernal war machine provokes an opportunity attack, the attacker can target the vehicle or any creature riding on or inside if that doesn’t have total cover and is within reach.

Also, that their driver can control their movement much like a mounter controls a (non-intelligent) mount’s movement :

While the vehicle is moving, the driver can steer it along any course.

And that they can make the vehicle Dash/Disengage (in a similar but different manner that a mounter commands a mount to do so) :

As a bonus action, the driver can do one of the following : […] Cause the infernal war machine to take the Dash or Disengage action while the vehicle’s engine is running.

In summary, Infernal War Machines seem similar, in certain points at least, to mounts. What I’m wondering here is : how would a driver with the Mounted Combatant feat interact with these Machines ? Would the feat’s benefits work with the Machines or not ?

Reminder on the Mounted Combatant feat :

You are a adangerous foe while mounted. While you are mounted and aren’t incapacitated, you gain the following benefits :

  • You have advantage on melee attack rolls against any unmounted creature that is smaller than your mount. You can force an attack targeted at your mount to target you instead.
  • You can force an attack targeted at your mount to target you instead.
  • If your mount is subjected to an effect that allows it to make a Dexterity saving throw to take only half damage, it instead takes no damage if it succeeds on the saving throw, and only half damage if it fails.

From a thematic standpoint, I think it would make sense for a specialized “Helldriver”, so to speak, to gain benefits from that feat while driving an Infernal War Machine, but actual-mechanics-wise, I am unsure.

Do steeds summoned with Find Greater Steed have other options than the usual control rules during mounted combat?

During mounted combat, I understand there are two possible options:

  1. You can control your mount, in which case your mount cannot make an attack, or
  2. You can opt to leave it independent (and controlled by the DM) in which case it can attack, but may do things you don’t expect.

The text of find greater steed contains this excerpt:

Your steed serves you as a mount, both in combat and out, and you have an instinctive bond with it that allows you to fight as a seamless unit.

Does this phrase imply that there is some special way to control the steed beyond the above two normal options for mounts? Are steeds summoned in this way special in regards to the control rules, or is that just flavor text? It seems to me that an independent mount which can take actions that I cannot predict is not fighting as a seamless unit with me. Am I misunderstanding something?

The question here certainly provides an answer, but it’s not satisfying since it assumes that the mount has to use one of the two above options and does not consider that there may be alternatives.

How to make sure a swapfile is on the external HDD after it is mounted and not before in the according directory?

I want to put the swapfile on an external HDD which is mounted on startup.

My /etc/dphys-swapfile is


and my /etc/fstab is

UUID=... /home/shares ext4 rw,auto,defaults,nofail,x-systemd.device-timeout=3 0 2 

The swap.file gets placed into the unmounted folder. Apart from the question how bad it is to have a swapfile in a folder that gets a mount afterwards I want to make sure it is not on the SD card (I am running a Raspberry Pi).

Also not sure if a debian question is right for askubuntu, but I think it is more general than just a Raspberry Pi question.

Dosen’t my computer has other partitions mounted?

I have an Ubuntu 18.04 loaded on my machine. I recently got a little mixed up and have made new partitions by making the others a little small. But now I have to delete them but not finding the way. I know my root directory which I should not delete and searching for all the other important partitions but I cannot get them as only root is stated. This is the result of lsblk /dev/sda

NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT sda       8:0    0 298.1G  0 disk  ├─sda1    8:1    0   6.9G  0 part  ├─sda3    8:3    0  35.6G  0 part  ├─sda5    8:5    0   3.7G  0 part  ├─sda6    8:6    0    47G  0 part  ├─sda7    8:7    0  13.7G  0 part  ├─sda8    8:8    0 103.5G  0 part / ├─sda9    8:9    0   6.8G  0 part  └─sda10   8:10   0   5.4G  0 part