Asustor AS7112R NAS HDDs not detected

Asustor AS7112R NAS HDDs not detected

  1. Customer contacted support saying HDDs 2,3,6, and 7 were not being detected after a power failure.


Unit was sent for repair to ASUSTOR and they replaced the backplane

Issue was still present after this replacement.

Solution:

1. Login as root in terminal with one hdd connected

2.       Confirm only one drive is connected
# toolbox nasstat -disk
# cat /proc/partitions

3.       Obtain path of connected drive
# cat /proc/partitions
Output will have only one listing that starts with sd
Then the path of the drive is /dev/sdX (X is whatever letter is shown in output)

4.       Proceed to erase the first 512M of the connected drive
# dd if=/dev/zero of=/dev/sdX bs=1M count=512

5. Perform GUI setup to initiate NAS




6. Once setup is complete, proceed to insert the remaining drives one-by-one



Every drives should show up under storage manager as you insert them.

7. Enable SSH is GUI



8. SSH into the NAS
NOTE 1: you might have to reset ssh keys on host to connect again





C:\Users\Mbuzz>ssh admin@192.168.1.210 -p 22
The authenticity of host '192.168.1.210 (192.168.1.210)' can't be established.
ECDSA key fingerprint is SHA256:o5CdFSzVDrNcGh6xKrrI3ZhEJAUePxCrf6JoAiI/jdI.
Are you sure you want to continue connecting (yes/no/[fingerprint])? y
Please type 'yes', 'no' or the fingerprint: yes
Warning: Permanently added '192.168.1.210' (ECDSA) to the list of known hosts.
Password:
admin@AS5304T-81A9:/volume1/home/admin $

NOTE 2: use the login that you made during GUI setup for ssh and escalate to "su" as shown:



9. Double check if all drives are populated by running the following command
# toolbox nasstat -disk

10. In the GUI migrate the first disk into the desired RAID configuration




NOTE: you can only move up raid configs (ie 1 to 5, 5 to 6 etc…)

Following example is for making RAID 10 with 4 drives (1 is initialized & 2-4 is joined with it to make RAID 10)








11. Create additional RAID partitions by going into:
Storage Manager -> Volume -> Create -> Advanced Setup







12. FINAL Volume overview after setting up two volumes:




ASUSTOR Terminal Commands & Explainations:

# toolbox nasstat -disk

displays connected disks and info



admin@NAS-ASTR-180:/volume1/home/admin $ toolbox nasstat -disk
SATA disks:
  SATA1 - Disk Id: [0x00, 0], Size: [9314] GB (9314 GB), Model: [TOSHIBA HDWG11A] Serial: [Z930A026FBDG]
    Dev [sda], Id: [0], Type/Port/Slot: [0/0/0], Box/Hub/Path: [0/0/0x000], Raid/Layout/Part/Nvme: [1/1/4/0]
    Sector: [512], Halt/State: [0x00/0x00], Power Mode: [0], Rot/Trim/Dzat: [1/0/0], Init/HAdd/Fast: [1/0/0]
  SATA2 - Disk Id: [0x01, 1], Size: [9314] GB (9314 GB), Model: [TOSHIBA HDWG11A] Serial: [Z910A0NDFBDG]
    Dev [sdb], Id: [1], Type/Port/Slot: [0/0/1], Box/Hub/Path: [0/0/0x000], Raid/Layout/Part/Nvme: [1/1/4/0]
    Sector: [512], Halt/State: [0x00/0x00], Power Mode: [0], Rot/Trim/Dzat: [1/0/0], Init/HAdd/Fast: [1/0/0]

Dump all NAS disks:
  Dev sda - Id: [0], Size: [9314] GB (9314 GB), Model: [TOSHIBA HDWG11A] Serial: [Z930A026FBDG]
    Alias: [SATA1], Disk Id: [0x00, 0], Type/Port/Slot: [0/0/0], Box/Hub/Path: [0/0/0x000], Raid/Layout/Part/Nvme: [1/1/4/0]
    Sector: [512], Halt/State: [0x00/0x00], Power Mode: [0], Rot/Trim/Dzat: [1/0/0], Init/HAdd/Fast: [1/0/0]
  Dev sdb - Id: [1], Size: [9314] GB (9314 GB), Model: [TOSHIBA HDWG11A] Serial: [Z910A0NDFBDG]
    Alias: [SATA2], Disk Id: [0x01, 1], Type/Port/Slot: [0/0/1], Box/Hub/Path: [0/0/0x000], Raid/Layout/Part/Nvme: [1/1/4/0]
    Sector: [512], Halt/State: [0x00/0x00], Power Mode: [0], Rot/Trim/Dzat: [1/0/0], Init/HAdd/Fast: [1/0/0]
  Dev sdc - Id: [2], Size: [0] MB (0 GB), Model: [ADATA IUM01-512MFHL] Serial: [121071111710001955]
    Alias: [DOM], Disk Id: [0xB0, 176], Type/Port/Slot: [5/0/0], Box/Hub/Path: [0/0/0x000], Raid/Layout/Part/Nvme: [0/-1/3/0]
    Sector: [512], Halt/State: [0x80/0x00], Power Mode: [0], Rot/Trim/Dzat: [0/0/0], Init/HAdd/Fast: [0/0/0]

admin@NAS-ASTR-180:/volume1/home/admin $

Below is same command in our production Asustor (192.168.1.X)



# dmesg

show logs



admin@NAS-ASTR-180:/volume1/home/admin $ dmesg 
[    0.000000] Linux version 5.13.x (root@sw1-dailybuild) (x86_64-asustor_x64_g3_2020.12.24-linux-gnu-gcc (crosstool-NG 1.24.0) 7.4.0, GNU ld (crosstool-NG 1.24.0) 2.32) #1 SMP Wed Jul 13 00:14:49 CST 2022
[    0.000000] Command line: BOOT_IMAGE=(hd0,gpt2)/bzImage console=ttyS0,115200n8 bootpart=2 uuid=16587257-2f06-4a65-8b1b-8eadcaa6ab6e
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Hygon HygonGenuine
[    0.000000]   zhaoxin   Shanghai
[    0.000000] x86/fpu: x87 FPU will use FXSAVE
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000006efff] usable
[    0.000000] BIOS-e820: [mem 0x000000000006f000-0x000000000006ffff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x0000000000070000-0x000000000008ffff] usable
[    0.000000] BIOS-e820: [mem 0x0000000000090000-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000007a4befff] usable
[    0.000000] BIOS-e820: [mem 0x000000007a4bf000-0x000000007aebefff] reserved
[    0.000000] BIOS-e820: [mem 0x000000007aebf000-0x000000007bfbefff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000007bfbf000-0x000000007bffefff] ACPI data
[    0.000000] BIOS-e820: [mem 0x000000007bfff000-0x000000007bffffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000e00f8000-0x00000000e00f8fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed01000-0x00000000fed01fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ffc00000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000017fffffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] efi: EFI v2.40 by INSYDE Corp.
[    0.000000] efi: ACPI 2.0=0x7bffe014 SMBIOS=0x7a84f000 ESRT=0x7a852718
[    0.000000] SMBIOS 2.8 present.
[    0.000000] DMI: Insyde AS61xx/Type2 - Board Product Name, BIOS V2.23 06/02/2016
[    0.000000] tsc: Detected 1600.000 MHz processor
[    0.002901] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.002911] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.002924] last_pfn = 0x180000 max_arch_pfn = 0x400000000
[    0.002976] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
[    0.003383] last_pfn = 0x7c000 max_arch_pfn = 0x400000000
[    0.010498] esrt: Reserving ESRT space from 0x000000007a852718 to 0x000000007a852750.
[    0.011687] Secure boot could not be determined
[    0.011691] RAMDISK: [mem 0x3612a000-0x3708cfff]
[    0.011702] ACPI: Early table checksum verification disabled
[    0.011710] ACPI: RSDP 0x000000007BFFE014 000024 (v02 INSYDE)
[    0.011722] ACPI: XSDT 0x000000007BFFE120 000094 (v01 INSYDE INSYDE   00000003      01000013)
[    0.011738] ACPI: FACP 0x000000007BFFA000 00010C (v05 INSYDE INSYDE   00000003 ACPI 00040000)
[    0.011754] ACPI: DSDT 0x000000007BFEA000 00ABBE (v02 INSYDE INSYDE   00000003 ACPI 00040000)
[    0.011766] ACPI: FACS 0x000000007BFBB000 000040
[    0.011776] ACPI: UEFI 0x000000007BFFD000 000236 (v01 INSYDE INSYDE   00000001 ACPI 00040000)
[    0.011788] ACPI: UEFI 0x000000007BFFB000 000042 (v01 INSYDE INSYDE   00000000 ACPI 00040000)
[    0.011799] ACPI: APIC 0x000000007BFF9000 000084 (v03 INSYDE INSYDE   00000003 ACPI 00040000)
[    0.011810] ACPI: MCFG 0x000000007BFF8000 00003C (v01 INSYDE INSYDE   00000003 ACPI 00040000)
[    0.011822] ACPI: SLIC 0x000000007BFF7000 000176 (v01 INSYDE INSYDE   00000003 ACPI 00040000)
[    0.011833] ACPI: WDAT 0x000000007BFF6000 0001C4 (v01 INSYDE INSYDE   00000003 ACPI 00040000)
[    0.011844] ACPI: WDRT 0x000000007BFF5000 000047 (v01 INSYDE INSYDE   00000003 ACPI 00040000)
[    0.011855] ACPI: SSDT 0x000000007BFE9000 000763 (v01 INSYDE CpuPm    00003000 ACPI 00040000)
[    0.011867] ACPI: SSDT 0x000000007BFE8000 000290 (v01 INSYDE Cpu0Tst  00003000 ACPI 00040000)
[    0.011878] ACPI: SSDT 0x000000007BFE7000 00017A (v01 INSYDE ApTst    00003000 ACPI 00040000)
[    0.011889] ACPI: SSDT 0x000000007BFE6000 000DF9 (v01 INSYDE SIOACPI  00001000 ACPI 00040000)
[    0.011901] ACPI: FPDT 0x000000007BFE5000 000044 (v01 INSYDE INSYDE   00000002 ACPI 00040000)
[    0.011912] ACPI: BGRT 0x000000007BFE4000 000038 (v01 INSYDE INSYDE   00000001 ACPI 00040000)
[    0.011922] ACPI: Reserving FACP table memory at [mem 0x7bffa000-0x7bffa10b]
[    0.011928] ACPI: Reserving DSDT table memory at [mem 0x7bfea000-0x7bff4bbd]
[    0.011933] ACPI: Reserving FACS table memory at [mem 0x7bfbb000-0x7bfbb03f]
[    0.011938] ACPI: Reserving UEFI table memory at [mem 0x7bffd000-0x7bffd235]
[    0.011943] ACPI: Reserving UEFI table memory at [mem 0x7bffb000-0x7bffb041]
[    0.011948] ACPI: Reserving APIC table memory at [mem 0x7bff9000-0x7bff9083]
[    0.011953] ACPI: Reserving MCFG table memory at [mem 0x7bff8000-0x7bff803b]
[    0.011958] ACPI: Reserving SLIC table memory at [mem 0x7bff7000-0x7bff7175]
[    0.011963] ACPI: Reserving WDAT table memory at [mem 0x7bff6000-0x7bff61c3]
[    0.011968] ACPI: Reserving WDRT table memory at [mem 0x7bff5000-0x7bff5046]
[    0.011973] ACPI: Reserving SSDT table memory at [mem 0x7bfe9000-0x7bfe9762]
[    0.011978] ACPI: Reserving SSDT table memory at [mem 0x7bfe8000-0x7bfe828f]
[    0.011983] ACPI: Reserving SSDT table memory at [mem 0x7bfe7000-0x7bfe7179]
[    0.011988] ACPI: Reserving SSDT table memory at [mem 0x7bfe6000-0x7bfe6df8]
[    0.011993] ACPI: Reserving FPDT table memory at [mem 0x7bfe5000-0x7bfe5043]
[    0.011998] ACPI: Reserving BGRT table memory at [mem 0x7bfe4000-0x7bfe4037]
[    0.012019] ACPI: Local APIC address 0xfee00000
[    0.012153] No NUMA configuration found
[    0.012157] Faking a node at [mem 0x0000000000000000-0x000000017fffffff]
[    0.012169] NODE_DATA(0) allocated [mem 0x17fffa000-0x17fffdfff]
[    0.012223] Zone ranges:
[    0.012227]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.012234]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.012240]   Normal   [mem 0x0000000100000000-0x000000017fffffff]
[    0.012246] Movable zone start for each node
[    0.012250] Early memory node ranges
[    0.012252]   node   0: [mem 0x0000000000001000-0x000000000006efff]
[    0.012258]   node   0: [mem 0x0000000000070000-0x000000000008ffff]
[    0.012262]   node   0: [mem 0x0000000000100000-0x000000007a4befff]
[    0.012268]   node   0: [mem 0x000000007bfff000-0x000000007bffffff]
[    0.012273]   node   0: [mem 0x0000000100000000-0x000000017fffffff]
[    0.012279] Initmem setup node 0 [mem 0x0000000000001000-0x000000017fffffff]
[    0.012286] On node 0 totalpages: 1025102
[    0.012290]   DMA zone: 64 pages used for memmap

# cat /proc/partitions

(lists all partitions&drives, sd is for sata disk (numbered from ‘a’ onwards to indicate drive num)



admin@NAS-ASTR-180:/volume1/home/admin $ cat /proc/partitions
major minor  #blocks  name

   1        0      65536 ram0
   1        1      65536 ram1
   1        2      65536 ram2
   1        3      65536 ram3
   1        4      65536 ram4
   1        5      65536 ram5
   1        6      65536 ram6
   1        7      65536 ram7
   1        8      65536 ram8
   1        9      65536 ram9
   1       10      65536 ram10
   1       11      65536 ram11
   1       12      65536 ram12
   1       13      65536 ram13
   1       14      65536 ram14
   1       15      65536 ram15
   7        0       1024 loop0
   8        0 9766436864 sda
   8        1     261120 sda1
   8        2    2097152 sda2
   8        3    2097152 sda3
   8        4 9761979392 sda4
   8       16 9766436864 sdb
   8       17     261120 sdb1
   8       18    2097152 sdb2
   8       19    2097152 sdb3
   8       20 9761979392 sdb4
   9        0    2095104 md0
   9      126    2095104 md126
   9        1 9761848320 md1
admin@NAS-ASTR-180:/volume1/home/admin $

# dd if=/dev/zero of=/dev/sda bs=1M count=512
(erases sda)

Following wipes /dev/sdc:



# toolbox nasvol
(manages volumes and creates raid partitions)









    • Related Articles

    • Initializing ASUSTOR NAS

      Initializing ASUSTOR NAS Initializing an ASUSTOR NAS is easy to accomplish in a few steps. Steps to follow Finding ASUSTOR NASS and Updating ADM Initializing the NASS Finding ASUSTOR NAS and Updating ADM Download and install ASUSTOR Control Center ...
    • Link Aggregation Creation and Troubleshooting Steps of Asustor AS6512RD

      Create Link Aggregation on Asustor AS6512RD Steps to Create Link Aggregation Login to your asustor device Go to Setting > Network > Network Interface > Add > Create Link Aggregation Select an aggregation mode from the drop-down list. Round-Robin: ...
    • How to Setup Link Aggregation on Asustor NAS

      What is Link Aggregation? Link aggregation (also known as trunking, bonding, or teaming) is the process of combining two or more network connections into one. Link aggregation requires that your Ethernet cables be connected to the same network switch ...
    • NVMe Devices Not Detected During Early Boot with Existing BIOS

      Overview This KB document addresses an issue where some NVMe devices are not detected during system startup, causing the operating system to fail to recognize all installed NVMe drives. The issue is related to limitations in PCIe device enumeration ...
    • NAS Power Supply Issue

      Troubleshooting Guide - Troubleshooting Guide Ref Ticket No.: 11151_Beacon Red Investment_NAS_DXB Overview This article provides troubleshooting steps for NAS units that fail to power on despite both power supply units (PSUs) showing as healthy. ...