gparted reports a problem with a working drive

[Peter Pfeiffer]

Error recieved: Error fsyncing/closing /dev/sdh: Remote I/O error
gparted version 0.18.0
kernel version 3.13.0-53-generic
Description: Ubuntu 14.04.2 LTS
This drive is attached to a builtin USB port
Device info: Samsung MP0402H ; 37.31 GB

This same drive has Ubuntu 12.04.5 installed (3.13.0.32) with gparted 0.11.0 and is working perfectly.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gparted 0.18.0-1
ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
Uname: Linux 3.13.0-53-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jun 10 21:29:49 2015
InstallationDate: Installed on 2014-04-04 (432 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gparted
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: pfeiffep 5385 F.... pulseaudio
 /dev/snd/controlC0: pfeiffep 5385 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=91da439c-443c-4f70-b042-ffeef1f8373f
InstallationDate: Installed on 2014-04-04 (435 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404)
MachineType: Hewlett-Packard HPE-580t
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-54-generic root=UUID=fbf29380-b1fc-4c8a-bc03-6365d5803394 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-54-generic N/A
 linux-backports-modules-3.13.0-54-generic N/A
 linux-firmware 1.127.12
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
Tags: trusty
Uname: Linux 3.13.0-54-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/18/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6.13
dmi.board.asset.tag: N/A
dmi.board.name: 2A86
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.04E01
dmi.chassis.asset.tag: 2MD1180PCF
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.13:bd03/18/2011:svnHewlett-Packard:pnHPE-580t:pvr:rvnPEGATRONCORPORATION:rn2A86:rvr1.04E01:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: HPE-580t
dmi.sys.vendor: Hewlett-Packard

[Phillip Susi (psusi)]

Please check dmesg or /var/log/kern.log after getting this error for more detailed messages.

[Peter Pfeiffer (pfeiffep)]

also happens with vivid
pfeiffep@pete-HP:~$ uname -r
3.19.0-18-generic
pfeiffep@pete-HP:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 15.04
Release: 15.04
Codename: vivid

gparted version 0.19.0

/var/log/dmesg
(Nothing has been logged yet.)
dmesg (END)

var/log/kern.log
Jun 11 13:17:14 pete-HP gnome-session[1636]: Entering running state
Jun 11 13:17:16 pete-HP kernel: [ 40.268812] blk_update_request: critical target error, dev sdh, sector 0
Jun 11 13:17:16 pete-HP kernel: [ 40.268844] JBD2: recovery failed
Jun 11 13:17:16 pete-HP kernel: [ 40.268847] EXT4-fs (sdh1): error loading journal
Jun 11 13:17:36 pete-HP kernel: [ 60.097542] ata3.00: Enabling discard_zeroes_data
Jun 11 13:17:36 pete-HP kernel: [ 60.098395] sda: sda1 sda2 sda3
Jun 11 13:17:36 pete-HP kernel: [ 60.101902] blk_update_request: critical target error, dev sdh, sector 0
Jun 11 13:17:45 pete-HP kernel: [ 69.427629] blk_update_request: critical target error, dev sdh, sector 0
Jun 11 13:17:46 pete-HP kernel: [ 70.701003] blk_update_request: critical target error, dev sdh, sector 0
Jun 11 13:17:47 pete-HP kernel: [ 71.279133] blk_update_request: critical target error, dev sdh, sector 0
Jun 11 13:17:48 pete-HP kernel: [ 71.918717] ata3.00: Enabling discard_zeroes_data
Jun 11 13:17:48 pete-HP kernel: [ 71.918999] sda: sda1 sda2 sda3
Jun 11 13:17:48 pete-HP kernel: [ 72.217302] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:f8:e4:fb:8f:27:dc:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
Jun 11 13:17:52 pete-HP kernel: [ 76.030808] blk_update_request: critical target error, dev sdh, sector 0
Jun 11 13:17:53 pete-HP kernel: [ 77.561968] blk_update_request: critical target error, dev sdh, sector 0

[Phillip Susi (psusi)]

It certainly looks like a hardware error, but if you say it works under 12.04, then it could be a kernel issue. Please attach your whole kern.log.

[Peter Pfeiffer (pfeiffep)]

I'll attach the kern.log from 15... later
Here's more evidence from gdisk that it's working (and it very well may be a hardware error, but it does have 12.04.5 installed on it)
pfeiffep@pete-HP:~$ sudo gdisk -l /dev/sdh
[sudo] password for pfeiffep:
GPT fdisk (gdisk) version 0.8.10

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************
Disk /dev/sdh: 78242976 sectors, 37.3 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 460F1C67-51D0-4BB6-92EA-2C8B8EA62128
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 78242942
Partitions will be aligned on 1-sector boundaries
Total free space is 117909 sectors (57.6 MiB)

Number Start (sector) End (sector) Size Code Name
   1 63 78125062 37.3 GiB 8300 Linux filesystem
pfeiffep@pete-HP:~$ sudo gdisk -p /dev/sdh
GPT fdisk (gdisk) version 0.8.10

[Peter Pfeiffer (pfeiffep)]

Phillip, I've attached 1504 kern.log. The drive in question has 12.04.5 installed and I booted from the same USB port that produced the failure in 1504.

[Peter Pfeiffer (pfeiffep)]

Here's the kern.log from 12.04

[Phillip Susi (psusi)]

You need to grab the log after doing whatever it is you did that caused the original error. This appears to be from a boot of the system with no errors.

[Peter Pfeiffer (pfeiffep)]

Thanks the whole point was to show you there were no errors on the drive with 12.04 installed. Apparently the 1504 log wasn't uploaded ...I'll try again

[Peter Pfeiffer (pfeiffep)]

Post #6 & 9 have 15.04 kern.log
post #7 has the log from the drive booted to 12.04 showing that at least with 12.04 there's no issue.
It's the exact same drive using the exact same usb port

[Peter Pfeiffer (pfeiffep)]

Christopher M. Penalver, I think I've unintentionally confused the trouble shooting efforts for this. I've tested the drive on 2 different machines with 3 different Ubuntu versions. The original bug was reported on a machine running Ubuntu 14.04.2; I'll attempt to gather the requested information using the suggested command, however I run bleachbit prior to every shutdown on this machine so maybe the info is gone. When I get to that machine I'll check if the info is still available.

[Peter Pfeiffer (pfeiffep)]

apport information

[Peter Pfeiffer (pfeiffep)]

apport information

[Peter Pfeiffer (pfeiffep)]

apport information

[Peter Pfeiffer (pfeiffep)]

apport information

[Peter Pfeiffer (pfeiffep)]

apport information

[Peter Pfeiffer (pfeiffep)]

apport information

[Peter Pfeiffer (pfeiffep)]

apport information

[Peter Pfeiffer (pfeiffep)]

apport information

[Peter Pfeiffer (pfeiffep)]

apport information

[Peter Pfeiffer (pfeiffep)]

apport information

[Peter Pfeiffer (pfeiffep)]

apport information

[Peter Pfeiffer (pfeiffep)]

apport information

[Peter Pfeiffer (pfeiffep)]

apport information

[Peter Pfeiffer (pfeiffep)]

apport information

[Peter Pfeiffer (pfeiffep)]

apport information

[Peter Pfeiffer (pfeiffep)]

As I suspected ...

apport-collect 1464060
The authorization page:
 (https://launchpad.net/+authorize-token?oauth_token=hnpfznsF2HLV8LNvcNnK&allow_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Press any key to continue or wait (5) seconds...
Waiting to hear from Launchpad about your decision...

(process:28044): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
dpkg-query: no packages found matching linux

I can easily duplicate the symptoms. Any suggestions as to how to faciltate reporting the information you requested? should I just submit another report and use the command with the new report # ???

[Peter Pfeiffer (pfeiffep)]

Christopher M. Penalver please see bug 1464905 for the information you requested.
Sorry for the confusion

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[penalvch (penalvch)]

Peter Pfeiffer, as per http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-Elite-HPE-500-Desktop-PC-series/5035344/model/5061007 an update to your computer's buggy and outdated BIOS is available (6.16). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]