Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 816443

Summary: install rhev-h onto kingston sd card fails
Product: Red Hat Enterprise Linux 6 Reporter: yuanquan chen <yuachen>
Component: ovirt-nodeAssignee: Mike Burns <mburns>
Status: CLOSED NOTABUG QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 6.3CC: acathrow, bsarathy, cshao, fdeutsch, gouyang, jboggs, leiwang, mburns, ovirt-maint, shcao, ycui
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-27 10:02:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
ovirt log of Installation none

Description yuanquan chen 2012-04-26 05:10:29 UTC
Description of problem:
RHEV-H fails to install into kingston sd card at creating the partitions
for rhev-h installation.

It fails on kingston sd card read(FCR-HS219_1) with kingston sd card, while it success to install rhev-h into sandisk sd card(readSD_SDDR-189) with sandisk sd card.

Version-Release number of selected component (if applicable):
rhevh-6.3-20120419.0.el6

How reproducible:
100%

Steps to Reproduce:
1. add a kingston sd card to the specified kingston sd card reader, connect the card reader to host though usb cable
the card reader modele: FCR_HS219_1
the card reader serial: kingston_FCR-HS219_1_111201000775-0:1
2. boot rhev-h from pxe, choose to install into sd card
  
Actual results:
The installation fails

Expected results:
The installation to sd card successes, rhev-h can boot up from the
installed sd card


Additional info:

Comment 2 yuanquan chen 2012-04-26 06:23:32 UTC
Created attachment 580365 [details]
ovirt log of Installation

Comment 3 yuanquan chen 2012-04-26 06:34:46 UTC
Though it fails to install rhev-h into kingston sd card which is connected via kingston sd card reader, it can successes to install rhev-h into the kingston sd card connected via sandisk reader.

Comment 4 Mike Burns 2012-04-26 13:18:24 UTC
So to summarize:

kingston card + kingston reader == FAIL
sandisk card + sandisk reader == PASS
kingston card + sandisk reader == PASS

What about sandisk card and kingston reader?

Comment 5 yuanquan chen 2012-04-27 07:02:31 UTC
(In reply to comment #4)
> So to summarize:
> 
> kingston card + kingston reader == FAIL
> sandisk card + sandisk reader == PASS
> kingston card + sandisk reader == PASS
> 
> What about sandisk card and kingston reader?

Hi Mike,

Please ignore my comment#3, I mess up the result at that time, and I tested today, the results is:

kingston card + kingston reader == FAIL
kingston card + sandisk reader == FAIL
sandisk card + sandisk reader == PASS
sandisk card + kingston reader == PASS

So it seems it's the the kingston card problem. I also try to format it manually, it fails also, details as below:

1. make 4 primer partitions as 256M, 256M, 256M, the rest of disk size
2. format each partition as ext2 filesystem
3. the formatting of partition 3 fails at writing inode table:

[chenyq@localhost ~]$ sudo mkfs /dev/sdc3 
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
65536 inodes, 262144 blocks
13107 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67371008
32 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks: 
	8193, 24577, 40961, 57345, 73729, 204801, 221185

Writing inode tables:  2/32
Could not write 5 blocks in inode table starting at 16387: Attempt to write block from filesystem resulted in short write

Then the disk could not be found by the system.

Comment 6 Fabian Deutsch 2012-04-27 08:06:55 UTC
I've read about USB stick claiming to be larger than they are.
Could this be the case here?

Comment 7 Guohua Ouyang 2012-04-27 08:22:37 UTC
(In reply to comment #6)
> I've read about USB stick claiming to be larger than they are.
> Could this be the case here?

I've suspected this reason too, but after read the /var/log/ovirt.log, it seems not.  According to bz815721, it seems does not report error even size is not enough, QE will re-test this on the new build.

Comment 8 yuanquan chen 2012-04-27 10:02:27 UTC
Using the method "mkfs.ext2 -cc /dev/sdc" to check the sd card bad blocks, then it successes to install rhev-h into the kingston sd card connected via kingston reader. So it's a sd card issue, not a bug.

After installing rhev-h into kingston sd card, boot rhev-h from the installed card:

[root@localhost admin]# lvs
  LV      VG     Attr     LSize Pool Origin Data%  Move Log Copy%  Convert
  Config  HostVG -wi-ao-- 8.00m                                           
  Data    HostVG -wi-ao-- 4.48g                                           
  Logging HostVG -wi-ao-- 2.00g                                           
[root@localhost admin]# pvs
  PV         VG     Fmt  Attr PSize PFree
  /dev/sdc4  HostVG lvm2 a--  6.49g    0 
[root@localhost admin]# udevadm info -q env -n /dev/sdc
sdc   sdc1  sdc2  sdc3  sdc4  
[root@localhost admin]# udevadm info -q env -n /dev/sdc4 
UDEV_LOG=3
DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/host6/target6:0:0/6:0:0:1/block/sdc/sdc4
MAJOR=8
MINOR=36
DEVNAME=/dev/sdc4
DEVTYPE=partition
SUBSYSTEM=block
MPATH_SBIN_PATH=/sbin
ID_VENDOR=Kingston
ID_VENDOR_ENC=Kingston
ID_VENDOR_ID=11b0
ID_MODEL=FCR-HS219_1
ID_MODEL_ENC=FCR-HS219\x2f1\x20\x20\x20\x20\x20
ID_MODEL_ID=6148
ID_REVISION=9745
ID_SERIAL=Kingston_FCR-HS219_1_111201000775-0:1
ID_SERIAL_SHORT=111201000775
ID_TYPE=disk
ID_INSTANCE=0:1
ID_BUS=usb
ID_USB_INTERFACES=:080650:
ID_USB_INTERFACE_NUM=00
ID_USB_DRIVER=usb-storage
ID_PATH=pci-0000:00:1a.0-usb-0:1.4:1.0-scsi-0:0:0:1
ID_PART_TABLE_TYPE=gpt
ID_FS_UUID=tnNTkQ-xPLt-AWnC-dXrE-HwlY-DDDu-ii3F5K
ID_FS_UUID_ENC=tnNTkQ-xPLt-AWnC-dXrE-HwlY-DDDu-ii3F5K
ID_FS_VERSION=LVM2\x20001
ID_FS_TYPE=LVM2_member
ID_FS_USAGE=raid
LVM_SBIN_PATH=/sbin
DEVLINKS=/dev/block/8:36 /dev/disk/by-id/usb-Kingston_FCR-HS219_1_111201000775-0:1-part4 /dev/disk/by-path/pci-0000:00:1a.0-usb-0:1.4:1.0-scsi-0:0:0:1-part4