- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: RN2120 Full Disc Inactive Volumes
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
RN2120 Full Disc Inactive Volumes
HI, Its been a while since I have gone and purged my 24/7 video recordings, as I went to check on my files I couldn't access the folders on the NAS anymore, I can still log in and navigate through the OS through the IP address but all drives are shown as inactive. From the Kernel.log file this is whats shown:
Feb 21 18:35:07 nas-36-12-CE kernel: BTRFS critical (device md127): unable to find logical 13915984560128 len 4096
I had no idea that the discs become inaccessible when full, is there a way to access the drives to make space for further operation?
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RN2120 Full Disc Inactive Volumes
@jkucukov wrote:
I had no idea that the discs become inaccessible when full
They don't always, but running out of free space can result in the file system becoming corrupted.
It's not the only cause though - are you sure that the issue was a result of a full volume?
@jkucukov wrote:
is there a way to access the drives to make space for further operation?
If you have a backup (or don't need the data), then the simplest path is to destroy the volume and re-create it.
If you need to offload data, you will probably need data recovery.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RN2120 Full Disc Inactive Volumes
The performance status of all 4 discs appears healthy. Is it possible to go into read only mode to take out the important files first?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RN2120 Full Disc Inactive Volumes
By definition, you cannot delete anything when in read-only mode. Have you even been able to boot to read-only mode?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RN2120 Full Disc Inactive Volumes
I haven't tried the boot menu yet, I was hoping to enter the read-only mode in an attempt to copy out the important files. Is it possible to get to the boot menu from the IP Admin page or do I have to physically be at the unit and go through the reset button sequence during boot up?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RN2120 Full Disc Inactive Volumes
@jkucukov wrote:
I was hoping to enter the read-only mode in an attempt to copy out the important files.
Read-only mode won't repair the file system, so it won't mount the inactive Volume(s). Therefore it won't help you offload data.
You say "Volumes" - if you were using the default X-RAID,then you'd only have one volume. Can you clarify what RAID mode you are using, and how many volumes you had?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RN2120 Full Disc Inactive Volumes
I was afraid of that, the only way to go about taking out the important data is with some sort of data recovery software. Its a shame that the NAS itself cannot be used for data recovery in this instance. Or at least not needing to get SATA expansion ports with cables.
The 4 drives are set up as RAID 5, I do see under the Volumes tab that the X-RAID is turned on.
The message that's shown when I log in to the Admin page shows "Remove inactive volumes to use the disk. Disk #1, 2, 3, 4" is probably where I got the volumes part
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RN2120 Full Disc Inactive Volumes
@jkucukov wrote:
Its a shame that the NAS itself cannot be used for data recovery in this instance.
It can be. Netgear does offer a data recovery service, but recently folks have had trouble accessing it.
There are some cases where you can forcibly mount the volume. Seeing if that is possible would require a full analysis of the log zip file.