NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
JBOD Volume creation failed
I have a ReadyNas RN102, and up until now, it was running with a single 4TB NAS disk in X-RAID mode.
A few days ago, i've bough a new 4TB NAS disk, and, as expected (and i have forgotten), being in X-RAID mode, it immediatly started to synchronizae both disks.
As my goal is two have the disks as two separated disks, thus having 8TB available, i stopped the process.
Following the information from this forum, i've tried the following procedure:
1. Disable X-RAID
2. Destroy the existent partition (DISK1),
3. Create a new JBOD Volume (DISK1)
4. Format DISK2
5. Create a new Volume on DISK2
Unfortunately, this didn't work, and the Volume creation failed an error.
This is what i'm seeing in the UI.
After creating JBOD Volume on DISK1:
- https://i.imgur.com/TAbwmPi.png
Trying to create new JBOD Volume on DISK2
- https://i.imgur.com/WbusfZb.png
The failed volume creation error:
- https://i.imgur.com/BfEiReW.png
Don't know if it matters, but after the failed volumen creation, the DISK2 light at the botton is not green:
- https://i.imgur.com/DJEzTfq.png
I've tried a lot of things, such as:
- Perform a factory Reset
- Perform a OS Re-Install
- Zeroing DISK2 with (dd if=/dev/zero of=/dev/sdb bs=4M) => This didn't complete, as it took almost a day to zero 2TB, and due to a restart, the PUTTY window was closed.
RAIDAR indicates that both disks are OK:
- https://i.imgur.com/OuVE0Ce.png
I also performed a Disk Test through the Boot menu, and for the DISK2, it showed:
-----------------------
Disk sdb:
HostID: 00000000
Flags: 0x0
Size: 7814037168 (3726 GB)
Free: 7804599886
Controller 0
Channel: 1
Model: ST4000VN008
Serial: ZM40REBE
Firmware: SC60
Class: SATA (3)
RPM: 7200
SMART data
Temperature: 0
Latest Self Test: Passed
-----------------------
Full logs can be downloaded here: <redacted>
Thank you very much in advance for any help.
PS: Please excuse me for the images, but i wasn't able to include them in the content of the post, so i only included the imgur links.
You really shouldn't post log zip files publicly, so consider unsharing the zip.
Look in rn-expand.log
-- Logs begin at Sun 2020-03-15 15:57:40 GMT, end at Mon 2020-03-16 00:06:06 GMT. -- Mar 15 15:58:35 nas-35-A8-1B rn-expand[2336]: Creating pool: DISK2 Mar 15 15:58:35 nas-35-A8-1B rn-expand[2336]: * Level: 1 Mar 15 15:58:35 nas-35-A8-1B rn-expand[2336]: * Disks: Mar 15 15:58:35 nas-35-A8-1B rn-expand[2336]: 0:1 (sdb,ST4000VN008,3726GB) Mar 15 15:58:35 nas-35-A8-1B rn-expand[2336]: prepare_disk: Prepare disk 0:1 (sdb,ST4000VN008,3726GB) with partition size 7804599872 Mar 15 15:58:35 nas-35-A8-1B rn-expand[2336]: Found sdb is not a member of root Mar 15 15:58:42 nas-35-A8-1B rn-expand[2336]: Partitioning failed! [4] Mar 15 15:58:42 nas-35-A8-1B rn-expand[2336]: output: Warning! Read error 5; strange behavior now likely!;Warning! Read error 5; strange behavior now likely!;Creating new GPT entries in memory.;Warning! GPT main header not overwritten! Error is 5;Warning: The kernel is still using the old partition table.;The new table will be used at the next reboot or after you;run partprobe(8) or kpartx(8);GPT data structures destroyed! You may now partition the disk using fdisk or;other utilities.;Warning! MBR not overwritten! Error is 5!;Warning! Read error 5; strange be Mar 15 15:58:42 nas-35-A8-1B rn-expand[2336]: adding partition failed [5] Mar 15 15:58:42 nas-35-A8-1B rn-expand[2336]: Found sdb is not a member of swap Mar 15 15:58:43 nas-35-A8-1B rn-expand[2336]: Partitioning failed! [4] Mar 15 15:58:43 nas-35-A8-1B rn-expand[2336]: output: Warning! Read error 5; strange behavior now likely!;Warning! Read error 5; strange behavior now likely!;Creating new GPT entries in memory.;Unable to save backup partition table! Perhaps the 'e' option on the experts';menu will resolve this problem.;Warning! An error was reported when writing the partition table! This error;MIGHT be harmless, or the disk might be damaged! Checking it is advisable.; Mar 15 15:58:46 nas-35-A8-1B rn-expand[2336]: Partitioning failed! [4] Mar 15 15:58:46 nas-35-A8-1B rn-expand[2336]: output: Warning! Read error 5; strange behavior now likely!;Warning! Read error 5; strange behavior now likely!;Creating new GPT entries in memory.;Unable to save backup partition table! Perhaps the 'e' option on the experts';menu will resolve this problem.;Warning! An error was reported when writing the partition table! This error;MIGHT be harmless, or the disk might be damaged! Checking it is advisable.;
And disk errors in kernel.log
Mar 15 16:20:51 Multimedia kernel: ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 13 dma 4096 in res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error) Mar 15 16:20:51 Multimedia kernel: ata2.00: status: { DRDY ERR } Mar 15 16:20:51 Multimedia kernel: ata2.00: error: { ABRT } Mar 15 16:20:51 Multimedia kernel: ata2.00: configured for UDMA/133 (device error ignored) Mar 15 16:20:51 Multimedia kernel: ata2: EH complete Mar 15 16:20:51 Multimedia kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 15 16:20:51 Multimedia kernel: ata2.00: irq_stat 0x40000001 Mar 15 16:20:51 Multimedia kernel: ata2.00: failed command: READ DMA Mar 15 16:20:51 Multimedia kernel: ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 14 dma 4096 in res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error) Mar 15 16:20:51 Multimedia kernel: ata2.00: status: { DRDY ERR } Mar 15 16:20:51 Multimedia kernel: ata2.00: error: { ABRT }I suggest testing this disk in a Windows PC with Seatools. Run the extended non-destructive test first. If that passes, then run the full erase test.
I don't expect it to pass both Seatools tests - I think this disk has failed. If this is a new disk, then try to exchange it with the seller - that will give you full warranty coverage on the replacement.
6 Replies
Replies have been turned off for this discussion
When analysing the dmes.log file, it seems the disk has several errors?
--------------------------------------------
[Sun Mar 15 23:31:05 2020] sd 1:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[Sun Mar 15 23:31:05 2020] sd 1:0:0:0: [sdb] Write Protect is off
[Sun Mar 15 23:31:05 2020] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[Sun Mar 15 23:31:05 2020] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[Sun Mar 15 23:31:05 2020] sd 1:0:0:0: Attached scsi generic sg1 type 0
[Sun Mar 15 23:31:05 2020] ata2.00: READ LOG DMA EXT failed, trying unqueued
[Sun Mar 15 23:31:05 2020] ata2: failed to read log page 10h (errno=-5)
[Sun Mar 15 23:31:05 2020] ata2.00: exception Emask 0x1 SAct 0x800000 SErr 0x0 action 0x0
[Sun Mar 15 23:31:05 2020] ata2.00: irq_stat 0x40000001
[Sun Mar 15 23:31:05 2020] ata2.00: failed command: READ FPDMA QUEUED
[Sun Mar 15 23:31:05 2020] ata2.00: cmd 60/08:b8:00:00:00/00:00:00:00:00/40 tag 23 ncq 4096 in
res 51/04:b8:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error)
[Sun Mar 15 23:31:05 2020] ata2.00: status: { DRDY ERR }
[Sun Mar 15 23:31:05 2020] ata2.00: error: { ABRT }
[Sun Mar 15 23:31:05 2020] ata2.00: configured for UDMA/133 (device error ignored)
[Sun Mar 15 23:31:05 2020] ata2: EH complete
[Sun Mar 15 23:31:05 2020] ata2: failed to read log page 10h (errno=-5)
[Sun Mar 15 23:31:05 2020] ata2.00: NCQ disabled due to excessive errors
[Sun Mar 15 23:31:05 2020] ata2.00: exception Emask 0x1 SAct 0x2000000 SErr 0x0 action 0x0
[Sun Mar 15 23:31:05 2020] ata2.00: irq_stat 0x40000001
[Sun Mar 15 23:31:05 2020] ata2.00: failed command: READ FPDMA QUEUED
[Sun Mar 15 23:31:05 2020] ata2.00: cmd 60/08:c8:00:00:00/00:00:00:00:00/40 tag 25 ncq 4096 in
res 51/04:c8:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error)
[Sun Mar 15 23:31:05 2020] ata2.00: status: { DRDY ERR }
[Sun Mar 15 23:31:05 2020] ata2.00: error: { ABRT }
[Sun Mar 15 23:31:05 2020] ata2.00: configured for UDMA/133 (device error ignored)
[Sun Mar 15 23:31:05 2020] ata2: EH complete
[Sun Mar 15 23:31:05 2020] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Sun Mar 15 23:31:05 2020] ata2.00: irq_stat 0x40000001
[Sun Mar 15 23:31:05 2020] ata2.00: failed command: READ DMA
[Sun Mar 15 23:31:05 2020] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 4 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[Sun Mar 15 23:31:05 2020] ata2.00: status: { DRDY ERR }
[Sun Mar 15 23:31:05 2020] ata2.00: error: { ABRT }
[Sun Mar 15 23:31:05 2020] ata2.00: configured for UDMA/133 (device error ignored)
[Sun Mar 15 23:31:05 2020] ata2: EH complete
[Sun Mar 15 23:31:05 2020] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[Sun Mar 15 23:31:05 2020] ata2.00: irq_stat 0x40000001
[Sun Mar 15 23:31:05 2020] ata2.00: failed command: READ DMA
[Sun Mar 15 23:31:05 2020] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 5 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)-------------------------------------------------------------------------------
PS: Full logs are provided in a link from the above message.
You really shouldn't post log zip files publicly, so consider unsharing the zip.
Look in rn-expand.log
-- Logs begin at Sun 2020-03-15 15:57:40 GMT, end at Mon 2020-03-16 00:06:06 GMT. -- Mar 15 15:58:35 nas-35-A8-1B rn-expand[2336]: Creating pool: DISK2 Mar 15 15:58:35 nas-35-A8-1B rn-expand[2336]: * Level: 1 Mar 15 15:58:35 nas-35-A8-1B rn-expand[2336]: * Disks: Mar 15 15:58:35 nas-35-A8-1B rn-expand[2336]: 0:1 (sdb,ST4000VN008,3726GB) Mar 15 15:58:35 nas-35-A8-1B rn-expand[2336]: prepare_disk: Prepare disk 0:1 (sdb,ST4000VN008,3726GB) with partition size 7804599872 Mar 15 15:58:35 nas-35-A8-1B rn-expand[2336]: Found sdb is not a member of root Mar 15 15:58:42 nas-35-A8-1B rn-expand[2336]: Partitioning failed! [4] Mar 15 15:58:42 nas-35-A8-1B rn-expand[2336]: output: Warning! Read error 5; strange behavior now likely!;Warning! Read error 5; strange behavior now likely!;Creating new GPT entries in memory.;Warning! GPT main header not overwritten! Error is 5;Warning: The kernel is still using the old partition table.;The new table will be used at the next reboot or after you;run partprobe(8) or kpartx(8);GPT data structures destroyed! You may now partition the disk using fdisk or;other utilities.;Warning! MBR not overwritten! Error is 5!;Warning! Read error 5; strange be Mar 15 15:58:42 nas-35-A8-1B rn-expand[2336]: adding partition failed [5] Mar 15 15:58:42 nas-35-A8-1B rn-expand[2336]: Found sdb is not a member of swap Mar 15 15:58:43 nas-35-A8-1B rn-expand[2336]: Partitioning failed! [4] Mar 15 15:58:43 nas-35-A8-1B rn-expand[2336]: output: Warning! Read error 5; strange behavior now likely!;Warning! Read error 5; strange behavior now likely!;Creating new GPT entries in memory.;Unable to save backup partition table! Perhaps the 'e' option on the experts';menu will resolve this problem.;Warning! An error was reported when writing the partition table! This error;MIGHT be harmless, or the disk might be damaged! Checking it is advisable.; Mar 15 15:58:46 nas-35-A8-1B rn-expand[2336]: Partitioning failed! [4] Mar 15 15:58:46 nas-35-A8-1B rn-expand[2336]: output: Warning! Read error 5; strange behavior now likely!;Warning! Read error 5; strange behavior now likely!;Creating new GPT entries in memory.;Unable to save backup partition table! Perhaps the 'e' option on the experts';menu will resolve this problem.;Warning! An error was reported when writing the partition table! This error;MIGHT be harmless, or the disk might be damaged! Checking it is advisable.;
And disk errors in kernel.log
Mar 15 16:20:51 Multimedia kernel: ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 13 dma 4096 in res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error) Mar 15 16:20:51 Multimedia kernel: ata2.00: status: { DRDY ERR } Mar 15 16:20:51 Multimedia kernel: ata2.00: error: { ABRT } Mar 15 16:20:51 Multimedia kernel: ata2.00: configured for UDMA/133 (device error ignored) Mar 15 16:20:51 Multimedia kernel: ata2: EH complete Mar 15 16:20:51 Multimedia kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 15 16:20:51 Multimedia kernel: ata2.00: irq_stat 0x40000001 Mar 15 16:20:51 Multimedia kernel: ata2.00: failed command: READ DMA Mar 15 16:20:51 Multimedia kernel: ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 14 dma 4096 in res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error) Mar 15 16:20:51 Multimedia kernel: ata2.00: status: { DRDY ERR } Mar 15 16:20:51 Multimedia kernel: ata2.00: error: { ABRT }I suggest testing this disk in a Windows PC with Seatools. Run the extended non-destructive test first. If that passes, then run the full erase test.
I don't expect it to pass both Seatools tests - I think this disk has failed. If this is a new disk, then try to exchange it with the seller - that will give you full warranty coverage on the replacement.
Thank you for your response.
Its a new disk, do you have any guess on why a new disk has failed?
VascoOliveira wrote:Its a new disk, do you have any guess on why a new disk has failed?
Sometimes they fail out-of-the-box (I've had a couple that have done that). That could be a manufacturing issue with that particular disk, or perhaps it was mishandled during shipment.
I always test mine before I install them into the NAS. You can do that by connecting it to a windows PC and running Seatools - running both the long non-destructive test and the full erase (write zeros) test. The write zeros test sometimes will uncover problems that the non-destructive test won't. Note you can either connect the disk using SATA or a USB adapter/dock.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
