How to acces the HDD via UBuntu LInux

[angelp25]

Hello to everyone.

I am having issues with my case, both PCB, the HDDs and the white case were broken, now i had bought the HDDS PCB and it runs, but i need to acces the info via Ubuntu and i am having issues.

First: GParted stuck on Analysing /dev/sda

WHit commad: sudo lsblk appears:

Code: Select all

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0    7:0    0   500M  0 loop
loop1    7:1    0   1,9G  0 loop /rofs
loop2    7:2    0  88,5M  1 loop /snap/core/7270
loop3    7:3    0  54,4M  1 loop /snap/core18/1066
loop4    7:4    0  42,8M  1 loop /snap/gtk-common-themes/1313
loop5    7:5    0 149,9M  1 loop /snap/gnome-3-28-1804/67
loop6    7:6    0     4M  1 loop /snap/gnome-calculator/406
loop7    7:7    0  14,8M  1 loop /snap/gnome-characters/296
loop8    7:8    0  1008K  1 loop /snap/gnome-logs/61
loop9    7:9    0   3,7M  1 loop /snap/gnome-system-monitor/100


I suppose the 3Tb partition is broken or somethng like that.

THanks.

Even GPARTED Live gave me this message:
[ img ]

[fvdw]

Where does this disk comes from? It is so to see not a disk setup for fvdw-sl firmware. Does it contain data you want to recover?


What does gdisk and fdisk gives as output?

Seems the partition table is corrupt or (partly) deleted.
The input output errors may be caused by disk bad sectors.

PS. As it is an 4 TB disk using msdos type partition table will only let you use 2TB of the disk, you will need to use GPT partition table to use the total capacity

[angelp25]

Where does this disk comes from? It is so to see not a disk setup for fvdw-sl firmware. Does it contain data you want to recover?


What does gdisk and fdisk gives as output?

Seems the partition table is corrupt or (partly) deleted.
The input output errors may be caused by disk bad sectors.

PS. As it is an 4 TB disk using msdos type partition table will only let you use 2TB of the disk, you will need to use GPT partition table to use the total capacity

Hi, thanks for reply.

The disk is a 3Tb Lacie Cloudbox, both board were broken, so now i have repaired with a new board the HDD 3Tb Seagate.

I t dows not have fvdw firmware, is with the original firmware.

I want to acces to the 2,7Tb partition, supposed to be the 8th.

With R-Linux, the recovery program, it says that has a lot of bad sectors, gives me E/S error on many sectors and tells me the capacity is 128Gb not 3Tb. Maybe is not the correcto program.

How can i know if the disk is corrupted or even recover some data.

Could you give me some nerd step by step guide.

Thanks.

[fvdw]

ok that makes it a little more clear.

As far as I can see the lsblk output that you posted is not related to this 3 TB disk you are referring to. This because it concern a loop device and data doesn't match in any way with output of gparted that sda is reported to be 4GB and sdb 250 GB.

Furthermore lsblk output is not specifying a lacie partition table but so to see another linux system, probably the linux system you are running on your pc

The fact that lsblk does not list your disk means probably that is not accessible.
You could try to use command blkid and lsscsi to see if they find the disk and the partitions


This is an example of an original couldbox partition table, in this example a 2TB disk

Code: Select all

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048            4095   1024.0 KiB  EF02  grub_core      fvdw: ef02 is bios boot partition
   2            4096          397311   192.0 MiB   8300  boot_rescue    fvdw: 8300 is a linux file system
   3          397312          399359   1024.0 KiB  8300  nv_data   fvdw: 8300 is a linux file system
   4          399360         3545087   1.5 GiB     FD00  root_1      fvdw: fd00 Linux raid
   5         3545088         6690815   1.5 GiB     FD00  root_2
   6         6690816         8787967   1024.0 MiB  FD00  var
   7         8787968         9312255   256.0 MiB   FD00  swap
   8         9312256      3907029134   1.8 TiB     FD00  user_data

The data partition is partition 8, as you see lacie uses raid for that partition it is complicated to read data from it as first you need to assemble the raid array

[fvdw]

to try to recover your data, this topic could be helpfull
https://plugout.net/viewtopic.php?f=28&t=2499

[angelp25]

ok that makes it a little more clear.

As far as I can see the lsblk output that you posted is not related to this 3 TB disk you are referring to. This because it concern a loop device and data doesn't match in any way with output of gparted that sda is reported to be 4GB and sdb 250 GB.

Furthermore lsblk output is not specifying a lacie partition table but so to see another linux system, probably the linux system you are running on your pc

The fact that lsblk does not list your disk means probably that is not accessible.
You could try to use command blkid and lsscsi to see if they find the disk and the partitions


This is an example of an original couldbox partition table, in this example a 2TB disk

Code: Select all

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048            4095   1024.0 KiB  EF02  grub_core      fvdw: ef02 is bios boot partition
   2            4096          397311   192.0 MiB   8300  boot_rescue    fvdw: 8300 is a linux file system
   3          397312          399359   1024.0 KiB  8300  nv_data   fvdw: 8300 is a linux file system
   4          399360         3545087   1.5 GiB     FD00  root_1      fvdw: fd00 Linux raid
   5         3545088         6690815   1.5 GiB     FD00  root_2
   6         6690816         8787967   1024.0 MiB  FD00  var
   7         8787968         9312255   256.0 MiB   FD00  swap
   8         9312256      3907029134   1.8 TiB     FD00  user_data

The data partition is partition 8, as you see lacie uses raid for that partition it is complicated to read data from it as first you need to assemble the raid array

blkid show me this code, when the hdd is directly connected

Code: Select all

ubuntu@ubuntu:~$ blkid
/dev/sdb1: LABEL="HDD 3 - 2TB" UUID="48A83758A83743AA" TYPE="ntfs" PARTUUID="de2cd2ce-01"
/dev/sdc1: LABEL="Reservado para el sistema" UUID="2C22D87922D84A0A" TYPE="ntfs" PARTUUID="5714fa6d-01"
/dev/sdc2: UUID="9894DB3F94DB1F16" TYPE="ntfs" PARTUUID="5714fa6d-02"
/dev/sdc3: UUID="7E429DF9429DB67D" TYPE="ntfs" PARTUUID="5714fa6d-03"
/dev/sdd1: LABEL="HDD 2 - 1TB" UUID="01D4D8DCEF1A4CF0" TYPE="ntfs" PARTUUID="1b650f8b-01"
/dev/sdf1: LABEL="MYLINUXLIVE" UUID="30C7-9661" TYPE="vfat" PARTUUID="0d82903d-01"
/dev/loop0: UUID="38657318-a690-244e-ab3e-6a69db1c2975" TYPE="ext2"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"


lsscsi show me this code

Code: Select all

[1:0:0:0]    disk    ATA      ST3000DM001      CC27  /dev/sda
[3:0:0:0]    disk    ATA      TOSHIBA MQ01ABB2 0U    /dev/sdb
[4:0:0:0]    disk    ATA      Samsung SSD 840  BB6Q  /dev/sdc
[5:0:0:0]    disk    ATA      WDC WD10EARS-22Y 0A80  /dev/sdd
[6:0:0:0]    disk    USB Mass  Storage Device  1.00  /dev/sde
[7:0:0:0]    disk    Kingston DataTraveler 2.0 1.00  /dev/sdf

The 3Tb HDD is ST3000DM001

Even, i want to say that when the HDD turns on it makes 5 noises, like knocks and after that it starts.

GPARTED and FDISK stuck analysing the HDD3TB device.... The HDD board is new, because the previous board was broken.

When using the code mdadm --assemble /dev/md0 /dev/sda8:

Code: Select all

sudo mdadm --assemble /dev/md0 /dev/sda8
mdadm: cannot open device /dev/sda8: No such file or directory
mdadm: /dev/sda8 has no superblock - assembly aborted


[fvdw]

For me its clear, your sda harddisk is not accesible, although it is detected by lsscsi on the scsi bus. But blkid doesn't find it so there is no partition table found. An if fdisk is not able to read the disk info, as how many heads, cilinders, sectors
and sector size, then all this means your disk is defective, or in other words it is dead.

[angelp25]

For me its clear, your sda harddisk is not accesible, although it is detected by lsscsi on the scsi bus. But blkid doesn't find it so there is no partition table found. An if fdisk is not able to read the disk info, as how many heads, cilinders, sectors
and sector size, then all this means your disk is defective, or in other words it is dead.

There is a way to format it? and unse as a internal hard drive on my desktop.

[fvdw]

Nope, if it is defective you can not use it anymore.

You could connect to another PC for instance using sata->usb interface or connecting it directly to a sata port. But from what you posted you seem to have done that already. If so that means game over for this disk

[angelp25]

Nope, if it is defective you can not use it anymore.

You could connect to another PC for instance using sata->usb interface or connecting it directly to a sata port. But from what you posted you seem to have done that already. If so that means game over for this disk

I want to buy a new white casing, the seller says it comes with fvdw firmware. The firmware is storaged inside the hddd no the white casing motherboard, so maybe, this new motherboard and white casing will revive my old 3Tb HDD with original firmware?

I can buy a 8Tb HDD and put it to the working white case?

Thanks.