[PlanetCCRMA] Re: [linux-audio-user] planetedge kernels
Joey Reid
joe at joeyreid.com
Wed Oct 13 09:19:01 PDT 2004
woops! Reply doesn't reply to the list, does it... either that or
Mail.app is braindead.
Begin forwarded message:
> From: Joey Reid <joe at joeyreid.com>
> Date: October 13, 2004 1:16:49 PM ADT
> To: Fernando Pablo Lopez-Lezcano <nando at ccrma.stanford.edu>
> Subject: Re: [PlanetCCRMA] Re: [linux-audio-user] planetedge kernels
>
>
> On Oct 13, 2004, at 12:54 PM, Fernando Pablo Lopez-Lezcano wrote:
>>>
>>> "VFS: Cannot open root device "LABEL=/" on unknown-block(0,0)
>>> Please append a correct "root=" boot option
>>> Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)"
>>
>> What are messages right before this? Just to get a handle of where in
>> the boot process you are at that point.
>>
>
> going from memory, it was loading XFS (quota, acl, etc) and initrd,
> but I am guessing. I will have to check again tonight.
>
>>> I posted this problem on linux-audio, and Fernando you suggested that
>>> the "root=" option would need to contain the scsi device name, since
>>> the newer kernel uses libata and therefore scsi to access SATA disks.
>>> Since my disk under 2.6.5 is called "/dev/hdc5" I tried
>>> "root=/dev/sdc5", but that did not work. I then tried guessing at the
>>> scsi disk number. It would not work with sda5, sdb5, sdc5, sdd5, or
>>> sde5 ;-)
>>
>> Hmmm... what I would have done, I guess. partition "5" is /boot? "5"
>> as
>> the number sounds strange, is this an extended partition? What is
>> partitioning of the disk like? (fdisk -l /dev/hda when booted in the
>> kernel that works).
>>
>
> Disk /dev/hdc: 163.9 GB, 163928604672 bytes
> 255 heads, 63 sectors/track, 19929 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/hdc1 * 18655 19929 10241437+ 7 HPFS/NTFS
> /dev/hdc2 1 13 104391 83 Linux
> /dev/hdc3 14 144 1052257+ 82 Linux swap
> /dev/hdc4 145 18654 148681575 f W95 Ext'd (LBA)
> /dev/hdc5 145 18654 148681543+ 83 Linux
>
> Partition table entries are not in disk order
>
>
>>> I don't know if this matters, but my root partition is using XFS
>>> (/boot
>>> is ext3). I know it might matter in that it may not allow using
>>> "LABEL=" (according to some info that google returned), but other
>>> than
>>> that I'm not sure it should matter. I do see the XFS driver loading
>>> immediately before it gives me the above error, so I know that it
>>> must
>>> be included in the initrd.
>>>
>>> soooo, any other ideas?
>>
>> I know the messages probably scroll too fast, but do you see anything
>> related to sdx while the boot is progressing? (just in case, turn off
>> the graphical boot by editing the grub kernel boot command line and
>> erasing the "rhgb -etc-" part).
>>
> I never reach the graphical boot part. I used SHIFT-PGUP to look back,
> but I don't see any messages that mention sdX, and I did look.
>
>> I have never tried xfs so I don't know if that may be the problem.
>> Changing fstab to ommit the label could be an option but first make
>> sure
>> that you can boot into rescue mode with a cd and revert it (if the
>> boot
>> fails).
>
> I'm pretty sure this is all happening before it gets to read
> /etc/fstab, since the message is about the "root=" parameter.
>
> Is there a way to tell a kernel to use an alternate fstab in order to
> switch between kernels if "LABEL=/" doesn't work?
>
>> But you have to find out what is the device name first (what is
>> x in sdx).
>>
>
> can anyone recommend a 2.6.8.1 based livecd? i really can't figure out
> another way to get the device name.
>
> fwiw, this is an nforce2 mb with SiI3112 sata controller and Maxtor
> 6Y160M0 hard disk.
>
> thanks.
>
> --
> Joey Reid
> Integration Specialist
> Alcatel I.C.E.
>
>
--
Joey Reid aka Dr.Whiz-Bang
Geek, musician, and friend of God
http://www.joeyreid.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 4256 bytes
Desc: not available
URL: <https://cm-mail.stanford.edu/pipermail/planetccrma/attachments/20041013/6a7da2f2/attachment.bin>
More information about the PlanetCCRMA
mailing list