Block storage attached but does not appear in file system
I'm having the same problem as described here.
The answer given there, which I understand as basically to follow the instructions for creating a file system on the volume, does not work and seems not to apply.
Specifically, the volume I created some 12 hours ago shows as attached to my linode in Linode Manager. I'm logged in as root to my linode using Lish. I started off trying to make a file system on volume as per the instructions given me:
root@localhost:~# mkfs.ext4 /dev/disk/by-id/scsi-0LinodeVolumemyvolume
mke2fs 1.44.1 (24-Mar-2018)
The file /dev/disk/by-id/scsi-0LinodeVolumemyvolume does not exist and no s.
Aha. A mystery. I've run the following terminal commands and get the following results:
root@localhost:~# ls -lah /dev/disk/by-id
total 0
drwxr-xr-x 2 root root 80 Jun 7 16:56 .
drwxr-xr-x 5 root root 100 Jun 7 16:56 ..
lrwxrwxrwx 1 root root 9 Jun 7 16:56 scsi-0QEMUQEMUHARDDISKdrive-scsi-disa lrwxrwxrwx 1 root root 9 Jun 7 16:56 scsi-0QEMUQEMUHARDDISKdrive-scsi-disbroot@localhost:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 968M 0 968M 0% /dev
tmpfs 200M 4.9M 195M 3% /run
/dev/sda 49G 5.6G 41G 12% /
tmpfs 997M 0 997M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 997M 0 997M 0% /sys/fs/cgroup
tmpfs 200M 0 200M 0% /run/user/0root@localhost:~# fdisk -l
Disk /dev/sda: 49.8 GiB, 53418655744 bytes, 104333312 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytesDisk /dev/sdb: 256 MiB, 268435456 bytes, 524288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
My conclusion: the volume is truly lost. How can I get it back?
Edit: I'm running Ubuntu 18.04 LTS
5 Replies
scrane
Linode Staff
Hey there,
That certainly is an odd situation. If you power the Linode down and detach the volume, then power the Linode on and reattach it, are you able to see it then? Do you have a Support Ticket open regarding this?
Thank you in advance!
I figured first I'd see if anyone could tell me what stupid thing I've done, but I just now opened a ticket.
I am also experiencing this situation.
My state:
- I attached the volume on a Linode VM.
- I renamed the volume.
- I tried to mount the volume in my OS (in my case, Debian 11), and it FAILED.
My solution (that worked):
- Detach the volume.
- Re-attach the volume.
- Re-mount--preceded with mkfs (SUCCEEDED).
I hope this is helpful.
I'm new to the platform and experiencing the same thing. I put in a kludge to perform this when a linode first comes up.
Seems pretty clear this is a bug. How do people report bugs like this to get them addressed?
Thanks.
CassandraD
Linode Staff
We did have issues with Block Storage volumes failing to attach a few days ago. If your issue was during that time, then I'd try again now that it was resolved.
If you're still having issues, you can open a Support Ticket to report a bug. That said, I'm having trouble recreating the problem. I followed our guides for attaching and configuring and mounting a volume, and everything is working for me as intended.
I did see an error saying The file /dev/disk/by-id/scsi-0testvolume does not exist and no size was specified. when I ran the command before the Volume had finished creating and attaching. Otherwise, it worked as intended.
Once I added the correct line (step 5D from the mounting guide) to my /etc/fstab file, the volume was attached and mounted on reboot as well.
If you are still having trouble and open a ticket, be sure to let us know what Volume and Linode you're referring to, tell us when the problem occured along with the timezone you're using, and share any screenshots or error codes you're seeing.