Not really sure what to do with this issue?
trying to mount an external drive, only advice im getting from google is to partition internal harddrive and/or wipe harddrive which doesnt seem like it has anything to do with the external drive?
View attachment 22866
checking dmesg provides this particular info.
unsure what to do about blockdev necessarily.
View attachment 22868
Perhaps the first step is discovering whether or not the kernel can see the external hard disk, since, if it can't, there's not much that can be done with it on that system. To discover the situation, one can run the following command with the system up and running and the external hard drive plugged in, for example on a machine here:
Code:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 1 28.7G 0 disk
└─sda1 8:1 1 28.7G 0 part
sr0 11:0 1 1024M 0 rom
nvme0n1 259:0 0 465.8G 0 disk
├─nvme0n1p1 259:1 0 476M 0 part /boot/efi
├─nvme0n1p2 259:2 0 14.9G 0 part [SWAP]
└─nvme0n1p3 259:3 0 450.4G 0 part /
This shows an external drive with the device name /dev/sda which has a single partition named
/dev/sda1.
If the kernel sees the partitions, they can normally be mounted. If one doesn't know the filesystem on the external disk, they can ask mount, as root, to discover it with a command like:
Code:
# mount -t auto /dev/sda1 /mnt
The message: "Can't look up blockdev" apparently was introduced in the 6.6 kernel according to my reading, and may actually be an indication of a kernel failure with this external hard disk. There are a few alternative actions one could take. One would be to reformat the whole external hard disk with the aim of creating a valid filesystem with properly created partitions. Normally one can do this from the running system with the hard disk unmounted and using either command line tools like fdisk for partitioning and mkfs for creating the filesystem, or using a GUI program like Gparted. After the filesystem has been created, one can check it with fsck. However, if the kernel cannot see the external hard disk at all, then one has to do something else, for example, look to another machine to see if that can see this disk and then try and do what needs to be done from there.
One should not omit checking the hardware connections, the cables, the switches and the power supplies. The usb cables are especially vulnerable, so it pays to have one known to be good.
