Perhaps the automatic check fails and you need to run it “by hand”.
lsblk -f
should list all connected disk devices
of course not
prefer text (copy/paste command and it’s output)
for pictures there are online services and you can share the link here
(yes, you can post these links - just format them as text, so they are not active)
I hope you did it unmounted from live session or a different Installation.
I would not says that fsck broke it, probably the writing while repairing made it RiP. Sounds pretty much like an hardware defect.
Not needed and not whished at all. You have a terminal where you get all information and where you can copy and paste texts here within a code block (preformatted text).
I understood that the partition should first be unmounted before doing the fsck which I did, but I did not do it from live/usb session… so yes, as you say I think maybe writing while repairing must have RiP’d it…
Okay, thank you for the cmd prompts, which return as:
[manjaro@manjaro ~]$ **sudo parted -l**
Model: USB2.0 Flash Disk (scsi)
Disk /dev/sda: 4089MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
2 3576MB 3580MB 4194kB primary esp
Warning: Error fsyncing/closing /dev/sdb1: Input/output error
Retry/Ignore? (not sure what to type here,)
New terminal:
[manjaro@manjaro ~]$ **sudo fdisk -l**
Disk /dev/sdc: 111.79 GiB, 120034123776 bytes, 234441648 sectors
Disk model: Hitachi HTS54251
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x946f91c4
Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 2048 234440703 234438656 111.8G 82 Linux swap / Solaris
Disk /dev/sda: 3.81 GiB, 4089446400 bytes, 7987200 sectors
Disk model: Flash Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 64 6983755 6983692 3.3G 0 Empty
/dev/sda2 6983756 6991947 8192 4M ef EFI (FAT-12/16/32)
Disk /dev/loop0: 140.23 MiB, 147038208 bytes, 287184 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
Disk /dev/loop1: 971.54 MiB, 1018736640 bytes, 1989720 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
Disk /dev/loop2: 1.35 GiB, 1444270080 bytes, 2820840 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
Disk /dev/loop3: 791.93 MiB, 830402560 bytes, 1621880 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
I fixed the terminal outputs and set them into a code block (preformmated text). Please do it like that in the future. It is more readable.
If you are talking about the disk /dev/sdb, then it looks like it is dead. A hardware failure.
That indicates it:
You could check the kernel messages:
sudo dmesg | grep "sdb"
But I don’t think that a normal user could save the data on the hard drive. I hope you have a backup, otherwise a rescue like this will be expensive with a specialist.
Hi, many thanks, yes I will have a go with that fancy formatting at some point, you are correct we were trying hard to access sdb but impossible, the plan is now to use some Linux recovery software and they try recover dat import word docx
By the way, while this thread is still active, can anyone advise how to disable ‘flight mode’. Since yesterday’s testing on the system I’ve been unable enable WiFi on the pc t430s which seems to be due to flight mode being on ‘permanently’. There is no response when selecting ‘off switch’,
