Beiträge von Mark81

Yep, in fact the problem is not solved since last year.
Because OMV is strictly tied to Debian are the same thing: I mean, I understand OMV is only the software layer, but because they choose Debian as o.s. I assume it should work for all OMV features. And USB/SATA adapters are not discouraged (at least, I didn't find any note about them).

The same hard-disks with the same USB/SATA adapter connected to a common Windows machine work fine also with very big files. So I don't think both have faulty SATA chipset.
Anyway, I will try to look at SMART data.

I have two NAS based on OMV, one is an Atom SBC the other is a RPi3.
Both have a USB external hard-disk, with dedicated power supply.

Whenever I try to write a "large" file (say > 1 GB) I got a lot of I/O errors and the disks disconnect. Example on RPi3:

[  487.411996] usb 1-1.2: USB disconnect, device number 6
[  487.417386] EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 10 writing to inode 2359299 (offset 58720256 size 2101248 starting block 49664)
[  487.417400] Buffer I/O error on device sda1, logical block 49152
[  487.417411] Buffer I/O error on device sda1, logical block 49153
[  487.417415] Buffer I/O error on device sda1, logical block 49154
[  487.417419] Buffer I/O error on device sda1, logical block 49155
[  487.417423] Buffer I/O error on device sda1, logical block 49156
[  487.417427] Buffer I/O error on device sda1, logical block 49157
[  487.417432] Buffer I/O error on device sda1, logical block 49158
[  487.417436] Buffer I/O error on device sda1, logical block 49159
[  487.417440] Buffer I/O error on device sda1, logical block 49160
[  487.417444] Buffer I/O error on device sda1, logical block 49161
[  487.419443] EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 10 writing to inode 2359299 (offset 58720256 size 4198400 starting block 49920)
[  487.419927] EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 10 writing to inode 2359299 (offset 58720256 size 4198400 starting block 50176)
[  487.421682] EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 10 writing to inode 2359299 (offset 58720256 size 6295552 starting block 50432)
[  487.422187] EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 10 writing to inode 2359299 (offset 58720256 size 6295552 starting block 50688)
[  487.423876] EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 10 writing to inode 2359299 (offset 58720256 size 8388608 starting block 50944)
[  487.424338] EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 10 writing to inode 2359299 (offset 58720256 size 8388608 starting block 51200)
[  487.426161] EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 10 writing to inode 2359299 (offset 58720256 size 8388608 starting block 51456)
[  487.427679] EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 10 writing to inode 2359299 (offset 67108864 size 3149824 starting block 51712)
[  487.428152] EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 10 writing to inode 2359299 (offset 67108864 size 3149824 starting block 51968)
[  487.503619] JBD2: Detected IO errors while flushing file data on sda1-8
[  487.503932] Aborting journal on device sda1-8.
[  487.503961] EXT4-fs (sda1): Delayed block allocation failed for inode 2359299 at logical offset 35152 with max blocks 640 with error 30
[  487.503994] JBD2: Error -5 detected when updating journal superblock for sda1-8.
[  487.508355] EXT4-fs (sda1): This should not happen!! Data will be lost


[  487.512962] EXT4-fs error (device sda1) in ext4_writepages:2907: Journal has aborted
[  487.515348] EXT4-fs (sda1): previous I/O error to superblock detected
[  487.516451] EXT4-fs (sda1): previous I/O error to superblock detected
[  487.516573] EXT4-fs error (device sda1): ext4_journal_check_start:61: Detected aborted journal
[  487.518940] EXT4-fs (sda1): Remounting filesystem read-only
[  487.521356] EXT4-fs (sda1): previous I/O error to superblock detected
[  495.390409] usb 1-1.2: new high-speed USB device number 7 using dwc_otg
[  495.521444] usb 1-1.2: New USB device found, idVendor=13fd, idProduct=0840
[  495.521457] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  495.521466] usb 1-1.2: Product: External
[  495.521474] usb 1-1.2: Manufacturer: Generic
[  495.521482] usb 1-1.2: SerialNumber: 533144354E53414639313631
[  495.522267] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[  495.525034] scsi host1: usb-storage 1-1.2:1.0
[  496.551133] scsi 1:0:0:0: Direct-Access     Generic  External         1.14 PQ: 0 ANSI: 4
[  496.552149] sd 1:0:0:0: Attached scsi generic sg0 type 0
[  496.552215] sd 1:0:0:0: [sdb] 234441647 512-byte logical blocks: (120 GB/112 GiB)
[  496.552621] sd 1:0:0:0: [sdb] Write Protect is off
[  496.552634] sd 1:0:0:0: [sdb] Mode Sense: 23 00 00 00
[  496.553106] sd 1:0:0:0: [sdb] No Caching mode page found
[  496.553124] sd 1:0:0:0: [sdb] Assuming drive cache: write through
[  496.577478]  sdb: sdb1
[  496.578920] sd 1:0:0:0: [sdb] Attached SCSI disk
[  497.343918] EXT4-fs (sdb1): mounting with "discard" option, but the device does not support discard
[  497.343929] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,discard,acl

On RPi3 the disk is remounted but on the other machine I have to cycle power the hard-disk and reconfigure the "Disk" section of OMV.
Because they are different platform, with different hard-disk and different USB controllers the only common thing is OMV.

It's not reliable with these problems. I must be able to write such a "large" files.
Please, would you help me to understand how to fix the problem?

Of course feel free to ask me any detail that might be useful.

Here I see several images, some for BananaPI BPI SBCs.
But I'm not sure which one is suitable for -M3 or how to make them compatible.
I tried the OMV_4_Banana_Pi.img.xz but it does not boot at all.

By the way there's another download: OMV_4_Banana_Pi_Pro.img.xz, but I cannot find it in the official product list

Zitat von votdev

It is not possible to install OMV on Ubuntu. It is tied to Debian only.

Ah ok, thanks.
And does this exclude Raspbian/Armbian as well?

I'm trying to install OMV on a Banana Pi-M3 running Ubuntu 16.04. I was able to satisfy all the requirements but btrfs-progs. It says:

Zitat

Package btrfs-progs is not available, but is referred to by another package.

This may mean that the package is missing, has been obsoleted, or
is only available from another source

Do I really build it from sources?
Any change to get OMV run on Ubuntu 16?

Hi, I'm kindly asking some suggestion to find out the root of my issue. I'm not sure if it's related to OMV.
I'm running OMV on a Debian machine (embedded PC) with an external USB/SATA hard-disk.
The USB enclosure and the HD works fine under Windows and Linux desktop machine.

When connected to this embedded PC w/ OMV, it happens that after exchanging (a lot of) data it disconnects. For example if I read or write large files (several hundreds of MB) OMV doesn't see it anymore.
I found this in the dmesg, but I'm not sure if there's a problem in the configuration of OMV or it's something related to my hardware.

<quote>
[504699.197953] usb 1-2.2: reset high-speed USB device number 3 using xhci_hcd
[504699.277816] usb 1-2.2: device descriptor read/64, error -71
[504699.465874] usb 1-2.2: device descriptor read/64, error -71
[504699.655456] usb 1-2.2: reset high-speed USB device number 3 using xhci_hcd
[504699.735015] usb 1-2.2: device descriptor read/64, error -71
[504699.926043] usb 1-2.2: device descriptor read/64, error -71
[504700.114119] usb 1-2.2: reset high-speed USB device number 3 using xhci_hcd
[504700.114309] usb 1-2.2: Device not responding to setup address.
[504700.321905] usb 1-2.2: Device not responding to setup address.
[504700.533918] usb 1-2.2: device not accepting address 3, error -71
[504700.614297] usb 1-2.2: reset high-speed USB device number 3 using xhci_hcd
[504700.614487] usb 1-2.2: Device not responding to setup address.
[504700.822532] usb 1-2.2: Device not responding to setup address.
[504701.030419] usb 1-2.2: device not accepting address 3, error -71
[504701.031018] scsi host0: uas_eh_bus_reset_handler FAILED err -19
[504701.031035] sd 0:0:0:0: Device offlined - not ready after error recovery
[504701.031046] sd 0:0:0:0: Device offlined - not ready after error recovery
[504701.031091] sd 0:0:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_TIME_OUT dri verbyte=DRIVER_OK
[504701.031109] sd 0:0:0:0: [sda] tag#1 CDB: Write(10) 2a 00 3a 04 1a 30 00 01 3 0 00
[504701.031120] blk_update_request: I/O error, dev sda, sector 973347376
[504701.031666] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyt e=DRIVER_TIMEOUT
[504701.031674] Aborting journal on device sda1-8.
[504701.031721] sd 0:0:0:0: rejecting I/O to offline device
[504701.031749] JBD2: Error -5 detected when updating journal superblock for sda 1-8.
[504701.032782] sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 6f 84 50 40 00 00 08 00
[504701.032793] blk_update_request: I/O error, dev sda, sector 1870942272
[504701.033379] usb 1-2.2: USB disconnect, device number 3
[504701.033391] sd 0:0:0:0: rejecting I/O to offline device
[504701.033889] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detect ed aborted journal
[504701.034491] EXT4-fs (sda1): Remounting filesystem read-only
[504701.034892] EXT4-fs (sda1): previous I/O error to superblock detected
[504701.070642] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[504701.310280] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte =DID_ERROR driverbyte=DRIVER_OK
[504701.438815] usb 1-2.2: new high-speed USB device number 5 using xhci_hcd
[504701.518690] usb 1-2.2: device descriptor read/64, error -71
[504701.706939] usb 1-2.2: device descriptor read/64, error -71
[504701.894978] usb 1-2.2: new high-speed USB device number 6 using xhci_hcd
[504701.975036] usb 1-2.2: device descriptor read/64, error -71
[504702.163685] usb 1-2.2: device descriptor read/64, error -71
[504702.271251] usb 1-2-port2: attempt power cycle
[504702.874833] usb 1-2.2: new high-speed USB device number 7 using xhci_hcd
[504702.875093] usb 1-2.2: Device not responding to setup address.
[504703.083455] usb 1-2.2: Device not responding to setup address.
[504703.291024] usb 1-2.2: device not accepting address 7, error -71
[504703.371513] usb 1-2.2: new high-speed USB device number 8 using xhci_hcd
[504703.371688] usb 1-2.2: Device not responding to setup address.
[504703.579348] usb 1-2.2: Device not responding to setup address.
[504703.787653] usb 1-2.2: device not accepting address 8, error -71
[504703.788225] usb 1-2-port2: unable to enumerate USB device
</quote>

I read the other threads about the empty folder issue in OMV. My situation is slightly different: using the built-in FTP client in windows (i.e. typing the address in Explorer) leads to show the actual content of the FTP folders.
Instead using other applications like FileZilla or ES File Explorer (Android) leads to a correct login but they show nothing in the folder.

May I assume at least the permissions are ok? Otherwise even Windows should not be able to access the files.

I attach the proftpd.conf file.

Found a way outside OMV, using nginx autolisting.

If I'm not wrong, some time ago I ran into this feature but I'm not able to reproduce again. Perhaps because I don't use the right words.
I would like to browse (= read-only) a shared folder via http. Addressing a browser to a specific url it should list the contents of that folder. I'm not talking now about how to gain access outside my router - I know how to. But just understand if (and how) browse files via http.

I read several other threads about SMB troubleshooting but I haven't found a fix yet.
I'm using OMV on Debian and I enabled home folders for users. I'm trying to access them from Windows 7 Home Premium.

Problems

• Windows doesn't show the server in the network places (not a big deal, just to report that)
• using either hostname or IP (i.e. \\192.168.1.200) shows folders "homes" and "share", but clicking on "homes" leads to the error 0x80070035, while I can enter in "share" but I have no permissions to write (no login was asked, though)

What I did

• disabled Firewall
• tried to use IP instead of hostname
• restart the server

Command's output

# ls -l /srv/
totale 12
drwxr-xr-x 5 root          root          4096 mar 29 12:58 dev-disk-by-label-data
drwxr-xr-x 2 ftp           nogroup       4096 mar 27 17:25 ftp

# ls -l /sharedfolders/
totale 8
drwxrwsr-x 4 root users 4096 mar 29 12:53 home
drwxrwsr-x 2 root users 4096 mar 29 12:58 share

# ls -l /sharedfolders/home/
totale 8
drwxrwxr-x  2 admin          admin 4096 mar 27 18:34 admin
drwxrwxr-x+ 4 mark           users 4096 apr 23 15:09 mark

/# groups mark
mark : users

Questions

• why Windows doesn't ask me for a password?
• where does the "homes" directory come from?
• any hint to fix the issues?

Hi all, before posting I searched in the old threads but I didn't find anything relevant.
I'm trying to install OMV from a USB pen to a mini PC that use UEFI.

I used Rufus to burn the ISO selecting the "GTP for UEFI" schema. But the boot options doesn't show my USB pen.
Is there something specific I need to do?