Thanks.
I would like explanation to always have an access for anonymous/ guest read only.
sometimes when I want to upload to OMV, use then a specific user
Thanks again
Thanks.
I would like explanation to always have an access for anonymous/ guest read only.
sometimes when I want to upload to OMV, use then a specific user
Thanks again
Hi,
After reading a loton news ransomware and because my kids grow up, I would like a guide or some advise on setting permission.
I have a shared folder with ACL to "users" on RWE. But "others" too (RWE) : I think it's not such a good idea (my omv is nbot open to internet though)
No user or group set (but plex)
don't need a folder for each user. Just an easy way to prevent deletions, or attacks from ransomware
thanks
Sorry, but no one has an answer ?
Thanks.
Hi,
after a bunch of bad things (RAID6 : clean, degraded), I went to linux-raid on irc where some told me to use write intent bitmaps for better recover when a disk jump out an array (if I get that clear) or in case of power failure etc...
I red some trackers, like here : http://bugtracker.openmediavault.org/view.php?id=669 and this : http://blog.liw.fi/posts/write-intent-bitmaps/
Thing is, if you specify the resolution, it appears that the impact on speed is not so big.
So do we manually need to mdadm --grow --bitmap=internal --bitmap-chunk=256M /dev/md0 via CLI or is it done by default ? Or is it not recommanded ?
Thanks
You have to put the result of :
When ssh into the system.
What is the output of (login as root):
cat /proc/mdstat
fdisk -l
blkid
Thanks ryecoaaron
I know about the backup, I have some data on another backup, but not "all" datas.
Just fast wiped dev/sdg, raid tab is still not showing grow, just recover. (the size of the array is still the same, so I don't understand why to grow)
I did reboot after a wipe, still the same. Here the details :
Version : 1.2
Creation Time : Sat Aug 31 01:10:06 2013
Raid Level : raid6
Array Size : 5860548608 (5589.05 GiB 6001.20 GB)
Used Dev Size : 1465137152 (1397.26 GiB 1500.30 GB)
Raid Devices : 6
Total Devices : 5
Persistence : Superblock is persistent
Update Time : Sat Feb 28 07:54:53 2015
State : clean, degraded
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Name : zetta:0
UUID : 96b0e7b7:83aa203f:1545031b:43caaa85
Events : 34062
Number Major Minor RaidDevice State
0 8 80 0 active sync /dev/sdf
1 8 32 1 active sync /dev/sdc
2 8 0 2 active sync /dev/sda
3 8 64 3 active sync /dev/sde
4 8 16 4 active sync /dev/sdb
5 0 0 5 remove
Display More
Here :
root@Zetta:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid6 sdf[0] sdb[4] sde[3] sda[2] sdc[1]
5860548608 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/5] [UUUUU_]
unused devices: <none>
root@Zetta:~# blkid
/dev/sda: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="70983681-b5c2-9f70-1801-948b1b7c97d1" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sdc: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="2873612e-8481-0c22-4d4f-9183d2bf6a6d" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sdb: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="66843575-1a9c-30a6-8172-29f3ded468dc" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sdd1: UUID="b364f189-c9af-4774-92ba-a49307966cf7" TYPE="ext4"
/dev/sdd5: UUID="c78b6a64-1caa-4290-bc1a-eebe67731ca5" TYPE="swap"
/dev/sdf: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="b2460066-00b1-5070-cfe3-7ac67aae96c1" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sde: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="ee7eab8f-dc90-e3be-146d-a4e09d104418" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/md0: LABEL="ZettaFiles" UUID="76c7546c-5ae6-4884-ac9f-3ecda0f473bc" TYPE="ext4"
root@Zetta:~# fdisk -l
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 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
Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 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/sdc doesn't contain a valid partition table
Disk /dev/sdd: 100.0 GB, 100030242816 bytes
255 heads, 63 sectors/track, 12161 cylinders, total 195371568 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: 0x0008101c
Device Boot Start End Blocks Id System
/dev/sdd1 * 2048 187367423 93682688 83 Linux
/dev/sdd2 187369470 195371007 4000769 5 Extended
/dev/sdd5 187369472 195371007 4000768 82 Linux swap / Solaris
Disk /dev/sde: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/sde doesn't contain a valid partition table
Disk /dev/sdg: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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/sdg doesn't contain a valid partition table
Disk /dev/sdf: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/sdf doesn't contain a valid partition table
Disk /dev/md0: 6001.2 GB, 6001201774592 bytes
2 heads, 4 sectors/track, 1465137152 cylinders, total 11721097216 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 2097152 bytes
Disk identifier: 0x00000000
Disk /dev/md0 doesn't contain a valid partition table
Display More
EDIT : 03/01/2015 13:35 GMT : I went to linux-raid to have some help, I launched a badblock stress test on /dev/sdg while monitoring smart values and dmesg. Here the syslog I grabed in var/log when the disk was kicked out : http://pastebin.com/vjmVe7K7. Someone told me about write-intent bitmap that I might want to look into adding a write-intent bitmap for my array. Then I looked on a bugtracker http://bugtracker.openmediavault.org/view.php?id=669 about this feature, and slow speed http://blog.liw.fi/posts/write-intent-bitmaps/.
The performance penalty depends of what bitmap chunk size I use, he said. He said I could use something big like 256MiB for example, he remember seeing some test results where bigger chunk sizes had a very minimal effect on performance. He wrote that it is easy to test for myself because bitmaps can be added and removed on the fly and that omv probably should revisit their decision of not enabling it by default.
EDIT2-4 : Added the package iotop to monitor my badblacks writing, beacause it's veryyyyy slooooooooooowwwwwwwwwwww (and it is : 4849 be/4 root 0.00 B/s 7.19 M/s 0.00 % 99.99 % badblocks -w -s /dev/sdg). Added a -b xxx and -s xxxx and badblocks writing is now on 129M/s
Edit 3 : Ryecoaaron, should I add the disk via the cli (beacause the gui won't let me, via mdadm --add /dev/md0 /dev/sdg ?
EDIT 5 : I did add sdg to md0 via CLI, now it's recovering. should I add mdadm --grow --bitmap=internal --bitmap-chunk=256M /dev/md0 after ?
OK, thanks !
I did not do anything though. Should I recover (there is no option for grow that is availbale for md0)
I do not see md127 in the raid management tab.
Should I begin with the grow button anyway ?
EDIt : I cant grow, I only have recover that I can use.
What happened before ? Do you have an idea why I got a degraded state ?
root@Zetta:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md127 : inactive sdg[5](S)
1953383512 blocks super 1.2
md0 : active raid6 sdf[0] sdb[4] sde[3] sda[2] sdc[1]
5860548608 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/5] [UUUUU_]
unused devices: <none>
root@Zetta:~# blkid
/dev/sda: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="70983681-b5c2-9f70-1801-948b1b7c97d1" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sdc: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="2873612e-8481-0c22-4d4f-9183d2bf6a6d" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sdb: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="66843575-1a9c-30a6-8172-29f3ded468dc" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sdd1: UUID="b364f189-c9af-4774-92ba-a49307966cf7" TYPE="ext4"
/dev/sdd5: UUID="c78b6a64-1caa-4290-bc1a-eebe67731ca5" TYPE="swap"
/dev/sdf: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="b2460066-00b1-5070-cfe3-7ac67aae96c1" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sde: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="ee7eab8f-dc90-e3be-146d-a4e09d104418" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/sdg: UUID="96b0e7b7-83aa-203f-1545-031b43caaa85" UUID_SUB="5692ca13-808b-56c0-8bf5-066f5574a5c4" LABEL="zetta:0" TYPE="linux_raid_member"
/dev/md0: LABEL="ZettaFiles" UUID="76c7546c-5ae6-4884-ac9f-3ecda0f473bc" TYPE="ext4"
root@Zetta:~# fdisk -l
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 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/sdc doesn't contain a valid partition table
Disk /dev/sdf: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/sdf doesn't contain a valid partition table
Disk /dev/sde: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000
Disk /dev/sde doesn't contain a valid partition table
Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 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
Disk /dev/sdd: 100.0 GB, 100030242816 bytes
255 heads, 63 sectors/track, 12161 cylinders, total 195371568 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: 0x0008101c
Device Boot Start End Blocks Id System
/dev/sdd1 * 2048 187367423 93682688 83 Linux
/dev/sdd2 187369470 195371007 4000769 5 Extended
/dev/sdd5 187369472 195371007 4000768 82 Linux swap / Solaris
Disk /dev/sdg: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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/sdg doesn't contain a valid partition table
Disk /dev/md0: 6001.2 GB, 6001201774592 bytes
2 heads, 4 sectors/track, 1465137152 cylinders, total 11721097216 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 2097152 bytes
Disk identifier: 0x00000000
Disk /dev/md0 doesn't contain a valid partition table
Display More
OK, just did replace the cable. How do I put the disk back into the array ?
In gui ? raid management, recover ?
thanks
I had a mail this morning :
This is an automatically generated mail message from mdadmrunning on ZettaA DegradedArray event had been detected on md device /dev/md/zetta:0.Faithfully yours, etc.P.S. The /proc/mdstat file currently contains the following:Personalities : [raid6] [raid5] [raid4]md0 : active raid6 sdf[0] sdb[4] sde[3] sda[2] sdc[1] 5860548608 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/5] [UUUUU_]unused devices: <none>
Here is the details of RAID
Version : 1.2
Creation Time : Sat Aug 31 01:10:06 2013
Raid Level : raid6
Array Size : 5860548608 (5589.05 GiB 6001.20 GB)
Used Dev Size : 1465137152 (1397.26 GiB 1500.30 GB)
Raid Devices : 6
Total Devices : 5
Persistence : Superblock is persistent
Update Time : Fri Feb 27 11:30:46 2015
State : clean, degraded
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Name : zetta:0
UUID : 96b0e7b7:83aa203f:1545031b:43caaa85
Events : 27546
Number Major Minor RaidDevice State
0 8 80 0 active sync /dev/sdf
1 8 32 1 active sync /dev/sdc
2 8 0 2 active sync /dev/sda
3 8 64 3 active sync /dev/sde
4 8 16 4 active sync /dev/sdb
5 0 0 5 removed
Display More
Seems that sdbg is missing (added it one month ago via a pci-raid card)
Here the smart of sdbg (smart is showing some errors) :
Thanks
Yes thanks,
I though it would be specific on install on omv, but no, you're right
resolved anyway, thanks again
Thanks again for your time.
If I'm at home and look on the transfert rate, it appears that they're far at the limit of my isp, does it go through smartphone-wan-internet nebula-wan-omv or smartphone-wan-omv ?
Thanks subzero79 worked with private windows
is there any more complete guide on Sync ?
i did add a folder in omv but seems not to be the right way if I just need to backup some folder on my phone.
Deleted the share folder and added some on my phone then pasted the link on the gui , is it the right way ?
If I'm at home, could the file only use my WAN ?
(sorry for all the questions)
invalid request
Hi,
Installed btsync on omv, added one folder that should have multiple backup folder of my phone.
In Btsync, you could add a sync folder (no bulk folder addind, strange) or a one way folder (http://help.getsync.com/custom…-data-from-android-device)
But how do I add those links created by btsync ? (I red that I should qo the the web ui, but it does not work on port 8888)
Thanks
Thanks, done, resolved, sorry for the time...
Hi,
totally lost with btsync, I tried to add some folder, no permission, I see those folder, cant delete them....
Should I add a user ? I don't have any
Any guide or tutorial ?
thanks
Red this, but again... lost... what should I do ?
Really ? That's why my disks are not spinning down ? I set them for two hours.
Soll ich dann denen auf 30 minuten einstellen ?
Merci beaucoup.