Hi Andras, On Jun 17, 2014, at 19:02 , Andras Horvath wrote:
> On Tue, 17 Jun 2014 15:52:58 +0200 > Stephan Wiesand <[email protected]> wrote: >> On 2014-06-17, at 11:08, Andras Horvath <[email protected]> wrote: >> >>> On Tue, 17 Jun 2014 10:50:17 +0200 >>> Stephan Wiesand <[email protected]> wrote: >>> >>>>> I've got the following server: >>>>> >>>>> DELL Poweredge T110 II >>>>> 01:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2008 >>>>> [Falcon] (rev 03) >>>>> System is SL 6.5 64 bit with hw raid 1 setup, so array is seen as sda >>>> >>>> is that a Dell card? >>> >>> I don't know but it came with the server preinstalled. I can look after >>> this info if it can help. >> >> Looks like an H310. I just booted an R420 with such a card into -431.17.1 >> and it works just fine. Here's the lspci -nn data: >> >> 01:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS >> 2008 [Falcon] [1000:0073] (rev 03) >> >>>>> I'm having problem with the latest kernel version for some time now. The >>>>> previous kernel version boots fine and everything works just well, but >>>>> the latest kernel (v2.6.32-431.17.1.el6.x86_64) cannot boot and Grub says >>>>> something like "trying to reach blocks outside of partition" and that's >>>>> all the message there is and boot hangs. >>>> >>>> If it's really Grub saying this, the kernel hasn't even started. Is /boot >>>> a separate partition? Size and fs? Have you fsck'ed it? Checked free space >>>> and inodes? Tried to reinstall the kernel and the initramfs? >>> >>> Since this is a hardver Raid, I can see only a single sda device. I have >>> also only a single root partition, the boot is not a separate one. The size >>> is 1.8 TB (2 x 2 TB disks in the array, the raid BIOS of the card does not >>> show any problem). I've got plenty of free space and should not be at the >>> limit of the inodes either I believe. Also, I entirely reinstalled the >>> kernel thinking that something could have gone wrong during the update, but >>> it gives the same result. >> >> It really seems Grub has trouble with your /boot. Maybe due to a filesystem >> inconsistency. Maybe due to a large inode number it can't deal with (does >> "ls -i /boot" reveal anything unusual?). > # ls -i /boot | sort -n > 140811 grub > 141909 extlinux > 177524 System.map-2.6.32-431.5.1.el6.x86_64 > 177525 config-2.6.32-431.5.1.el6.x86_64 > 177526 symvers-2.6.32-431.5.1.el6.x86_64.gz > 177542 vmlinuz-2.6.32-431.5.1.el6.x86_64 > 177582 initramfs-2.6.32-431.11.2.el6.x86_64.img > 178327 System.map-2.6.32-431.11.2.el6.x86_64 > 178348 initramfs-2.6.32-358.14.1.el6.x86_64.img > 178452 config-2.6.32-431.11.2.el6.x86_64 > 178453 symvers-2.6.32-431.11.2.el6.x86_64.gz > 178458 initramfs-2.6.32-431.5.1.el6.x86_64.img > 178529 vmlinuz-2.6.32-431.11.2.el6.x86_64 > 181915 System.map-2.6.32-358.14.1.el6.x86_64 > 181916 config-2.6.32-358.14.1.el6.x86_64 > 181917 symvers-2.6.32-358.14.1.el6.x86_64.gz > 181918 vmlinuz-2.6.32-358.14.1.el6.x86_64 > 191634 efi > 192173 elf-memtest86+-4.10 > 192174 memtest86+-4.10 > 262276 boot > > > Does it seem high number? No, but then there are no files for -431.17.1 ... can you install it and try again? Stephan -- Stephan Wiesand DESY -DV- Platanenenallee 6 15738 Zeuthen, Germany
