How to get the HDD available in OMV without the Formatting problems I experience?
Manually done in "fstab" I read about...?
You have to mount it in the GUI of OMV. Otherwise you will not be able to use it in the GUI of OMV.
If you mount it manually from CLI or by editing fstab, you will not be able to create shared folders in OMV.
So, in the GUI of OMV
No, usually you can mount drives from other linux systems.
No, usually you can mount drives from other linux systems.
but probably not using W10 partition tools as in post 13.
You should follow the SBC guide and install Armbian Buster
Use faster SD card and make sure flashmemory plugin is installed.
That's why, to get the drive working on OMV it should first be wiped, then formatted.
You have to mount it in the GUI of OMV. Otherwise you will not be able to use it in the GUI of OMV.If you mount it manually from CLI or by editing fstab, you will not be able to create shared folders in OMV.
So, in the GUI of OMV
- wipe the drive
- create a filesystem (ext4)
- mount it
Well guys...
Started again, now with an eMMC 16GB module together with Armbian as suggested
Setup OMV went fine
UNTIL creating the File System
Again I got the Communication Errors as before
Again wiping the HDD and will try to Format again...
System is holding up longer then yesterday now
Initializing....
ZitatAlles anzeigenCreating the file system, please wait ...
===== Wipe signatures from device =====
===== Create partition =====
Creating new GPT entries.
Disk /dev/sda: 5860533168 sectors, 2.7 TiB
Model: WDC WD30EFRX-68E
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): F5A4F6BA-7EB3-4A91-A62E-E252BD48E752
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 5860533134 2.7 TiB 8300
The operation has completed successfully.
===== Create file system =====
mke2fs 1.44.5 (15-Dec-2018)
Creating filesystem with 732566385 4k blocks and 183148544 inodes
Filesystem UUID: 3ef041b7-0a33-46ee-a903-2ccf09f1b7e7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544
Allocating group tables: 0/22357 done
Writing inode tables: 0/22357 96/22357 254/22357 319/22357 351/22357 362/22357 366/22357
As an alternative, Format the HDD under Ubuntu as EXT4 will get me a HDD with File System that can be Mounted directly and used in OMV?
Again I got the Communication Errors as before
No idea. Maybe the usb enclosure you are using sucks? Are you connecting via wireless? If so, maybe your wireless connection is weak.
As an alternative, Format the HDD under Ubuntu as EXT4 will get me a HDD with File System that can be Mounted directly and used in OMV?
No need. mkfs.ext4 /dev/sda should format the drive from the OMV command line without using partitions. Then you should be able to mount it in the OMV web interface Filesystems tab (don't use create if you format it from the command line).
Which USB or Wireless?
I mean this errors while initializing
Thx, will try the command line this evening
Which USB or Wireless?
I mean this errors while initializing
I knew which error you meant. A slow connection to the system over wireless could cause that problem. A bad usb to sata adapter could cause issues formatting and/or high load on the system as well. Anything that adds i/o wait could cause this. It is tough to figure out because anything making the system slow could cause it.
Any idea what's going on here?
ayufan is the expert. He suggests too small of a power supply at beginning. Probably an issue with the kernel. I'm running Bionic on mine and have no issues. I would try one of the armbian images (those come from ayufan's work too) - https://dl.armbian.com/rockpro64/archive/. I have had better luck with the 4.x kernels over the 5.x kernels.
Armbian_20.02.0-rc1_Rockpro64_buster_current_5.4.14_desktop.7z
Nope. That has desktop in the name.
other strange thing: I disabled auto logout
but still OMV logs out of the WebIf
Maybe it is the power supply then.
Put the 3TB WD Red HDD in an external case with his own power supply
Connected via USB3 between RockPro64 and the external case
Now it formats without problems, see screenshot
Never came this far...
Will this power supply giving me problems on normal use, reading / writing data on the disk?
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
Armbian_20.02.0-rc1_Rockpro64_buster_current_5.4.14_desktop.7z