From what i can see from the process tree, maybe it's a grub2 problem, since it seems to be failing at drakrpm -> grub2.script
Still, dmesg shows very weird messages, maybe related to device-mapper (which i think has been updated recently):
[ 629.772110] device-mapper: uevent: version 1.0.3
[ 629.772191] device-mapper: ioctl: 4.26.0-ioctl (2013-08-15) initialised: dm-devel@redhat.com
[ 630.634289] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[ 630.651089] JFS: nTxBlock = 8192, nTxLock = 65536
[ 630.673333] NTFS driver 2.1.30 [Flags: R/O MODULE].
[ 630.696391] QNX4 filesystem 0.2.3 registered.
[ 630.921226] EXT2-fs (sda2): error: unable to read superblock
[ 630.922955] EXT4-fs (sda2): unable to read superblock
[ 630.924234] cramfs: wrong magic
[ 630.933761] EXT3-fs (sda2): error: unable to read superblock
[ 630.935247] XFS (sda2): bad magic number
[ 630.935251] ffff880157409000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 630.935253] ffff880157409010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 630.935254] ffff880157409020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 630.935255] ffff880157409030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 630.935257] XFS (sda2): Internal error xfs_sb_read_verify at line 637 of file fs/xfs/xfs_sb.c. Caller 0xffffffffa1000525
[ 630.935261] CPU: 2 PID: 265 Comm: kworker/2:1H Tainted: P O 3.12.13-desktop-2.mga4 #1
[ 630.935262] Hardware name: Gigabyte Technology Co., Ltd. GA-MA790XT-UD4P/GA-MA790XT-UD4P, BIOS F9b 08/17/2012
[ 630.935290] Workqueue: xfslogd xfs_buf_iodone_work [xfs]
[ 630.935292] 0000000000000001 ffff8802246fdd68 ffffffff8160f53e ffff88021f300800
[ 630.935294] ffff8802246fdd80 ffffffffa100362b ffffffffa1000525 ffff8802246fddb8
[ 630.935296] ffffffffa1003685 0000027d00000000 ffff8801574f6000 0000000000000016
[ 630.935297] Call Trace:
[ 630.935302] [<ffffffff8160f53e>] dump_stack+0x45/0x56
[ 630.935314] [<ffffffffa100362b>] xfs_error_report+0x3b/0x40 [xfs]
[ 630.935325] [<ffffffffa1000525>] ? xfs_buf_iodone_work+0x85/0xf0 [xfs]
[ 630.935335] [<ffffffffa1003685>] xfs_corruption_error+0x55/0x80 [xfs]
[ 630.935352] [<ffffffffa1057560>] xfs_sb_read_verify+0x130/0x150 [xfs]
[ 630.935362] [<ffffffffa1000525>] ? xfs_buf_iodone_work+0x85/0xf0 [xfs]
[ 630.935372] [<ffffffffa1000525>] xfs_buf_iodone_work+0x85/0xf0 [xfs]
[ 630.935376] [<ffffffff8107b15c>] process_one_work+0x17c/0x410
[ 630.935378] [<ffffffff8107bd41>] worker_thread+0x121/0x3b0
[ 630.935379] [<ffffffff8107bc20>] ? rescuer_thread+0x320/0x320
[ 630.935381] [<ffffffff81082750>] kthread+0xc0/0xd0
[ 630.935383] [<ffffffff81082690>] ? kthread_create_on_node+0x120/0x120
[ 630.935386] [<ffffffff8161e70c>] ret_from_fork+0x7c/0xb0
[ 630.935387] [<ffffffff81082690>] ? kthread_create_on_node+0x120/0x120
[ 630.935389] XFS (sda2): Corruption detected. Unmount and run xfs_repair
[ 630.935406] XFS (sda2): SB validate failed with error 22.
[ 630.944509] FAT-fs (sda2): bogus number of reserved sectors
[ 630.944513] FAT-fs (sda2): Can't find a valid FAT filesystem
[ 630.948508] FAT-fs (sda2): bogus number of reserved sectors
[ 630.948518] FAT-fs (sda2): Can't find a valid FAT filesystem
[ 630.956147] MINIX-fs: unable to read superblock
[ 630.962279] attempt to access beyond end of device
[ 630.962290] sda2: rw=0, want=3, limit=2
[ 630.962296] hfsplus: unable to find HFS+ superblock
[ 630.968086] qnx4: wrong fsid in superblock.
[ 630.970736] You didn't specify the type of your ufs filesystem
Funny thing is, there's no sda2! I mean, not really, it's an extended partition:
parted -l
Model: ATA M4-CT064M4SSD2 (scsi)
Disk /dev/sda: 64,0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Numero Inicio Fin Tamaño Typo Sistema de ficheros Banderas
1 2097kB 21,5GB 21,5GB primary ntfs arranque
2 21,5GB 64,0GB 42,5GB extended
5 21,5GB 43,0GB 21,5GB logical ext4
6 43,0GB 45,1GB 2147MB logical linux-swap(v1)
7 45,1GB 62,3GB 17,2GB logical ext4
Obviously i'm forced to kill drakrpm, and luckily the packages are successfully installed/removed. Still, i've run rpm --rebuilddb just in case.
Any clues on this? I would've reported it as a bug, but i'm not sure what causes it.