Author Topic: LS-WXL. Disk 2 damaged (3 pcs one sec blinging red)?  (Read 325 times)

navinavi

  • Calf
  • *
  • Posts: 5
LS-WXL. Disk 2 damaged (3 pcs one sec blinging red)?
« on: October 12, 2020, 09:54:29 am »
LS-WXL with 2 pcs 2 TB disks. Error LED blinkin: 3 times red (duration 1 sec).


LinkStation NAS Navigator: SYSTEM - STORAGE


DISKS

Disk 1: Array 1. Unitname ST20000DM001-1CH1. Unit capasity -    Amount used -    % Used -
Disk 2: Error


So Disk 1 can not be read and disk 2 is in Error mode. Removing Disk 2: same situation.


RAID ARRAY
Array 1: Raid mode = Not Configured.

I am pretty sure that this should be RAID1.

Shared Folders are OK (another way: NAS Navigator showing folders)  but can not access any data of LX-WXL would not work as storage in my Network anymore.

Is the only problem that Disk 2 is broken and replacing it would solve this problem (because RAID 1).  I do not understand why RAID array is: Not configured. Do we have any instruction how to build up this array with new disk?
« Last Edit: October 12, 2020, 10:10:30 am by navinavi »

davo

  • Really Big Bull
  • VIP
  • *
  • Posts: 5958
Re: LS-WXL. Disk 2 damaged (3 pcs one sec blinging red)?
« Reply #1 on: October 13, 2020, 09:30:54 am »
If the RAID is showing as not configured then you had RAID0, not RAID1.

The data on the unit is now gone so you will need to refer to your backup.
PM me for TFTP / Boot Images / Recovery files  LSRecovery.exe file.

navinavi

  • Calf
  • *
  • Posts: 5
Re: LS-WXL. Disk 2 damaged (3 pcs one sec blinging red)?
« Reply #2 on: October 13, 2020, 11:27:26 am »
On Linux / Ubuntu:

DISK1


Gpareted
could not shown anything of this.

Filesystems:

Disk (2,0 Tt)
ST2000DM001 (2000 398 934016 bytes)

/dev/md0
Size 0,0 kt
Array is empty




lsblk

NAME  MAJ:MIN  RM  SIZE   R0   TYPE   MOUNTPOINT
sdb       8:16        0  1 ,8 T    0   disk


sudo blkid /dev/sdb


/dev/sdb: PTTYPE="PMBR"


sudo fdisk -l /dev/sdb

GPT PMRB size mismatch (3907029167 != 488378645) will be corrected by w/rite)
Disk /dev/sdb: 1,8 TiB 20003989934016 bytes 488378648 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal) 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0X0000000

Units             starting    end    sectors           Size    ID  Type
/dev/sdb1    1  3907029167    3907029167   14,7T  ee  GPT



sudo parted /dev/sdb print

Error: /dev/sdb: unreconised disk label
Model ST20000DM  001-1CH64  (scsi)
Disk /dev/sdb/ 2000GB
Sector size (logical/physical): 4096B/4096B
Partition Table: unknown
Disk Flags:


This diksk is not founded on fstab table! There is only sda mentioned (configured)

Because I could not found correct UUID of this disk (sudo blkid /dev/sdb), I can not add this for fstab.

So I can not mount thisdisk to Ubuntu. (sudo mount -a)

Is this disk really empty or does this related to RAID1. Should I try to mount both disks to Ubuntu in same time?

---------------------------------------------------------

DISK2


Gpareted


I/O error during read on /dev/sbd   


Filesystems:

Disk (4,1 Tt)
ST2000DM001 (2000 398 934016 bytes)
Size 4,1 Gt (4142 054 400 byte)
Disk is Ok, one bad sector

/dev/md0
Size ------



NOTE!

DISK SIZE IS 2 TiB but filesystems says 4,1 Gt



lsblk

NAME  MAJ:MIN  RM  SIZE   R0   TYPE   MOUNTPOINT

NOT SHOW ANYTHING ABOUT THIS DIKS


sudo fdisk -l /dev/sdb

Can not open this unit: I/O Error



sudo parted /dev/sdb print

Error: /dev/sdb: unreconised disk label
Model ST20000DM  001-1CH64  (scsi)
Disk /dev/sdb/ 4142 MB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:


NOTE! Sector size is different than on Disk1 (4096B)


This diksk is not founded on fstab table! There is only sda mentioned (configured)

Because I could not found correct UUID of this disk (sudo blkid /dev/sdb), I can not add this for fstab.

So I can not mount thisdisk to Ubuntu. (sudo mount -a)


Is this disk broken or only lost partition or something?

Can I do anything else? Last backup is quite old (unfortunately).

1000001101000

  • Debian Wizard
  • Big Bull
  • *****
  • Posts: 849
  • There's no problem so bad you cannot make it worse
Re: LS-WXL. Disk 2 damaged (3 pcs one sec blinging red)?
« Reply #3 on: October 13, 2020, 12:35:29 pm »
Use mdadm to print out raid info for the data array(s):
Code: [Select]
mdadm 容xamine /dev/sd*6
That will give you information like raid0 vs raid1 and status

navinavi

  • Calf
  • *
  • Posts: 5
Re: LS-WXL. Disk 2 damaged (3 pcs one sec blinging red)?
« Reply #4 on: October 13, 2020, 02:48:31 pm »
Thanks for answer, but I already done that:

mdadm 容xamine /dev/sdb

=> No superblock detected.

But I will use this mdadm 容xamine /dev/sd*6 and try it again, after I finnished using Testdisk.

Right now I am using Testdisk to scan / analayze can I recover partition / Superblock. 17% done:

Cylinder 5244 / 30399: 17%

Founded:

MS Data  256   250351     250096
Linix Raid    450359962500080  250367    2000784  (md0)
Linux Raid      250368    10248680      9998313   [UNINSPECTED-EMCBE:1]
MS Data        some sectors.....
MS Data        some sectors.....
Unkown        some sectors.....    [~]T and some chinese mark ]
MS Data        some sectors.....
MS data        some sectors.....
Ms Data        some sectors.....

1000001101000

  • Debian Wizard
  • Big Bull
  • *****
  • Posts: 849
  • There's no problem so bad you cannot make it worse
Re: LS-WXL. Disk 2 damaged (3 pcs one sec blinging red)?
« Reply #5 on: October 13, 2020, 02:52:24 pm »
The superblocks will be on partitions rather than disks so not finding one on sdb makes sense.

if your testdisk scan is read-only it should be safe to examine the superblocks while it's running.

navinavi

  • Calf
  • *
  • Posts: 5
Re: LS-WXL. Disk 2 damaged (3 pcs one sec blinging red)?
« Reply #6 on: October 13, 2020, 03:29:43 pm »
Yes, TestDisk is on read only mode.

mdadm 容xamine /dev/sd*6

Gives: Cannot open /dev/sd*6  No such file or directory.

But

mdadm 容xamine /dev/sd*

Gives (sda is computers own internal harddisk):

/dev/sda:
   MBR Magic  : aa55
Partition (0) :    500115456  sector  at  2048 (type 83)
mdadm: No md superblock detected on /dev/sda1
mdadm: No md superblock detected on /dev/sdb.

« Last Edit: October 13, 2020, 03:32:03 pm by navinavi »

1000001101000

  • Debian Wizard
  • Big Bull
  • *****
  • Posts: 849
  • There's no problem so bad you cannot make it worse
Re: LS-WXL. Disk 2 damaged (3 pcs one sec blinging red)?
« Reply #7 on: October 13, 2020, 03:35:08 pm »
maybe we should take a step back and start by listing your partitions:
Quote
lsblk

navinavi

  • Calf
  • *
  • Posts: 5
Re: LS-WXL. Disk 2 damaged (3 pcs one sec blinging red)?
« Reply #8 on: October 13, 2020, 04:36:44 pm »
Okkey, but first backround.

I have two 2 TiB disk installed on Buffalo LX-WXL. See first post. I removed both disk and installed those alternately for my computer (Ubuntu) USB port. One seems to be broken (Disk 2). So there is SDA installed on this computer (partitions loop0 to loop20 and sda (238,5 GB)  -> sda1 (238,5 GB). Loops are part of Gnome and size is 2 to 97 MB.  This Disks workin correct. I am not running live-linux, in this computer there is no other operating system than Ubuntu.

lsblk: sda-partitions are fine. Do you need this information (I have to copy these information manually to this computer because this computer what I used right now is different).

But sdb (this USB harddisk):

sdb    8:16  0  1,8T  0  disk

So it seems that there is no any partition?

Cat fstab:

Only sda1 and swapfile is listed.

1000001101000

  • Debian Wizard
  • Big Bull
  • *****
  • Posts: 849
  • There's no problem so bad you cannot make it worse
Re: LS-WXL. Disk 2 damaged (3 pcs one sec blinging red)?
« Reply #9 on: October 13, 2020, 10:15:54 pm »
If it were me my goal would be to determine the state of the raid array and if possible re-assemble it to recover the data.

The first step of that process would be to identify the partition that housed the data. It will be the biggest one on the disk. Then I would use mdadm to examine the superblock.