New approach for Raspberry Pi OMV images

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • lex wrote:

      my point is, I miss the old Raspbian images and its little bit strange to switch to the Arabian image, which is build from someone who bash permanent the raspberry pi
      Sorry, can't help you with your understanding problems :)

      In my opinion it's pretty easy to get that any Raspberry Pi is the most lousy SBC possible for NAS use cases since bottlenecked by 'single USB2' and suffering from underpowering problems. No idea how this can be missed if you look more closely at the hardware?

      Then what do you not understand wrt focusing on OMV users? Why shouldn't we care about users any more?
      • Since the RPi is such a lousy choice for a NAS it's important that users be aware of that. So they can choose optimal hardware for the use case they're interested in
      • Since an awful lot of users have already an RPi lying around why not trying to provide them with the best OMV experience possible? Why not letting RPi users too benefit from our 'OMV on ARM devices' journey that started almost a year ago? Why should we exclude them?
      If you're not able to understand how limited every RPi out there is when it's about NAS usage then I'm sorry but I fear nobody can help you. Same with asking to exclude the many RPi users from good software. Why should this happen? Why shouldn't RPi users also be able to run 'best OMV possible'?

      Or are you asking for fanboy behaviour? Sorry, impossible.

      BTW: Since there's a potential performance problem with the freshly announced RPi 3 B+ I thought it's a good idea to both check for this issue with RPi folks and to prepare a new OMV image for RPi that already supports the new board (needs a new 'firmware'), is based on OMV4 and contains the few missing tweaks from the other ARM images.

      I ordered an RPi 3 B+ an hour ago but canceled it right now and deleted the preparations for the new OMV4 image. Thanks for the reminder that it's simply not worth the efforts with this target audience :)
    • C'mon @tkaiser.

      Lot's of people stumble onto OMV, by the impulse purchase of a Raspberry PI.
      (It's kind of like the first junker car young folks buy until they realize that, by "saving money", they've bought into a lot of mechanical problems.) With that experience in hand, the second time around, generally they do better.

      An R-PI is a kind of "gateway" device. When new users learn about an R-PI's limitations, many buy better hardware.
      (I'd have to include myself in that group.)

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.13, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk

      The post was edited 1 time, last by flmaxey: edit ().

    • For users of freshly released RPi 3 B+

      Since RPi Foundation changed hardware requiring both new 'firmware' and kernel support the currently available OMV image won't boot on the new board. Symptom looks like undervoltage when a display is connected (displaying the yellow lightning bolt) but it's simply the old firmware refusing to boot the new hardware.

      So it's necessary to replace the entire contents of the /boot partition (FAT partition so accessible from a PC or Mac too) with this:…mp/ZCLu0r/RPi_3B_Plus.tgz (archive created with most recent Raspbian Lite image -- please do NOT touch/replace cmdline.txt, see below)

      This should then boot the RPi 3 B+ with latest RPi 4.9.80 kernel, as usual a network connection is needed and the installation will finish itself (depending on the random IO performance of the SD card used this might take between 10 and 40 minutes). Whole procedure is not tested so you're on your own :)

      As a reference the MD5 hashes of the files below:

      Source Code

      1. /bcm2708-rpi-0-w.dtb = d30b0502fc64ae3823f06dad9434be49
      2. /bcm2708-rpi-b-plus.dtb = 675f76122229998987ed7a1a0f39f9b7
      3. /bcm2708-rpi-b.dtb = 58d5ad9bb6ca5a40638f6a05d2d68c04
      4. /bcm2708-rpi-cm.dtb = 22c3b79d9d9d8cebdb66fcbddaac4580
      5. /bcm2709-rpi-2-b.dtb = 1e85b095e25e251283c5f57ab240e57f
      6. /bcm2710-rpi-3-b-plus.dtb = 486e9842b90882d15b1256f766dc7a65
      7. /bcm2710-rpi-3-b.dtb = abecabda368546d919b6fe36614ffa3a
      8. /bcm2710-rpi-cm3.dtb = 42c574ddf5e0656cd281bf7b24ebc57f
      9. /bootcode.bin = 17efaf1c1ef89289168d71cdc8194982
      10. /cmdline.txt = cc7ccb294005ab749b7ad05c95f86ef1
      11. /config.txt = 80b7eb3ff610070c7f12a64ee6488462
      12. /COPYING.linux = d7810fab7487fb0aad327b76f1be7cd7
      13. /fixup_cd.dat = 6a1ddd7c356c6b8c17a17325c0f401c4
      14. /fixup_db.dat = 855c94dbf591d47c0899e0b6826bfc3c
      15. /fixup_x.dat = d7204150b473ad2c12fa8f2f7a900c35
      16. /fixup.dat = ac7285bb66213dea31b075a85e0e85c1
      17. /issue.txt = bdc6492254aec36a53f90506a22ba6a9
      18. /kernel.img = 5a7a829c42fbf63ea6a60d3096786ec8
      19. /kernel7.img = e9c2785ad16ebea292ec72f437dbcdb2
      20. /LICENCE.broadcom = 4a4d169737c0786fb9482bb6d30401d1
      21. / = bcd91fdfffb0cf7518016189fca363ee
      22. /start_cd.elf = 0e45ec15dfc04478d8250e75a5ac4241
      23. /start_db.elf = f9f48941e4dc7464a0043f1e6701fed0
      24. /start_x.elf = 0397cdeca76af918d1d734a69392a741
      25. /start.elf = e0ba1be18e5226992a90255c7c9443ec
      26. /overlays/adau1977-adc.dtbo = 8c9f2e2565679f0289f34496616306ae
      27. /overlays/adau7002-simple.dtbo = 619d88a7ce4139bfa69822d2df2ac140
      28. /overlays/ads1015.dtbo = 9f1acfc8e39f637c97a26ae34013fccd
      29. /overlays/ads1115.dtbo = 23acc514a7b5ca9d9f6f03ad1f0b9985
      30. /overlays/ads7846.dtbo = 9d26ce0b38a8d145ac06a4677b22264d
      31. /overlays/akkordion-iqdacplus.dtbo = 78533766c36019cdefc3aa2ee5be6209
      32. /overlays/allo-boss-dac-pcm512x-audio.dtbo = 5d2b1ed068fc3b1d2025f090e8ec2270
      33. /overlays/allo-digione.dtbo = f6c53b64b7c0bcb12f1e02e90f27c9ed
      34. /overlays/allo-piano-dac-pcm512x-audio.dtbo = aec52dfb7d7a43c1364ab1322ab67b77
      35. /overlays/allo-piano-dac-plus-pcm512x-audio.dtbo = 66da42d386cc14ee56f5c4b6aade4ec6
      36. /overlays/applepi-dac.dtbo = 19d95819caa574c5ba7adb4ac416db4b
      37. /overlays/at86rf233.dtbo = 3deab7985101cba215b819ab3cd2bd65
      38. /overlays/audioinjector-addons.dtbo = ac92353363c8d535301c556cd48f0bc0
      39. /overlays/audioinjector-wm8731-audio.dtbo = dbfe8d5d7766641840a03e9d222ccddd
      40. /overlays/audremap.dtbo = 5293741528ecc872dc5ceec69edbf54a
      41. /overlays/bmp085_i2c-sensor.dtbo = 70e8a67c9e86332e05f4d8f8269359a7
      42. /overlays/dht11.dtbo = a290239cfc535a392900d59e9568fd76
      43. /overlays/dionaudio-loco-v2.dtbo = 340115ac68a8bc9c460b554681939dd7
      44. /overlays/dionaudio-loco.dtbo = 18e14bb636e18334be73e66bbe5862b5
      45. /overlays/dpi18.dtbo = 7bc3103e84a97cdfca4ecb530cf01422
      46. /overlays/dpi24.dtbo = fbfe3584aaca14fffef539ec3f074664
      47. /overlays/dwc-otg.dtbo = 7bff9a325a00819223503456fa947a9c
      48. /overlays/dwc2.dtbo = 96d7487944d606ff3417043b7ad99984
      49. /overlays/enc28j60-spi2.dtbo = ae574e33edd6b7f8e3492ac0ffaae304
      50. /overlays/enc28j60.dtbo = 2e11117a6ea394f70db231e223db1cc3
      51. /overlays/exc3000.dtbo = 1079762f4ea6b6b4bd12e77110ced7b3
      52. /overlays/fe-pi-audio.dtbo = df6eae2270e551bebb2949f9937f681f
      53. /overlays/goodix.dtbo = 36b66a17a735cdec865457ac4507b546
      54. /overlays/googlevoicehat-soundcard.dtbo = 9a9f56649c06f35ae375c6fdb53d1233
      55. /overlays/gpio-ir.dtbo = 51abcdf45839d43098b6019a0d739d97
      56. /overlays/gpio-key.dtbo = ef6850555b528969311c10f4f648af4a
      57. /overlays/gpio-poweroff.dtbo = 2e1987470d43c4203b4a88e8d003a14c
      58. /overlays/gpio-shutdown.dtbo = f425f8034019e8a8e2f197e66f06d7db
      59. /overlays/hifiberry-amp.dtbo = 55d846402c6b97a14eba51d101067be9
      60. /overlays/hifiberry-dac.dtbo = b7bc0a27f234efbeb05361739c4c18d3
      61. /overlays/hifiberry-dacplus.dtbo = 78dbe42826ba6d1d95b359d596a7a1ae
      62. /overlays/hifiberry-digi-pro.dtbo = feb36e425b6abfc54dd7025bfa8e5771
      63. /overlays/hifiberry-digi.dtbo = 83d53a61ee079f39356f8d795907d84a
      64. /overlays/hy28a.dtbo = 2efdaf270f05f961cc05426429bea405
      65. /overlays/hy28b.dtbo = 20fee2a45add1ef7287be160a25180a6
      66. /overlays/i2c-bcm2708.dtbo = 9d8bcf63ca0fe4e7b10d63aead511868
      67. /overlays/i2c-gpio.dtbo = 26c2fec82f78960e84b503a409899313
      68. /overlays/i2c-mux.dtbo = f9dd2b3934177d2ea7d7a5a47bbaf1af
      69. /overlays/i2c-pwm-pca9685a.dtbo = d3ccf890ce6166bb78fb9c6832a1cc02
      70. /overlays/i2c-rtc-gpio.dtbo = 765ce90447d9aba02fccbc32d8cb32f3
      71. /overlays/i2c-rtc.dtbo = f160b232729be7f6a497ec3c48f30d03
      72. /overlays/i2c-sensor.dtbo = 58fa5a09da06587378c83b2c389daee0
      73. /overlays/i2c0-bcm2708.dtbo = 4a82245332e74002e7ea0b5d52280b44
      74. /overlays/i2c1-bcm2708.dtbo = e5f15029c18ba752bb39ff4ea3407ade
      75. /overlays/i2s-gpio28-31.dtbo = b425e56201d7abec38fb6700b86028ae
      76. /overlays/iqaudio-dac.dtbo = f32d33216eecfc1270d8070a5ba0e28a
      77. /overlays/iqaudio-dacplus.dtbo = e1a235ecbf6f7a39e3c1b499f6d352b0
      78. /overlays/iqaudio-digi-wm8804-audio.dtbo = cce62a21f17ef66b9ba9109775860ce2
      79. /overlays/justboom-dac.dtbo = 206f25aca7f4dfd7cb1e9b6632706001
      80. /overlays/justboom-digi.dtbo = c92d86b016cd1dc9efc12ecf9833c86c
      81. /overlays/lirc-rpi.dtbo = ee909db3c7a18a61554f271fece272ed
      82. /overlays/mbed-dac.dtbo = 56581be308c7c3627d6126a4b369c210
      83. /overlays/mcp23s17.dtbo = 8ef72b235cd76a573a3b55683041b2db
      84. /overlays/mcp2515-can0.dtbo = 14a6bba9a2603393f1057ad4ecdfee85
      85. /overlays/mcp2515-can1.dtbo = 5ff277894b00e7c014ab4bc3254d514e
      86. /overlays/mcp3008.dtbo = 2637ec10a2fe0dffc68270734b924f84
      87. /overlays/mcp3202.dtbo = 853b850cb0f0519afe03ad66ecf1332f
      88. /overlays/mcp23017.dtbo = fa0acb72660a7ce2e4b0e0128ab679db
      89. /overlays/media-center.dtbo = e9545a7db2c0e939201e9557d013ef81
      90. /overlays/midi-uart0.dtbo = cf7cd3017d0bea33a6d3391b2561a7ce
      91. /overlays/midi-uart1.dtbo = 1838f1e4c44899d575e861f470e9b18f
      92. /overlays/mmc.dtbo = 0342255f947824abbab6fa90f2c47b96
      93. /overlays/mpu6050.dtbo = 1888ac8c2cc5e5b7184cf8aa1a2bda9b
      94. /overlays/mz61581.dtbo = 554fc649784b040f4d031a36bb817ce9
      95. /overlays/papirus.dtbo = e8fc532be9c3aee91b615120934d2213
      96. /overlays/pi3-act-led.dtbo = df6772b1084a3a39d680c8e8720647a2
      97. /overlays/pi3-disable-bt.dtbo = b1a5c032c04eb41c4b91abe959a89bb7
      98. /overlays/pi3-disable-wifi.dtbo = d79490897d3dfb9693c557c54636f971
      99. /overlays/pi3-miniuart-bt.dtbo = bc8c331ad2e494b37f72389a9fdf599d
      100. /overlays/piscreen.dtbo = 212ff887bc71772c0d3ebd7f97afa0af
      101. /overlays/piscreen2r.dtbo = 441f35003d0cb8db276200cb2d11bddb
      102. /overlays/pisound.dtbo = 27a561f056b80e2afddc444b4043ca76
      103. /overlays/pitft22.dtbo = c92865fca63ca320bc4bab14b9b80c99
      104. /overlays/pitft28-capacitive.dtbo = 15dd29939e6358a5f1295046e91b03e6
      105. /overlays/pitft28-resistive.dtbo = d693a0ebe5b4fa3aefb37a94cda9f202
      106. /overlays/pitft35-resistive.dtbo = e9377c23a8169852f050853e17e779cd
      107. /overlays/pps-gpio.dtbo = 306b992c4f2c9bd607f2147e4854d1bf
      108. /overlays/pwm-2chan.dtbo = 2955e1577479b02c4b202aed852ba0fa
      109. /overlays/pwm.dtbo = f0db2ac4a9d4bc81a8fcc067cea34e3d
      110. /overlays/qca7000.dtbo = 65c687e51bddfea4ce8fdcc86b48e7bc
      111. /overlays/raspidac3.dtbo = a38202a2ee6d79603ffa8cdc652a6008
      112. /overlays/README = 1942d572661ff80ff3c28d3d7a65a6c0
      113. /overlays/rotary-encoder.dtbo = 0c3cac7d442d1c36d9eebebd84bd7571
      114. /overlays/rpi-backlight.dtbo = cef94731b0416864bdcc30f62bdba03a
      115. /overlays/rpi-cirrus-wm5102.dtbo = 7e0d44c9a28dc83f9fc9dfe9494d1d53
      116. /overlays/rpi-dac.dtbo = cb2871bec47cb1db46b21ce981a7a422
      117. /overlays/rpi-display.dtbo = 481d139c020f0ade417e45b23d32671e
      118. /overlays/rpi-ft5406.dtbo = 448b791c76b481b8250f397690f306f5
      119. /overlays/rpi-proto.dtbo = 383830fe141c0cb5763e4eeaf22e5393
      120. /overlays/rpi-sense.dtbo = 0eb16d590b35339e2b1272edcdbb2b7c
      121. /overlays/rpi-tv.dtbo = 2bcc95bd016a934b55cb489a7e99cd83
      122. /overlays/rra-digidac1-wm8741-audio.dtbo = 87472d6a47766d846b9b420e5574c5dd
      123. /overlays/sc16is750-i2c.dtbo = 75b5fb84aadfb2d55bd36e89c0a56feb
      124. /overlays/sc16is752-spi1.dtbo = e43107b02a42eed39684eaa8324ccc38
      125. /overlays/sdhost.dtbo = fc90ea81d398b67478efec0e1362d601
      126. /overlays/sdio-1bit.dtbo = a0172054e302f5dbd138188bfdc0dc8e
      127. /overlays/sdio.dtbo = 5e1d27ff963aedf31fe65a0a7f6c2c0d
      128. /overlays/sdtweak.dtbo = fba033aa2b9d264b5d70dc15c39b8cac
      129. /overlays/smi-dev.dtbo = 903d0d7da4a28bafea3b4304cc10a52c
      130. /overlays/smi-nand.dtbo = 29466091b650c2835f22e7f6d064513d
      131. /overlays/smi.dtbo = 6ca622f5455763c2c35b9418ca2263e4
      132. /overlays/spi-gpio35-39.dtbo = 430a3122eea8612bf08acba76795b553
      133. /overlays/spi-rtc.dtbo = 91bf1249c74532cae3f6371bc526ae89
      134. /overlays/spi0-cs.dtbo = be6f917da5d26245fe710679de2bf504
      135. /overlays/spi0-hw-cs.dtbo = af2b2de321be09ae6298c9328981368f
      136. /overlays/spi1-1cs.dtbo = a5e264188fd67b308c8be3e81a275497
      137. /overlays/spi1-2cs.dtbo = e3a9d8e0bd94762e9be165a5f3d1000f
      138. /overlays/spi1-3cs.dtbo = 54ac01b7374025d7ad246e23f5e78730
      139. /overlays/spi2-1cs.dtbo = bf0ba44ded0dabb8e4d3c27d7341d648
      140. /overlays/spi2-2cs.dtbo = 82aba35b9699cb2c84d268aea0008202
      141. /overlays/spi2-3cs.dtbo = 4e93b93d3d3b1729c1eb5ed6b525b92a
      142. /overlays/tinylcd35.dtbo = 60bb5f8c22cb2929bc32ed8bfb9bf7de
      143. /overlays/uart0.dtbo = 28ef560266c74fee69c006280a771263
      144. /overlays/uart1.dtbo = 7695386c7c30301ad4c0ae306cefcdd1
      145. /overlays/vc4-fkms-v3d.dtbo = 21f49cf49a0f5cd140d406c2900e5bcc
      146. /overlays/vc4-kms-v3d.dtbo = ea3faf5e38c65e52767c530921961a26
      147. /overlays/vga666.dtbo = 3d8e7f0800cf779f5df54b2f9f10bafd
      148. /overlays/w1-gpio-pullup.dtbo = e56386e3f5ea3d4a979f91674eacc5d4
      149. /overlays/w1-gpio.dtbo = 7097448f7f7a7d56d97ae4cca2def6ef
      150. /overlays/wittypi.dtbo = 521ff8be6df8c3c152a094da925b3aed
      Display All

      Edit: Silly me forgot to add that if you already have an RPi 2 or 3 then booting the OMV image there and applying all available updates (happens at 1st boot anyway) should also lead to an image that is ready for the RPi 3 B+ -- the necessary updates for kernel and bootloader are part of RPi's Stretch repos which the OMV image is able to use (via apt pinning).

      Edit 2:


      The above archive contains cmdline.txt from Rapsbian Lite image which should not be used since referencing the rootfs via an UUID not matching the rootfs from our image and also contains 'init=/usr/lib/raspi-config/' which can't work. So please exclude cmdline.txt when replacing the files on the /boot partition

      The post was edited 4 times, last by tkaiser: Not relevant any more ().

    • While a bit off topic:

      @tkaiser, note that I'm saying this with true sincerity.

      I appreciated both your skill set and grasp of the issues that surrounding the R-PI (and this newest version), and SBC's as a whole class of computing devices.

      These wrinkles and twists that the OEM's throw out there, represent real effort to fix or remediate. Most users don't understand the level of effort required in development, not so much in the time required for a single fix, but in the gathering of the skills necessary to come up with solutions. (Years, even decades of experience are required.)

      While there will always be a few who lack the understanding of what is involved in developing these images, there are scores more who appreciate being able to boot a NAS operating system on a SBC.

      I'm one of them so let me say "Thanks" for a job well and skillfully done.

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.13, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk

      The post was edited 2 times, last by flmaxey: edit ().

    • On the subject of the new RPi 3 B+......

      I have updated an existing OMV installation on a RPi 3 as per @tkaiser's post above.

      That worked fine and dandy.

      I put the SD card from this RPi into a new RPi 3 B+.

      Would you expect it to just work?

      It boots up to a command line login prompt but the system itself seems not to be working (I cannot access it through a browser). Also, the static IP address it was running on the older machine is not being used.

      Any pointers very much appreciated.
    • To cover the base;
      (Since existing installs can get "dirty" with use.)

      How about building a new install from scratch, on an R-PI 3 (where all of the latest updates are applied before the first boot). Then, with no configuration or alterations, moving it to the 3 B+ ?

      This is speculation, but worth a try.

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.13, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk

      The post was edited 1 time, last by flmaxey: edit ().

    • Yeah, I know how that is. :)

      The build is short, about 15 minutes of time, and then leaving it alone for an hour or so to be safe is easy enough. It's the (re)configuration that can take a good bit of time.

      In any case, you could try it with a spare SD-card as a test.
      If you don't have a spare SD-card - you really need one. (To clone the boot drive.)

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.13, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk
    • Hello,

      I am new to this forum and only users of OMV. I have a new RPi+ and would like to build a small NAS. With an old pi I could create a bootable image. Sounds good!. The pi boots and I can configure it via the webgui. But there are issues with media playback. The pi seems to lose connection to either the HDD or the network or it has an hardware issue. The stream stops after minutes. The stream also stops when rewinding and rewinding. Maybe someone can help. Thank's!

      With NFS I get this error
      ntfs-3g[8720]: Failed to read $MFT bitmap: Input/output error
      kernel: [ 2702.857586] Buffer I/O error on dev sda5, logical block 20, async page read

      Pi 3+ (Pi3 power supply)
      HDD with external power supply

      What was I trying to do:
      NFS/FTP/SMB all the same issue
      Separate HDD, Separate power supplies

      This configuration runs on the old Pi 3 without issues!

      The post was edited 1 time, last by tr59: log ().

    • SimonM wrote:

      The last post is specific to rasppi. Would it be worth including the following tweak in the distribution ?

      /etc/init.d/mdadm-raid file and inserted the linepartprobe
      Not in my opinion for two reasons:
      1 - raid shouldn't be used on an RPi
      2 - OMV doesn't create raid arrays using partitions
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13 plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Important to know for RPi B 3+ users!

      Now that we provide a new OMV image for RPi that also contains an updated ThreadX (that's the primary operating system running on all RPi euphemistically called 'firmware') and updated kernel+device-tree stuff booting the OMV image on latest RPi is possible. If you're interested in all the hassles and details here you go:

      The important bits:
      • On first boot we limit RPi B 3+ to just 600 MHz since an awful lot of RPi installations uses insufficient powering leading to voltage drops under load that result in instable behaviour (freezes, crashes, kernel panics, data corruption). Staying at 600 MHz results in lower consumption so under-voltage can not be triggered that easy. After the installation has been finished and the Pi reboots one time, OMV checks for under-voltage and only if this hasn't occured RPi 3 B+ will be unlocked to full performance (1400 MHz).
      • By default networking on RPi B 3+ will remain at 100 Mbits/sec. An awful lot of users replacing an older Pi with their new 3+ uses insufficient Ethernet cabling resulting in lower throughput and/or weird network problems. If you think this is not an issue in your installation feel free to edit one single config file to allow for Gigabit Ethernet (though speed improvements are not that great anyway, it's still 'shared USB2' and GbE NAS performance will be only a fifth of what all the better ARM boards provide)
      For all the following steps you need SSH access to your OMV box or display and keyboard. In any case use the web interface first and create there a new user account being member of both 'sudo' and 'ssh' groups. Afterwards you can login with this user through SSH (e.g. using the Putty program on Windows, built-in ssh command everywhere else) or at the console.

      To check for under-voltage do a 'sudo cat /var/log/raspihealth.log' or 'sudo raspimon' as explained on the first page of this thread. If you have an issue you need to fix it. This is a hardware issue. Buy a good PSU providing a stable 5.2V to your board, for example the official RPi PSU if you haven't already. Amperage ratings of the PSU are more or less irrelevant as long as they exceed 2A since the RPi problem is called 'voltage drop'. The power circuitry is that bad that you can't feed more than 2A anyway so all you have to take care of is a stable voltage provided to your Pi (cheap PSU don't, average Micro USB cables don't -- that's why a good PSU with a fixed and thick cable with low resistance is mandatory)

      In case you want to enable Gigabit Ethernet you need to edit /etc/rc.local and put a '#' in front of the ethtool line. So you do a 'sudo nano /etc/rc.local', navigate to the bottom and edit the line so it reads like this afterwards:

      Source Code

      1. # /sbin/ethtool -s eth0 speed 100 duplex full autoneg on
      Save the file and reboot. If you now run into instabilities you're affected by under-voltage (Gigabit Ethernet increases idle consumption by approx. 500mW, load consumption slightly more since more data will be transmitted in less time). Switching back to Fast Ethernet will help, using a switch that is capable of EEE/IEEE 802.3az will help too (numbers)

      If your network performance is now worse than before then you have an issue with cabling. Gigabit Ethernet uses 4 cable pairs while Fast Ethernet only 2. You can have cables that work very well with 100 Mbits/sec and you achieve 95 Mbits/sec transfer speeds in this mode while activating Gigabit Ethernet with the same cables can result in way lower numbers and tons of retransmits (since the other 2 cable pairs are the problem) or even no connection any more at all (rare).

      To check for this use iperf3 (not iperf) since this tool lists not only transfer numbers but also count of retransmits (those retransmits trash the performance: TCP/IP just like any other protocol suite uses checksums to ensure data integrity. If data got corrupted at the wire the receiver takes notice and forces the sender to retransmit the packet. The more retransmits the lower the throughput. To get an idea on what's happening at lower layers -- Ethernet frames instead of TCP/IP packages -- you could run for example iperf3 in UDP mode)

      The post was edited 2 times, last by tkaiser ().

    • And for anyone ever questioning our decision to limit RPi 3 B+ to Fast Ethernet by default... just read through this sad story: (archived version)

      RPi users refusing both to test appropriately and to accept reality. If you have retransmits you have to get rid of them. Check your cable, check your switch port, eliminate the retransmits and then performance won't suffer any more.

      People who are not network experts most probably will never get the idea that latency and round-trip times matter with lost packets, that any USB2 attached Gigabit Ethernet behaves totally different compared to any real Gigabit Ethernet implementation on the other SBC and that retransmits affect connections with high round-trip times a lot more than those with short ones (higher latency adds to lower throughput when packet loss occurs -- that's simple network basics).

      Maybe I should remove the instructions above how to get the ethtool call out of the way to save us from unnecessary support hassles with reluctant RPi users? Anyone choosing a Raspberry Pi as NAS is not interested in NAS performance anyway. Fast Ethernet is totally fine for this target audience :)

      The post was edited 1 time, last by tkaiser ().

    • dogg!~ wrote:

      let people know that time machine backups would not work when I enabled gigabit ethernet
      TimeMachine backups work pretty well with Gigabit Ethernet on single board computers. Personally tested with these boards: Banana Pi, Banana Pro, Olimex Lime 2, Clearfog Pro, EspressoBin, Rock64, Orange Pi Plus 2E, ODROID HC1 and HC2 and an i.MX6 Wandboard.

      I don't see a reason why it shouldn't work also with the new Raspberry Pi. Are you sure you're not running in underpowering issues (Gigabit Ethernet needs more juice)? Care to provide output from 'armbianmonitor -u' and 'cat /var/log/raspihealth.log'
    • dogg!~ wrote:

      I think my power supply is ok. below is the screenshot of cat /var/log/raspihealth.log
      Yeah, no under-voltage occured so far. You might want to check this thread here discussing network problems with the new Pi:…80e47fb2f880a197&start=50

      Please remember: on every 'network equipped' Raspberry Pi there's no network in reality. It's always an integrated USB Ethernet adapter behind an USB hub (which is something you usually want to avoid). And USB on the Raspberry Pi has been a sh*t show since the early days: -- reading through this from back in the early days it seems like a wonder that this worked somehow at all in the following years :)
    • Users Online 2

      2 Guests