On 2014-10-04 07:56, cgarai wrote:
>
> Sorry, hit submit before checking
> linux-hive:/home/chris # lsblk --output NAME,KNAME,RM,SIZE,RO,TYPE,FSTYPE,LABEL,PARTLABEL,MOUNTPOINT,UUID,PARTUUID,MODEL,ALIGNMENT
> NAME KNAME RM SIZE RO TYPE FSTYPE LABEL PARTLABEL MOUNTPOINT UUID PARTUUID MODEL ALIGNMENT
> sda sda 0 149.1G 0 disk WDC WD1600JB-00G 0
> ├─sda1 sda1 0 90.3G 0 part ntfs Backups 2660ED1860ECF00B 0
> ├─sda2 sda2 0 406M 0 part ext4 /boot 13a6b655-4066-4c42-9ace-e41ef359b313 0
> └─sda3 sda3 0 58.3G 0 part LVM2_member urH8PD-MlK1-0sX2-DDDl-hh1j-LgPP-RexgSG 0
> ├─system-home
> dm-0 0 25G 0 lvm ext4 /home 094342ea-fbea-4c71-ae0d-5307b89f4956 0
> ├─system-root
> dm-1 0 20G 0 lvm ext4 / 80e74d8a-ca13-4b29-bee8-a47b5f4c184d 0
> └─system-swap
> dm-2 0 2G 0 lvm swap [SWAP] 1853cdb8-76da-42cf-9dc3-9ba45df2a04a 0
> sdb sdb 0 186.3G 0 disk WDC WD2000JS-00M 0
> ├─sdb1 sdb1 0 97.7G 0 part ntfs Programs /windows/C_Programs B0C48337C482FEBA 0
> ├─sdb2 sdb2 0 1K 0 part 0
> ├─sdb5 sdb5 0 88G 0 part ntfs DATA /windows/D_DATA 11AB766F2ADB5869 0
> └─sdb6 sdb6 0 724M 0 part ext4 /var/run/media/chris/4a83efba-5074-4ec7-8d95-a263b1935a74 4a83efba-5074-4ec7-8d95-a263b1935a74 0
> sr0 sr0 1 1024M 0 rom DVDRW LH-18A1P 0
> sr1 sr1 1 1024M 0 rom CD-RW SOHR-5239V 0
Well, there is currently nothing labeled “sdc”, but…
> linux-hive:/home/chris # ls -l /dev/sd?
> brw-rw---- 1 root disk 8, 0 Oct 3 15:29 /dev/sda
> brw-rw---- 1 root disk 8, 16 Oct 3 15:29 /dev/sdb
> brw-rw---- 1 root disk 8, 32 Oct 3 15:29 /dev/sdc
> brw-rw---- 1 root disk 8, 48 Oct 3 15:29 /dev/sdd
> brw-rw---- 1 root disk 8, 64 Oct 3 15:29 /dev/sde
> brw-rw---- 1 root disk 8, 80 Oct 3 15:29 /dev/sdf
… there was.
Still, there also were sdd, sde, sdf, and these do not cause zypper to barf.
Maybe a reference in the repo list :-?
Have a look on the files at “/etc/zypp/repos.d/”, see if anyone makes a reference that could point to “sdc”.
The error we are looking at is:
# ERROR: asr: reading /dev/sdc[Input/output error]
# ERROR: ddf1: reading /dev/sdc[Input/output error]
# ERROR: ddf1: reading /dev/sdc[Input/output error]
Now, what is asr or ddf1, I don’t know/remember :-?
Wait!
# Perl-Bootloader: 2014-10-02 14:13:29 <3> pbl-2197.2 Core::RunCommand.1642: Error: Command '/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg >/var/log/YaST2/y2log_bootloader 2>&1' failed with code 2 and output: Generating grub.cfg ...
# Found theme: /boot/grub2/themes/openSUSE/theme.txt
# Found linux image: /boot/vmlinuz-3.11.10-21-desktop
# Found initrd image: /boot/initrd-3.11.10-21-desktop
# Found linux image: /boot/vmlinuz-3.11.10-7-desktop
# Found initrd image: /boot/initrd-3.11.10-7-desktop
# Found memtest image: /boot/memtest.bin
# ERROR: asr: reading /dev/sdc[Input/output error]
# ERROR: ddf1: reading /dev/sdc[Input/output error]
# ERROR: ddf1: reading /dev/sdc[Input/output error]
.....
It is grub2 which is accessing sdc. Rather, Perl-Bootloader calling grub2-mkconfig.
Have a good look at it.
A grub2 expert can take over here now, please? 
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)