N40l Installation problems and constant errors

valve90210 · 18. November 2016

Hi

I just got myself an HP N40l which I intend to install OMV on to be my media store. The server I have has been upgraded to 8gb ram and has a video card installed. It has a 250gb drive in the 5.25" bay at the top and a 3tb drive in the first drive bay.

On Wednesday I used a usb stick to install OMV on the 250gb and all seemed to go ok, I got users and groups and network shares set up fine and installed a couple of plugins, one of which failed a couple of times before I got it to work by installing manually.

Last night I started the server with a view to setting up the plugins however I couldn't log into the webif despite definitely using the correct username and password. I hooked up a monitor to the server to see if there was anything to see and was presented with a stream of error messages. I wondered if ti might have something to do with the failed plugin installs so decided to start again from scratch.

I tried a reinstall which failed due to existing files being found on the drive I was installing to so I used a live Gparte usb and deleted everything on the drive ready to start again.

This time it failed when trying to install grub, though it gave the option to retry which I did and it seemed to work and everything else did so too and all seemed well. I rebooted and it seemed ok, I could log in to the webif from my pc and it seemed alright but on the monitor on the server I was getting a constant stream of errors so I downloaded the syslog, an example of the stream of errors is below and I have attached the syslog

Code

Nov 17 23:09:24 openmediavault collectd[1217]: Initialization complete, entering read-loop.
Nov 17 23:09:24 openmediavault collectd[1217]: rrdcached plugin: rrdc_stats_get failed with status 107.
Nov 17 23:09:24 openmediavault collectd[1217]: read-function of plugin `rrdcached' failed. Will suspend it for 20 seconds.
Nov 17 23:09:24 openmediavault kernel: [   18.088103] ata5.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Nov 17 23:09:24 openmediavault kernel: [   18.091970] ata5.01: BMDMA stat 0x4
Nov 17 23:09:24 openmediavault kernel: [   18.095838] ata5.01: failed command: WRITE DMA EXT
Nov 17 23:09:24 openmediavault kernel: [   18.099715] ata5.01: cmd 35/00:60:30:01:85/00:01:13:00:00/f0 tag 0 dma 180224 out
Nov 17 23:09:24 openmediavault kernel: [   18.099718]          res 51/84:f1:9f:01:85/84:00:13:00:00/f0 Emask 0x10 (ATA bus error)
Nov 17 23:09:24 openmediavault kernel: [   18.107595] ata5.01: status: { DRDY ERR }
Nov 17 23:09:24 openmediavault kernel: [   18.111578] ata5.01: error: { ICRC ABRT }
Nov 17 23:09:24 openmediavault kernel: [   18.115573] ata5: soft resetting link
Nov 17 23:09:24 openmediavault kernel: [   18.300516] ata5.01: configured for UDMA/25
Nov 17 23:09:24 openmediavault kernel: [   18.300563] ata5: EH complete
Nov 17 23:09:24 openmediavault kernel: [   18.350156] ata5.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Nov 17 23:09:24 openmediavault kernel: [   18.354143] ata5.01: BMDMA stat 0x4
Nov 17 23:09:24 openmediavault kernel: [   18.358060] ata5.01: failed command: WRITE DMA EXT
Nov 17 23:09:24 openmediavault kernel: [   18.361993] ata5.01: cmd 35/00:48:d8:04:85/00:02:13:00:00/f0 tag 0 dma 299008 out
Nov 17 23:09:24 openmediavault kernel: [   18.361996]          res 51/84:c9:57:05:85/84:01:13:00:00/f0 Emask 0x10 (ATA bus error)
Nov 17 23:09:24 openmediavault kernel: [   18.369906] ata5.01: status: { DRDY ERR }
Nov 17 23:09:24 openmediavault kernel: [   18.373825] ata5.01: error: { ICRC ABRT }
Nov 17 23:09:25 openmediavault kernel: [   18.377839] ata5: soft resetting link
Nov 17 23:09:25 openmediavault dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Nov 17 23:09:25 openmediavault dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Nov 17 23:09:25 openmediavault dhclient: DHCPOFFER from 192.168.1.1
Nov 17 23:09:25 openmediavault kernel: [   18.564514] ata5.01: configured for UDMA/25
Nov 17 23:09:25 openmediavault kernel: [   18.564556] ata5: EH complete
Nov 17 23:09:25 openmediavault kernel: [   18.566191] ata5.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Nov 17 23:09:25 openmediavault kernel: [   18.570197] ata5.01: BMDMA stat 0x4
Nov 17 23:09:25 openmediavault kernel: [   18.574152] ata5.01: failed command: WRITE DMA EXT
Nov 17 23:09:25 openmediavault kernel: [   18.578130] ata5.01: cmd 35/00:48:d8:04:85/00:02:13:00:00/f0 tag 0 dma 299008 out
Nov 17 23:09:25 openmediavault kernel: [   18.578133]          res 51/84:09:17:05:85/84:02:13:00:00/f0 Emask 0x10 (ATA bus error)
Nov 17 23:09:25 openmediavault kernel: [   18.586013] ata5.01: status: { DRDY ERR }
Nov 17 23:09:25 openmediavault kernel: [   18.589897] ata5.01: error: { ICRC ABRT }
Nov 17 23:09:25 openmediavault kernel: [   18.593820] ata5: soft resetting link
Nov 17 23:09:25 openmediavault kernel: [   18.776527] ata5.01: configured for UDMA/25
Nov 17 23:09:25 openmediavault kernel: [   18.776561] ata5: EH complete
Nov 17 23:09:25 openmediavault wd_keepalive[1015]: stopping watchdog keepalive daemon (5.12)
Nov 17 23:09:25 openmediavault monit[1267]: Starting monit daemon with http interface at [localhost:2812]
Nov 17 23:09:25 openmediavault monit[1267]: Monit start delay set -- pause for 30s
Nov 17 23:09:25 openmediavault monit[1274]: State file '/var/lib/monit/state': Unable to read magic
Nov 17 23:09:25 openmediavault dhclient: DHCPACK from 192.168.1.1
Nov 17 23:09:25 openmediavault kernel: [   18.903348] ata5.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Nov 17 23:09:25 openmediavault kernel: [   18.907362] ata5.01: BMDMA stat 0x4
Nov 17 23:09:25 openmediavault kernel: [   18.911335] ata5.01: failed command: WRITE DMA EXT
Nov 17 23:09:25 openmediavault kernel: [   18.915291] ata5.01: cmd 35/00:70:00:48:85/00:03:13:00:00/f0 tag 0 dma 450560 out
Nov 17 23:09:25 openmediavault kernel: [   18.915293]          res 51/84:31:3f:4a:85/84:01:13:00:00/f0 Emask 0x10 (ATA bus error)
Nov 17 23:09:25 openmediavault kernel: [   18.923201] ata5.01: status: { DRDY ERR }
Nov 17 23:09:25 openmediavault kernel: [   18.927159] ata5.01: error: { ICRC ABRT }
Nov 17 23:09:25 openmediavault kernel: [   18.927221] ata5: soft resetting link
Nov 17 23:09:25 openmediavault kernel: [   19.112516] ata5.01: configured for UDMA/25
Nov 17 23:09:25 openmediavault kernel: [   19.112561] ata5: EH complete
Nov 17 23:09:25 openmediavault kernel: [   19.202764] ata5.01: limiting speed to PIO4
Nov 17 23:09:25 openmediavault kernel: [   19.202778] ata5.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Nov 17 23:09:25 openmediavault kernel: [   19.209015] ata5.01: BMDMA stat 0x4
Nov 17 23:09:25 openmediavault kernel: [   19.215040] ata5.01: failed command: WRITE DMA EXT
Nov 17 23:09:25 openmediavault kernel: [   19.220974] ata5.01: cmd 35/00:78:30:51:85/00:03:13:00:00/f0 tag 0 dma 454656 out
Nov 17 23:09:25 openmediavault kernel: [   19.220978]          res 51/84:09:9f:52:85/84:02:13:00:00/f0 Emask 0x10 (ATA bus error)
Nov 17 23:09:25 openmediavault kernel: [   19.232727] ata5.01: status: { DRDY ERR }
Nov 17 23:09:25 openmediavault kernel: [   19.238451] ata5.01: error: { ICRC ABRT }
Nov 17 23:09:25 openmediavault kernel: [   19.244209] ata5: soft resetting link
Nov 17 23:09:26 openmediavault kernel: [   19.432475] ata5.01: configured for PIO4
Nov 17 23:09:26 openmediavault kernel: [   19.432520] ata5: EH complete
Nov 17 23:09:26 openmediavault kernel: [   19.646919] ata5.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Nov 17 23:09:26 openmediavault kernel: [   19.651540] ata5.01: failed command: WRITE MULTIPLE EXT
Nov 17 23:09:26 openmediavault kernel: [   19.656080] ata5.01: cmd 39/00:78:30:51:85/00:03:13:00:00/f0 tag 0 pio 454656 out

Alles anzeigen

If anyone could give me an idea of what the problem might be I would be very grateful as I don't know what I'm looking at really or what the problem might be. Having got the serer and drive secondhand I'd quite like to get to the bottom of it asap as if it's something major I'll be needing to contact the seller to get it sorted.

I should also point out that I am a total noob when it comes to linux (or any coding/command line stuff) so any advice could do with being really simply spelt out for me...

Thanks for any help anyone can give me.
syslog_17_Nov_2016.txt

Olivier · 18. November 2016

Several questions :

- Did you manage to login sucessfuly on the admin web tool at least one time ?
- Did you come to change the default admin password ?
- What is the version of OMV you are using ? 2.0 or 3.0 ?
- What is the type of RAM you are using ? 1x 8Gb ? 2x 4Gb ? Brand ? Specs?
- What is the video card for ? can't you remove it to reduce overall consumption ?

valve90210 · 18. November 2016

1) Yes, I managed to get logged in with the default password and the webif seemed ok, had it not been for having the monitor plugged in I wouldn't have known about the errors

2) I didn't change it no, I noticed the stream of errors and just went to the logs bit and downloaded the syslog

3) Version 2.0 (I did select it in the thread creation...

4) Not sure, I'll have to check that

5) Video card was in there when I got it, gives an hdmi and DVI output (which I've been using to hook it up to a monitor. I don't really need it in there.

Olivier · 18. November 2016

Might be an obvious remark, but the rrdcached plugin seems to fail at writing data on your HDD.
I don't know the deamon/plugin but you can read the man for more info :

https://linux.die.net/man/1/rrdcached

At the end of the man there are several warnings about security and authorizations.
Cannot hurt to read them quickly.

I hope this helps

valve90210 · 18. November 2016

Had a skim of that but it's totally over my head!! I'm a total noob with this sort of thing.

Olivier · 18. November 2016

Seems like your HDD has some SATA chipset issues.
Is it a secondhand drive ? or brand new one ? If you have a Seagates 3tb this smells bad... (but you can be given back the money in some cases)

Try to install you OMV on a new USB key (4gb USB 2.0 at least)
Then boot on the key, mount the HDD.
Deactivate all the plugins you don't need right now and activate SMART and System Stats
Watch for any unusual temperature jump or read/write faults.

valve90210 · 18. November 2016

It's a second hand 250gb drive that came with the server, the other drive I have (it's a 3tb Toshiba), I removed for the installation so I knew I was definitely installing on the correct drive

I thought about trying to install on another hard drive to see if it's the disc that's the issue. which would essentially be the same as what you're saying wouldn't it?

Olivier · 18. November 2016

Zitat von valve90210

I thought about trying to install on another hard drive to see if it's the disc that's the issue. which would essentially be the same as what you're saying wouldn't it?

The pen drive solution is quicker and cheaper in order to test.
But if you already have another HDD for a fresh install I think it's not a bad idea to install directly on it.

valve90210 · 18. November 2016

Only reason I was thinking of testing with a different drive is that I have one laying around which I could just pop in there.

If it works on there I'll get myself a new drive for my final installation.

My fear is that it won't work on a the other drive either in which case I'm stumped... seems odd that it worked fine initially.

N40l Installation problems and constant errors

Jetzt mitmachen!

Tags