I´m trying to use a 2BIGN2 with a raid 1 (2TB each and MBR) but it stuck on creating journal.
Fresh install 18.3 with empty disks.
- Code: Select all
Setup task makeraid.sh is now running
Found disk: sda(XXXXXXX)
Found disk: sdb(XXXXXXX)
Create raid device md0
=>OK: md0 created (raid1)
Format partition md0 with file system ext4:
=>mke2fs 1.43.4 (31-Jan-2017)
Discarding device blocks: done
Warning: could not erase sector 2: Input/output error
Creating filesystem with 487556640 4k blocks and 121896960 inodes
Filesystem UUID: 429471d1-1243-40f0-bb56-47c3d0a88d3e
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
Allocating group tables: done
Warning: could not read block 0: Input/output error
Warning: could not erase sector 0: Input/output error
Writing inode tables: done
Creating journal (262144 blocks):
What i´m doing bad? it´s the second time i tryed it (on the 1st try i waited more than 2 hours).
I reinizializated both disk again, and retryed but it´s seem that is the same result.
And on other hand, and looking for in the forum i saw that post:
viewtopic.php?f=27&t=3659&p=38601&hilit=raid1#p38601
I'm very disappointed because this is NOT a real RAID1 firmware.
Someone who choose to set a NAS to RAID1 is for data security. So when any disk fail, NAS MUST can boot with only one disk in any slot.
Edit:
Solved reading...
It´s that true? can be solved by installing fdwl firmare on both disk (sda+sdb)?
https://plugout.net/viewtopic.php?f=7&t=1271
-If you have a multi disk nas and use the fvdw-sl console and standalone kernel install only 1 disk in the nas in slot 1 (most lefthand slot seen from back) to prepare the system disk.
- Code: Select all
boot_disk4=disk ${kernel_addr} 1:${primaryPart}; setenv rootfs /dev/sdb7;
boot_disk3=if disk ${kernel_addr} 0:${primaryPart}; then setenv rootfs /dev/sda7; else run boot_disk4; fi
boot_disk2=if disk ${kernel_addr} 1:${secondaryPart}; then setenv rootfs /dev/sdb7; else run boot_disk3; fi
boot_disk1=if disk ${kernel_addr} 0:${secondaryPart}; then setenv rootfs /dev/sda7; else run boot_disk2; fi
boot_disk=if test ${resetFlag_env} -eq 0; then run boot_disk1; else run boot_disk3; fi
disk_disk=run boot_disk; setenv bootargs console=ttyS0,115200 root=${rootfs} ro reset=${resetFlag_env} productType=${productType_env}; bootm ${kernel_addr};
- But in uboot args it seems to be supported. Although since I don't have much knowledge in this area, I suppose I might be wrong.
Thanks a lot!