| View previous topic :: View next topic |
| Author |
Message |
NotExcessive
Apprentice
Joined: 10 May 2005
Posts: 235
|
 Posted: Sun Feb 24, 2013 2:26 am Post subject: [SOLVED] VFS: ...unknown-block(104,4): error -2 on a DL380G4 |
 |
|
Hi all;
I'm trying to get a new installation going on a DL380 G4 with the HP 6i disk controller. Everything built according to plan with gentoo-sources-3.7.9 and Grub2 installed without dramas.
I used the latest LiveCD, and the cciss driver is being used for the controller.
Problem is the dreaded | Code: | | VFS: Cannot open root device "cciss/c0d0p4" or unknown-block(104,4): error -2 |
message when I try and boot up the new system for the first time.
The entries in fstab are correct, the supported file systems are included in the kernel, as are all the drivers (as far as I can tell) for the HP 6i controller.
The (104,4) tells me that the system can see the controller, but that's as far as I can get. I've tried changing all the references of cciss to sda just in case the driver's doing some renaming, but that doesn't change anything.
Not sure if "104" is correct or not... I'm just used to seeing single digits in other installations.
Can anyone shed light on what's going on?
Last edited by NotExcessive on Sun Feb 24, 2013 12:04 pm; edited 1 time in total |
|
| Back to top |
|
 |
cach0rr0
Bodhisattva
Joined: 13 Nov 2008
Posts: 4123
Location: Houston, Republic of Texas
|
| Posted: Sun Feb 24, 2013 3:40 am Post subject: |
|
|
not knowing heaps about that specific setup (or, well, not having touched HP raid since like '07), i can offer one suggestion that may prove useful - make a tiny initramfs that does nothing more than launch a busybox shell
my thinking, basically, is if you have an initramfs that drops you to a busybox shell, you can see what /dev looks like after the kernel loads, then sorta step through piece by piece and see what's missing
when you have things sorted, nuke that initrd reference from grub2.cfg and carry on. Basically a tiny initramfs for the sole purpose of troubleshooting - though if youre doing this all over SSH that could be a PITA, and, disregard
your assertions thus far make perfect sense, and though ages ago i remember similar hurdles, so, that would be my own next step if i ran into such a thing.
HTH (?)
_________________
Lost configuring your system?
dump lspci -n here | see Pappy's guide | Link Stash |
|
| Back to top |
|
|
Jaglover
Watchman
Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana
|
|
| Back to top |
|
|
NotExcessive
Apprentice
Joined: 10 May 2005
Posts: 235
|
| Posted: Sun Feb 24, 2013 6:26 am Post subject: |
|
|
This is driving me batty. I've just built up a DL580G5 and a DL360G4p (and the DL360 uses the exact same disk controller), without any problem.
Just to experiment, I deleted the Grub2 configuration, and installed Grub-0.97, did the "fdisk, a, 1" thing (even though it's a GPT disk) and rebooted. Exactly the same result. |
|
| Back to top |
|
|
Jaglover
Watchman
Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana
|
|
| Back to top |
|
|
NotExcessive
Apprentice
Joined: 10 May 2005
Posts: 235
|
| Posted: Sun Feb 24, 2013 11:18 am Post subject: |
|
|
| Jaglover wrote: | | You didn't miss GPT partition table in kernel config? |
I have EFI_PARTITION set to "yes".
REVISION:
Cracked it. You're not going to believe this (on the other hand, you will), but changing the boot entry in Grub from root=/dev/cciss/c0d0p4 to root=/dev/cciss!c0d0p4 solved everything. This is what drove me nuts: the labeling has always been /dev/cciss/c0d0 and somewhere along the line, the driver's calling it /dev/cciss!c0d0 instead! No wonder I couldn't find the bloody thing.
The version of gentoo-sources I used for this machine is 3.7.9. With the DL360G4p I built recently, the version was 3.6.11. I can only surmise somebody changed something along the way.
I think I need a drink. |
|
| Back to top |
|
|
jmartos
Tux's lil' helper
Joined: 23 Mar 2008
Posts: 76
|
| Posted: Sun Mar 03, 2013 6:41 pm Post subject: |
|
|
| Thank you NotExcessive. I had the same issue with kernel 3.7.9 and a P400 controller. The root device needed to be changed from root=/dev/cciss/c0d0p3 to root=/dev/cciss!c0d0p3 in the grub config file. |
|
| Back to top |
|
|
cgill27
n00b
Joined: 15 Mar 2008
Posts: 23
|
| Posted: Mon Mar 18, 2013 4:45 pm Post subject: |
|
|
| After some googling on why my kernel 3.7.10 was kernel panic'ing on boot after working fine in 3.6 I came across your post, thanks again for sharing the solution! It was the "!" replacement |
|
| Back to top |
|
|
|
Installing Gentoo
