Beiträge von chudak

Zitat von Soma

Are you running a Pi?

Disable backports on omv-extras click apt clean.

Yes I run on pi

Thx it helped

Do I keep backports disabled?

Zitat von macom

Please go the bell icon in the top right corner of the GUI and copy the complete error message. Than paste here in a code box </>

I did not realize it has more when you use copy to clipboard

Thx and pls see above ^

Got a 500 error at the end of update, rebooted the system

Still, see 500 trying to refresh updates

500 - Internal Server Error

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sb...

a few seconds ago

Zitat von ryecoaaron

I just noticed this is not right. It should 192.168.90.2:/export/Public. You can see the exports with: showmount -e 192.168.90.2 on the client

Yes, that worked!!!

Why did it change?

Thx a million!

Zitat von ryecoaaron

I just noticed this is not right. It should 192.168.90.2:/export/Public. You can see the exports with: showmount -e 192.168.90.2 on the client

Do you mean in /etc/fstab?

I have now:

#NFS mount

192.168.90.2:/Public /media/pi-nas-nfs nfs defaults 0 0

showmount -e 192.168.90.2

Export list for 192.168.90.2:

/export *

/export/Public *

Zitat von ryecoaaron

You could or on my network, I set it to 192.168.1.0/24

Tried all combinations and none worked

Also, reset all persons to all read/write

Zitat von Louie1961

Check that you have permissions correctly set on the server side for the shared folder. You could also try adding "no_root_squash" to your options

Like this? What do I use for the Client? * ?

Zitat von ryecoaaron

The ability to add support protocols have changed. I would remove a protocol (nfsv2 isn't needed by almost all people) and then apply changes.

Made this change

So far no love

Hello

I've had NFS set for a long time (not really used it, instead used Samba mounts)

But still, I see that there was some change in July-August as some users experienced issues with NFS

I am not able to connect. See an error during mourning mount.nfs: access denied by server while mounting 192.168.90.2:/Public

My setup looks like this:

Needless to say, I have not touched my setup in months and therefore am hesitant to change anything unless I check with experts here.

Any clues on what changed?

TIA

Hello

Before upgrading to 6.x I was able to see and tail rsync.log in /var/log/

I don't see it updated anymore when rsync runs

What am I missing?

Thx

Zitat von Soma

Ok, let's redo the steps:

You went to update management settings and ticked both boxes.

Some updates showed.

Then you untick them again (press save, I hope) but the updates still show although they're from "beta" sources, correct?

Have you tried to click the magnifying lens again?

P.S: the OMV update is NOT "beta"

Alles anzeigen

Yes done that.

But those are still listed and this seems to be a problem.

Thx

I run 6.0.30-1 on R Pi 4 and tried to see what updates are available with options:

Pre-release updates

Community-maintained updates

Checked those options, ran the update, and got these packages:

Now I wanted to uncheck those options and return back to the initial condition, but that did not work.

Any clues on how to fix it?

Thx

Zitat von Soma

Running 64Bit without any issue on 6.0.7-1

did you do upgrade or clean install?

Thx

Zitat von chente

How is the disk connected?

A USB to SATA adapter? What is the make and model?

An external USB disk enclosure? What is the make and model?

Another device? What brand and model of device?

USB external drive from Costco "Seagate One Touch 5TB"

https://www.costco.com/seagate…es.product.100761181.html

No USB enclosure, no other devices

OMV running on R-Pi4

Zitat von Soma

What you need to tell or show is how and with what type of thingamadjing you have your drive connected to the Pi.

Your smart ctl depends on it

I'd love to show tell this if I knew.

Can you elaborate on how to get this info?

Zitat von anotherchris

I was finally able to try this today. No go for now.

Code

pi@raspberrypi:~ $ cat /etc/modprobe.d/usb-storage-quirks.conf
options usb-storage quirks=0bc2:ab28:u


pi@raspberrypi:~ $ lsusb
Bus 002 Device 002: ID 0bc2:ab28 Seagate RSS LLC 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


pi@raspberrypi:~ $ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
    |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M

Alles anzeigen

Some dmesg extracts.

Code

[    1.842018] usb 2-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[    1.872913] usb 2-2: New USB device found, idVendor=0bc2, idProduct=ab28, bcdDevice= 1.00
[    1.874066] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    1.881237] usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[    1.889543] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    1.903765] usb 2-2: Product: BUP BK
[    1.907405] usb 2-2: Manufacturer: Seagate
[    1.911589] usb 2-2: SerialNumber: NA9SL9P9
[    1.921713] devtmpfs: mounted
[    1.933109] Freeing unused kernel memory: 2048K
[    1.942575] scsi host0: uas
[    1.946738] scsi 0:0:0:0: Direct-Access     Seagate  BUP BK           0304 PQ: 0 ANSI: 6
[    1.955369] Run /sbin/init as init process
[    1.956562] sd 0:0:0:0: [sda] Spinning up disk...


[    9.272418] sd 0:0:0:0: [sda] 9767541167 512-byte logical blocks: (5.00 TB/4.55 TiB)
[    9.272433] sd 0:0:0:0: [sda] 2048-byte physical blocks
[    9.286014] sd 0:0:0:0: [sda] Write Protect is off
[    9.286031] sd 0:0:0:0: [sda] Mode Sense: 4f 00 00 00
[    9.286375] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    9.286999] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (2048 bytes)
[    9.364214]  sda: sda1
[    9.366807] sd 0:0:0:0: [sda] Attached SCSI disk

Alles anzeigen

smartctl output.

Code

pi@raspberrypi:~ $ sudo smartctl --health -T permissive /dev/sda
smartctl 6.6 2017-11-05 r4594 [armv7l-linux-4.19.93-v7l+] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org


Read Device Identity failed: scsi error unsupported field in scsi command


SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
pi@raspberrypi:~ $

Alles anzeigen

Any suggestions?

Alles anzeigen

Did you finally solve your issue?

Thx

Can someone give me a hand and help fix a similar issue pls?

I have Rpi-4 and Seagate 5TB drive

Here is some info:

$ sudo smartctl --health /dev/sda

smartctl 6.6 2017-11-05 r4594 [armv7l-linux-5.10.63-v7l+] (local build)

Copyright (C) 2002-17, Bruce Allen, Christian Franke, http://www.smartmontools.org

Read Device Identity failed: scsi error unsupported field in scsi command

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

$ sudo smartctl --health -d sat -a -T verypermissive /dev/sda

smartctl 6.6 2017-11-05 r4594 [armv7l-linux-5.10.63-v7l+] (local build)

Copyright (C) 2002-17, Bruce Allen, Christian Franke, http://www.smartmontools.org

Read Device Identity failed: scsi error unsupported field in scsi command

=== START OF INFORMATION SECTION ===

Device Model: [No Information Found]

Serial Number: [No Information Found]

Firmware Version: [No Information Found]

Device is: Not in smartctl database [for details use: -P showall]

ATA Version is: [No Information Found]

Local Time is: Tue Dec 7 16:05:42 2021 PST

SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.

SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.

Checking to be sure by trying SMART RETURN STATUS command.

SMART support is: Unknown - Try option -s with argument 'on' to enable it.

Read SMART Data failed: scsi error unsupported field in scsi command

=== START OF READ SMART DATA SECTION ===

SMART Status command failed: scsi error unsupported field in scsi command

SMART overall-health self-assessment test result: UNKNOWN!

SMART Status, Attributes and Thresholds cannot be read.

Read SMART Error Log failed: scsi error unsupported field in scsi command

Read SMART Self-test Log failed: scsi error unsupported field in scsi command

Selective Self-tests/Logging not supported

$ lsusb

Bus 002 Device 002: ID 0bc2:ac2b Seagate RSS LLC

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Thanks in advance!

macom

While we are on this topic I have a hypothetical question

So my failed and new drives were identical and were devices as /dev/sda

Assuming that I got a completely different new drive say SSD, will it be possible to use the same process or something else to make it work in my case?

Thx

OK so after all - everything worked fine.

I followed the steps with a slight change in the order.

On another Linux machine ubuntu:

1. connected the new drive
2. deleted all pre-formatted partitions
3. added ext4 partition
4. added label MAIN
5. connected to pi OMV
6. verified connection, rebooted
7. changed permissions on MAIN to be user_name:users
8. rsync data files

Thank you for your help!

macom thanks a million!