Well, I got it to boot. Now that it's up, I can see what the problem was/is.
There are no disk device files in /dev.
I created the appropriate nodes and things went much better.
The problem was that CONFIG_SYSFS_DEPRECATED_V2 was on
I just closed up the chassis and it will ship in the morning
On 10/15/2010 12:23 PM, Mike Diehl wrote:
> On Friday 15 October 2010 11:40:34 am Florian Philipp wrote:
>> Am 15.10.2010 19:29, schrieb Mike Diehl:
>>> Hi all.
>>>
>>> I've never had this much trouble with a server before, but I've been
>>> pulling my hair out.
>>>
>>> The install seemed to go wel
Am 15.10.2010 21:23, schrieb Mike Diehl:
> On Friday 15 October 2010 11:40:34 am Florian Philipp wrote:
>> Am 15.10.2010 19:29, schrieb Mike Diehl:
>>> Hi all.
>>>
>>> I've never had this much trouble with a server before, but I've been
>>> pulling my hair out.
>>>
>>> The install seemed to go well
Apparently, though unproven, at 19:47 on Friday 15 October 2010, Mike Diehl
did opine thusly:
> > Instead of your brute-force "yes to all" approach, newer kernels also
> > support `make localyesconfig` which takes all modules currently used in
> > the running kernel and compiles them into the new
One more interesting tidbit:
When it boots, I can see that VFS was able to mount ROOT on device 8:3.
So, it doesn't seem to be hardware or driver related. Looks like something
with the filesystem? fsck.ext2 is the only thing complaining. However, when
I boot from CD, I can mount it just fine
On Friday 15 October 2010 11:40:34 am Florian Philipp wrote:
> Am 15.10.2010 19:29, schrieb Mike Diehl:
> > Hi all.
> >
> > I've never had this much trouble with a server before, but I've been
> > pulling my hair out.
> >
> > The install seemed to go well, but when I rebooted it from it's own har
fre 2010-10-15 klockan 11:29 -0600 skrev Mike Diehl:
> Hi all.
>
> I've never had this much trouble with a server before, but I've been pulling
> my hair out.
>
> The install seemed to go well, but when I rebooted it from it's own hard
> drive, it fails. fsck claims that it can't open /dev/sda
On 15/10/2010 10:47 AM, Mike Diehl wrote:
> On Friday 15 October 2010 11:40:34 am Florian Philipp wrote:
>> Instead of your brute-force "yes to all" approach, newer kernels also
>> support `make localyesconfig` which takes all modules currently used in
>> the running kernel and compiles them into t
On Friday 15 October 2010 11:40:34 am Florian Philipp wrote:
>
> *All* of the drivers could be too much. There is a generic driver which
> can prevent the "right" driver from taking over. In that case you end up
> with a /dev/hda node and no DMA. Try to deactivate "Generic ATA support"
> = CONFIG
Am 15.10.2010 19:29, schrieb Mike Diehl:
> Hi all.
>
> I've never had this much trouble with a server before, but I've been pulling
> my hair out.
>
> The install seemed to go well, but when I rebooted it from it's own hard
> drive, it fails. fsck claims that it can't open /dev/sda3 or that th
Hi all.
I've never had this much trouble with a server before, but I've been pulling
my hair out.
The install seemed to go well, but when I rebooted it from it's own hard
drive, it fails. fsck claims that it can't open /dev/sda3 or that the
superblock doesn't describe a valid ext2 filesystem.
11 matches
Mail list logo
