Buffer I/O error on device sdc1/end_request: I/O error, dev sdc

DatScreamer · 6. Januar 2016

Hi. straight to the point: Fresh install, installed on flash drive, 2 raid mirrored 1TB HDDS, Lenovo thinkcenter 4GB RAM 2 Core "Core Duo 1.8 GHz (Or 2.1 GHz, can't remember as had 2x of these with diff specs)

So what is this issue.

Logs are litterally like
[1114.523223] Buffer I/O error on device sdc1, logical block 23424323
[1114.523223] end_request: I/O error, dev sdc, sector 234453453
[1114.523223] Buffer I/O error on device sdc1, logical block 23424323
[1114.523223] end_request: I/O error, dev sdc, sector 234453453
[1114.523223] Buffer I/O error on device sdc1, logical block 23424323
[1114.523223] end_request: I/O error, dev sdc, sector 234453453
[1114.523223] Buffer I/O error on device sdc1, logical block 23424323
[1114.523223] end_request: I/O error, dev sdc, sector 234453453
[1114.523223] Buffer I/O error on device sdc1, logical block 23424323
[1114.523223] end_request: I/O error, dev sdc, sector 234453453
[1114.523223] Buffer I/O error on device sdc1, logical block 23424323
[1114.523223] end_request: I/O error, dev sdc, sector 234453453
[1114.523223] Buffer I/O error on device sdc1, logical block 23424323
[1114.523223] end_request: I/O error, dev sdc, sector 234453453
[1114.523223] Buffer I/O error on device sdc1, logical block 23424323
[1114.523223] end_request: I/O error, dev sdc, sector 234453453
[1114.523223] end_request: I/O error, dev sdc, sector 234453453
[1114.523223] end_request: I/O error, dev sdc, sector 234453453
[1114.523223] end_request: I/O error, dev sdc, sector 234453453
[1114.523223] end_request: I/O error, dev sdc, sector 234453453

omv-firstaid
/usr/sbin/omv-firstaid: 517: /user/sbin/opv-firstaid: cannot create /tmp/omv-setup13685: Read-only files system

df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 14G 1014M 12G 8% /
udev 10M 0 10M 0% /dev
tmpfs 352M 296K 352M 1% /run
/dev/disk/by-uuid/9f9ada87-6561-42a4-831a-ed44ab2b451a 14G 1013M 12G 8% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 834M 0 834M 0% /run/shm

ryecoaaron · 6. Januar 2016

sdc1 tells me that the drive has partitions and OMV doesn't use partitions for raid. So, I'm guessing the usb stick is going bad.

DatScreamer · 6. Januar 2016

How though. Its brand new literally. So what do I do now? Re install OMV for the 2-34024324 millionth time?

ryecoaaron · 6. Januar 2016

I don't know what else to tell you. I have killed a brand new usb stick in less than 24 hours. Have all of your million installs been on usb sticks? Did you install the flashmemory plugin? It should be the first thing you install.

DatScreamer · 6. Januar 2016

It is the first thing I install, except OMV-extras. I installed most of them on various USB sticks and a 320GB HDD. All not very hopefull. I have realistically attemped to install OMV for 2.5/3 weeks 6 hours/day = 100x attemps.

subzero79 · 6. Januar 2016

Zitat von DatScreamer

It is the first thing I install, except OMV-extras

The plugin uses a package called folder2ram, and it is distributed through omv-extras, didn't the installation said anything about that, like missing or borken dependencies ?

You need omv-extras for the plugin to fetch the package automatically

DatScreamer · 6. Januar 2016

I do not understand what you just said what your talking about? Sorry.

subzero79 · 6. Januar 2016

You just said you installed the flashmemory plugin but you did not install omv-extras plugin, is that correct?

DatScreamer · 6. Januar 2016

No. I install both plugins, omv-extras first and then flashmemory.

Also. I cant uninstall omv-extras. It did not install correctly.

subzero79 · 6. Januar 2016

Zitat von DatScreamer

Also. I cant uninstall omv-extras. It did not install correctly.

Why do you need to uninstall it? that would also remove the flashmemory plugin.

and what errors ?

DatScreamer · 6. Januar 2016

Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
openmediavault-omvextrasorg
0 upgraded, 1 newly installed, 0 to remove and 38 not upgraded.
Need to get 0 B/274 kB of archives.
After this operation, 1022 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
openmediavault-omvextrasorg
Authentication warning overridden.
Selecting previously unselected package openmediavault-omvextrasorg.
(Reading database ... 28884 files and directories currently installed.)
Unpacking openmediavault-omvextrasorg (from .../openmediavault-omvextrasorg_latest_all.deb) ...
Processing triggers for openmediavault ...

>>> *************** Error ***************
communication failure
<<< *************************************

subzero79 · 6. Januar 2016

That's in the webUI right?
is the same in terminal ssh?

DatScreamer · 6. Januar 2016

SSH not configured, yes its the web GUI. The GUI is really really slow.

DatScreamer · 6. Januar 2016

Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
openmediavault-omvextrasorg
0 upgraded, 1 newly installed, 0 to remove and 38 not upgraded.
Need to get 0 B/274 kB of archives.
After this operation, 1022 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
openmediavault-omvextrasorg
Authentication warning overridden.
Selecting previously unselected package openmediavault-omvextrasorg.
(Reading database ... 28884 files and directories currently installed.)
Unpacking openmediavault-omvextrasorg (from .../openmediavault-omvextrasorg_latest_all.deb) ...
Processing triggers for openmediavault ...

>>> *************** Error ***************
communication failure
<<< *************************************
Restarting engine daemon ...
Setting up openmediavault-omvextrasorg (2.12.2) ...
Initialize configuration

>>> *************** Error ***************
communication failure
<<< *************************************

More errors.

DatScreamer · 6. Januar 2016

On the server I am getting errors:
EXT4-FS error (Device sda1): ext4_find_entry:932: inode #2332332 comm cron-apt: reading directory Iblock 0
EXT4-FS error (Device sda1): ext4_find_entry:932: inode #2332332 comm cron-apt: reading directory Iblock 0
EXT4-FS error (Device sda1): ext4_find_entry:932: inode #2332332 comm cron-apt: reading directory Iblock 0
EXT4-FS error (Device sda1): ext4_find_entry:932: inode #2332332 comm cron-apt: reading directory Iblock 0
EXT4-FS error (Device sda1): ext4_find_entry:932: inode #2332332 comm cron-apt: reading directory Iblock 0
EXT4-FS error (Device sda1): ext4_find_entry:932: inode #2332332 comm cron-apt: reading directory Iblock 0
EXT4-FS error (Device sda1): ext4_find_entry:932: inode #2332332 comm cron-apt: reading directory Iblock 0
EXT4-FS error (Device sda1): ext4_find_entry:932: inode #2332332 comm cron-apt: reading directory Iblock 0
EXT4-FS error (Device sda1): ext4_find_entry:932: inode #2332332 comm cron-apt: reading directory Iblock 0
EXT4-FS error (Device sda1): ext4_find_entry:932: inode #2332332 comm cron-apt: reading directory Iblock 0
EXT4-FS error (Device sda1): ext4_find_entry:932: inode #2332332 comm cron-apt: reading directory Iblock 0
EXT4-FS error (Device sda1): ext4_find_entry:932: inode #2332332 comm cron-apt: reading directory Iblock 0
usb 2-3: device descriptor read/64, error -110
usb 2-3: device descriptor read/8, error -110
usb 2-3: device descriptor read/8, error -110

etc...

What are these from? Why are they happening. This is a fresh install and new usb stick yet I am getting what I think are HDD errors.

subzero79 · 6. Januar 2016

Zitat von DatScreamer

What are these from? Why are they happening.

Those are fs errors, and i don't why are they there, you could have faulty hardware memory maybe. Don't have an answer because i've never seen that error again.
Can you spare a partition hard drive and use a real one just to discard the usb bus maybe?
Also what brand/model of memory stick are you using?

ryecoaaron · 6. Januar 2016

I think most of these problems come from using usb sticks. Try temporarily using a hard drive just one time. Once a usb stick has an issue, throw it away (or at least never install OMV on it again).

DatScreamer · 6. Januar 2016

Ok. I am making a video of the whole process of installing OMV on a hard drive.

Jetzt mitmachen!