[RAID1] Need some advice on setting up a second disk

[danyboy666]

I've completed the fvdw-sl install without a hitch and i find it to be a great piece of software but i need a RAID1 setup which is still not available in the web interface.

Can a little how-to be posted for this purpose? I've read the PDF documentation viewtopic.php?f=7&t=2006#p16710 but it doesn't mention how to setup the partitions in the first place.

Code: Select all

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               9          72      514080  83 Linux
/dev/sda2              73         136      514080  83 Linux
/dev/sda3             137         200      514080  82 Linux swap
/dev/sda4             201      121601   975153532+  5 Extended
/dev/sda5             209         312      835380  83 Linux
/dev/sda6             321         328       64260  83 Linux
/dev/sda7             337         400      514080  83 Linux
/dev/sda8             409      121601   973482772+ 83 Linux


Should i just copy that partition table to the second disk and proceed with your tutorial for how to setup the RAID? (what is "add-ons volume" and "technical shares" by the way?)

Oh by the way the package sfdisk is not available on fvdw-sl so i can't really export the partition table. I will need to do this manually from a to z.

How can i be sure i set my disk as RAID1 correctly without screwing up my install? Do i only need to create sdb8 partition or do i have to copy the whole partition table without copying fvdw files to the second disk from sda to sdb and set up a raid only for partition sd[ab]8 partition?

What happens if my install goes bad? Let say i lose /dev/sda for some reason since i don't have your firmware install on sdb i will lose the nas again and then I will need to go thru the step to reinstall your firmware again to recover my data from sdb8?

In reality this does not fit my description for a RAID1 setup. Can you explain this to me? Maybe i got this wrong though.

Thanks again.

Here's a dmesg output:

Code: Select all

dmesg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.2 (root@fvdwsl-5big2.local) (gcc version 4.8.1 (GCC) ) #6 Sat Nov 29 22:15:32 CET 2014
[    0.000000] CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: LaCie 2Big Network
[    0.000000] Clearing invalid memory bank 0KB@0x00000000
[    0.000000] Clearing invalid memory bank 0KB@0x00000000
[    0.000000] Clearing invalid memory bank 0KB@0x00000000
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x41000403
[    0.000000] Memory policy: Data cache writeback
[    0.000000] On node 0 totalpages: 32768
[    0.000000] free_area_init_node: node 0, pgdat c03f0934, node_mem_map c7efb000
[    0.000000]   Normal zone: 256 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 32768 pages, LIFO batch:7
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda7 ro boardType=mv88F5182 productType=2Big reset=0
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 125664K/131072K available (2863K kernel code, 158K rwdata, 852K rodata, 125K init, 206K bss, 5408K reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xc8800000 - 0xff000000   ( 872 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc03a8fec   (3716 kB)
[    0.000000]       .init : 0xc03a9000 - 0xc03c862c   ( 126 kB)
[    0.000000]       .data : 0xc03ca000 - 0xc03f1ac0   ( 159 kB)
[    0.000000]        .bss : 0xc03f1ac0 - 0xc0425680   ( 207 kB)
[    0.000000] NR_IRQS:64
[    0.000023] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 25769803770ns
[    1.587876] Console: colour dummy device 80x30
[    1.587925] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)
[    1.657506] pid_max: default: 32768 minimum: 301
[    1.657787] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    1.657824] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    1.658974] CPU: Testing write buffer coherency: ok
[    1.659645] Setting up static identity map for 0x2d1678 - 0x2d16b4
[    1.664589] VFP support v0.3: not present
[    1.665843] NET: Registered protocol family 16
[    1.667092] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    1.671756] Orion ID: MV88F5182-A2. TCLK=166666667.
[    1.672759] initial MPP regs: 00000003 55000000 ffff0000
[    1.672816]   final MPP regs: 00000003 55000000 ffff5555
[    1.678206] net2big: Flash writing is not yet supported.
[    1.724479] bio: create slab <bio-0> at 0
[    1.726284] vgaarb: loaded
[    1.728259] SCSI subsystem initialized
[    1.729572] libata version 3.00 loaded.
[    1.732216] usbcore: registered new interface driver usbfs
[    1.732738] usbcore: registered new interface driver hub
[    1.733328] usbcore: registered new device driver usb
[    1.737879] Switched to clocksource orion_clocksource
[    1.778680] NET: Registered protocol family 2
[    1.779924] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    1.779999] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    1.780058] TCP: Hash tables configured (established 1024 bind 1024)
[    1.780209] TCP: reno registered
[    1.780247] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    1.780317] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    1.780722] NET: Registered protocol family 1
[    1.780806] PCI: CLS 0 bytes, default 32
[    1.784659] futex hash table entries: 256 (order: -1, 3072 bytes)
[    1.785910] VFS: Disk quotas dquot_6.5.2
[    1.786048] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.786386] msgmni has been set to 245
[    1.790145] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    1.790180] io scheduler noop registered
[    1.790202] io scheduler deadline registered
[    1.790275] io scheduler cfq registered (default)
[    1.790856] mv_xor mv_xor.0: Marvell shared XOR driver
[    1.827581] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[    1.867583] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[    1.884471] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    1.907143] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3, base_baud = 10416666) is a 16550A
[    2.302588] console [ttyS0] enabled
[    2.332802] brd: module loaded
[    2.348728] loop: module loaded
[    2.352704] Uniform Multi-Platform E-IDE driver
[    2.358146] ide-gd driver 1.18
[    2.363675] sata_mv sata_mv.0: version 1.28
[    2.363845] sata_mv sata_mv.0: cannot get optional clkdev
[    2.370217] sata_mv sata_mv.0: slots 32 ports 2
[    2.384619] scsi0 : sata_mv
[    2.389032] scsi1 : sata_mv
[    2.393024] ata1: SATA max UDMA/133 irq 29
[    2.397129] ata2: SATA max UDMA/133 irq 29
[    2.402599] tun: Universal TUN/TAP device driver, 1.6
[    2.407682] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    2.414395] ipddp.c:v0.01 8/28/97 Bradford W. Johnson <johns393@maroon.tc.umn.edu>
[    2.423931] ipddp0: Appletalk-IP Encap. mode by Bradford W. Johnson <johns393@maroon.tc.umn.edu>
[    2.441054] libphy: orion_mdio_bus: probed
[    2.445697] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    2.530542] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:d0:4b:88:ec:69
[    2.542506] aoe: cannot create debugfs directory
[    2.547417] aoe: AoE v85 initialised.
[    2.551775] mousedev: PS/2 mouse device common for all mice
[    2.558676] i2c /dev entries driver
[    2.564503] rtc-rs5c372 0-0032: can't read registers
[    2.569526] rtc-rs5c372: probe of 0-0032 failed with error -5
[    2.577441] at24 0-0050: 1024 byte 24c08 EEPROM, writable, 1 bytes/write
[    2.592894] Netfilter messages via NETLINK v0.30.
[    2.598208] ipip: IPv4 over IPv4 tunneling driver
[    2.604856] TCP: cubic registered
[    2.608231] NET: Registered protocol family 17
[    2.612713] NET: Registered protocol family 5
[    2.619552] console [netcon0] enabled
[    2.623211] netconsole: network logging started
[    2.627790] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    2.907524] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    2.927867] ata1.00: ATA-9: WDC WD10EZEX-00BN5A0, 01.01A01, max UDMA/133
[    2.934566] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    2.957895] ata1.00: configured for UDMA/133
[    2.962890] scsi 0:0:0:0: Direct-Access     ATA      WDC WD10EZEX-00B 01.0 PQ: 0 ANSI: 5
[    2.972363] fvdw1 disk index before get_sd_name = 0
[    2.977237] device-name= sata_mv
[    2.980502] fvdw2 disk index after get_sd_name = 1
[    2.985280] fvdw3 prefix[0]=s  prefix[1]=d
[    2.989393] fvdw4 diskname = sdb
[    2.993952] sd 0:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[    3.001653] sd 0:0:0:0: [sdb] 4096-byte physical blocks
[    3.009446] sd 0:0:0:0: [sdb] Write Protect is off
[    3.014262] sd 0:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    3.014689] sd 0:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.039722]  sdb: unknown partition table
[    3.046767] sd 0:0:0:0: [sdb] Attached SCSI disk
[    3.517520] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    3.537887] ata2.00: ATA-10: WDC WD10EZEX-00WN4A0, 01.01A01, max UDMA/133
[    3.544673] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[    3.567892] ata2.00: configured for UDMA/133
[    3.572872] scsi 1:0:0:0: Direct-Access     ATA      WDC WD10EZEX-00W 01.0 PQ: 0 ANSI: 5
[    3.582318] fvdw1 disk index before get_sd_name = 1
[    3.587196] device-name= sata_mv
[    3.590463] fvdw2 disk index after get_sd_name = 0
[    3.595246] fvdw3 prefix[0]=s  prefix[1]=d
[    3.599358] fvdw4 diskname = sda
[    3.603927] sd 1:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[    3.611630] sd 1:0:0:0: [sda] 4096-byte physical blocks
[    3.618718] sd 1:0:0:0: [sda] Write Protect is off
[    3.623530] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    3.623953] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.681608]  sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
[    3.695367] sd 1:0:0:0: [sda] Attached SCSI disk
[    3.711175] kjournald starting.  Commit interval 5 seconds
[    3.716710] EXT3-fs (sda7): mounted filesystem with ordered data mode
[    3.723235] VFS: Mounted root (ext3 filesystem) readonly on device 8:23.
[    3.730899] Freeing unused kernel memory: 124K (c03a9000 - c03c8000)
[    3.958744] EXT3-fs (sda7): using internal journal
[    5.207808] kjournald starting.  Commit interval 5 seconds
[    5.213714] EXT3-fs (sda1): using internal journal
[    5.237662] EXT3-fs (sda1): recovery complete
[    5.242028] EXT3-fs (sda1): mounted filesystem with ordered data mode
[    7.087798] kjournald starting.  Commit interval 5 seconds
[    7.093348] EXT3-fs (sda5): warning: checktime reached, running e2fsck is recommended
[    7.101565] EXT3-fs (sda5): using internal journal
[    7.137661] EXT3-fs (sda5): recovery complete
[    7.142025] EXT3-fs (sda5): mounted filesystem with ordered data mode
[    7.308701] random: mkswap urandom read with 113 bits of entropy available
[    7.370280] Adding 514076k swap on /dev/sda3.  Priority:-1 extents:1 across:514076k
[    8.266108] random: nonblocking pool is initialized
[    9.641055] NTFS driver 2.1.30 [Flags: R/W MODULE].
[    9.699383] fuse init (API version 7.22)
[    9.757559] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    9.765733] ehci-orion: EHCI orion driver
[    9.769963] orion-ehci orion-ehci.0: EHCI Host Controller
[    9.775418] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[    9.783351] orion-ehci orion-ehci.0: irq 17, io mem 0xf1050000
[    9.807522] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[    9.815342] hub 1-0:1.0: USB hub found
[    9.819231] hub 1-0:1.0: 1 port detected
[    9.823915] orion-ehci orion-ehci.1: EHCI Host Controller
[    9.829415] orion-ehci orion-ehci.1: new USB bus registered, assigned bus number 2
[    9.837315] orion-ehci orion-ehci.1: irq 12, io mem 0xf10a0000
[    9.857511] orion-ehci orion-ehci.1: USB 2.0 started, EHCI 1.00
[    9.865016] hub 2-0:1.0: USB hub found
[    9.868900] hub 2-0:1.0: 1 port detected
[    9.927782] usbcore: registered new interface driver usb-storage
[    9.981791] usbcore: registered new interface driver usblp
[   10.056889] RPC: Registered named UNIX socket transport module.
[   10.062853] RPC: Registered udp transport module.
[   10.067576] RPC: Registered tcp transport module.
[   10.072276] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   10.168246] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   10.231490] Loading iSCSI transport class v2.0-870.
[   10.253139] iscsi: registered transport (tcp)
[   10.314789] Linux video capture interface: v2.00
[   10.435010] uvcvideo: Unable to create debugfs directory
[   10.440642] usbcore: registered new interface driver uvcvideo
[   10.446376] USB Video Class driver (1.1.1)
[   10.575518] md: raid0 personality registered for level 0
[   10.630800] md: raid1 personality registered for level 1
[   10.858139] raid6: int32x1     19 MB/s
[   11.028988] raid6: int32x2     29 MB/s
[   11.197837] raid6: int32x4     30 MB/s
[   11.368926] raid6: int32x8     36 MB/s
[   11.372674] raid6: using algorithm int32x8 (36 MB/s)
[   11.377657] raid6: using intx1 recovery algorithm
[   11.389395] async_tx: api initialized (async)
[   11.396738] xor: measuring software checksum speed
[   11.497486]    arm4regs  :   308.800 MB/sec
[   11.597484]    8regs     :   206.800 MB/sec
[   11.697484]    32regs    :   263.200 MB/sec
[   11.701664] xor: using function: arm4regs (308.800 MB/sec)
[   11.731919] md: raid6 personality registered for level 6
[   11.737233] md: raid5 personality registered for level 5
[   11.742583] md: raid4 personality registered for level 4
[   11.799791] md: raid10 personality registered for level 10
[   24.537175] udevd (710): /proc/710/oom_adj is deprecated, please use /proc/710/oom_score_adj instead.
[   24.546597] udev: starting version 130
[   40.227813] kjournald starting.  Commit interval 5 seconds
[   40.240158] EXT3-fs (sda8): warning: checktime reached, running e2fsck is recommended
[   40.253148] EXT3-fs (sda8): using internal journal
[   40.317672] EXT3-fs (sda8): recovery complete
[   40.322034] EXT3-fs (sda8): mounted filesystem with ordered data mode
[   42.098269] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
[   43.719608] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled

btw why is there information about raid personnalities in the boot process?

[danyboy666]

I've recreated partion info from sda on sdb and followed the procedure from the PDF. The raid is syncing

Code: Select all

 cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sda8[2] sdb8[1]
      973482688 blocks [2/1] [_U]
      [>....................]  recovery =  3.2% (31563392/973482688) finish=103.5min speed=151657K/sec

unused devices: <none>


I'll wait until it finishes to reboot the NAS and see if everything seem to have went well

[danyboy666]

The raid sync as ended i rebooted the NAS but the front LED is blinking red.

Everything seem to be working i.e samba share is available from my windows pc at least...

Here's some cli output.

Code: Select all

 cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sda8[0] sdb8[1]
      973482688 blocks [2/2] [UU]

unused devices: <none>
root@NAS-fvdwsl:/ # fdisk -l

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb1               9          72      514080  83 Linux
/dev/sdb2              73         136      514080  83 Linux
/dev/sdb3             137         200      514080  82 Linux swap
/dev/sdb4             201      121601   975153532+  5 Extended
/dev/sdb5             209         312      835380  83 Linux
/dev/sdb6             321         328       64260  83 Linux
/dev/sdb7             337         400      514080  83 Linux
/dev/sdb8             409      121601   973482772+ 83 Linux

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               9          72      514080  83 Linux
/dev/sda2              73         136      514080  83 Linux
/dev/sda3             137         200      514080  82 Linux swap
/dev/sda4             201      121601   975153532+  5 Extended
/dev/sda5             209         312      835380  83 Linux
/dev/sda6             321         328       64260  83 Linux
/dev/sda7             337         400      514080  83 Linux
/dev/sda8             409      121601   973482772+ 83 Linux

Disk /dev/md0: 996.8 GB, 996846272512 bytes
2 heads, 4 sectors/track, 243370672 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md0 doesn't contain a valid partition table

mke2fs -t ext3 -j -m 1 /dev/md0
mke2fs 1.42.11 (09-Jul-2014)
/dev/md0 contains a ext3 file system
        last mounted on Wed Nov 16 12:00:34 2011
Proceed anyway? (y,n) n



How come md0 isn't reconized as a valid partition table?

[Jocko]

Hi danyboy666,

So you found all asked information yourself :thumbup :thumbup

About your last output, please to note /dev/md0 is only a partition and not a block device so you get this error message with fdisk command (So no issue here):on my 5big2,

Code: Select all

root@Acrab:/ # fdisk -l
...

Disk /dev/md0 doesn't contain a valid partition table
fdisk: device has more than 2^32 sectors, can't use all of them

...

Disk /dev/md1 doesn't contain a valid partition table

Other advice: never try to format a partition already mounted and if you see your samba shares that means md0 is currently mounted

[danyboy666]

Thanks for answering

Yeah Jocko i usually am persistant in what i do.

Pretty much the only question left now here is why the front LED is blinking red? Is this normal behaviour once we set up these NASes in RAID1 with fvdw-ls? I did use the option in web interface "move add-ons and technicals shares" before adding sda8 to the raid array.

Let me think this thru and please correct me if i'm wrong:

In theory from what i can figure out the OS is still on sda4 only. The addons (well the word says it all i guess :P I was able to get some addons like Plex from this forum) volumes and technicals share (smb, nfs, etc) are moved from sda8 to md0.

For the simple minded like me would it be possible to create some new RAID1 devices for the OS files and the rest of sda (like boot partition , swap etc). Well a little like LaCie did originaly i guess and multiple other software raid like i.e. freePBX etc... My end goal here would be to able to boot from one disk or the other in case something goes bad and i loose a HDD. I could recover the NAS from the other disk without having to reinstall fvdw-sl...

If not what other options (if any) are there to acheive my end goal?

edit: It seem plexmediaserver was already part of the basic package so i won't need the plex addons after all

[danyboy666]

Well now the front led is solid blue for some reason :/ this NAS confuses me more and more. I think there is a issue were i does not completely reboot when i use the web interface shutdown/reboot command. This as cause me problems a couple time with the install of fvdw where i had to do the install procedure twice using fvdw-sl console. Again once i was able to get full acces to the NAS via the web interface i had to upload the firmware a second time after i had troubles with the clock.

[Jocko]

Ouups, I forgot this red LED issue and it is the expected behaviour :
As long as the raid is not fully synchronized, the red LED is blinked.

Now I think your raid as a clean status : you can check that in the disks menu.
Note: more details in the help page of the main setup menu

For the simple minded like me would it be possible to create some new RAID1 devices for the OS files and the rest of sda (like boot partition , swap etc). Well a little like LaCie did originaly i guess and multiple other software raid like i.e. freePBX etc... My end goal here would be to able to boot from one disk or the other in case something goes bad and i loose a HDD. I could recover the NAS from the other disk without having to reinstall fvdw-sl...

It is not our intention : there is no benefit. We don't want to follow the same way than the Lacie firmware which occurs a lot of issue when the firmware fails to restore the raid on its fs partitions.
Note: with fvdw-sl console you can restore them easily.

[danyboy666]

Alright thanks for the info. I guess i'll be able to manage as long as i know i have a backup for my data on sdb8. Yes you are right about the raid being clean it saw it in the web interface.

Also about that front LED should i expect the RAID to be syncing every at every reboot? Which mean about 90 minutes of syncing. I have just rebooted and now the front led is blinking red so does the HDD (sda) status led. sdb is quiet though. Its status led isn't doing anything at all.

here are the HDD info from disk setup tab:

Code: Select all

Disk-A
RD1-0      clean   raid1   928.39 GB   904.00 GB
Disk-B
RD1-0      clean   raid1   928.39 GB   904.00 GB

also

Code: Select all

cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sda8[0] sdb8[1]
      973482688 blocks [2/2] [UU]

unused devices: <none>


But front LED is still blinking its heart out :/ lol

edit: now i just saw sdb status LED light up it guess everything is working at it shoyuld i should just be have more patience with it.
edit2: the led does not stop blinking RED unless i completely unplug the power supply from the NAS and leave it still for about 10 minutes.

[Jocko]

edit2: the led does not stop blinking RED unless i completely unplug the power supply from the NAS and leave it still for about 10 minutes.

Currently I don't have an explanation about it :scratch Very amazing!

As you use version 16.0 for a first install, I think you should install this patch : viewtopic.php?f=7&t=2314.

Indeed without it, LED settings are initialized twice and in your case I think the second initialization overwrites the actions of mdadm monitoring which sets the LED state in accordance with the raid status. (This can explain fully or not your LED issue).

[danyboy666]

I want to test te patch but i want to make sure it is safe for me to use since i've already upgraded to 16.1?

edit : Well it does say the patch was successful. I reboot an test it right away.

edit : The NAS Front LED blinking RED unfortunately