Seagate Personal Cloud can only ping on Windows CMD

[bistels]

After booting from sda7, it became version 18.1, updated again through web interface to 18.2.
The work is fully restored and all files, settings are in place. :woohoo

fvdw, thank you very much for your help. :punk

[ajornada]

Hi fvdw Team, it's me again, I started this thread 2 months ago,

The problem was initially solved, but it happened again, in a similar way. The led light keeps always blinking and it's inacessible.

Now, I cannot ping the Personal Cloud NAS via Windows Command (CMD) prompt, but, I connected the NAS directly to notebook LAN ethernet port, I set the IP of computer on 192.168.0.2, and gateway 192.168.0.10 and DNS 192.168.0.10. On fvdw-console I set 192.168.0.10 to NAS too.

1) Turned off NAS;
2) Opened fvdw Console
3) I have a Personal Cloud NAS, so I choosed ARMADA SRN12C UIMAGE
4) on waiting for U-boot screen I connected the power cable to NAS
5) The tftp transfer goes OK, and the Telnet window appears

The Telnet is giving timeout error, so I click on "Remote System" and it accepts the connection, and I goes to prompt:

root@sg-armada-370-sta:/ #

With Telnet connected, I tried to mount sda1 and sda7, and instal glibc mini and tools, the answers are below:

Test 1: Mount sda7

Code: Select all

mkdir /sda7
mount /dev/sda7 /sda7
mount: mounting /dev/sda7 on /sda7 failed: No such device or address

Test 2: Mount sda1

Code: Select all

mkdir /sda1
root@sg-armada-370-sta:/ # mount /dev/sda1 /sda1
mount: mounting /dev/sda1 on /sda1 failed: No such device or address

Test 3: glib tools and e2fsck
after fvdw-sl-programs, installed glib mini and tool

Code: Select all

e2fsck -y /dev/sda1
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such device or address while trying to open /dev/sda1
Possibly non-existent or swap device?

Some additional notes about the NAS behavior:
1) It has only one on/off button and a reset button. The on/off button doesn't work fine with fvdw, and when I ask to shutdown via webinterface it hangs the device and doesn't off
2) Is it possible that my hard drive inside the NAS is dying and I'm oftenly losing the sectors that keeps the interface and the system files?

Thanks in advance

[fvdw]

Indeed this looks like a bad disk behavior

What does this command give as output

Code: Select all

gdisk -l /dev/sda

[ajornada]

Hi fvdw, the answer to "gdisk" was

root@sg-armada-370-sta:/ # gdisk -l /dev/sda

Code: Select all

GPT fdisk (gdisk) version 0.8.5

Warning! Read error 5; strange behavior now likely!
Warning! Read error 5; strange behavior now likely!
Partition table scan:
  MBR: not present
  BSD: not present
  APM: not present
  GPT: not present

Creating new GPT entries.
Disk /dev/sda: 8089950 sectors, 3.9 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 00000000-0000-0000-0000-000000000000
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 8089916
Partitions will be aligned on 2048-sector boundaries
Total free space is 8089883 sectors (3.9 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name

root@sg-armada-370-sta:/ #

I don't know what means, but appears to not be good! :?

[Jocko]

@ fvdw
Maybe there are more information with dmesg

[fvdw]

No indeed that doesn't look good.

We had the same issue reported by a member in 2018 see https://plugout.net/viewtopic.php?f=28&t=2865&start=10
gdisk reports error 5 and only 8089950 sectors of 512 bytes each as capacity. Thats only about 4 GB.
Typical that that member had exactly the same problem.
Anyhow it means the biggest part of the disk is not accessible and the drive data cannot be read because of I/O (read) error. In other words a failing hard disk

I do not know a way to test it further on the nas itself using our standalone kernel and tools.I am afraid this disk has a fatal hardware error and that your data is lost.
You could try to connect it to another pc and use a disk test program of the manufacturer to a let it scan the disk to see whats wrong and if it can be repaired. If it is a seagate disk then you could use seagate tools.

[fvdw]

@ fvdw
Maybe there are more information with dmesg

I don't think so. According gdisk the disk has no partition table anymore and cannot be read meaning the first sectors containing the partition table cannot be read or are corrupt. Also it reports a capacity of only 3,9 GB.
Honestly speaking I think this disk is lost. As said he could try a disk test program of the manufacturer to see if the disk can be repaired