hi ryecoaaron,
i haved tried now samba with rsync. i still have problems with the mounting.
now i use /dev/sda/ as NAS via samba, and /dev/sdb as backup via rsync. i just made a reboot and both HDDs were not mounted! i had to do this manually. maybe the reason for this problems is the general mounting of an USB drive.
it is really frustrating...
Hi rfv,
I am not an Linux Pro, so i am not able to solve this problems alone.
reagarding this post klick klack, mabye RAID is not the perfect solution for me.
Maybe a simple Samba Share with an manual Backup for exampe every weekend is easier to maintain and to handle...
I'd prefer a RAID 1 Array AND a manual Backup, for exampe every week or every two weeks.
Now i have no backup.
greeting from Austria
hi rfv-370
do you use an powerd USB hub? In my case i've connected my USB HDDs directly to the Raspberry Pi. One possible error source could be the insufficient power supply from the Raspberry Pi. I use a 2,5 Ampere power supply.
maybe i should try this with an USB hub...
kind regards
PS: found now the Tec Specs from WD. Maximum electrical current consumption for a 2 TB is 0,67 Ampere at Startup. So with two HDDs maximum around 1,2 A. that means there are still 1,3 Ampere for the Raspi, which should be enough, i hope
Hello,
I tried to set up an NAS with an RAID 1 (Mirror) array on a Raspberry Pi 3. At the Moment I use 2x Western Digital Elements 25A2 USB 3.0 1 TB Harddrives. The Image from the Download Server was written to the SD Card. I've made all Updates & Upgrades incl. the Topic with the PUBLIC_KEY.
It took around 30 Minutes until the RAID Array was complete. Afterwards I made a User, a Share and configured SMB/CIFS. The NAS was quickly found by my Mac and also from my Windows 10 PC. I've copied some Files on the NAS, what worked perfect. As a further Test I've done a reboot. And now the NAS Share is not found anymore. The HDDs should be EXT4.
Now to the Facts:
Version: 2.2.7 (Stone Burner)
Processor: ARMv 7 Processor rev 4(v7l)
Kernel: Linux 4.4.13-v7+
Details Storage - Physical Disks (See Screenshot)
Device Model Serialnumer Vendor Capacity
/dev/mmcblk0 n/a n/a n/a 14,84 GiB
/dev/sda Elements 25A2 Serialnumber Western Digital 931,48 GiB
/dev/sdb Elements 25A2 Serialnumber Western Digital 931,48 GiB
Details Storage - RAID Management: (See Screenshot)
Empty, no Data
Details Storage - File System (See Screenshot)
Further Informations:
cat /proc/mdstat
Personalities :
unused devies: none
blkid
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="boot" UUID="7D5C-A285" TYPE="vfat"
/dev/mmcblk0p2: UUID="5d18be51-3217-4679-9c72-a54e0fc53d6b" TYPE="ext4" LABEL="omv"
/dev/mmcblk0p3: LABEL="data" UUID="fa36508a-b3c4-4499-b30a-711dd5994225" TYPE="ext4"
/dev/sdb: UUID="2df86e3b-ce69-3f15-cab5-71cd1c411e56" UUID_SUB="9fd4398b-3ea3-d849-e1e6-add66ae0b18c" LABEL="RasPi3NAS:OMVNAS" TYPE="linux_raid_member"
/dev/sda: UUID="2df86e3b-ce69-3f15-cab5-71cd1c411e56" UUID_SUB="fefbed98-7ec4-db1f-3428-7b788e91c792" LABEL="RasPi3NAS:OMVNAS" TYPE="linux_raid_member"
fdisk -l
Disk /dev/mmcblk0: 15.9 GB, 15931539456 bytes
4 heads, 16 sectors/track, 486192 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b5098
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 8192 122879 57344 c W95 FAT32 (LBA)
/dev/mmcblk0p2 122880 7028735 3452928 83 Linux
/dev/mmcblk0p3 7028736 31116287 12043776 83 Linux
Disk /dev/sdb: 1000.2 GB, 1000170586112 bytes
255 heads, 63 sectors/track, 121597 cylinders, total 1953458176 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/sda: 1000.2 GB, 1000170586112 bytes
255 heads, 63 sectors/track, 121597 cylinders, total 1953458176 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/sda doesn't contain a valid partition table
cat /etc/mdadm/mdadm.conf
root@RasPi3NAS:~# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 name=RasPi3NAS:OMVNAS UUID=2df86e3b:ce693f15:cab571cd:1c411e56
# instruct the monitoring daemon where to send mail alerts
MAILADDR ...@gmx.at
MAILFROM root
mdadm --detail -- scan --verbose
no Output
Thanks in advance for your help!
Greetings from Austria
