Hello, default 3.6.10-4.fc18.x86_64 f18 install kernel is ok. Instead both kernel-3.8.4-202.fc18 and 3.7.9-205.fc18
stop at boot with error and systemd emergency shell and journalctl shows like in this picture:
https://docs.google.com/file/d/0BwoPbcrMv8mvd0Z0bExhTDYxQjQ/edit?usp=sharing
any hint? I suspect raid controller: The same thing happens on two intel blades after I install f18 and run a yum update.
[root@management02 ~]# cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.6.10-4.fc18.x86_64 root=/dev/mapper/fedora_management02-root ro nomodeset rd.md=0 rd.lvm.lv=fedora_management02/root rd.dm=0 rd.lvm.lv=fedora_management02/swap rd.luks=0 vconsole.keymap=us rhgb quiet
[root@management02 ~]# lspci|grep SCSI 04:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1064ET PCI-Express Fusion-MPT SAS (rev 08)
[root@management02 ~]# cat /proc/mpt/version mptlinux-3.04.20 Fusion MPT base driver Fusion MPT SAS host driver
[root@management02 ~]# cat /proc/mpt/summary ioc0: LSISAS1064E B3, FwRev=011e0000h, Ports=1, MaxQ=277, IRQ=30
processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU X5570 @ 2.93GHz stepping : 5 microcode : 0x11 cpu MHz : 1596.000 cache size : 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida dtherm tpr_shadow vnmi flexpriority ept vpid bogomips : 5852.54 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management:
...
Thanks in advance, Gianluca
Am 30.03.2013 17:35, schrieb Gianluca Cecchi:
default 3.6.10-4.fc18.x86_64 f18 install kernel is ok. Instead both kernel-3.8.4-202.fc18 and 3.7.9-205.fc18
stop at boot with error and systemd emergency shell and journalctl shows like in this picture:
https://docs.google.com/file/d/0BwoPbcrMv8mvd0Z0bExhTDYxQjQ/edit?usp=sharing
any hint? I suspect raid controller: The same thing happens on two intel blades after I install f18 and run a yum update.
[root@management02 ~]# lspci|grep SCSI 04:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1064ET PCI-Express Fusion-MPT SAS (rev 08)
[root@management02 ~]# cat /proc/mpt/version mptlinux-3.04.20 Fusion MPT base driver Fusion MPT SAS host driver
make a bugreport and consider use software-RAID which works damned well and makes you independent of the hardware up to move the whole RAID disks in another machine like the one below has a older bitwise-clone on the other side of the city with different hardware
[root@srv-rhsoft:~]$ uname -r 3.8.5-201.fc18.x86_64 #1 SMP Thu Mar 28 21:01:19 UTC 2013
--------------------------------------------------------------------------------- /dev/md0: Version : 1.0 Creation Time : Wed Jun 8 13:10:48 2011 Raid Level : raid1 Array Size : 511988 (500.07 MiB 524.28 MB) Used Dev Size : 511988 (500.07 MiB 524.28 MB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent
Update Time : Fri Mar 29 16:38:00 2013 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0
Name : localhost.localdomain:0 UUID : 1d691642:baed26df:1d197496:4fb00ff8 Events : 476
Number Major Minor RaidDevice State 0 8 49 0 active sync /dev/sdd1 5 8 33 1 active sync /dev/sdc1 4 8 1 2 active sync /dev/sda1 3 8 17 3 active sync /dev/sdb1 --------------------------------------------------------------------------------- /dev/md1: Version : 1.1 Creation Time : Wed Jun 8 13:10:52 2011 Raid Level : raid10 Array Size : 30716928 (29.29 GiB 31.45 GB) Used Dev Size : 15358464 (14.65 GiB 15.73 GB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Sat Mar 30 17:39:12 2013 State : active Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0
Layout : near=2 Chunk Size : 512K
Name : localhost.localdomain:1 UUID : b7475879:c95d9a47:c5043c02:0c5ae720 Events : 11654
Number Major Minor RaidDevice State 0 8 50 0 active sync /dev/sdd2 5 8 34 1 active sync /dev/sdc2 4 8 2 2 active sync /dev/sda2 3 8 18 3 active sync /dev/sdb2 --------------------------------------------------------------------------------- /dev/md2: Version : 1.1 Creation Time : Wed Jun 8 13:10:56 2011 Raid Level : raid10 Array Size : 3875222528 (3695.70 GiB 3968.23 GB) Used Dev Size : 1937611264 (1847.85 GiB 1984.11 GB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Sat Mar 30 17:39:05 2013 State : active Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0
Layout : near=2 Chunk Size : 512K
Name : localhost.localdomain:2 UUID : ea253255:cb915401:f32794ad:ce0fe396 Events : 268057
Number Major Minor RaidDevice State 0 8 51 0 active sync /dev/sdd3 5 8 35 1 active sync /dev/sdc3 4 8 3 2 active sync /dev/sda3 3 8 19 3 active sync /dev/sdb3 --------------------------------------------------------------------------------- Personalities : [raid10] [raid1] md1 : active raid10 sdb2[3] sda2[4] sdd2[0] sdc2[5] 30716928 blocks super 1.1 512K chunks 2 near-copies [4/4] [UUUU] bitmap: 1/1 pages [4KB], 65536KB chunk
md0 : active raid1 sda1[4] sdb1[3] sdd1[0] sdc1[5] 511988 blocks super 1.0 [4/4] [UUUU]
md2 : active raid10 sda3[4] sdb3[3] sdd3[0] sdc3[5] 3875222528 blocks super 1.1 512K chunks 2 near-copies [4/4] [UUUU] bitmap: 3/29 pages [12KB], 65536KB chunk
unused devices: <none> ---------------------------------------------------------------------------------
On Sat Mar 30 16:41:10 UTC 2013 Reindl Harald wrote:
make a bugreport and consider use software-RAID which works damned well and makes you independent of the hardware
Unfortunately I have not great control on the hw... Opened bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=947255
After updating the system, if I boot with original stock f18 kernel is ok, while newer ones drive to emergency shell...
From lshw I see
... *-scsi description: SCSI storage controller product: SAS1064ET PCI-Express Fusion-MPT SAS vendor: LSI Logic / Symbios Logic physical id: 0 bus info: pci@0000:04:00.0 logical name: scsi1 version: 08 width: 64 bits clock: 33MHz capabilities: scsi pm pciexpress msi msix bus_master cap_list rom scsi-host configuration: driver=mptsas latency=0 resources: irq:30 ioport:1000(size=256) memory:b1910000-b1913fff memory:b1900000-b190ffff memory:b1c00000-b1dfffff *-disk description: SCSI Disk product: Multi-Flex vendor: Intel physical id: 0.0.0 bus info: scsi@1:0.0.0 logical name: /dev/sda version: 0308 serial: 4C202020000000000000000078164A5806D0806B size: 20GiB (21GB) capacity: 20GiB (21GB) capabilities: 15000rpm partitioned partitioned:dos configuration: ansiversion=5 sectorsize=512 signature=00020619
...
Gianluca