At startup, the last 2 led remain solid

[Draftmancorp]

Hi all,
I've a problem today. It's almost 2 weeks that i do not power on my Nas.
Today i power it on, and i'm notice that no ping come from that nas.

So i see behind it and i notice that the last 2 led remain solid on blue. What this is mean?

the nas is not reachable from web page.
not reachable from Windows ip ping.
is not reachable from putty.

thanks.

[Draftmancorp]

other info:

i tried to reboot it by the hard switch button.
I can see by leds and hear all 5 disks start spinning once by once, like a regular boot. First, secondo, third etc...
After all 5 disks are spinning, the last 2 HDD led return solid blue.
the first 3 leds remain off.
(i used the configuration for hide all leds of the nas in the fvdw web page, for energy saving and avoid the light)

this is the situation. 3 led off (as they have to be!) and last 2 led blue on.
and i have no way to connect to the nas.
@jocko any idea? :please i'm very unlucky with this nas.

[fvdw]

Well by now you should now how to investigate such problems
Load the standalone kernel and investigate content of boot.log on sda7 and sda1 or sda2 (dependent of system booting from sda1 or sda2)

[Draftmancorp]

Well by now you should now how to investigate such problems
Load the standalone kernel and investigate content of boot.log on sda7 and sda1 or sda2 (dependent of system booting from sda1 or sda2)

sems the PC can't see the u-boot...

Immagine 2022-09-23 141156.jpg

[Draftmancorp]

ok i made it with the laptop. dunno why the desktop can't see the u-boot.

sems no good answer:

Immagine 2022-09-23 143456.jpg

[Draftmancorp]

Problem opening /dev/sdc for reading! Error is 6.
This is the 4° disk,(the first of two with blue solid led)

Code: Select all

root@fvdw-sta-kirkwood:/ # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
unused devices: <none>
root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 485424C6-3BFF-4670-9703-E660DB98763B
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 5803998 sectors (2.8 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   8         5804032      3907029134   1.8 TiB     8300  Linux filesystem
root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sdb
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): F1004E80-3AD7-4A21-9A29-A612310467E9
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 5803998 sectors (2.8 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   8         5804032      3907029134   1.8 TiB     8300  Linux filesystem
root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sdc
GPT fdisk (gdisk) version 0.8.5
Problem opening /dev/sdc for reading! Error is 6.
root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sdd
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdd: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): F1004E80-3AD7-4A21-9A29-A612310467E9
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 5803998 sectors (2.8 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   8         5804032      3907029134   1.8 TiB     8300  Linux filesystem
root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sde
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sde: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 485424C6-3BFF-4670-9703-E660DB98763B
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 5803998 sectors (2.8 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   8         5804032      3907029134   1.8 TiB     8300  Linux filesystem
root@fvdw-sta-kirkwood:/ #


[Draftmancorp]

In the meantime, i try togive you many information i can get:

Code: Select all

root@fvdw-sta-kirkwood:/ # fdisk -l /dev/sda

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1      242252  1953514583+ ee EFI GPT
root@fvdw-sta-kirkwood:/ #


[Draftmancorp]

Code: Select all

root@fvdw-sta-kirkwood:/ # e2fsck -n /dev/md0
-sh: e2fsck: not found

[Draftmancorp]

Code: Select all

bin/
bin/bash
bin/dd-64


                         Upload and extract glibc mini and tools script version 1.0 ┐
                         │                                                          │ 
                         │ Archive successfully extracted                           │ 
                         │                                                          │ 
                         │  ┌────────────────────────────────────────────────────┐  │ 
                         │  │                        100%                        │  │ 
                         │  └────────────────────────────────────────────────────┘  │ 
                         └──────────────────────────────────────────────────────────┘ 
                           
root@fvdw-sta-kirkwood:/ # e2fsck -y /dev/sda5
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such device or address while trying to open /dev/sda5
Possibly non-existent or swap device?
root@fvdw-sta-kirkwood:/ # e2fsck -y /dev/sda7
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such device or address while trying to open /dev/sda7
Possibly non-existent or swap device?
root@fvdw-sta-kirkwood:/ # 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?
root@fvdw-sta-kirkwood:/ # e2fsck -y /dev/sda2
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such device or address while trying to open /dev/sda2
Possibly non-existent or swap device?
root@fvdw-sta-kirkwood:/ # e2fsck -y /dev/sda4
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such device or address while trying to open /dev/sda4
Possibly non-existent or swap device?
root@fvdw-sta-kirkwood:/ #


[Draftmancorp]

for give a refreshing to your memory, this is the RAID nas that I restored soldering a new 2.7v capacitor: http://plugout.net/viewtopic.php?f=26&t=3604&start=70
It worked greatly since now...

(i think something wrong in the disk n° 4)