I have a external hadedisk with much saved material connected by USB now it doesn't open in the launchpad

What file system is the drive using?
If you boot with it unplugged, log in and wait for the OS to settle. Plug in the drive, open a terminal and run:

sudo parted -l; dmesg | tail; lsb_release -a; uname -a

What is the full output please?

Thanks

Model: ATA MTFDDAK256MAM-1K (scsi)
Disk /dev/sda: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
 1 1049kB 248GB 248GB primary ext4 boot
 2 248GB 256GB 8017MB extended
 5 248GB 256GB 8017MB logical linux-swap(v1)

Model: SanDisk Cruzer Blade (scsi)
Disk /dev/sdb: 4022MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
 1 19,5kB 4014MB 4014MB primary fat32

Model: SanDisk Cruzer Blade (scsi)
Disk /dev/sdc: 4022MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
 1 19,5kB 4014MB 4014MB primary fat32 boot, lba

Warning: Error fsyncing/closing /dev/sdd1: Remote I/O error
Retry/Ignore?
I'm using Ubuntu 16 04 ext4

Hi, Same error that has shown up before. The hard-disk does not register on the terminal.

Warning: Error fsyncing/closing /dev/sdd1: Remote I/O error

Try:

sudo fsck /dev/sdd1

May help

Retry/Ignore? sudo fsck /dev/sdd1
parted: invalid token: sudo
Retry/Ignore? I'm afraid not

https://help.ubuntu.com/community/FilesystemTroubleshooting

Sorry to complicated, remember I am a newbie - so many command/code possibilities is beyond me.

graeme@graeme-ThinkCentre:~$ /dev/sda3
bash: /dev/sda3: No such file or directory
graeme@graeme-ThinkCentre:~$ 1ag
No command '1ag' found, did you mean:
 Command 'ag' from package 'silversearcher-ag' (universe)
 Command 'mag' from package 'texlive-binaries' (main)
1ag: command not found
graeme@graeme-ThinkCentre:~$ umount /dev/sda3
umount: /dev/sda3: No such file or directory
graeme@graeme-ThinkCentre:~$

Is there anywhere else I can get help?
Regards Graeme

These commands won't work.

Warning: Error fsyncing/closing /dev/sdd1: Remote I/O error
Retry/Ignore?

That indicates a serious problem with the drive on kernel level. Please make sure the drive is connected correctly va SATA or IDE and configured correctly within your BIOS or EFI/UEFI, preferably as an IDE (not SATA or AHCI) device.

Then reboot and check if the device is listed in the BIOS or EFI boot screen (or within the BIOS or EFI itself). Look also within /var/log/ (dmesg, syslog, etc.) for errors at the last boot.

Finally try to list all block devices via »ls -slaph /dev/sd* && ls -slaph /dev/hd*« and execute »sudo fdisk -l« or run gparted.

@A. Denton (aquina)

Hi I'm really having a hard time understanding what you are saying let alone carrying out your suggestions, please remember I'm a newbie. I have written a whole lot different commands, but the one below is the first that the terminal has actually recognized the hard-disk. That is Bus 002 Device 003: ID 059f:0351 LaCie, Ltd
Bus 002 Device 002: ID 059f:0363 LaCie, Ltd

graeme@graeme-ThinkCentre:~$ "lsusb"
Bus 002 Device 005: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 002 Device 003: ID 059f:0351 LaCie, Ltd
Bus 002 Device 002: ID 059f:0363 LaCie, Ltd
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 002: ID 046d:c404 Logitech, Inc. TrackMan Wheel
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 002: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0781:5567 SanDisk Corp. Cruzer Blade
Bus 001 Device 002: ID 0781:5567 SanDisk Corp. Cruzer Blade
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
At last I've seen the hard-disk in the terminal using the above command, but not in the launchpad. Graeme <PS tomorrow I will try the commands you have suggested.

raeme@graeme-ThinkCentre:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop1 7:1 0 86,6M 1 loop /snap/core/4486
sdb 8:16 0 74,5G 0 disk
├─sdb2 8:18 0 1K 0 part
├─sdb5 8:21 0 74,1G 0 part
└─sdb1 8:17 0 487M 0 part
sr0 11:0 1 1024M 0 rom
loop0 7:0 0 162,1M 1 loop /snap/spotify/13
sda 8:0 0 238,5G 0 disk
├─sda2 8:2 0 1K 0 part
├─sda5 8:5 0 7,5G 0 part
│ └─cryptswap1 253:0 0 7,5G 0 crypt [SWAP]
└─sda1 8:1 0 231G 0 part /
sr1 11:1 1 1024M 0 rom

This must be the external hard-disk??? sdb 8:16 0 74,5G 0 disk . Graeme

graeme@graeme-ThinkCentre:~$ sudo fsck /dev/sdc1
[sudo] password for graeme:
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
fsck.ext2: No such file or directory while trying to open /dev/sdc1
Possibly non-existent device?
graeme@graeme-ThinkCentre:~$ sudo fsck sdb 8:16 0 74,5G 0 disk
fsck from util-linux 2.27.1
Usage: fsck.ext4 [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
  [-I inode_buffer_blocks] [-P process_inode_size]
  [-l|-L bad_blocks_file] [-C fd] [-j external_journal]
  [-E extended-options] device

Emergency help:
 -p Automatic repair (no questions)
 -n Make no changes to the filesystem
 -y Assume "yes" to all questions
 -c Check for bad blocks and add them to the badblock list
 -f Force checking even if filesystem is marked clean
 -v Be verbose
 -b superblock Use alternative superblock
 -B blocksize Force blocksize when looking for superblock
 -j external_journal Set location of the external journal
 -l bad_blocks_file Add to badblocks list
 -L bad_blocks_file Set badblocks list
graeme@graeme-ThinkCentre:~$ sudo fsck Bus 002 Device 003: ID 059f:0351 LaCie, Ltd
fsck from util-linux 2.27.1
Usage: fsck.ext4 [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
  [-I inode_buffer_blocks] [-P process_inode_size]
  [-l|-L bad_blocks_file] [-C fd] [-j external_journal]
  [-E extended-options] device

Emergency help:
 -p Automatic repair (no questions)
 -n Make no changes to the filesystem
 -y Assume "yes" to all questions
 -c Check for bad blocks and add them to the badblock list
 -f Force checking even if filesystem is marked clean
 -v Be verbose
 -b superblock Use alternative superblock
 -B blocksize Force blocksize when looking for superblock
 -j external_journal Set location of the external journal
 -l bad_blocks_file Add to badblocks list
 -L bad_blocks_file Set badblocks list
graeme@graeme-ThinkCentre:~$ sudo fsck Bus 002 Device 002: ID 059f:0363 LaCie, Ltd
fsck from util-linux 2.27.1
Usage: fsck.ext4 [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
  [-I inode_buffer_blocks] [-P process_inode_size]
  [-l|-L bad_blocks_file] [-C fd] [-j external_journal]
  [-E extended-options] device

Emergency help:
 -p Automatic repair (no questions)
 -n Make no changes to the filesystem
 -y Assume "yes" to all questions
 -c Check for bad blocks and add them to the badblock list
 -f Force checking even if filesystem is marked clean
 -v Be verbose
 -b superblock Use alternative superblock
 -B blocksize Force blocksize when looking for superblock
 -j external_journal Set location of the external journal
 -l bad_blocks_file Add to badblocks list
 -L bad_blocks_file Set badblocks list
graeme@graeme-ThinkCentre:~$
After these commands I recieved these results. I havn't rebooted yet. Graeme

graeme@graeme-ThinkCentre:~$ sudo tail -f /var/log/syslog
[sudo] password for graeme:
Apr 29 11:08:50 graeme-ThinkCentre systemd[1]: Stopped User Manager for UID 108.
Apr 29 11:08:50 graeme-ThinkCentre systemd[1]: Removed slice User Slice of lightdm.
Apr 29 11:08:50 graeme-ThinkCentre systemd[1]: fwupd.service: Start operation timed out. Terminating.
Apr 29 11:08:51 graeme-ThinkCentre systemd[1]: Failed to start Firmware update daemon.
Apr 29 11:08:51 graeme-ThinkCentre systemd[1]: Startup finished in 9.733s (kernel) + 2min 3.883s (userspace) = 2min 13.617s.
Apr 29 11:08:51 graeme-ThinkCentre systemd[1]: fwupd.service: Unit entered failed state.
Apr 29 11:08:51 graeme-ThinkCentre systemd[1]: fwupd.service: Failed with result 'timeout'.
Apr 29 11:15:57 graeme-ThinkCentre kernel: [ 560.470855] perf: interrupt took too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
Apr 29 11:17:01 graeme-ThinkCentre CRON[3252]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 29 11:17:06 graeme-ThinkCentre sudo: pam_ecryptfs: pam_sm_authenticate: /home/graeme is already mounted

@A. Denton (aquina)

graeme@graeme-ThinkCentre:~$ ls -slaph /dev/sd* && ls -slaph /dev/hd*
0 brw-rw---- 1 root disk 8, 0 apr 29 12:02 /dev/sda
0 brw-rw---- 1 root disk 8, 1 apr 29 12:02 /dev/sda1
0 brw-rw---- 1 root disk 8, 2 apr 29 12:02 /dev/sda2
0 brw-rw---- 1 root disk 8, 5 apr 29 12:02 /dev/sda5
0 brw-rw---- 1 root disk 8, 16 apr 29 12:02 /dev/sdb
0 brw-rw---- 1 root disk 8, 17 apr 29 12:02 /dev/sdb1
0 brw-rw---- 1 root disk 8, 18 apr 29 12:02 /dev/sdb2
0 brw-rw---- 1 root disk 8, 21 apr 29 12:02 /dev/sdb5
ls: cannot access '/dev/hd*': No such file or directory
graeme@graeme-ThinkCentre:~$ sudo fdisk -l« or run gparted.
[sudo] password for graeme:
fdisk: invalid option -- '�'
The result of some of your suggestions Graeme

Usage:
 fdisk [options] <disk> change partition table
 fdisk [options] -l [<disk>] list partition table(s)

Display or manipulate a disk partition table.

Options:
 -b, --sector-size <size> physical and logical sector size
 -B, --protect-boot don't erase bootbits when create a new label
 -c, --compatibility[=<mode>] mode is 'dos' or 'nondos' (default)
 -L, --color[=<when>] colorize output (auto, always or never)
                                 colors are enabled by default
 -l, --list display partitions end exit
 -o, --output <list> output columns
 -t, --type <type> recognize specified partition table type only
 -u, --units[=<unit>] display units: 'cylinders' or 'sectors' (default)
 -s, --getsz display device size in 512-byte sectors [DEPRECATED]
     --bytes print SIZE in bytes rather than in human readable format

 -C, --cylinders <number> specify the number of cylinders
 -H, --heads <number> specify the number of heads
 -S, --sectors <number> specify the number of sectors per track

 -h, --help display this help and exit
 -V, --version output version information and exit

Available columns (for -o):
 gpt: Device Start End Sectors Size Type Type-UUID Attrs Name UUID
 dos: Device Start End Sectors Cylinders Size Type Id Attrs Boot End-C/H/S
      Start-C/H/S
 bsd: Slice Start End Sectors Cylinders Size Type Bsize Cpg Fsize
 sgi: Device Start End Sectors Cylinders Size Type Id Attrs
 sun: Device Start End Sectors Cylinders Size Type Id Flags

For more details see fdisk(8).
graeme@graeme-ThinkCentre:~$ fdisk(8)
bash: syntax error near unexpected token `8'
graeme@graeme-ThinkCentre:~$ fdisk

Usage:
 fdisk [options] <disk> change partition table
 fdisk [options] -l [<disk>] list partition table(s)

Display or manipulate a disk partition table.

Options:
 -b, --sector-size <size> physical and logical sector size
 -B, --protect-boot don't erase bootbits when create a new label
 -c, --compatibility[=<mode>] mode is 'dos' or 'nondos' (default)
 -L, --color[=<when>] colorize output (auto, always or never)
                                 colors are enabled by default
 -l, --list display partitions end exit
 -o, --output <list> output columns
 -t, --type <type> recognize specified partition table type only
 -u, --units[=<unit>] display units: 'cylinders' or 'sectors' (default)
 -s, --getsz display device size in 512-byte sectors [DEPRECATED]
     --bytes print SIZE in bytes rather than in human readable format

 -C, --cylinders <number> specify the number of cylinders
 -H, --heads <number> specify the number of heads
 -S, --sectors <number> specify the number of sectors per track

 -h, --help display this help and exit
 -V, --version output version information and exit

Available columns (for -o):
 gpt: Device Start End Sectors Size Type Type-UUID Attrs Name UUID
 dos: Device Start End Sectors Cylinders Size Type Id Attrs Boot End-C/H/S
      Start-C/H/S
 bsd: Slice Start End Sectors Cylinders Size Type Bsize Cpg Fsize
 sgi: Device Start End Sectors Cylinders Size Type Id Attrs
 sun: Device Start End Sectors Cylinders Size Type Id Flags

For more details see fdisk(8).
graeme@graeme-ThinkCentre:~$

@A. Denton (aquina)
@actionparsnip (andrew-woodhead666)

Isn't anybody home? Graeme PS please inform me i there is nothing more to be done.

1. A general recommendation: If you want to identify an external hard disk, you should remove all other external storage devices to keep the output of commands like lsusb, fdisk -l etc. as short as possible.
There are several disks and partitions listed in your output, how do you expect that we know which one you are talking about?

2. The output "Warning: Error fsyncing/closing /dev/sdd1: Remote I/O error" indicates a severe problem on one of the hard disk partitions. I am not sure whether it will be possible to revive that disk at all.

3. Some more commands for diagnostics:

Boot your computer without USB sticks and external disks connected.
Wait five minutes that it is fully started
plug the external disk into the system, wait half a minute and then execute the command

lsusb
dmesg | tail
sudo fdisk -l

and copy/paste the output into this question document.

graeme@graeme-ThinkCentre:~$ lsusb
Bus 002 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 002 Device 002: ID 059f:0363 LaCie, Ltd
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 002: ID 046d:c404 Logitech, Inc. TrackMan Wheel
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 004: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 059f:0351 LaCie, Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
graeme@graeme-ThinkCentre:~$ dmesg | tail
[ 83.038051] scsi host7: usb-storage 1-2:1.0
[ 83.053892] usbcore: registered new interface driver uas
[ 84.064711] scsi 7:0:0:0: Direct-Access WDC WD800BB-00FJA0
13.0 PQ: 0 ANSI: 2
[ 84.065082] sd 7:0:0:0: Attached scsi generic sg3 type 0
[ 84.066064] sd 7:0:0:0: [sdb] 156301488 512-byte logical blocks: (80.0
GB/74.5 GiB)
[ 84.067063] sd 7:0:0:0: [sdb] Write Protect is off
[ 84.067066] sd 7:0:0:0: [sdb] Mode Sense: 53 00 00 08
[ 84.070772] sd 7:0:0:0: [sdb] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[ 84.095188] sdb: sdb1 sdb2 < sdb5 >
[ 84.098323] sd 7:0:0:0: [sdb] Attached SCSI disk
graeme@graeme-ThinkCentre:~$ sudo fdisk -l
[sudo] password for graeme:
Disk /dev/loop0: 162,1 MiB, 169943040 bytes, 331920 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: 86,6 MiB, 90759168 bytes, 177264 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/sda: 238,5 GiB, 256060514304 bytes, 500118192 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
Disklabel type: dos
Disk identifier: 0x55ad2300

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 484456447 484454400 231G 83 Linux
/dev/sda2 484458494 500117503 15659010 7,5G 5 Extended
/dev/sda5 484458496 500117503 15659008 7,5G 82 Linux swap / Solaris

Disk /dev/mapper/cryptswap1: 7,5 GiB, 8016887808 bytes, 15657984 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/sdb: 74,5 GiB, 80026361856 bytes, 156301488 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
Disklabel type: dos
Disk identifier: 0xe497b97e

Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 999423 997376 487M 83 Linux
/dev/sdb2 1001470 156301311 155299842 74,1G 5 Extended
/dev/sdb5 1001472 156301311 155299840 74,1G 8e Linux LVM
graeme@graeme-ThinkCentre:~$

On 29 April 2018 at 18:17, Manfred Hampl <
<email address hidden>> wrote:

> Your question #668308 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/668308
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> 1. A general recommendation: If you want to identify an external hard
> disk, you should remove all other external storage devices to keep the
> output of commands like lsusb, fdisk -l etc. as short as possible.
> There are several disks and partitions listed in your output, how do you
> expect that we know which one you are talking about?
>
> 2. The output "Warning: Error fsyncing/closing /dev/sdd1: Remote I/O
> error" indicates a severe problem on one of the hard disk partitions. I
> am not sure whether it will be possible to revive that disk at all.
>
> 3. Some more commands for diagnostics:
>
> Boot your computer without USB sticks and external disks connected.
> Wait five minutes that it is fully started
> plug the external disk into the system, wait half a minute and then
> execute the command
>
> lsusb
> dmesg | tail
> sudo fdisk -l
>
> and copy/paste the output into this question document.
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+question/668308
>
> You received this question notification because you asked the question.
>

Bus 002 Device 002: ID 059f:0363 LaCie, Ltd This is the hard-disk,I
actually pointed that out in one of my earlier posts - Graeme

On 29 April 2018 at 23:15, Graeme Booth <email address hidden> wrote:

> graeme@graeme-ThinkCentre:~$ lsusb
> Bus 002 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
> Bus 002 Device 002: ID 059f:0363 LaCie, Ltd
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 008 Device 002: ID 046d:c404 Logitech, Inc. TrackMan Wheel
> Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 007 Device 004: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard
> Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 002: ID 059f:0351 LaCie, Ltd
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> graeme@graeme-ThinkCentre:~$ dmesg | tail
> [ 83.038051] scsi host7: usb-storage 1-2:1.0
> [ 83.053892] usbcore: registered new interface driver uas
> [ 84.064711] scsi 7:0:0:0: Direct-Access WDC WD800BB-00FJA0
> 13.0 PQ: 0 ANSI: 2
> [ 84.065082] sd 7:0:0:0: Attached scsi generic sg3 type 0
> [ 84.066064] sd 7:0:0:0: [sdb] 156301488 512-byte logical blocks: (80.0
> GB/74.5 GiB)
> [ 84.067063] sd 7:0:0:0: [sdb] Write Protect is off
> [ 84.067066] sd 7:0:0:0: [sdb] Mode Sense: 53 00 00 08
> [ 84.070772] sd 7:0:0:0: [sdb] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [ 84.095188] sdb: sdb1 sdb2 < sdb5 >
> [ 84.098323] sd 7:0:0:0: [sdb] Attached SCSI disk
> graeme@graeme-ThinkCentre:~$ sudo fdisk -l
> [sudo] password for graeme:
> Disk /dev/loop0: 162,1 MiB, 169943040 bytes, 331920 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: 86,6 MiB, 90759168 bytes, 177264 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/sda: 238,5 GiB, 256060514304 bytes, 500118192 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
> Disklabel type: dos
> Disk identifier: 0x55ad2300
>
> Device Boot Start End Sectors Size Id Type
> /dev/sda1 * 2048 484456447 484454400 231G 83 Linux
> /dev/sda2 484458494 500117503 15659010 7,5G 5 Extended
> /dev/sda5 484458496 500117503 15659008 7,5G 82 Linux swap / Solaris
>
> Disk /dev/mapper/cryptswap1: 7,5 GiB, 8016887808 bytes, 15657984 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/sdb: 74,5 GiB, 80026361856 bytes, 156301488 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
> Disklabel type: dos
> Disk identifier: 0xe497b97e
>
> Device Boot Start End Sectors Size Id Type
> /dev/sdb1 2048 999423 997376 487M 83 Linux
> /dev/sdb2 1001470 156301311 155299842 74,1G 5 Extended
> /dev/sdb5 1001472 156301311 155299840 74,1G 8e Linux LVM
> graeme@graeme-ThinkCentre:~$
>
>
> On 29 April 2018 at 18:17, Manfred Hampl <question668308@answers.
> launchpad.net> wrote:
>
>> Your question #668308 on Ubuntu changed:
>> https://answers.launchpad.net/ubuntu/+question/668308
>>
>> Status: Open => Needs information
>>
>> Manfred Hampl requested more information:
>> 1. A general recommendation: If you want to identify an external hard
>> disk, you should remove all other external storage devices to keep the
>> output of commands like lsusb, fdisk -l etc. as short as possible.
>> There are several disks and partitions listed in your output, how do you
>> expect that we know which one you are talking about?
>>
>> 2. The output "Warning: Error fsyncing/closing /dev/sdd1: Remote I/O
>> error" indicates a severe problem on one of the hard disk partitions. I
>> am not sure whether it will be possible to revive that disk at all.
>>
>> 3. Some more commands for diagnostics:
>>
>> Boot your computer without USB sticks and external disks connected.
>> Wait five minutes that it is fully started
>> plug the external disk into the system, wait half a minute and then
>> execute the command
>>
>> lsusb
>> dmesg | tail
>> sudo fdisk -l
>>
>> and copy/paste the output into this question document.
>>
>> --
>> To answer this request for more information, you can either reply to
>> this email or enter your reply at the following page:
>> https://answers.launchpad.net/ubuntu/+question/668308
>>
>> You received this question notification because you asked the question.
>>
>
>

Oh holy lord! You wrote, quote:
"This must be the external hard-disk??? sdb 8:16 0 74,5G 0 disk ."

But then you execute, quote:
"sudo fsck /dev/sdc1"

Well, that probably won't work. First connect the disk properly, then locate it and then scan it via fsck, preferably with options/parameters -v -f and -b if needed. Try »man fsck« if in doubt.

You also executed, quote:
"sudo fdisk -l« or run gparted."

That is utter nonsense. the command is »sudo fdisk -l« (of course without the »«, which are called chevrons or guillemets). see: https://de.wikipedia.org/wiki/Guillemets

If in doubt please ask someone in your family, neighborhood or colleague at work. This is not a Ubuntu related problem suitable for launchpad, but a hardware related problem.

GNU/Linux systems like Ubuntu are suitable for beginners in GNU/Linux, but not people who start to use a computer or an operating system.

The last output looks better, no more "Remote I/O error" error.

Can you now access the contents of the disk?

graeme@graeme-ThinkCentre:~$ fsck
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
/dev/sda1 is mounted.

WARNING!!! The filesystem is mounted. If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.

Do you really want to continue<n>?
Ok sahall I chance it, to continue?

It seems that you have not understood all details of the disk and partition naming in Linux.

Each disk that is connected to the system receives a name like /dev/sda, /dev/sdb, /dev/hda, /dev/hdb or similar.
And the partitions on these disks get a name that consists of the disk reference plus a number
/dev/sda1, /dev/sda2, /dev/sdb1, /dev/sdb2 etc.

You have to be aware, that the letter in the disk name may change, depending on the way that you boot your system.
If you boot your system from an USB stick, all your disks (and consequently the partitions) may receive different letters compared to a ession that was booted from the primary hard disk. What once was /dev/sda may be /dev/sdb if you boot from an USB stick.

If you want to run a file system check (fsck) on a partition, you have to be careful to select the correct partition.
You should never attempt to run fsck on a partition that is in use by the system.

1. Are the data on the external disk already accessible?

2. If not (or if you want to run fsck on it anyhow), what is the /dev/xxx name of the partition in question - to be confirmed in the current session that you are running? I assume that it is NOT /dev/sda1.

@Manfred Hampl (m-hampl) @A. Denton (aquina)
To answer your question - no it still refuses to show up in the launchpad. Everybody agrees that it is dangerous to use :fsck - when the filesystem is mounted. (you can see from the previous mail) I tried to run it from the install DVD - in "try it out" mode, but that did nothing. This seems to be a catch 22 situation.
Hi A Denton, you must realize that I for the most part have no idea of what I am doing, I'm just clutching at straws. Ok, great it's hardware related - I'm here to learn. But I'm not so crazy about your tone. As a newbie I don't feel much Ubuntu community in it. Perhaps a little understanding that many who come to this site are beginners and new to a whole world of coding and commands that Linux enthusiasts are so immersed in morning,noon and night. Remember your roll as teacher.

If is's mechanical then I suppose we can call it quites. Thanks for your time and impatiens. Graeme

Have you already tried running fsck /dev/sdxn - with the correct partition name?

Hi again, I saw your last mail and the result is:

graeme@graeme-ThinkCentre:~$ fsck /dev/sdxn -Disk /dev/sdb
fsck from util-linux 2.27.1
fsck.ext2: invalid option -- 'i'
Usage: fsck.ext2 [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
  [-I inode_buffer_blocks] [-P process_inode_size]
  [-l|-L bad_blocks_file] [-C fd] [-j external_journal]
  [-E extended-options] device

Emergency help:
 -p Automatic repair (no questions)
 -n Make no changes to the filesystem
 -y Assume "yes" to all questions
 -c Check for bad blocks and add them to the badblock list
 -f Force checking even if filesystem is marked clean
 -v Be verbose
 -b superblock Use alternative superblock
 -B blocksize Force blocksize when looking for superblock
 -j external_journal Set location of the external journal
 -l bad_blocks_file Add to badblocks list
 -L bad_blocks_file Set badblocks list
fsck.ext2: invalid option -- 'i'
Usage: fsck.ext2 [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
  [-I inode_buffer_blocks] [-P process_inode_size]
  [-l|-L bad_blocks_file] [-C fd] [-j external_journal]
  [-E extended-options] device

Emergency help:
 -p Automatic repair (no questions)
 -n Make no changes to the filesystem
 -y Assume "yes" to all questions
 -c Check for bad blocks and add them to the badblock list
 -f Force checking even if filesystem is marked clean
 -v Be verbose
 -b superblock Use alternative superblock
 -B blocksize Force blocksize when looking for superblock
 -j external_journal Set location of the external journal
 -l bad_blocks_file Add to badblocks list
 -L bad_blocks_file Set badblocks list
graeme@graeme-ThinkCentre:~$

Again you are using wrong parameters to the command.
It has to be the partition (with a number at the end), not the disk!
And you have to remove all my comments and explanations and use just the correct command and the correct parameters!

IF the disk and partition naming in the current session is the same as during comment #16, then I assume that the command has to be

sudo fdisk /dev/sdb5

but if the disk naming is different in this current session, this might be wrong again.

graeme@graeme-ThinkCentre:~$ sudo fdisk /dev/sdb5
[sudo] password for graeme:

Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0x84adb2e7.

Command (m for help): m

Help:

  DOS (MBR)
   a toggle a bootable flag
   b edit nested BSD disklabel
   c toggle the dos compatibility flag

  Generic
   d delete a partition
   F list free unpartitioned space
   l list known partition types
   n add a new partition
   p print the partition table
   t change a partition type
   v verify the partition table
   i print information about a partition

  Misc
   m print this menu
   u change display/entry units
   x extra functionality (experts only)

  Script
   I load disk layout from sfdisk script file
   O dump disk layout to sfdisk script file

  Save & Exit
   w write table to disk and exit
   q quit without saving changes

  Create a new label
   g create a new empty GPT partition table
   G create a new empty SGI (IRIX) partition table
   o create a new empty DOS partition table
   s create a new empty Sun partition table

Command (m for help): F
Unpartitioned space /dev/sdb5: 74,1 GiB, 79512469504 bytes, 155297792 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Start End Sectors Size
 2048 155299839 155297792 74,1G

Command (m for help): sudo fdisk /dev/sdb5
Created a new partition 1 of type 'Linux native' and of size 74 GiB.
Created a new partition 2 of type 'Linux swap' and of size 50 MiB.
Created a new partition 3 of type 'Whole disk' and of size 74,1 GiB.
Created a new Sun disklabel.

Command (m for help):
The result. G

oops, sorry, this was the wrong command

sudo fsck /dev/sdb5

Command (m for help): sudo fdisk /dev/sdb5
Created a new partition 1 of type 'Linux native' and of size 74 GiB.
Created a new partition 2 of type 'Linux swap' and of size 50 MiB.
Created a new partition 3 of type 'Whole disk' and of size 74,1 GiB.
Created a new Sun disklabel.

Command (m for help): sudo fsck /dev/sdb5
Created a new partition 1 of type 'Linux native' and of size 74 GiB.
Created a new partition 2 of type 'Linux swap' and of size 50 MiB.
Created a new partition 3 of type 'Whole disk' and of size 74,1 GiB.
Created a new Sun disklabel.

Command (m for help):
This is the result, I don'i seem to have a home partition anymore.

Don't you see the different prompts?
graeme@graeme-ThinkCentre:~$
versus
Command (m for help):
?

You are still inside the fdisk program !

Press q and press the enter key to quit without saving.

And then (at the normal system prompt with your username) issue the command

sudo fsck /dev/sdb5

graeme@graeme-ThinkCentre:~$ sudo fsck /dev/sdb5
[sudo] password for graeme:
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
fsck.ext2: No such file or directory while trying to open /dev/sdb5
Possibly non-existent device?
graeme@graeme-ThinkCentre:~$

graeme@graeme-ThinkCentre:~$ sudo fsck /dev/sdb5
[sudo] password for graeme:
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb5

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

graeme@graeme-ThinkCentre:~$ e2fsck -b 8193 <device>
bash: syntax error near unexpected token `newline'
graeme@graeme-ThinkCentre:~$ e2fsck -b 32768 <device>
bash: syntax error near unexpected token `newline'
graeme@graeme-ThinkCentre:~$

What is superblock? G

@Manfred Hampl (m-hampl)
Hej Manfred I see from my terminal that superblock may be corrupted. Everybody warns the system must be unmounted if one is to fix it without causing new problems. https://www.cyberciti.biz/faq/recover-bad-superblock-from-corrupted-partition/ At the the above Linux recovery site - the same. All very well, but I attempted from the DVD type recovery, but not really knowing how to go about it I had to exit without getting anywhere. Do you have a suggestion? Cheers G

Again the same problem:

sudo fsck /dev/sdb5
... fsck.ext2: No such file or directory while trying to open /dev/sdb5

You have to make sure that you are using the correct device name. I already told that the device naming will change if you do not boot from the built-in hard disk, but from a live system.

We cannot see your system, only you can check whether the device name is correct.

But I just rechecked your output, and it seems that that external disk is formatted with LVM? Do you know anything about this?
In that case running fsck directly on it is nonsense, but the file system check has to be done on the logical volume

What is the output of the command

lvscan

(if it responds with missing access rights, then re-try with "sudo lvscan").

graeme@graeme-ThinkCentre:~$ lvscan
The program 'lvscan' is currently not installed. You can install it by typing:
sudo apt install lvm2
graeme@graeme-ThinkCentre:~$ sudo apt install lvm2
[sudo] password for graeme:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-4.13.0-36 linux-headers-4.13.0-36-generic
  linux-image-4.13.0-36-generic linux-image-extra-4.13.0-36-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5
Suggested packages:
  thin-provisioning-tools
The following NEW packages will be installed:
  dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5
  lvm2
0 upgraded, 6 newly installed, 0 to remove and 10 not upgraded.
Need to get 1 784 kB of archives.
After this operation, 5 554 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 libdevmapper-event1.02.1 amd64 2:1.02.110-1ubuntu10 [12,2 kB]
Get:2 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 liblvm2cmd2.02 amd64 2.02.133-1ubuntu10 [518 kB]
Get:3 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 dmeventd amd64 2:1.02.110-1ubuntu10 [31,3 kB]
Get:4 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 liblvm2app2.2 amd64 2.02.133-1ubuntu10 [392 kB]
Get:5 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 libreadline5 amd64 5.2+dfsg-3build1 [99,5 kB]
Get:6 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 lvm2 amd64 2.02.133-1ubuntu10 [731 kB]
Fetched 1 784 kB in 0s (3 489 kB/s)
Selecting previously unselected package libdevmapper-event1.02.1:amd64.
(Reading database ... 257917 files and directories currently installed.)
Preparing to unpack .../libdevmapper-event1.02.1_2%3a1.02.110-1ubuntu10_amd64.deb ...
Unpacking libdevmapper-event1.02.1:amd64 (2:1.02.110-1ubuntu10) ...
Selecting previously unselected package liblvm2cmd2.02:amd64.
Preparing to unpack .../liblvm2cmd2.02_2.02.133-1ubuntu10_amd64.deb ...
Unpacking liblvm2cmd2.02:amd64 (2.02.133-1ubuntu10) ...
Selecting previously unselected package dmeventd.
Preparing to unpack .../dmeventd_2%3a1.02.110-1ubuntu10_amd64.deb ...
Unpacking dmeventd (2:1.02.110-1ubuntu10) ...
Selecting previously unselected package liblvm2app2.2:amd64.
Preparing to unpack .../liblvm2app2.2_2.02.133-1ubuntu10_amd64.deb ...
Unpacking liblvm2app2.2:amd64 (2.02.133-1ubuntu10) ...
Selecting previously unselected package libreadline5:amd64.
Preparing to unpack .../libreadline5_5.2+dfsg-3build1_amd64.deb ...
Unpacking libreadline5:amd64 (5.2+dfsg-3build1) ...
Selecting previously unselected package lvm2.
Preparing to unpack .../lvm2_2.02.133-1ubuntu10_amd64.deb ...
Unpacking lvm2 (2.02.133-1ubuntu10) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for systemd (229-4ubuntu21.2) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Setting up libdevmapper-event1.02.1:amd64 (2:1.02.110-1ubuntu10) ...
Setting up liblvm2app2.2:amd64 (2.02.133-1ubuntu10) ...
Setting up libreadline5:amd64 (5.2+dfsg-3build1) ...
Setting up liblvm2cmd2.02:amd64 (2.02.133-1ubuntu10) ...
Setting up dmeventd (2:1.02.110-1ubuntu10) ...
Setting up lvm2 (2.02.133-1ubuntu10) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for systemd (229-4ubuntu21.2) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for initramfs-tools (0.122ubuntu8.11) ...
update-initramfs: Generating /boot/initrd.img-4.13.0-39-generic
graeme@graeme-ThinkCentre:~$ sudo lvscan
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
graeme@graeme-ThinkCentre:~$
Sorry that I am bean-head when it comes to understanding internal computer function. Part of my accuse is that I am 72 and relatively recently started using computers. This comment you made - (if you do not boot from the built-in hard disk, but from a live system) I am not to sure what you mean. I tried to find the/no of the hard-disk but apparently failed.

If you do not have confidence in yourself, you should look for external help. Maybe there is some local Linux community in your vicinity which you can meet?

OK, thanks I guess we can call it a day. I don't have any group but maybe I can find one. By the way it's not about confidence, but knowledge and experience. Graeme