Give results of:
ls -la /etc/apt/sources.list.d/
OpenMediaVault only recognizes drives in 2 out of 4 bays in my former Windows Home Server
-
- OMV 2.x
- creamsicle
-
-
Give results of:
ls -la /etc/apt/sources.list.d/ -
When you go to System/Update Manager/Settings did you enable any of these?
Pre-release updates.
or
Community-maintained updates.If so disable them.
-
When you go to System/Update Manager/Settings did you enable any of these?
Pre-release updates.
or
Community-maintained updates.If so disable them.
No, both of those have never been enabled.
-
I'm currently prepping a USB non-flash external hard drive. Will swap out the flash drive and report back.
-
Have you tried alternative mirrors repos?
-
Have you tried alternative mirrors repos?
How do I do that?
That said, it feels unlikely that the answer could be something so simple. The breadth of the problems are staggering. Beyond the hardware recognition problem for the drives there are:
1. uploading plugins via the Plugins tab fails
2. wget can't download the plugin
3. SMB hangs when creating a new file
4. SFTP errors on file upload
5. apt-get -f install and apt-get update both can't connect to the reposAll the while DNS and Internet connectivity work with pings.
I'm assuming these problems are not ordinary, so it seems reasonable to assume they probably have some shared underlying fault. It's hard to imagine what it could be at this point other than some problem with the install. That said, this is a fresh install, so that doesn't seem terribly likely, but I don't know what else to try at this point.
-
On such a bad scenario, use a new stick or spin disk
-
If you don't use the flash memory plugin with usb stick they will be toast in no time, couple weeks.
-
Lots of updates on the situation.
I installed OpenMediaVault following the same procedure onto a spinning disk external hard drive, and it got the exact same problems. Upload of plugins failed. Wget couldn't download files that were readily accessible by every other computer on the network.
I took this drive, deleted the 70-persistent-net.rules again, and booted from it on a different computer. This time everything worked perfectly.
Corrupted install can safely be ruled out as the cause of the disparate problems on my target server.
While the drive was in that other computer, I took the opportunity to install the omv-extras plugin, and used that to install the BPO kernel.
Putting the updated drive into the target server again, all problems remain. Looking back on the long list of problems that the system is running into, besides the driver issue with the SATA controller, everything is related in some way to networking. Could it be there is some sort of bizarre half-working half-broken incompatibility with the Ethernet on my target server?
Any suggestions on how to debug?
-
If you think the card is the problem, do you have in hand a USB wireless adapter use it to test? I say this because is common object to have around. Hopefully not one with a Broadcom chipset.
-
If you think the card is the problem, do you have in hand a USB wireless adapter use it to test? I say this because is common object to have around. Hopefully not one with a Broadcom chipset.
I plugged in two USB wired adapters, and while they show up under the persistent rules, they don't give the system network access for some reason. Is there something else I need to do to enable network connectivity?
-
Well if you still have access through eth0, you can configure it through the webUI, have to enter the wireless network name and key. Only WPA is supported.
-
Also you mentioned you're booting now bpo kernel and drives still don't show ?
-
Well if you still have access through eth0, you can configure it through the webUI, have to enter the wireless network name and key. Only WPA is supported.
It's hard for me to believe, but I got the USB Ethernet adapter working, and now all the networking related problems have disappeared.
Sooo....what that means is that somehow the internal Ethernet adapter is recognized, Linux believes it to be working, it can ping, it can use DNS, it can connect, it can transfer directory listings, it can SSH, HOWEVER, it is somehow unable to download and upload files over any protocol, including encrypted protocols like SFTP. This is one of the weirdest incompatibilities I've ever seen before.
How can this even be possible?
Also you mentioned you're booting now bpo kernel and drives still don't show ?
Yes, unfortunately, that's right. Is there a step 2 for trying to get the drives to be recognized?
-
Another important thing to note is that weirdly, there are tons of results when searching for people installing Linux onto HP Mediasmart servers, including Amahi, Ubuntu, etc. but somehow, none of them seem to mention either incompatibilities with the internal NIC or the SATA RAID controller.
-
There is a mention in Debian thread about the network problem. But that was with Debian squeeze.
According to this website you have two sata comtrollershttp://kmuto.jp/debian/hcl/HP/MediaSmart+EX470
check with lsmod that the modules are loaded for the controllers. You can see the name in the table.
you can force load with modprobe modulename
-
There is a mention in Debian thread about the network problem. But that was with Debian squeeze.
According to this website you have two sata comtrollershttp://kmuto.jp/debian/hcl/HP/MediaSmart+EX470
check with lsmod that the modules are loaded for the controllers. You can see the name in the table.
you can force load with modprobe modulename
Based on that link, I checked sata_sis, ahci, and pata_marvell and all 3 of them show up in lsmod:
-
Don't have anything more to add. You can go from here and try a fedora latest release or Ubuntu see if the problems are similar.
Also maybe does fdisk displays the disks ?
fdisk -lif the /dev shows different as usual (sda) omv won't display it in physical section
-
Don't have anything more to add. You can go from here and try a fedora latest release or Ubuntu see if the problems are similar.
Also maybe does fdisk displays the disks ?
fdisk -lif the /dev shows different as usual (sda) omv won't display it in physical section
No, unfortunately, fdisk also only shows the same drives.
Okay, thanks for all the help.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!