Segmentation Fault on Fresh Install

bbddpp · 3. Dezember 2016

I am seeing segmentation faults on a fresh install of OMV on a new SSD. Smart data is fine, green light and all tests good on SSD. Prior SSD had gone red so I thought a new one would solve it.

So, things I have tried:

- Immediately installed flashmemory plugin (first boot)
- Backports Kernel
- Changed SSD
- Uninstalling and re-installing plugins
- Clean fresh install of OMV
- Changing SATA data cable to SSD

I have now tried 3 different SSD drives and all 3 are throwing segmentation faults. What else could cause this and should I be checking? Memory? Something else? Is it possible I am using some sort of system that is incompatible with OMV and will throw segmentation faults?

Log snippets:

Zitat

Unpacking openmediavault-nzbget (from .../openmediavault-nzbget_1.6_all.deb) ...

Processing triggers for man-db ...
Processing triggers for install-info ...
Processing triggers for openmediavault ...
Restarting engine daemon ...
Segmentation fault
Restarting OpenMediaVault engine daemon:
.
omv-engined[6553]: Daemon already running (pid=6551)
invoke-rc.d: initscript openmediavault-engined, action "restart" failed.
dpkg: error processing openmediavault (--unpack):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
openmediavault
Creating index of upgradeable packages ...
Creating index of openmediavault plugins ...
E: Sub-process /usr/bin/dpkg returned an error code (1)

Alles anzeigen

I'm stumped.

bbddpp · 3. Dezember 2016

Is it possible that it's not the drive's fault even though I see the error during a write operation?

Could it be CPU or Memory causing this to occur? Or an incorrect BIOS setting or unsupported hardware?

I'm running a memtest next.

stockenberger · 3. Dezember 2016

I'm getting the same error ("Segmentation fault") on a new SSD. I tried reinstalling serval times, but nothing has helped so far.

Nibb31 · 3. Dezember 2016

It could be RAM. Is it OMV 2 or 3?

stockenberger · 3. Dezember 2016

Its OMV 2. I checked the RAM with Memtest. Nothing is wrong. Its a brand new HP Proliant MicroServer Gen8.

Nibb31 · 3. Dezember 2016

Could it be a corrupted image ?

You should probably switch to OMV3 by now, unless you are using a plugin that hasn't been ported yet.

stockenberger · 3. Dezember 2016

Yeah, I switched to OMV3, now its working...do you know if its safe to use OMV3? Because its still in Beta...?

ryecoaaron · 3. Dezember 2016

Zitat von stockenberger

do you know if its safe to use OMV3? Because its still in Beta...?

Yes it is safe. I don't consider it beta anymore.

bbddpp · 3. Dezember 2016

Thanks for the push into 3.0, ryecoaaron.

That fixed all my problems with the segmentation faults.

Just troubleshooting a MySQL plugin issue now, but will start a thread for that in the proper place.

3.0 looks nice, all the stuff that made 2.0 great, made even more efficient. And no segmentation faults is awesome too. That was driving me nuts at 2 AM last night!

Jetzt mitmachen!