Seagate Personal Cloud can only ping on Windows CMD

[ajornada]

Hi everyone,

I have fvdw running on a Personal Cloud about 2 years. I used the procedure described on viewtopic.php?f=38&t=3274 to install it.

Somedays ago, I think because a eletrical energy fault, it doesn't bot anymore. It powers on, and start blink the led in white color, the blink is continuous, I waited for 24h+ and it doesn't stop.

I can ping the Personal Cloud on Windows CMD, and only this.

I tried to access WebInterface, and FTP as usually and cannot.

I tried fvdw-sl-assistant to scan, it doesnt find my Seagate Personal Cloud.

I tried Putty to SSH and it doesn't connect, but I don't know much about SSH and Putty so I can do something wrong.

What do you suggest? Remove Hard Disk and read on a HD bay?

I have a partial backup also. From one month ago. But I would like to keep using my Personal Cloud, so I need to put it to work.

Thanks.

[fvdw]

You mention this

I can ping the Personal Cloud on Windows CMD, and only this

That means it has an ip address. What exact response do you get when you ping the nas?

Anyhow to find out what is wrong please use fvdw-sl console (running in your windows pc) and load and start the armada standalone kernel (read the help pages of the fvdw-sl console) and connect with the telnet client that pops up.
If this succeeds give these commands

Code: Select all

mkdir /sda7
mount /dev/sda7 /sda7
ls -al /sda7/lacie-boot


And post here the output of the ls command

[ajornada]

1) The answer to ping command on windows cmd was:

ping 192.168.0.10

Disparando 192.168.0.10 com 32 bytes de dados:
Resposta de 192.168.0.10: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.0.10: bytes=32 tempo=4ms TTL=64
Resposta de 192.168.0.10: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.10: bytes=32 tempo=1ms TTL=64

Estatísticas do Ping para 192.168.0.10:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de
perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 0ms, Máximo = 4ms, Média = 1ms

Sorry for the portuguese-br Windows, but we can see normal ping return


2) Load and start standard kernel

fvdw-sl console connected easily, and I loaded and started standalone Armada Kernel as you asked.

Telnet opened sucessfully, I entered @root, and typed the commands.

The commands and answers are below:

root@sg-armada-370-sta:/ # mkdir /sda7
root@sg-armada-370-sta:/ # mount /dev/sda7 /sda7
root@sg-armada-370-sta:/ # ls -al /sda7/lacie-boot
total 8
drwxrwxr-x 2 root root 4096 Apr 9 2020 .
drwxr-xr-x 23 root root 4096 Apr 9 2020 ..
-rw-r--r-- 1 root root 0 Apr 9 2020 sda1boot
root@sg-armada-370-sta:/ #

Some extra details, while I was in Telnet terminal, the white blinking led, became an always on white led, and stopped blinking.

Now fvdw-assistant locates the NAS "sg-armada-370-sta"

In advance, thanks for answer so fast my initial question!

[Jocko]

Hi

Now fvdw-assistant locates the NAS "sg-armada-370-sta"

fvdw-sl assistant detects it because the nas does not start from the disk (sda1) and then I assume it will fail again when you perform a nas rebooting.

So to find where is the issue, you have to post

Code: Select all

mkdir /sda1
mount /dev/sda1 /sda1
cat /sda1/boot.log

[ajornada]

Code: Select all

mkdir /sda1
mount /dev/sda1 /sda1
cat /sda1/boot.log

Returned this:

mount: mounting /dev/sda1 on /sda1 failed: Invalid argument

So, I should replace sda1 to sda7 like fdvw user msg above on this thread?

[fvdw]

mmm...it seems file system on sda1 has a problem.
No changing command to sda7 is not necessary, lets see if we can repair the file system
Load standalone kernel and connect with telnet and give this command

Code: Select all

fvdw-sl-programs

choose option 4, upload and extract glibc mini and tools
When upload finished give command

Code: Select all

e2fsck -y /dev/sda1

and see if errors are found and repaired, if errors are repaired try to mount /dev/sda1 again

[ajornada]

So far, so good.

1) I uploaded and extracted glibc mini and tools, using your "fvdw-sl-programs", choosing option 4;

2) I gave the command "e2fsck -y /dev/sda1", the exit of this command is pasted below;

3) I mounted /dev/sda1, and run "cat /sda1/boot.log", the exit of this command is pasted below;

4) When I saw, a lot of "OK" on boot.log, I became hope, Unplugged the cable, and restarted Personal Cloud, and everything was fine, all the configuration that I made to fvdw web interface and even the files on the shares were recovered.

So now, I will do a file scan check, and probably make a donation!

You helped me very well. Thks. :applause :applause :applause :applause

Command: e2fsck -y /dev/sda1
e2fsck 1.41.14 (22-Dec-2010)
/dev/sda1: recovering journal
Error reading block 2048 (Attempt to read block from filesystem resulted in short read). Ignore error? yes

Force rewrite? yes

Superblock last mount time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set) Fix? yes

/dev/sda1: clean, 5868/32768 files, 44035/131072 blocks

Command: cat /sda1/boot.log
start boot log
is a physical machine
detect and set platform
srn21c
srn21c
UIMAGE-414133-ARMADA370_SRN21C-1
Current kernel: 4.14.133 #1 Sun Jul 28 15:49:01 CEST 2019
srn21c
srn21c
mount dev/pts
update dev nodes
booting using sda1 root file system...
enable IP forwarding...
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'iscsi_trgt' not found
start buttons control daemon
device = srn21c
source = buttons-nwsp2
buttons-nwsp2 daemon started
initializing date
Mon Jan 1 12:00:00 AMST 2018
create temporary passwd file
create temporary group file
set samba environment for version 3.0.37
configure loopback network interface
setting reboot and standby
srn21c
rebootd-nwsp2
srn21c
standbyd-nwsp2
starting php based setup routines step 1
* Initialize the volatile db file... [ OK ]
* Starting udevd... [ OK ]
* Finishing restore RAID devices... [ OK ]
* Found database configuration file... [ OK ]
* Updating Disks database... [ OK ]
* Starting mount of volumes...
- Mounting volume Vol-A: [ OK ]
* Finishing mount of volumes... [ OK ]
* Generating Hosts File... [ OK ]
* Configuring System Hostname... [ OK ]
* Configuring LAN interface... [ OK ]
* Initializing Timezone... [ OK ]
* Starting web server... [ OK ]
* Starting mount of internal USB ...
* Finishing mount internal USB ... [ OK ]
* Configuring Disks... [ OK ]
* Configuring Samba... [ OK ]
* Configuring System Users...
Root password: use default password
Set users, linux and samba accounts [ OK ]
* Starting Fvdw-sl Discovery Daemon... [ OK ]
start rpcbind service
starting php based setup routines step 2
* Starting dropbear... [ OK ]
* Kill temporary dropbear... [ OK ]
starting php based setup routines step 3
* Starting daemon update Hosts File... [ OK ]
* Starting mount of remote shares...
* Finishing mount shares... [ OK ]
* Starting FTP Service... [ OK ]
* Starting NTP client... [ OK ]
* Starting Minidlna Server... [ OK ]
* Starting Transmission Client... [ OK ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
This is fvdw-sl version: fvdw-sl 18.2
built on: October 18 2019

LAN IP address: 192.168.0.10 (DHCP)

Port configuration:

LAN -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
move smbd en nmbd db files away from ram disk to prevent hanging samba server
LED settings
else loop1 finished
rcS finished

[fvdw]

glad to hear that your problem is solved :thumbup

[bistels]

Hello.

I also had a "Seagate Personal Cloud can only ping on Windows CMD" problem.

After executing "e2fsck -y / dev / sda1" an error of length 0 was found in some place and was successfully cleaned up.
Now SRN21 starts successfully, except for the web interface is gone).
Work: ssh, smb, transmission. I think those blocks that cleaned on sda1 contained files for the web server.

How can I overwrite the current firmware whith keeping settings and files (or files)?

My device-SRN21 with fwdv-18.2.

Thank you!

start boot log
is a physical machine
detect and set platform
srn21c
srn21c
UIMAGE-414133-ARMADA370_SRN21C-1
Current kernel: 4.14.133 #1 Sun Jul 28 15:49:01 CEST 2019
srn21c
srn21c
mount dev/pts
update dev nodes
booting using sda1 root file system...
enable IP forwarding...
run udevstart to update dev nodes when necessary
inserting kernel modules:
modprobe: module 'iscsi_trgt' not found
start buttons control daemon
device = srn21c
source = buttons-nwsp2
buttons-nwsp2 daemon started
initializing date
Mon Jan 1 12:00:00 FET 2018
create temporary passwd file
create temporary group file
set samba environment for version 4.x
configure loopback network interface
setting reboot and standby
srn21c
rebootd-nwsp2
srn21c
standbyd-nwsp2
starting php based setup routines step 1
* Initialize the volatile db file... [ OK ]
* Starting udevd... [ OK ]
* Finishing restore RAID devices... [ OK ]
* Found database configuration file... [ OK ]
* Updating Disks database... [ OK ]
* Starting mount of volumes...
- Mounting volume Vol-A: [ OK ]
- Mounting volume USB-B-1: [ USB : mounted later ]
* Finishing mount of volumes... [ OK ]
* Generating Hosts File... [ OK ]
* Configuring System Hostname... [ OK ]
* Configuring LAN interface... [ OK ]
* Initializing Timezone... [ OK ]
* Starting web server... * Starting mount of internal USB ...
* Finishing mount internal USB ... [ OK ]
* Configuring Disks... [ OK ]
* Configuring Samba... [ OK ]
* Configuring System Users...
Root password: use default password
Set users, linux and samba accounts [ OK ]
* Starting Fvdw-sl Discovery Daemon... [ OK ]
start rpcbind service
starting php based setup routines step 2
* Starting dropbear... [ OK ]
* Kill temporary dropbear... [ OK ]
starting php based setup routines step 3
* Starting daemon update Hosts File... [ OK ]
* Starting USB Spin-down Guard... [ OK ]
* Starting NTP Server ... [ OK ]
* Starting mount of remote shares...
* Finishing mount shares... [ OK ]
* Starting NTP client... [ OK ]
* Starting vnstat daemon... [ OK ]
* Starting Transmission Client... [ OK ]
starting php based setup routines step banner


*** fvdw-sl NAS firmware
This is fvdw-sl version: fvdw-sl 18.2
built on: October 18 2019

LAN IP address: 192.168.1.5 (DHCP)

Port configuration:

LAN -> eth0
php based setup routines finished
web permission on resolv.conf
set device tuning for dms performance
move smbd en nmbd db files away from ram disk to prevent hanging samba server
LED settings
else loop1 finished
rcS finished

[fvdw]

If you have still ssh access, connect via it and on command line give command

Code: Select all

ls -al /lacie-boot

It should give as output sda1boot
If this is the case give command

Code: Select all

unlink /lacie-boot/sda1boot

Repeat the ls command to see if the file is gone
If so give command

Code: Select all

reboot

Please be aware that this procedure will force the nas to boot from sda7 probably containg fvdw-sl 18-1.
So 18-1 will come up after reboit and you will need to upgrade to 18-2 again.