NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RN212 Disk 2: Volume Creation Failed
Hi, I recently bought a RN212 and started with one Seagate Ironwolf 4T ST4000VN008, which should be supported. It started with no problems. Alas, last week I bought the same disk: Seagat...
MichelTiberghi wrote:
So I'll have to send back my disk
That makes sense, since you can't test it in a PC. I do suggest picking up a USB adapter/dock - the adapters are pretty inexpensive, and they are useful when you need to test a disk.
Did you first turn off XRAID? If not, the NAS was attempting to create a RAID1 from your two drives, and you would not have created a second volume for use as a backup (unless you believe RAID is backup).
Did you do anything with the drive before putting it in the NAS (like format it on a PC)? Did you hot insert the drive or do so with power off? Is your desire to get RAID redundancy for your volume, or do you really want a separate volume for backup (which is not really the best way to do backup)?
One possibility is that the drive is simply bad from the supplier, so testing with Seatools in a PC (via internal SATA connection or SATA to USB dock) is a good first step. Also, see if your NAS complains about a degraded (which means non-redundant RAID) condition with the new drive removed.
Hi Sandshark Sandshark
I feel really dumb, I think i insert the disk hot, while the nas was still on and the xraid on.
Can I still recover the disk?
MichelTiberghi wrote:
I think i insert the disk hot, while the nas was still on and the xraid on.
That does no damage, and in fact is what we normally recommend. Though since XRAID was on, the system should have created a RAID-1 array on the two disks.
Can you download the log zip file, and then copy/paste the contents of mdstat.log into a reply?
Hi
this is the log:
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md127 : active raid1 sda3[0]
3902168832 blocks super 1.2 [1/1] [U]
md1 : active raid1 sda2[0]
523712 blocks super 1.2 [1/1] [U]
md0 : active raid1 sda1[0]
4190208 blocks super 1.2 [1/1] [U]
unused devices: <none>
/dev/md/0:
Version : 1.2
Creation Time : Thu Feb 13 05:12:53 2020
Raid Level : raid1
Array Size : 4190208 (4.00 GiB 4.29 GB)
Used Dev Size : 4190208 (4.00 GiB 4.29 GB)
Raid Devices : 1
Total Devices : 1
Persistence : Superblock is persistentUpdate Time : Mon Dec 28 14:39:23 2020
State : active
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0Consistency Policy : unknown
Name : 6da64c9f:0 (local to host 6da64c9f)
UUID : 8ef37b25:c27d2f46:74f63c94:a78d288f
Events : 9Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
/dev/md/1:
Version : 1.2
Creation Time : Thu Feb 13 05:12:53 2020
Raid Level : raid1
Array Size : 523712 (511.44 MiB 536.28 MB)
Used Dev Size : 523712 (511.44 MiB 536.28 MB)
Raid Devices : 1
Total Devices : 1
Persistence : Superblock is persistentUpdate Time : Mon Dec 28 08:22:24 2020
State : clean
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0Consistency Policy : unknown
Name : 6da64c9f:1 (local to host 6da64c9f)
UUID : 887766c4:99261c50:8486d313:e27895ac
Events : 2Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
/dev/md/data-0:
Version : 1.2
Creation Time : Thu Feb 13 05:13:20 2020
Raid Level : raid1
Array Size : 3902168832 (3721.40 GiB 3995.82 GB)
Used Dev Size : 3902168832 (3721.40 GiB 3995.82 GB)
Raid Devices : 1
Total Devices : 1
Persistence : Superblock is persistentUpdate Time : Mon Dec 28 14:39:00 2020
State : clean
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0Consistency Policy : unknown
Name : 6da64c9f:data-0 (local to host 6da64c9f)
UUID : d9a97abf:710c5ee0:6afca304:863c9e43
Events : 3Number Major Minor RaidDevice State
0 8 3 0 active sync /dev/sda3
Hot insertion is normally the best practice to avoid issues like this one. The NAS does not have to figure out what you did while it was off, it sees the drive insertion after the volume is already mounted. With a simple configuration like yours, it should have been able to figure it out either way, except perhaps if the drive was previously used in another NAS.
How about my other questions? The logs may help, but knowing if the disk may have already been formatted by a PC (which can cause the NAS problems with some system reserved partition types) and that it's a good drive are important in diagnosing the issue. Knowing where you want to go (second volume or convert to RAID) will help in getting you there once the current problem is determined.
Hi,
I posted the log above...
Thx.
When you look at the volume tab in the web UI, are you seeing a green stripe through the XRAID control on the right?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
