Beiträge von shalin.mo

Zitat von Zoki

So your problem was that one device has been listed twice in the config.xml file (and therefore in fstab)?

thought so, but looks like its not . I commented the second entry and it worked for a day without any issues.

thanks for the replies

fixed using the second method here

My SSD auto unmount periodically and will have to restart the PI4 to get it back to normal

this error pops up when I try to remount using OVM file systems

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; mount -v --source '/dev/disk/by-uuid/7fa4e507-ca39-4236-a2e2-02e2273f0b00' 2>&1' with exit code '32': mount: /srv/dev-disk-by-uuid-7fa4e507-ca39-4236-a2e2-02e2273f0b00: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.

Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; mount -v --source '/dev/disk/by-uuid/7fa4e507-ca39-4236-a2e2-02e2273f0b00' 2>&1' with exit code '32': mount: /srv/dev-disk-by-uuid-7fa4e507-ca39-4236-a2e2-02e2273f0b00: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. in /usr/share/php/openmediavault/system/process.inc:196
Stack trace:
#0 /usr/share/php/openmediavault/system/filesystem/filesystem.inc(742): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(939): OMV\System\Filesystem\Filesystem->mount()
#2 [internal function]: Engined\Rpc\OMVRpcServiceFileSystemMgmt->mount(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('mount', Array, Array)
#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('FileSystemMgmt', 'mount', Array, Array, 1)
#6 {main}

im still having this problem , with a ssd, any solution?

Zitat von Zoki

Have you tried Solution 2 posted by Chente in the other thread?

nope, somehow i manage to access files by reverting. But now got a new problem

I cant create new shared folders, the device is not visible

but i cant see the ssd in storage and also properly mounted

Zitat von B3rnd

often it is a problem with the power supply, which is actually too low on a Raspi to run an external disk with.

Is that one usb-drive? Is it actively powered, perhaps via an active HUB?

just one - 1tb gigabyte ssb. it shoudnt be a problem to run one over usb

Zitat von Zoki

What do you mean by: "OVM was turning off my ssd randomly"?

Has this happened after you changed the mount command and what did you change exactly?

which means before doing all this, ssd randomly went offline. has restart to get it back

by earlier thread about it SSD goes offline - OVM 5

Zitat von Zoki

So you better find out, what is causing this instead of changing the fstab.

can you help me? please

The initial reason i change that format to dev/sda1 is that my drive (ssd) suddenly goes off line

internet. so it wont change sda to sdb upon restart

Hello ,

My OVM was turning off my ssd randomly so I had manually mount the ssd. After doing so it kept changing /sda to /sdb up on restart.

So I had to edit fstab and directly add uuid to a mount point (Yes I did this using rasperry pi terminal)

and now all my shares are inaccessible from my mac (smb fails), I can access then thru ssh though

How can I fix this.

Zitat von chente

I'd say it hasn't worked. Other things could be tried but you run the risk of breaking the hard drive. Not worth it.

I would move on to solutions 2 and 3.

ok

Zitat von Soma

Depends.

Not ALL people have a NAS with a portable drive.

Usually, what is attached is some kind of USB box with NAS quality drives (HDD ) and external power.

A portable disk implies that is meant to be portable and plugged in for a certain amount of time (to make a backup, copy some files/folders, watch a movie, for e.g.) and then switched off.

If you want 24/7 durability and to be reliable, you go for the good-stuff (and yes, it's more expensive).

But, take this opinion with a pinch of salt.

[EDIT]

If you still want to check some other probabilities, run:

dmesg | grep -i voltage to see if it is getting low voltage issues

If nothing shows then, voltage is OK

Alles anzeigen

Thanks for the help Soma . What i mean by other people is that , the people who runs off usb connected portable drives.

this was the output, but it worked somehow i guess

Zitat von Soma

If it's a portable drive, almost certain, it's the drive that goes on Sleep/Standby and Debian isn't able to wake it up.

Even though I only have a Portable Toshiba 4TiB HDD, it acts the same way (either Debian as Windows).

Only way to wake it up, is to reboot.

Don't know if there's any "Keep Alive" function on SSDs but you can maybe schedule a task to every hour, to do something on the drive to keep it awake.

sudo touch /srv/dev-disk-by-............/awake.txt

Or maybe macom has a different thought,

Alles anzeigen

if so many people should experience the same issue right?

Zitat von chente

Is the disk connected directly to the raspberry ?. This problem in raspberry could be caused by an incorrect power supply of the hard disk, it is advisable to have a separate power supply for the disk. Although in this case it is an SSD disk, it does not seem that this could be the problem.

What disk model is it? How is it formatted? How many discs are there? First you talk about a 1TB SSD drive and then you say the drives are disconnected.

just 1 1TB gigabyte SSD, connected thru a sata to usb 3 convertor (which has red and blue indicators). Formatted to ZFS

anyone?

HI I have connected one 1TB SSD to OVM on a raspberry pi. Time to time lets say 12 hours (in idle I assume, not sure), the drives goes offline .

When i click on shares it says not available, when i rebooted they are back again what could be the reason?

https://giphy.com/gifs/OaKK8FbvUrgiA9yw2R

Zitat von Soma

It will mess OMV5.

OMV5 runs on Buster. If you update to Bullseye, OMV will also update to 6.

And, FWIW, Raspberry Foundation don't endorse upgrading from Buster to Bullseye.

All infos available are unsupported methods of doing it (upgrading RaspiOS from Buster to Bullseye)

If you want the performance boost that comes with RaspiOS Bullseye:

First you need one of the latest versions of the Pi4 (I believe the 4Gb only after v1.2)

The 8Gb model (and the Pi 400) are guaranteed of beeing already capable.

And, the performance boost is somewhat of an overclock from base 1500Mhz to base 1800Mhz

Second, start fresh with a proper IMG from RaspiOS Bullseye (armhf or aarch64).

That will guarantee that no leftovers/missing/wrong versions are on the system.

Then, run the OMV script and you'll have a vanilla Debian11/OMV6 system

Alles anzeigen

Thanks