Hi, Running v6.9.3 After a reboot the NAS came up saying "No Volume Exists". Have done another couple of shutdowns and startups and it's now saying "Remove inactive volumes to use the disk. Disk #1,2,3,4,5,6,2,3,6,2,3." Can anyone advise on how best to approach? Had a quick look and none of the six disks are showing ATA Errors. Happy to provide log files. Thanks.

Hi Westyfield2, I have checked the logs. It is correct that the transactions are out of sync It says that the volume at this specific location knew it was going to complete a specific transaction (wanted) but, it found that it was only on a previous transaction. Normally, you should be able to contact support so they can fix it but, they will not be able to assist you on this because your NAS is a legacy x86 NAS converted to OS6. Hopefully, other Community members can chime in here so they assist you on this. Regards,

No Volume Exists - Remove inactive volumes in order to use the disk

18 Replies

Replies have been turned off for this discussion

JohnCM_S

NETGEAR Employee Retired

Apr 23, 2019

Hi Westyfield2,

You may upload the logs to Google Drive then send to me the download link via PM (private message). We will check what caused the error message.

Regards,

Tutor

PM sent

Tutor

So the disks look fine (:heart: WD Enterprise)

Device:             sda
Controller:         0
Channel:            0
Model:              WDC WD2003FYYS-02W0B0
Serial:             WD-WMAY01159942
Firmware:           01.01D01
Class:              SATA
RPM:                7200
Sectors:            3907029168
Pool:               data
PoolType:           RAID 5
PoolState:          5
PoolHostId:         33eadf27
Health data 
  ATA Error Count:                1
  Reallocated Sectors:            0
  Reallocation Events:            0
  Spin Retry Count:               0
  Current Pending Sector Count:   0
  Uncorrectable Sector Count:     0
  Temperature:                    35
  Start/Stop Count:               4740
  Power-On Hours:                 63000
  Power Cycle Count:              64
  Load Cycle Count:               4716

Device:             sdb
Controller:         0
Channel:            1
Model:              WDC WD6002FRYZ-01WD5B0
Serial:             NCHBG8GS
Firmware:           01.01M02
Class:              SATA
RPM:                7200
Sectors:            11721045168
Pool:               data
PoolType:           RAID 5
PoolState:          5
PoolHostId:         33eadf27
Health data 
  ATA Error Count:                0
  Reallocated Sectors:            0
  Reallocation Events:            0
  Spin Retry Count:               0
  Current Pending Sector Count:   0
  Uncorrectable Sector Count:     0
  Temperature:                    35
  Start/Stop Count:               29
  Power-On Hours:                 20494
  Power Cycle Count:              29
  Load Cycle Count:               866

Device:             sdc
Controller:         0
Channel:            2
Model:              WDC WD6002FRYZ-01WD5B0
Serial:             NCGWTDVV
Firmware:           01.01M02
Class:              SATA
RPM:                7200
Sectors:            11721045168
Pool:               data
PoolType:           RAID 5
PoolState:          5
PoolHostId:         33eadf27
Health data 
  ATA Error Count:                0
  Reallocated Sectors:            0
  Reallocation Events:            0
  Spin Retry Count:               0
  Current Pending Sector Count:   0
  Uncorrectable Sector Count:     0
  Temperature:                    35
  Start/Stop Count:               32
  Power-On Hours:                 22223
  Power Cycle Count:              32
  Load Cycle Count:               938

Device:             sdd
Controller:         0
Channel:            3
Model:              WDC WD2003FYYS-02W0B1
Serial:             WD-WMAY04428148
Firmware:           01.01D02
Class:              SATA
RPM:                7200
Sectors:            3907029168
Pool:               data
PoolType:           RAID 5
PoolState:          5
PoolHostId:         33eadf27
Health data 
  ATA Error Count:                0
  Reallocated Sectors:            0
  Reallocation Events:            0
  Spin Retry Count:               0
  Current Pending Sector Count:   0
  Uncorrectable Sector Count:     0
  Temperature:                    37
  Start/Stop Count:               4759
  Power-On Hours:                 60625
  Power Cycle Count:              55
  Load Cycle Count:               4736

Device:             sde
Controller:         0
Channel:            4
Model:              WDC WD2003FYYS-02W0B1
Serial:             WD-WMAY04905430
Firmware:           01.01D02
Class:              SATA
RPM:                7200
Sectors:            3907029168
Pool:               data
PoolType:           RAID 5
PoolState:          5
PoolHostId:         33eadf27
Health data 
  ATA Error Count:                0
  Reallocated Sectors:            0
  Reallocation Events:            0
  Spin Retry Count:               0
  Current Pending Sector Count:   0
  Uncorrectable Sector Count:     0
  Temperature:                    36
  Start/Stop Count:               4318
  Power-On Hours:                 56959
  Power Cycle Count:              53
  Load Cycle Count:               4290

Device:             sdf
Controller:         0
Channel:            5
Model:              WDC WD4000F9YZ-09N20L0
Serial:             WD-WCC131766520
Firmware:           01.01A01
Class:              SATA
RPM:                7200
Sectors:            7814037168
Pool:               data
PoolType:           RAID 5
PoolState:          5
PoolHostId:         33eadf27
Health data 
  ATA Error Count:                0
  Reallocated Sectors:            0
  Reallocation Events:            0
  Spin Retry Count:               0
  Current Pending Sector Count:   0
  Uncorrectable Sector Count:     0
  Temperature:                    32
  Start/Stop Count:               1775
  Power-On Hours:                 43200
  Power Cycle Count:              36
  Load Cycle Count:               1754

From memory I think it probably had about 1.5TB free space when it failed.

But it looks like the transactions are slightly out of sync.

[Wed Apr 24 19:31:56 2019] md125: detected capacity change from 0 to 4000511819776
[Wed Apr 24 19:31:56 2019] BTRFS: device label 33eadf27:data devid 2 transid 1187337 /dev/md125
[Wed Apr 24 19:31:56 2019] BTRFS info (device md125): has skinny extents
[Wed Apr 24 19:32:15 2019] BTRFS error (device md125): parent transid verify failed on 9209338265600 wanted 1187338 found 1187336
[Wed Apr 24 19:32:15 2019] BTRFS error (device md125): parent transid verify failed on 9209338265600 wanted 1187338 found 1187336
[Wed Apr 24 19:32:15 2019] BTRFS warning (device md125): failed to read log tree
[Wed Apr 24 19:32:15 2019] BTRFS error (device md125): open_ctree failed

Forum Discussion

No Volume Exists - Remove inactive volumes in order to use the disk

18 Replies

Related Content

ReadyNAS RN424 | Inactive Volume + RAID Issue

RN104 Remove inactive volumes Disk 3,4

Remove inactive volumes

Volume Expansion question

Volumes now showing inactive after reboot

NETGEAR Academy

ProSupport for Business