Re: [gentoo-user] Problems booting vanilla kernel 4.1.x
On Sun, 30 Aug 2015, Fernando Rodriguez wrote: > And you should still try suggestion #2 because it's very likely to only affect > one specific configuration. Thanks, I did that just now. Took another, but didn't give me any more data to go by. Getting set up for bisecting and doing real work on this would probably fill my evenings until end of next week. Nowadays I just don't have the time to fiddle around with computers any more (and it's not fun any more, either). I guess, I'll just go back to a kernel version with longterm support. Thanks anyway for your help! Peter.
Re: [gentoo-user] Problems booting vanilla kernel 4.1.x
On Sunday, August 30, 2015 6:11:00 PM Fernando Rodriguez wrote: > On Sunday, August 30, 2015 10:51:57 PM Peter Weilbacher wrote: > > Hi Fernando, > > > > On Sun, 30 Aug 2015, Fernando Rodriguez wrote: > > > > > 1. Add loglevel=7 to your kernel parameters and see what it prints before > it > > > hangs. > > > > That helped, it showed me something about drm, so... > > > > > 3. From your kernel parameters I assume you're using the radeon free > driver > > > right? If that's the case disable it (don't compile it in or just delete > the > > > module) and try to boot wiith a framebuffer. > > > > ... this was a good suggestion. Switching off DRM/Radeon gets me a > > kernel that boots. However, with that config I cannot run X (which then > > complains about missing kernel mode switching). If I follow > > wiki.gentoo.org/wiki/Xorg/Guide#Kernel_modesetting I again arrive at the > > kernel settings that I previously had and which didn't work with 4.1.x. > > > > Any more suggestions? > >Peter. > > > > At least you norrowed down, that was the idea. > I would suspect a new bug, so post to the radeon mailing list. Doing the git > bisect first will make it easier for them so they'll be more willing to help. I > would try booting without those radeon paremeters first. > > You could try the proprietary driver but the one in the portage tree will not > build with a kernel >3.18.19 but if you search b.g.o there are patches to make > it build. Or you could try my ebuild but I'm not sure that it will build > either since I'm using 3.18.20 now: > > https://github.com/fernando-rodriguez/portage-overlay/tree/master/x11-drivers/ati-drivers And you should still try suggestion #2 because it's very likely to only affect one specific configuration. -- Fernando Rodriguez
Re: [gentoo-user] Problems booting vanilla kernel 4.1.x
On Sunday, August 30, 2015 10:51:57 PM Peter Weilbacher wrote: > Hi Fernando, > > On Sun, 30 Aug 2015, Fernando Rodriguez wrote: > > > 1. Add loglevel=7 to your kernel parameters and see what it prints before it > > hangs. > > That helped, it showed me something about drm, so... > > > 3. From your kernel parameters I assume you're using the radeon free driver > > right? If that's the case disable it (don't compile it in or just delete the > > module) and try to boot wiith a framebuffer. > > ... this was a good suggestion. Switching off DRM/Radeon gets me a > kernel that boots. However, with that config I cannot run X (which then > complains about missing kernel mode switching). If I follow > wiki.gentoo.org/wiki/Xorg/Guide#Kernel_modesetting I again arrive at the > kernel settings that I previously had and which didn't work with 4.1.x. > > Any more suggestions? >Peter. > At least you norrowed down, that was the idea. I would suspect a new bug, so post to the radeon mailing list. Doing the git bisect first will make it easier for them so they'll be more willing to help. I would try booting without those radeon paremeters first. You could try the proprietary driver but the one in the portage tree will not build with a kernel >3.18.19 but if you search b.g.o there are patches to make it build. Or you could try my ebuild but I'm not sure that it will build either since I'm using 3.18.20 now: https://github.com/fernando-rodriguez/portage-overlay/tree/master/x11-drivers/ati-drivers -- Fernando Rodriguez
Re: [gentoo-user] Problems booting vanilla kernel 4.1.x
Hi Fernando, On Sun, 30 Aug 2015, Fernando Rodriguez wrote: > 1. Add loglevel=7 to your kernel parameters and see what it prints before it > hangs. That helped, it showed me something about drm, so... > 3. From your kernel parameters I assume you're using the radeon free driver > right? If that's the case disable it (don't compile it in or just delete the > module) and try to boot wiith a framebuffer. ... this was a good suggestion. Switching off DRM/Radeon gets me a kernel that boots. However, with that config I cannot run X (which then complains about missing kernel mode switching). If I follow wiki.gentoo.org/wiki/Xorg/Guide#Kernel_modesetting I again arrive at the kernel settings that I previously had and which didn't work with 4.1.x. Any more suggestions? Peter.
Re: [gentoo-user] Problems booting vanilla kernel 4.1.x
On Tuesday, August 25, 2015 6:40:01 PM Peter Weilbacher wrote:
> Hi Alexander,
>
> On Sun, 23 Aug 2015, Alexander Kapshuk wrote:
>
> > On Sun, Aug 23, 2015 at 4:08 PM, Peter Weilbacher
wrote:
> > >
> > > after successfully using kernel 4.0.5 (vanilla-sources) for a while, I
> > > upgraded to 4.1.5 last week and 4.1.6 today. I cannot boot either of
> > > them. On the screen I see
> > >
> > >Decompressing Linux... Parsing ELF... done.
> > >Booting the kernel.
> > >
> > > as the last thing, then it just sits there.
> >
> > I am running vanilla-sources 4.1.6, and so far I have not had any
> > trouble booting it.
> >
> > Are you able to boot some of your previous kernels? If so, what does
> > your '/boot/grub/grub.cfg' look like?
> > What is the output of 'cat /etc/fstab' and 'ls -1 /boot'?
>
> I can still boot 4.0.5 fine, with the same setup. I use lilo, and I
> checked that I changed the two/four digits correctly in /etc/lilo.conf.
>
> By chance I left the boot sit there for more than the typical minute,
> and got multiple messages like
>
> INFO: rcu_sched self-detected stall on CPU { 3} (t=6 jiffies g=-256
c=-257 q=193)
> rcu_sched kthread starved for 50027 jiffies!
>
> right after the above "Booting the kernel." line.
>
> Do I need to activate a different kind of clocking or a CPU feature in
> 4.1.x?
>
>Peter.
>
Here's how I would go about it:
1. Add loglevel=7 to your kernel parameters and see what it prints before it
hangs.
2. Change your scheduler settings (ie. if you're using the preemptive
scheduler or voluntary premption scheduler switch to the regular one) and try
again.
3. From your kernel parameters I assume you're using the radeon free driver
right? If that's the case disable it (don't compile it in or just delete the
module) and try to boot wiith a framebuffer. If you're using the proprietary
driver it has problem with preemptive kernels, with the 3.18.x series it
started logging a lot of errors which I assume where warnings of some change
yet to come.
4. If all else fails clone the kernel repo (be prepared to download a 2GB
repo) and do a git bisect (google it) between the last kernel that worked and
the first that didn't. That will eventually give you the exact commit that
broke it. From there you can post on the mailing list for the relevant
subsystem or you could try emailing the dev that commited it.
--
Fernando Rodriguez
Re: [gentoo-user] Problems booting vanilla kernel 4.1.x
On Sat, 29 Aug 2015, Alexander Kapshuk wrote: > You probably did look into this yourself, but did you double-check > your /etc/lilo.conf? Is everything fine there? At least it's identical between 4.0.5 and 4.1.6: image=/boot/kernel-genkernel-x86_64-4.0.5 label=Linux405 read-only # read-only for checking root=/dev/ram0 append="init=/linuxrc keymap=de ramdisk=8192 real_root=/dev/sda6 splash=verbose,theme:default console=tty1 quiet radeon.modeset=1 video=radeon:mtrr:3,ywrap,1680x1050-32@60 ahci.marvell_enable=0" initrd=/boot/initramfs-genkernel-x86_64-4.0.5 Don't ask me where all those options came from, they grew with time... > Here are my RCU kernel config options. What do yours look like? > % uname -r > 4.1.6-vanilla > % grep RCU .config > # RCU Subsystem > CONFIG_TREE_RCU=y > CONFIG_SRCU=y > # CONFIG_TASKS_RCU is not set > CONFIG_RCU_STALL_COMMON=y > CONFIG_RCU_FANOUT=32 > CONFIG_RCU_FANOUT_LEAF=16 > # CONFIG_RCU_FANOUT_EXACT is not set > # CONFIG_RCU_FAST_NO_HZ is not set > # CONFIG_TREE_RCU_TRACE is not set > CONFIG_RCU_KTHREAD_PRIO=0 > # CONFIG_RCU_NOCB_CPU is not set > # CONFIG_RCU_EXPEDITE_BOOT is not set > # RCU Debugging > # CONFIG_PROVE_RCU is not set > # CONFIG_SPARSE_RCU_POINTER is not set > # CONFIG_RCU_TORTURE_TEST is not set > CONFIG_RCU_CPU_STALL_TIMEOUT=21 > # CONFIG_RCU_CPU_STALL_INFO is not set > # CONFIG_RCU_TRACE is not set Thanks. The only difference to my config there is that I have CONFIG_RCU_FANOUT=64 and CONFIG_RCU_CPU_STALL_TIMEOUT=60 (don't ask me where the values come from, I don't remember ever setting them different from the default). But since that is all the same between 4.0.5 and 4.1.6, I don't think it has anything to do with my problem. Could the RCU message just be telling me that since the machine doesn't properly boot, it doesn't have anything to do? Cheers, Peter.
Re: [gentoo-user] Problems booting vanilla kernel 4.1.x
On Sat, Aug 29, 2015 at 3:09 PM, Peter Weilbacher
wrote:
> On Tue, 25 Aug 2015, Alexander Kapshuk wrote:
>
>> I've never experienced this particular kernel trouble myself, so I'm
>> not sure if my input would be of much help.
>> Here's what the kernel documentation has to say about this kind of issue:
>>
>> /usr/src/linux/Documentation/RCU/stallwarn.txt:29,33
> [...]
>> Have a look for possibly stack traces in these log files:
>> /var/log/{messages,dmesg}.
>>
>> Hopefully, someone else with more kernel debugging experience will
>> have something more substantial to say about this.
>
> Thanks for the reply, Alex. I had googled for those messages, too, and
> had found that RCU info. Unfortunately, I have no idea what to do with
> it, since it stops right at the booting stage, right before init starts,
> so before I can do anything interactive.
>
> I have posted a message to the LKML, maybe someone there has a hint.
> (The machine is old and rarely used, but I would still like to run the
> newest software because it is connected to the net.)
>
>Peter.
>
Hope you do get this sorted.
You probably did look into this yourself, but did you double-check
your /etc/lilo.conf? Is everything fine there?
Here are my RCU kernel config options. What do yours look like?
% uname -r
4.1.6-vanilla
% grep RCU .config
# RCU Subsystem
CONFIG_TREE_RCU=y
CONFIG_SRCU=y
# CONFIG_TASKS_RCU is not set
CONFIG_RCU_STALL_COMMON=y
CONFIG_RCU_FANOUT=32
CONFIG_RCU_FANOUT_LEAF=16
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_RCU_FAST_NO_HZ is not set
# CONFIG_TREE_RCU_TRACE is not set
CONFIG_RCU_KTHREAD_PRIO=0
# CONFIG_RCU_NOCB_CPU is not set
# CONFIG_RCU_EXPEDITE_BOOT is not set
# RCU Debugging
# CONFIG_PROVE_RCU is not set
# CONFIG_SPARSE_RCU_POINTER is not set
# CONFIG_RCU_TORTURE_TEST is not set
CONFIG_RCU_CPU_STALL_TIMEOUT=21
# CONFIG_RCU_CPU_STALL_INFO is not set
# CONFIG_RCU_TRACE is not set
Re: [gentoo-user] Problems booting vanilla kernel 4.1.x
On Tue, 25 Aug 2015, Alexander Kapshuk wrote:
> I've never experienced this particular kernel trouble myself, so I'm
> not sure if my input would be of much help.
> Here's what the kernel documentation has to say about this kind of issue:
>
> /usr/src/linux/Documentation/RCU/stallwarn.txt:29,33
[...]
> Have a look for possibly stack traces in these log files:
> /var/log/{messages,dmesg}.
>
> Hopefully, someone else with more kernel debugging experience will
> have something more substantial to say about this.
Thanks for the reply, Alex. I had googled for those messages, too, and
had found that RCU info. Unfortunately, I have no idea what to do with
it, since it stops right at the booting stage, right before init starts,
so before I can do anything interactive.
I have posted a message to the LKML, maybe someone there has a hint.
(The machine is old and rarely used, but I would still like to run the
newest software because it is connected to the net.)
Peter.
Re: [gentoo-user] Problems booting vanilla kernel 4.1.x
On Tue, Aug 25, 2015 at 7:40 PM, Peter Weilbacher
wrote:
> Hi Alexander,
>
> On Sun, 23 Aug 2015, Alexander Kapshuk wrote:
>
>> On Sun, Aug 23, 2015 at 4:08 PM, Peter Weilbacher
>> wrote:
>> >
>> > after successfully using kernel 4.0.5 (vanilla-sources) for a while, I
>> > upgraded to 4.1.5 last week and 4.1.6 today. I cannot boot either of
>> > them. On the screen I see
>> >
>> >Decompressing Linux... Parsing ELF... done.
>> >Booting the kernel.
>> >
>> > as the last thing, then it just sits there.
>>
>> I am running vanilla-sources 4.1.6, and so far I have not had any
>> trouble booting it.
>>
>> Are you able to boot some of your previous kernels? If so, what does
>> your '/boot/grub/grub.cfg' look like?
>> What is the output of 'cat /etc/fstab' and 'ls -1 /boot'?
>
> I can still boot 4.0.5 fine, with the same setup. I use lilo, and I
> checked that I changed the two/four digits correctly in /etc/lilo.conf.
>
> By chance I left the boot sit there for more than the typical minute,
> and got multiple messages like
>
> INFO: rcu_sched self-detected stall on CPU { 3} (t=6 jiffies g=-256
> c=-257 q=193)
> rcu_sched kthread starved for 50027 jiffies!
>
> right after the above "Booting the kernel." line.
>
> Do I need to activate a different kind of clocking or a CPU feature in
> 4.1.x?
>
>Peter.
>
I've never experienced this particular kernel trouble myself, so I'm
not sure if my input would be of much help.
Here's what the kernel documentation has to say about this kind of issue:
/usr/src/linux/Documentation/RCU/stallwarn.txt:29,33
CONFIG_RCU_CPU_STALL_INFO
This kernel configuration parameter causes the stall warning to
print out additional per-CPU diagnostic information, including
information on scheduling-clock ticks and RCU's idle-CPU tracking.
/usr/src/linux/Documentation/RCU/stallwarn.txt:104,109
If the CONFIG_RCU_CPU_STALL_INFO kernel configuration parameter is set,
more information is printed with the stall-warning message, for example:
INFO: rcu_preempt detected stall on CPU
0: (63959 ticks this GP) idle=241/3fff/0 softirq=82/543
(t=65000 jiffies)
/usr/src/linux/Documentation/RCU/stallwarn.txt:240,250
To diagnose the cause of the stall, inspect the stack traces.
The offending function will usually be near the top of the stack.
If you have a series of stall warnings from a single extended stall,
comparing the stack traces can often help determine where the stall
is occurring, which will usually be in the function nearest the top of
that portion of the stack which remains the same from trace to trace.
If you can reliably trigger the stall, ftrace can be quite helpful.
RCU bugs can often be debugged with the help of CONFIG_RCU_TRACE
and with RCU's event tracing. For information on RCU's event tracing,
see include/trace/events/rcu.h.
Have a look for possibly stack traces in these log files:
/var/log/{messages,dmesg}.
Hopefully, someone else with more kernel debugging experience will
have something more substantial to say about this.
Re: [gentoo-user] Problems booting vanilla kernel 4.1.x
Hi Alexander,
On Sun, 23 Aug 2015, Alexander Kapshuk wrote:
> On Sun, Aug 23, 2015 at 4:08 PM, Peter Weilbacher
> wrote:
> >
> > after successfully using kernel 4.0.5 (vanilla-sources) for a while, I
> > upgraded to 4.1.5 last week and 4.1.6 today. I cannot boot either of
> > them. On the screen I see
> >
> >Decompressing Linux... Parsing ELF... done.
> >Booting the kernel.
> >
> > as the last thing, then it just sits there.
>
> I am running vanilla-sources 4.1.6, and so far I have not had any
> trouble booting it.
>
> Are you able to boot some of your previous kernels? If so, what does
> your '/boot/grub/grub.cfg' look like?
> What is the output of 'cat /etc/fstab' and 'ls -1 /boot'?
I can still boot 4.0.5 fine, with the same setup. I use lilo, and I
checked that I changed the two/four digits correctly in /etc/lilo.conf.
By chance I left the boot sit there for more than the typical minute,
and got multiple messages like
INFO: rcu_sched self-detected stall on CPU { 3} (t=6 jiffies g=-256
c=-257 q=193)
rcu_sched kthread starved for 50027 jiffies!
right after the above "Booting the kernel." line.
Do I need to activate a different kind of clocking or a CPU feature in
4.1.x?
Peter.
Re: [gentoo-user] Problems booting vanilla kernel 4.1.x
On Sun, Aug 23, 2015 at 4:08 PM, Peter Weilbacher wrote: > Dear all, > > after successfully using kernel 4.0.5 (vanilla-sources) for a while, I > upgraded to 4.1.5 last week and 4.1.6 today. I cannot boot either of > them. On the screen I see > >Decompressing Linux... Parsing ELF... done. >Booting the kernel. > > as the last thing, then it just sits there. > > To upgrade I copy the previously used .config to the new kernel > directory and run genkernel with --no-clean and --menuconfig so that I > get the same config as before -- unless I change something, which in > this case I didn't. (This has worked very nicely since 3.1.x or so). > > Does that ring a bell with someone? >Peter. > I am running vanilla-sources 4.1.6, and so far I have not had any trouble booting it. Are you able to boot some of your previous kernels? If so, what does your '/boot/grub/grub.cfg' look like? What is the output of 'cat /etc/fstab' and 'ls -1 /boot'? If you are not able to boot any of your kernels, if you could get a hold of a Rescue CD or something like that and run the command lines above, that would be helpful.
[gentoo-user] Problems booting vanilla kernel 4.1.x
Dear all, after successfully using kernel 4.0.5 (vanilla-sources) for a while, I upgraded to 4.1.5 last week and 4.1.6 today. I cannot boot either of them. On the screen I see Decompressing Linux... Parsing ELF... done. Booting the kernel. as the last thing, then it just sits there. To upgrade I copy the previously used .config to the new kernel directory and run genkernel with --no-clean and --menuconfig so that I get the same config as before -- unless I change something, which in this case I didn't. (This has worked very nicely since 3.1.x or so). Does that ring a bell with someone? Peter.
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On Thursday 29 July 2010 12:39:46 I wrote: > On Wednesday 28 July 2010 19:14:05 Bill Longman wrote: > > In the Device Drivers section, (this is for 2.6.34!), turn OFF the > > deprecated ATA/ATAPI/MFM/RLL support. That corresponds to > > CONFIG_IDE in your .config. Then, turn ON, Serial ATA and Parallel > > ATA drivers which corresponds to CONFIG_ATA in your .config. Then, > > under Serial ATA, you'll need to turn on ATA SFF and then Intel > > ESB, ICH, PIIX3, PIIX4 PATA/SATA support. > > But bear in mind that setting these does not produce a bootable > kernel on my P4 box, as I've said in another thread, so it's > possible that making the suggested changes will introduce more fog > rather than dispelling it. I'm not sure how likely it is though. For the record, this is now fixed. Eventually (this morning) I found a chipset option buried in the kernel config that I'd missed. The IDE disk is now /dev/sda and I can forget about /dev/hda and friends altogether. -- Rgds Peter. Linux Counter 5290, 1994-04-23.
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On Wednesday 28 July 2010 19:14:05 Bill Longman wrote: > In the Device Drivers section, (this is for 2.6.34!), turn OFF the > deprecated ATA/ATAPI/MFM/RLL support. That corresponds to CONFIG_IDE > in your .config. Then, turn ON, Serial ATA and Parallel ATA drivers > which corresponds to CONFIG_ATA in your .config. Then, under Serial > ATA, you'll need to turn on ATA SFF and then Intel ESB, ICH, PIIX3, > PIIX4 PATA/SATA support. But bear in mind that setting these does not produce a bootable kernel on my P4 box, as I've said in another thread, so it's possible that making the suggested changes will introduce more fog rather than dispelling it. I'm not sure how likely it is though. -- Rgds Peter. Linux Counter 5290, 1994-04-23.
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On 07/28/2010 11:54 AM, Mick wrote: > On Wednesday 28 July 2010 17:35:44 KH wrote: >> Am 28.07.2010 17:30, schrieb Bill Longman: >>> On 07/28/2010 08:18 AM, KH wrote: Hi Mick, but typing ls /dev/hd* or ls /dev/sd* should show up something. Shouldn't it? df -h shows /dev/hda3 is mounted on / For me this is strange. >>> >>> How is /dev mounted right now? What does "udevadm --version" tell you? >> >> udev is 151 and baselayout is 1.12.13 > > Yes this is indeed strange ... short of having some strange access rights or > umask in your fstab ... is it the same when you ls as root user? Are there any red flags in dmesg?
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On Wednesday 28 July 2010 17:35:44 KH wrote: > Am 28.07.2010 17:30, schrieb Bill Longman: > > On 07/28/2010 08:18 AM, KH wrote: > >> Hi Mick, > >> > >> but typing ls /dev/hd* or ls /dev/sd* should show up something. > >> Shouldn't it? df -h shows /dev/hda3 is mounted on / > >> For me this is strange. > > > > How is /dev mounted right now? What does "udevadm --version" tell you? > > udev is 151 and baselayout is 1.12.13 Yes this is indeed strange ... short of having some strange access rights or umask in your fstab ... is it the same when you ls as root user? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On 07/28/2010 09:37 AM, KH wrote: > Am 28.07.2010 17:27, schrieb Bill Longman: >> On 07/28/2010 07:56 AM, KH wrote: >>> Am 28.07.2010 15:45, schrieb Bill Longman: Konstantin, please post what your kernel has for IDE support. If you have /proc/config.gz, then please post the results from "zgrep IDE /proc/config.gz" so we can get an idea of why you have no /dev/hd* devices. We will also need to know what kind of disk controller your server really has. Are they IDE or SATA controllers? >>> >>> Hi Bill, >>> >>> Now I am running 2.6.30-r8 but 2.6.34-r1 is ready but not jet copied to >>> /boot. btw it is a p3 coppermine. >>> >>> This is the output from zgrep IDE /proc/config.gz . >>> >>> >>> CONFIG_HAVE_IDE=y >>> CONFIG_IDE=y >>> # Please see Documentation/ide/ide.txt for help/info on IDE drives >>> CONFIG_IDE_XFER_MODE=y >>> CONFIG_IDE_TIMINGS=y >>> CONFIG_IDE_ATAPI=y >>> # CONFIG_BLK_DEV_IDE_SATA is not set >>> CONFIG_IDE_GD=y >>> CONFIG_IDE_GD_ATA=y >>> CONFIG_IDE_GD_ATAPI=y >>> CONFIG_BLK_DEV_IDECD=y >>> CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y >>> # CONFIG_BLK_DEV_IDETAPE is not set >>> CONFIG_BLK_DEV_IDEACPI=y >>> # CONFIG_IDE_TASK_IOCTL is not set >>> CONFIG_IDE_PROC_FS=y >>> # IDE chipset support/bugfixes >>> CONFIG_IDE_GENERIC=y >>> # CONFIG_BLK_DEV_IDEPNP is not set >>> CONFIG_BLK_DEV_IDEDMA_SFF=y >>> # PCI IDE chipsets support >>> CONFIG_BLK_DEV_IDEPCI=y >>> CONFIG_IDEPCI_PCIBUS_ORDER=y >>> CONFIG_BLK_DEV_IDEDMA_PCI=y >>> CONFIG_BLK_DEV_IDEDMA=y >>> # CONFIG_VIDEO_DEV is not set >>> # CONFIG_VIDEO_MEDIA is not set >>> # CONFIG_VIDEO_OUTPUT_CONTROL is not set >>> # CONFIG_FB_TRIDENT is not set >>> # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set >> >> I would expect to see: >> >> CONFIG_BLK_DEV_PIIX=y >> >> in your configuration given that it's a Coppermine. You might want to >> add that in the 2.6.30 and the 2.6.34 kernels, although DEV_GENERIC >> should give you what you need, as you are probably using that right now. >> >> Use "make menuconfig" to configure the kernel. Make sure it's "<*>" not >> "" for the PIIX controller and then rebuild and install the kernel. >> >> Do you have "lspci" installed? The results from "lspci -v" would be very >> helpful right now. >> >>> I just tried /etc/init.de/udev resart . I am getting errors not to use >>> the script with baselayout-1 . The box is very slow now. Will reboot and >>> see what baselayout is on it. >> >> Yeah, don't worry about this right now. >> > > lspci: > > 00:00.0 Host bridge: Intel Corporation 82815 815 Chipset Host Bridge and > Memory Controller Hub (rev 02) > Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard > Flags: bus master, fast devsel, latency 0 > Memory at f800 (32-bit, prefetchable) [size=64M] > Capabilities: [88] Vendor Specific Information > Capabilities: [a0] AGP version 2.0 > Kernel driver in use: agpgart-intel > > 00:01.0 PCI bridge: Intel Corporation 82815 815 Chipset AGP Bridge (rev > 02) (prog-if 00 [Normal decode]) > Flags: bus master, 66MHz, fast devsel, latency 64 > Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 > Memory behind bridge: ee00-efef > Prefetchable memory behind bridge: eff0-f7ff > > 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 02) (prog-if > 00 [Normal decode]) > Flags: bus master, fast devsel, latency 0 > Bus: primary=00, secondary=02, subordinate=02, sec-latency=32 > I/O behind bridge: d000-dfff > Memory behind bridge: ed80-edff > > 00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 02) > Flags: bus master, medium devsel, latency 0 > > 00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 Controller > (rev 02) (prog-if 80 [Master]) > Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard > Flags: bus master, medium devsel, latency 0 > [virtual] Memory at 01f0 (32-bit, non-prefetchable) [size=8] > [virtual] Memory at 03f0 (type 3, non-prefetchable) [size=1] > [virtual] Memory at 0170 (32-bit, non-prefetchable) [size=8] > [virtual] Memory at 0370 (type 3, non-prefetchable) [size=1] > I/O ports at b800 [size=16] > Kernel driver in use: PIIX_IDE > > 00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 > (rev 02) (prog-if 00 [UHCI]) > Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard > Flags: bus master, medium devsel, latency 0, IRQ 12 > I/O ports at b400 [size=32] > Kernel driver in use: uhci_hcd > > 00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus Controller (rev 02) > Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard > Flags: medium devsel, IRQ 10 > I/O ports at e800 [size=16] > > 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 > (rev 02) (prog-if 00 [UHCI]) > Subsystem: ASUSTeK Comput
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
Am 28.07.2010 17:27, schrieb Bill Longman: > On 07/28/2010 07:56 AM, KH wrote: >> Am 28.07.2010 15:45, schrieb Bill Longman: >>> >>> Konstantin, please post what your kernel has for IDE support. If you >>> have /proc/config.gz, then please post the results from "zgrep IDE >>> /proc/config.gz" so we can get an idea of why you have no /dev/hd* >>> devices. We will also need to know what kind of disk controller your >>> server really has. Are they IDE or SATA controllers? >>> >> >> Hi Bill, >> >> Now I am running 2.6.30-r8 but 2.6.34-r1 is ready but not jet copied to >> /boot. btw it is a p3 coppermine. >> >> This is the output from zgrep IDE /proc/config.gz . >> >> >> CONFIG_HAVE_IDE=y >> CONFIG_IDE=y >> # Please see Documentation/ide/ide.txt for help/info on IDE drives >> CONFIG_IDE_XFER_MODE=y >> CONFIG_IDE_TIMINGS=y >> CONFIG_IDE_ATAPI=y >> # CONFIG_BLK_DEV_IDE_SATA is not set >> CONFIG_IDE_GD=y >> CONFIG_IDE_GD_ATA=y >> CONFIG_IDE_GD_ATAPI=y >> CONFIG_BLK_DEV_IDECD=y >> CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y >> # CONFIG_BLK_DEV_IDETAPE is not set >> CONFIG_BLK_DEV_IDEACPI=y >> # CONFIG_IDE_TASK_IOCTL is not set >> CONFIG_IDE_PROC_FS=y >> # IDE chipset support/bugfixes >> CONFIG_IDE_GENERIC=y >> # CONFIG_BLK_DEV_IDEPNP is not set >> CONFIG_BLK_DEV_IDEDMA_SFF=y >> # PCI IDE chipsets support >> CONFIG_BLK_DEV_IDEPCI=y >> CONFIG_IDEPCI_PCIBUS_ORDER=y >> CONFIG_BLK_DEV_IDEDMA_PCI=y >> CONFIG_BLK_DEV_IDEDMA=y >> # CONFIG_VIDEO_DEV is not set >> # CONFIG_VIDEO_MEDIA is not set >> # CONFIG_VIDEO_OUTPUT_CONTROL is not set >> # CONFIG_FB_TRIDENT is not set >> # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set > > I would expect to see: > > CONFIG_BLK_DEV_PIIX=y > > in your configuration given that it's a Coppermine. You might want to > add that in the 2.6.30 and the 2.6.34 kernels, although DEV_GENERIC > should give you what you need, as you are probably using that right now. > > Use "make menuconfig" to configure the kernel. Make sure it's "<*>" not > "" for the PIIX controller and then rebuild and install the kernel. > > Do you have "lspci" installed? The results from "lspci -v" would be very > helpful right now. > >> I just tried /etc/init.de/udev resart . I am getting errors not to use >> the script with baselayout-1 . The box is very slow now. Will reboot and >> see what baselayout is on it. > > Yeah, don't worry about this right now. > lspci: 00:00.0 Host bridge: Intel Corporation 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 02) Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard Flags: bus master, fast devsel, latency 0 Memory at f800 (32-bit, prefetchable) [size=64M] Capabilities: [88] Vendor Specific Information Capabilities: [a0] AGP version 2.0 Kernel driver in use: agpgart-intel 00:01.0 PCI bridge: Intel Corporation 82815 815 Chipset AGP Bridge (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, 66MHz, fast devsel, latency 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: ee00-efef Prefetchable memory behind bridge: eff0-f7ff 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=32 I/O behind bridge: d000-dfff Memory behind bridge: ed80-edff 00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 02) Flags: bus master, medium devsel, latency 0 00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 Controller (rev 02) (prog-if 80 [Master]) Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard Flags: bus master, medium devsel, latency 0 [virtual] Memory at 01f0 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 03f0 (type 3, non-prefetchable) [size=1] [virtual] Memory at 0170 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 0370 (type 3, non-prefetchable) [size=1] I/O ports at b800 [size=16] Kernel driver in use: PIIX_IDE 00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 02) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard Flags: bus master, medium devsel, latency 0, IRQ 12 I/O ports at b400 [size=32] Kernel driver in use: uhci_hcd 00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus Controller (rev 02) Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard Flags: medium devsel, IRQ 10 I/O ports at e800 [size=16] 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 02) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard Flags: bus master, medium devsel, latency 0, IRQ 6 I/O ports at b000 [size=32] Kernel driver in use: uhci_hcd 01:00.0 VGA compatible controller: nVidia Corp
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
Am 28.07.2010 17:30, schrieb Bill Longman: > On 07/28/2010 08:18 AM, KH wrote: >> >> Hi Mick, >> >> but typing ls /dev/hd* or ls /dev/sd* should show up something. >> Shouldn't it? df -h shows /dev/hda3 is mounted on / >> For me this is strange. > > How is /dev mounted right now? What does "udevadm --version" tell you? > udev is 151 and baselayout is 1.12.13 Regards FilesystemSize Used Avail Use% Mounted on /dev/hda3 15G 8.2G 5.8G 59% / udev 10M 36K 10M 1% /dev tmpfs 2.5G 0 2.5G 0% /var/tmp/portage shm 187M 0 187M 0% /dev/shm
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On 07/28/2010 08:18 AM, KH wrote: > Am 28.07.2010 16:04, schrieb Mick: >> On 28 July 2010 14:53, Bill Longman wrote: >>> On 07/28/2010 06:42 AM, Mick wrote: On 28 July 2010 09:50, KH wrote: > I installed grub by connecting the hdd to my workstation. This did not > change anything. > Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc > boots fine now. I can use it but ... There is no /dev/hd* . Running > mount /boot I get the answer /dev/hda1 does not exist. Also there is no > /dev/sd* > > Any ideas? KH, if you have changed the kernel to use libATA (i.e. the newer SATA/PATA options) then you need to update your fstab from /dev/hdaX to /dev/sdaX and change your grub.conf accordingly. >>> >>> But he doesn't even have those devices, so this will not do him any good >>> until we know how the kernel is configured (or not) and get the devices >>> back. >> >> I am not sure that he does not have those devices ... I don't know if >> the error message is returned from grub or from the OS. >> >> It could be that the kernel stanza is wrongly pointing to /dev/hda, >> and, or fstab is not correct. > > Hi Mick, > > but typing ls /dev/hd* or ls /dev/sd* should show up something. > Shouldn't it? df -h shows /dev/hda3 is mounted on / > For me this is strange. How is /dev mounted right now? What does "udevadm --version" tell you?
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On 07/28/2010 07:56 AM, KH wrote: > Am 28.07.2010 15:45, schrieb Bill Longman: >> On 07/28/2010 01:50 AM, KH wrote: >>> >>> Hi, >>> >>> I installed grub by connecting the hdd to my workstation. This did not >>> change anything. >>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc >>> boots fine now. I can use it but ... There is no /dev/hd* . Running >>> mount /boot I get the answer /dev/hda1 does not exist. Also there is no >>> /dev/sd* >>> >>> Any ideas? >> >> Konstantin, please post what your kernel has for IDE support. If you >> have /proc/config.gz, then please post the results from "zgrep IDE >> /proc/config.gz" so we can get an idea of why you have no /dev/hd* >> devices. We will also need to know what kind of disk controller your >> server really has. Are they IDE or SATA controllers? >> > > Hi Bill, > > Now I am running 2.6.30-r8 but 2.6.34-r1 is ready but not jet copied to > /boot. btw it is a p3 coppermine. > > This is the output from zgrep IDE /proc/config.gz . > > > CONFIG_HAVE_IDE=y > CONFIG_IDE=y > # Please see Documentation/ide/ide.txt for help/info on IDE drives > CONFIG_IDE_XFER_MODE=y > CONFIG_IDE_TIMINGS=y > CONFIG_IDE_ATAPI=y > # CONFIG_BLK_DEV_IDE_SATA is not set > CONFIG_IDE_GD=y > CONFIG_IDE_GD_ATA=y > CONFIG_IDE_GD_ATAPI=y > CONFIG_BLK_DEV_IDECD=y > CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y > # CONFIG_BLK_DEV_IDETAPE is not set > CONFIG_BLK_DEV_IDEACPI=y > # CONFIG_IDE_TASK_IOCTL is not set > CONFIG_IDE_PROC_FS=y > # IDE chipset support/bugfixes > CONFIG_IDE_GENERIC=y > # CONFIG_BLK_DEV_IDEPNP is not set > CONFIG_BLK_DEV_IDEDMA_SFF=y > # PCI IDE chipsets support > CONFIG_BLK_DEV_IDEPCI=y > CONFIG_IDEPCI_PCIBUS_ORDER=y > CONFIG_BLK_DEV_IDEDMA_PCI=y > CONFIG_BLK_DEV_IDEDMA=y > # CONFIG_VIDEO_DEV is not set > # CONFIG_VIDEO_MEDIA is not set > # CONFIG_VIDEO_OUTPUT_CONTROL is not set > # CONFIG_FB_TRIDENT is not set > # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set I would expect to see: CONFIG_BLK_DEV_PIIX=y in your configuration given that it's a Coppermine. You might want to add that in the 2.6.30 and the 2.6.34 kernels, although DEV_GENERIC should give you what you need, as you are probably using that right now. Use "make menuconfig" to configure the kernel. Make sure it's "<*>" not "" for the PIIX controller and then rebuild and install the kernel. Do you have "lspci" installed? The results from "lspci -v" would be very helpful right now. > I just tried /etc/init.de/udev resart . I am getting errors not to use > the script with baselayout-1 . The box is very slow now. Will reboot and > see what baselayout is on it. Yeah, don't worry about this right now.
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
Am 28.07.2010 15:53, schrieb Bill Longman: > On 07/28/2010 06:42 AM, Mick wrote: >> On 28 July 2010 09:50, KH wrote: >> >>> I installed grub by connecting the hdd to my workstation. This did not >>> change anything. >>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc >>> boots fine now. I can use it but ... There is no /dev/hd* . Running >>> mount /boot I get the answer /dev/hda1 does not exist. Also there is no >>> /dev/sd* >>> >>> Any ideas? >> >> KH, if you have changed the kernel to use libATA (i.e. the newer >> SATA/PATA options) then you need to update your fstab from /dev/hdaX >> to /dev/sdaX and change your grub.conf accordingly. > > But he doesn't even have those devices, so this will not do him any good > until we know how the kernel is configured (or not) and get the devices > back. > > Konstantin, I'm assuming, from your original post, that you have not > changed your kernel in any way over the last few months. You said that > it was running fine for eight months but now after rebooting, you're in > trouble. Are you *sure* you haven't made any changes to the kernel? I'm > also assuming that you know that the kernel drivers for your disk > controllers should not be built as modules but built into the kernel so > that you don't need to go through creating an initramfs and hoping for > your devices to get populated. > Hi, I tried booting 2.6.28 / 2.6.29 / 2.6.30 . The 30 series has not been running on the box befor. Anyway the result is the same no matter which kernel I am booting. I use make oldconfig for uping the kernel. kh
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
Am 28.07.2010 16:04, schrieb Mick: > On 28 July 2010 14:53, Bill Longman wrote: >> On 07/28/2010 06:42 AM, Mick wrote: >>> On 28 July 2010 09:50, KH wrote: >>> I installed grub by connecting the hdd to my workstation. This did not change anything. Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc boots fine now. I can use it but ... There is no /dev/hd* . Running mount /boot I get the answer /dev/hda1 does not exist. Also there is no /dev/sd* Any ideas? >>> >>> KH, if you have changed the kernel to use libATA (i.e. the newer >>> SATA/PATA options) then you need to update your fstab from /dev/hdaX >>> to /dev/sdaX and change your grub.conf accordingly. >> >> But he doesn't even have those devices, so this will not do him any good >> until we know how the kernel is configured (or not) and get the devices >> back. > > I am not sure that he does not have those devices ... I don't know if > the error message is returned from grub or from the OS. > > It could be that the kernel stanza is wrongly pointing to /dev/hda, > and, or fstab is not correct. Hi Mick, but typing ls /dev/hd* or ls /dev/sd* should show up something. Shouldn't it? df -h shows /dev/hda3 is mounted on / For me this is strange. kh
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On 28 July 2010 15:27, Bill Longman wrote: > On 07/28/2010 07:04 AM, Mick wrote: >> On 28 July 2010 14:53, Bill Longman wrote: >>> On 07/28/2010 06:42 AM, Mick wrote: On 28 July 2010 09:50, KH wrote: > I installed grub by connecting the hdd to my workstation. This did not > change anything. > Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc > boots fine now. I can use it but ... There is no /dev/hd* . Running > mount /boot I get the answer /dev/hda1 does not exist. Also there is no > /dev/sd* > > Any ideas? KH, if you have changed the kernel to use libATA (i.e. the newer SATA/PATA options) then you need to update your fstab from /dev/hdaX to /dev/sdaX and change your grub.conf accordingly. >>> >>> But he doesn't even have those devices, so this will not do him any good >>> until we know how the kernel is configured (or not) and get the devices >>> back. >> >> I am not sure that he does not have those devices ... I don't know if >> the error message is returned from grub or from the OS. >> >> It could be that the kernel stanza is wrongly pointing to /dev/hda, >> and, or fstab is not correct. > > He says the "pc boots fine now" and he "can use it" and he goes on to > say that he has "no /dev/hd*" or "/dev/sd*" devices, so I have to > believe he's got a running system. Hmm ... he'll have to be able to hang his OS off some fs or other if it is indeed working. Unless he's running some clever ramdisk, then I would not reach the conclusion that he has a working OS. > Not having any /dev/hd* files would > support the error trying to mount /boot. Trying to fix /etc/fstab first > is not the way to attack his problem given the information we have now. Perhaps he passed the correct path to his grub and the boot sequence fails when it tries to find the devices listed in fstab, so the OS never completes booting. Either way, hopefully the OP will shed some light to this rather than us assuming more or less what might actually be the case. -- Regards, Mick
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
Am 28.07.2010 15:45, schrieb Bill Longman: > On 07/28/2010 01:50 AM, KH wrote: >> >> Hi, >> >> I installed grub by connecting the hdd to my workstation. This did not >> change anything. >> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc >> boots fine now. I can use it but ... There is no /dev/hd* . Running >> mount /boot I get the answer /dev/hda1 does not exist. Also there is no >> /dev/sd* >> >> Any ideas? > > Konstantin, please post what your kernel has for IDE support. If you > have /proc/config.gz, then please post the results from "zgrep IDE > /proc/config.gz" so we can get an idea of why you have no /dev/hd* > devices. We will also need to know what kind of disk controller your > server really has. Are they IDE or SATA controllers? > Hi Bill, Now I am running 2.6.30-r8 but 2.6.34-r1 is ready but not jet copied to /boot. btw it is a p3 coppermine. This is the output from zgrep IDE /proc/config.gz . CONFIG_HAVE_IDE=y CONFIG_IDE=y # Please see Documentation/ide/ide.txt for help/info on IDE drives CONFIG_IDE_XFER_MODE=y CONFIG_IDE_TIMINGS=y CONFIG_IDE_ATAPI=y # CONFIG_BLK_DEV_IDE_SATA is not set CONFIG_IDE_GD=y CONFIG_IDE_GD_ATA=y CONFIG_IDE_GD_ATAPI=y CONFIG_BLK_DEV_IDECD=y CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y # CONFIG_BLK_DEV_IDETAPE is not set CONFIG_BLK_DEV_IDEACPI=y # CONFIG_IDE_TASK_IOCTL is not set CONFIG_IDE_PROC_FS=y # IDE chipset support/bugfixes CONFIG_IDE_GENERIC=y # CONFIG_BLK_DEV_IDEPNP is not set CONFIG_BLK_DEV_IDEDMA_SFF=y # PCI IDE chipsets support CONFIG_BLK_DEV_IDEPCI=y CONFIG_IDEPCI_PCIBUS_ORDER=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_BLK_DEV_IDEDMA=y # CONFIG_VIDEO_DEV is not set # CONFIG_VIDEO_MEDIA is not set # CONFIG_VIDEO_OUTPUT_CONTROL is not set # CONFIG_FB_TRIDENT is not set # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set I just tried /etc/init.de/udev resart . I am getting errors not to use the script with baselayout-1 . The box is very slow now. Will reboot and see what baselayout is on it. Regards kh
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On 07/28/2010 07:04 AM, Mick wrote: > On 28 July 2010 14:53, Bill Longman wrote: >> On 07/28/2010 06:42 AM, Mick wrote: >>> On 28 July 2010 09:50, KH wrote: >>> I installed grub by connecting the hdd to my workstation. This did not change anything. Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc boots fine now. I can use it but ... There is no /dev/hd* . Running mount /boot I get the answer /dev/hda1 does not exist. Also there is no /dev/sd* Any ideas? >>> >>> KH, if you have changed the kernel to use libATA (i.e. the newer >>> SATA/PATA options) then you need to update your fstab from /dev/hdaX >>> to /dev/sdaX and change your grub.conf accordingly. >> >> But he doesn't even have those devices, so this will not do him any good >> until we know how the kernel is configured (or not) and get the devices >> back. > > I am not sure that he does not have those devices ... I don't know if > the error message is returned from grub or from the OS. > > It could be that the kernel stanza is wrongly pointing to /dev/hda, > and, or fstab is not correct. He says the "pc boots fine now" and he "can use it" and he goes on to say that he has "no /dev/hd*" or "/dev/sd*" devices, so I have to believe he's got a running system. Not having any /dev/hd* files would support the error trying to mount /boot. Trying to fix /etc/fstab first is not the way to attack his problem given the information we have now.
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On 28 July 2010 14:53, Bill Longman wrote: > On 07/28/2010 06:42 AM, Mick wrote: >> On 28 July 2010 09:50, KH wrote: >> >>> I installed grub by connecting the hdd to my workstation. This did not >>> change anything. >>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc >>> boots fine now. I can use it but ... There is no /dev/hd* . Running >>> mount /boot I get the answer /dev/hda1 does not exist. Also there is no >>> /dev/sd* >>> >>> Any ideas? >> >> KH, if you have changed the kernel to use libATA (i.e. the newer >> SATA/PATA options) then you need to update your fstab from /dev/hdaX >> to /dev/sdaX and change your grub.conf accordingly. > > But he doesn't even have those devices, so this will not do him any good > until we know how the kernel is configured (or not) and get the devices > back. I am not sure that he does not have those devices ... I don't know if the error message is returned from grub or from the OS. It could be that the kernel stanza is wrongly pointing to /dev/hda, and, or fstab is not correct. -- Regards, Mick
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On 07/28/2010 06:42 AM, Mick wrote: > On 28 July 2010 09:50, KH wrote: > >> I installed grub by connecting the hdd to my workstation. This did not >> change anything. >> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc >> boots fine now. I can use it but ... There is no /dev/hd* . Running >> mount /boot I get the answer /dev/hda1 does not exist. Also there is no >> /dev/sd* >> >> Any ideas? > > KH, if you have changed the kernel to use libATA (i.e. the newer > SATA/PATA options) then you need to update your fstab from /dev/hdaX > to /dev/sdaX and change your grub.conf accordingly. But he doesn't even have those devices, so this will not do him any good until we know how the kernel is configured (or not) and get the devices back. Konstantin, I'm assuming, from your original post, that you have not changed your kernel in any way over the last few months. You said that it was running fine for eight months but now after rebooting, you're in trouble. Are you *sure* you haven't made any changes to the kernel? I'm also assuming that you know that the kernel drivers for your disk controllers should not be built as modules but built into the kernel so that you don't need to go through creating an initramfs and hoping for your devices to get populated.
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On 07/28/2010 01:50 AM, KH wrote: > Am 25.07.2010 15:57, schrieb Mick: >> On Sunday 25 July 2010 09:18:33 Dale wrote: >>> Alan McKinnon wrote: On Sunday 25 July 2010 06:57:43 KH wrote: >> You said you ran e2fsck and it was OK. What was the command? >> >> >> >> Normally with an e2fsck on a journalled fs, the app will replay the >> journal and make a few minor checks. This takes about 4 seconds, not >> the 40 minutes it takes to do a ful ext2 check. >> >> >> >> I think you might need to fsck without the journal. I know there's a >> way to do this but a cursory glance at the man page didn't reveal it. >> Maybe an ext user will chip in with the correct method > > Hi, > > I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3 > /dev/sde3 . Yes, it only took some seconds. It's been a long time since I used ext3 so some of this might be wrong. An fsck that takes a few seconds is using the journal, which might not uncover deeper corruption. You should try disabling the journal (I couldn't find the way to do that though), but this will also work: Boot of a LiveCD, mount your root partition somewhere using type "ext2" and fsck it. This will invalidate the journal but that's OK, it gets recreated on the next proper boot. Let the fsck finish - it will take a while on a large fs. When done, reboot as normal and see if the machine boots up properly. >>> >>> And I would stand guard to make sure housekeeping doesn't come around. >>> ;-) Cutting power during all this wold not be good. >> >> KH, I think that this may not be related to a fs error as such. >> >> Yes, pulling the plug may have caused fs corruption. However, more likely >> is >> that pulling the plug did not allow you to do something that you should have >> done after you finished upgrading to grub-0.97-r9. The latest installation >> of >> grub asks you to reinstall in the MBR and point its root to wherever your >> /boot is. GRUB's fs and its drivers may have changed and therefore the old >> boot loader code is looking for files that no longer exist. >> >> So you'll probably be alright again if you boot with a fresh systemrescue >> LiveCD and run grub and then root (hd) and setup (hd0) before you quit >> and >> reboot. >> >> If that doesn't work then you most likely have a fs problem. >> >> HTH. > > Hi, > > I installed grub by connecting the hdd to my workstation. This did not > change anything. > Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc > boots fine now. I can use it but ... There is no /dev/hd* . Running > mount /boot I get the answer /dev/hda1 does not exist. Also there is no > /dev/sd* > > Any ideas? Konstantin, please post what your kernel has for IDE support. If you have /proc/config.gz, then please post the results from "zgrep IDE /proc/config.gz" so we can get an idea of why you have no /dev/hd* devices. We will also need to know what kind of disk controller your server really has. Are they IDE or SATA controllers?
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On 28 July 2010 09:50, KH wrote: > I installed grub by connecting the hdd to my workstation. This did not > change anything. > Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc > boots fine now. I can use it but ... There is no /dev/hd* . Running > mount /boot I get the answer /dev/hda1 does not exist. Also there is no > /dev/sd* > > Any ideas? KH, if you have changed the kernel to use libATA (i.e. the newer SATA/PATA options) then you need to update your fstab from /dev/hdaX to /dev/sdaX and change your grub.conf accordingly. PS. When you install GRUB use tab completion to see what's available and make sure you install it in the correct drive/partition. PPS. Peter, I installed the kernel option for [*] ATA SFF support and corresponding chipset (ICH) for my P4 and it now boots fine. So I suggest that you use lshw to find which chipset you must activate under ATA SFF (unless you have one of the more modern <*> AHCI SATA support controllers like I have on my i7 Dell). -- Regards, Mick
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
Am 25.07.2010 15:57, schrieb Mick: > On Sunday 25 July 2010 09:18:33 Dale wrote: >> Alan McKinnon wrote: >>> On Sunday 25 July 2010 06:57:43 KH wrote: > You said you ran e2fsck and it was OK. What was the command? > > > > Normally with an e2fsck on a journalled fs, the app will replay the > journal and make a few minor checks. This takes about 4 seconds, not > the 40 minutes it takes to do a ful ext2 check. > > > > I think you might need to fsck without the journal. I know there's a > way to do this but a cursory glance at the man page didn't reveal it. > Maybe an ext user will chip in with the correct method Hi, I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3 /dev/sde3 . Yes, it only took some seconds. >>> >>> It's been a long time since I used ext3 so some of this might be wrong. >>> >>> An fsck that takes a few seconds is using the journal, which might not >>> uncover deeper corruption. You should try disabling the journal (I >>> couldn't find the way to do that though), but this will also work: >>> >>> Boot of a LiveCD, mount your root partition somewhere using type "ext2" >>> and fsck it. This will invalidate the journal but that's OK, it gets >>> recreated on the next proper boot. Let the fsck finish - it will take a >>> while on a large fs. >>> >>> When done, reboot as normal and see if the machine boots up properly. >> >> And I would stand guard to make sure housekeeping doesn't come around. >> ;-) Cutting power during all this wold not be good. > > KH, I think that this may not be related to a fs error as such. > > Yes, pulling the plug may have caused fs corruption. However, more likely is > that pulling the plug did not allow you to do something that you should have > done after you finished upgrading to grub-0.97-r9. The latest installation > of > grub asks you to reinstall in the MBR and point its root to wherever your > /boot is. GRUB's fs and its drivers may have changed and therefore the old > boot loader code is looking for files that no longer exist. > > So you'll probably be alright again if you boot with a fresh systemrescue > LiveCD and run grub and then root (hd) and setup (hd0) before you quit > and > reboot. > > If that doesn't work then you most likely have a fs problem. > > HTH. Hi, I installed grub by connecting the hdd to my workstation. This did not change anything. Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc boots fine now. I can use it but ... There is no /dev/hd* . Running mount /boot I get the answer /dev/hda1 does not exist. Also there is no /dev/sd* Any ideas? Regards kh
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On Monday 26 July 2010 21:46:40 Mick wrote: > On Monday 26 July 2010 19:04:16 Alex Schuster wrote: > > Isn't there also some other SCSI stuff (which does not get selected > > automatically), necessary to make the new ATA drivers actually > > work? > > You mean: > > Device Drivers ---> > Generic Driver Options ---> > <*> Serial ATA and Parallel ATA drivers ---> > [*] ATA SFF support > > Symbol: ATA [=y] > Prompt: Serial ATA and Parallel ATA drivers I did have that selected, of course. > I also have a P4 but I haven't yet switched off the deprecated > drivers. Will have a go later in the week and see what gives. I'll be interested to hear how you get on. -- Rgds Peter. Linux Counter 5290, 1994-04-23.
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On Monday 26 July 2010 19:04:16 Alex Schuster wrote: > Peter Humphrey writes: > > On Monday 26 July 2010 16:13:19 Mick wrote: > > > On 26 July 2010 15:11, Peter Humphrey > > > > > > wrote: > > > > So udev is wrong in saying CONFIG_IDE should not be set - on that > > > > old P4 box it has to be to get ICH4 drivers. > > > > > > Hmm, did you try ATA_PIIX, or PATA_MPIIX, or PATA_SCH? > > > > I've just tried it again now, to make sure, and the answer's "yes". I > > set all of those, and I tried adding PATA_OLDPIIX to see if it helped. > > It didn't, and neither did the others, so I'll have to go back to > > CONFIG_IDE. > > Isn't there also some other SCSI stuff (which does not get selected > automatically), necessary to make the new ATA drivers actually work? You mean: Device Drivers ---> Generic Driver Options ---> <*> Serial ATA and Parallel ATA drivers ---> [*] ATA SFF support Symbol: ATA [=y] Prompt: Serial ATA and Parallel ATA drivers I also have a P4 but I haven't yet switched off the deprecated drivers. Will have a go later in the week and see what gives. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
Peter Humphrey writes: > On Monday 26 July 2010 16:13:19 Mick wrote: > > On 26 July 2010 15:11, Peter Humphrey > > wrote: > > > So udev is wrong in saying CONFIG_IDE should not be set - on that > > > old P4 box it has to be to get ICH4 drivers. > > > > Hmm, did you try ATA_PIIX, or PATA_MPIIX, or PATA_SCH? > > I've just tried it again now, to make sure, and the answer's "yes". I > set all of those, and I tried adding PATA_OLDPIIX to see if it helped. > It didn't, and neither did the others, so I'll have to go back to > CONFIG_IDE. Isn't there also some other SCSI stuff (which does not get selected automatically), necessary to make the new ATA drivers actually work? Wonko
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On Monday 26 July 2010 16:13:19 Mick wrote: > On 26 July 2010 15:11, Peter Humphrey wrote: > > So udev is wrong in saying CONFIG_IDE should not be set - on that > > old P4 box it has to be to get ICH4 drivers. > > Hmm, did you try ATA_PIIX, or PATA_MPIIX, or PATA_SCH? I've just tried it again now, to make sure, and the answer's "yes". I set all of those, and I tried adding PATA_OLDPIIX to see if it helped. It didn't, and neither did the others, so I'll have to go back to CONFIG_IDE. > Also, make sure you enable BLK_DEV_SR, for some reason I could get a > box to boot without it. The box in question is an ancient PIII > Coppermine! Hmm. Not surprisingly, that didn't help either. Thanks anyway. -- Rgds Peter. Linux Counter 5290, 1994-04-23.
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On 26 July 2010 15:11, Peter Humphrey wrote: > On Monday 26 July 2010 12:02:56 Mick wrote: > >> Another gotcha is when you disable the deprecated CONFIG_IDE in the >> kernel and you don't update your grub.conf and /etc/fstab to rename >> /dev/hda's into /dev/sda's. > > Drifting off topic somewhat, when I upgraded udev on my firewall box last > week I was told I shouldn't have CONFIG_IDE set, so I recompiled the > kernel without it and lo! a kernel panic during boot. And yes, I had > changed hdas to sdas. > > So udev is wrong in saying CONFIG_IDE should not be set - on that old P4 > box it has to be to get ICH4 drivers. Hmm, did you try ATA_PIIX, or PATA_MPIIX, or PATA_SCH? Also, make sure you enable BLK_DEV_SR, for some reason I could get a box to boot without it. The box in question is an ancient PIII Coppermine! -- Regards, Mick
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
William Kenworthy wrote: Might be time for a new setup - amd athlon 2500+ are not so cool these days :) BillK Mine still works well. Just have to blow out the dust every month or so. Dale :-) :-)
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On Monday 26 July 2010 12:02:56 Mick wrote: > Another gotcha is when you disable the deprecated CONFIG_IDE in the > kernel and you don't update your grub.conf and /etc/fstab to rename > /dev/hda's into /dev/sda's. Drifting off topic somewhat, when I upgraded udev on my firewall box last week I was told I shouldn't have CONFIG_IDE set, so I recompiled the kernel without it and lo! a kernel panic during boot. And yes, I had changed hdas to sdas. So udev is wrong in saying CONFIG_IDE should not be set - on that old P4 box it has to be to get ICH4 drivers. -- Rgds Peter. Linux Counter 5290, 1994-04-23.
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On 26 July 2010 11:54, William Kenworthy wrote: > Fixed it - was grub after all - it renumbered my drives (0 and 1 > swapped :( > > Complicated because this was one of the early sata boards with a fake > raid chip to handle the sata while the old IDE drives were on the normal > bus. > > Further complicated by the bios and raidchip changing drive assignments > depending on which drive/cd/floppy you booted from (i.e., what grub sees > as the drive numbers changes when the real OS is booted). I forgot what > hoops I had to jump through to get this going originally. > > Might be time for a new setup - amd athlon 2500+ are not so cool these > days :) Glad you got it working! Another gotcha is when you disable the deprecated CONFIG_IDE in the kernel and you don't update your grub.conf and /etc/fstab to rename /dev/hda's into /dev/sda's. -- Regards, Mick
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On Mon, 2010-07-26 at 09:05 +0800, Bill Kenworthy wrote: > On Sun, 2010-07-25 at 22:08 +0200, Alan McKinnon wrote: > > On Sunday 25 July 2010 10:18:33 Dale wrote: > > > Alan McKinnon wrote: > > > > [snip] > > > > > > When done, reboot as normal and see if the machine boots up properly. > > > > > > And I would stand guard to make sure housekeeping doesn't come around. > > > ;-) Cutting power during all this wold not be good. > > > > Here in Africa we use pythons for that. > > > > Real genuine live 10 foot snakes. In a terrarium of course. > > > > Trust me, it takes about 30 seconds after the first housekeeping person > > sees > > it until none of them goes anywhere near your stuff. > > > > :-) > > > I like the idea of pythons, as they swallow the prey whole its much less > messy than the redback spiders suggested for use here in West Oz ... > someone would have to clean up the bodies in the morning. > > Must be a coincidence, didnt update the MBR after installing grub and > failed to boot this morning - though the signs are more like disk > failure - even the live CD isnt helping :( > > Another job for tonight when I get home. > > BillK > Fixed it - was grub after all - it renumbered my drives (0 and 1 swapped :( Complicated because this was one of the early sata boards with a fake raid chip to handle the sata while the old IDE drives were on the normal bus. Further complicated by the bios and raidchip changing drive assignments depending on which drive/cd/floppy you booted from (i.e., what grub sees as the drive numbers changes when the real OS is booted). I forgot what hoops I had to jump through to get this going originally. Might be time for a new setup - amd athlon 2500+ are not so cool these days :) BillK
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On Sun, 2010-07-25 at 22:08 +0200, Alan McKinnon wrote: > On Sunday 25 July 2010 10:18:33 Dale wrote: > > Alan McKinnon wrote: > > [snip] > > > > When done, reboot as normal and see if the machine boots up properly. > > > > And I would stand guard to make sure housekeeping doesn't come around. > > ;-) Cutting power during all this wold not be good. > > Here in Africa we use pythons for that. > > Real genuine live 10 foot snakes. In a terrarium of course. > > Trust me, it takes about 30 seconds after the first housekeeping person sees > it until none of them goes anywhere near your stuff. > > :-) > I like the idea of pythons, as they swallow the prey whole its much less messy than the redback spiders suggested for use here in West Oz ... someone would have to clean up the bodies in the morning. Must be a coincidence, didnt update the MBR after installing grub and failed to boot this morning - though the signs are more like disk failure - even the live CD isnt helping :( Another job for tonight when I get home. BillK
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On Sunday 25 July 2010 17:24:46 cov...@ccs.covici.com wrote: > > > When done, reboot as normal and see if the machine boots up properly. > > > > > > > > > > > > > > And I would stand guard to make sure housekeeping doesn't come around. > > ;-) Cutting power during all this wold not be good. > > You don't need to invalidate the journal or mount ext2, just use -f if > memory serves, be sure the partition is unmounted and that will force a > full check. Yes, -f does seem to be the right option. It's been ages since I used ext3 and I have no real way to do a test, so I played safe. And the man page could be a little more descriptive too, -f left me with more questions than answers. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On Sunday 25 July 2010 10:18:33 Dale wrote: > Alan McKinnon wrote: [snip] > > When done, reboot as normal and see if the machine boots up properly. > > And I would stand guard to make sure housekeeping doesn't come around. > ;-) Cutting power during all this wold not be good. Here in Africa we use pythons for that. Real genuine live 10 foot snakes. In a terrarium of course. Trust me, it takes about 30 seconds after the first housekeeping person sees it until none of them goes anywhere near your stuff. :-) -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
Dale wrote: > Alan McKinnon wrote: > > On Sunday 25 July 2010 06:57:43 KH wrote: > > > >>> You said you ran e2fsck and it was OK. What was the command? > >>> > >>> > >>> > >>> Normally with an e2fsck on a journalled fs, the app will replay the > >>> journal and make a few minor checks. This takes about 4 seconds, not > >>> the 40 minutes it takes to do a ful ext2 check. > >>> > >>> > >>> > >>> I think you might need to fsck without the journal. I know there's a way > >>> to do this but a cursory glance at the man page didn't reveal it. Maybe > >>> an ext user will chip in with the correct method > >>> > >>> > >>> > >>> > >>> > >> Hi, > >> > >> I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3 > >> /dev/sde3 . Yes, it only took some seconds. > >> > > It's been a long time since I used ext3 so some of this might be wrong. > > > > An fsck that takes a few seconds is using the journal, which might not > > uncover > > deeper corruption. You should try disabling the journal (I couldn't find the > > way to do that though), but this will also work: > > > > Boot of a LiveCD, mount your root partition somewhere using type "ext2" and > > fsck it. This will invalidate the journal but that's OK, it gets recreated > > on > > the next proper boot. Let the fsck finish - it will take a while on a large > > fs. > > > > When done, reboot as normal and see if the machine boots up properly. > > > > > > > > And I would stand guard to make sure housekeeping doesn't come around. > ;-) Cutting power during all this wold not be good. You don't need to invalidate the journal or mount ext2, just use -f if memory serves, be sure the partition is unmounted and that will force a full check. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On Sunday 25 July 2010 09:18:33 Dale wrote: > Alan McKinnon wrote: > > On Sunday 25 July 2010 06:57:43 KH wrote: > >>> You said you ran e2fsck and it was OK. What was the command? > >>> > >>> > >>> > >>> Normally with an e2fsck on a journalled fs, the app will replay the > >>> journal and make a few minor checks. This takes about 4 seconds, not > >>> the 40 minutes it takes to do a ful ext2 check. > >>> > >>> > >>> > >>> I think you might need to fsck without the journal. I know there's a > >>> way to do this but a cursory glance at the man page didn't reveal it. > >>> Maybe an ext user will chip in with the correct method > >> > >> Hi, > >> > >> I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3 > >> /dev/sde3 . Yes, it only took some seconds. > > > > It's been a long time since I used ext3 so some of this might be wrong. > > > > An fsck that takes a few seconds is using the journal, which might not > > uncover deeper corruption. You should try disabling the journal (I > > couldn't find the way to do that though), but this will also work: > > > > Boot of a LiveCD, mount your root partition somewhere using type "ext2" > > and fsck it. This will invalidate the journal but that's OK, it gets > > recreated on the next proper boot. Let the fsck finish - it will take a > > while on a large fs. > > > > When done, reboot as normal and see if the machine boots up properly. > > And I would stand guard to make sure housekeeping doesn't come around. > ;-) Cutting power during all this wold not be good. KH, I think that this may not be related to a fs error as such. Yes, pulling the plug may have caused fs corruption. However, more likely is that pulling the plug did not allow you to do something that you should have done after you finished upgrading to grub-0.97-r9. The latest installation of grub asks you to reinstall in the MBR and point its root to wherever your /boot is. GRUB's fs and its drivers may have changed and therefore the old boot loader code is looking for files that no longer exist. So you'll probably be alright again if you boot with a fresh systemrescue LiveCD and run grub and then root (hd) and setup (hd0) before you quit and reboot. If that doesn't work then you most likely have a fs problem. HTH. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
Alan McKinnon wrote: On Sunday 25 July 2010 06:57:43 KH wrote: You said you ran e2fsck and it was OK. What was the command? Normally with an e2fsck on a journalled fs, the app will replay the journal and make a few minor checks. This takes about 4 seconds, not the 40 minutes it takes to do a ful ext2 check. I think you might need to fsck without the journal. I know there's a way to do this but a cursory glance at the man page didn't reveal it. Maybe an ext user will chip in with the correct method Hi, I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3 /dev/sde3 . Yes, it only took some seconds. It's been a long time since I used ext3 so some of this might be wrong. An fsck that takes a few seconds is using the journal, which might not uncover deeper corruption. You should try disabling the journal (I couldn't find the way to do that though), but this will also work: Boot of a LiveCD, mount your root partition somewhere using type "ext2" and fsck it. This will invalidate the journal but that's OK, it gets recreated on the next proper boot. Let the fsck finish - it will take a while on a large fs. When done, reboot as normal and see if the machine boots up properly. And I would stand guard to make sure housekeeping doesn't come around. ;-) Cutting power during all this wold not be good. Dale :-) :-)
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On Sunday 25 July 2010 06:57:43 KH wrote: > > You said you ran e2fsck and it was OK. What was the command? > > > > > > > > Normally with an e2fsck on a journalled fs, the app will replay the > > journal and make a few minor checks. This takes about 4 seconds, not > > the 40 minutes it takes to do a ful ext2 check. > > > > > > > > I think you might need to fsck without the journal. I know there's a way > > to do this but a cursory glance at the man page didn't reveal it. Maybe > > an ext user will chip in with the correct method > > > > > > > > > > Hi, > > I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3 > /dev/sde3 . Yes, it only took some seconds. It's been a long time since I used ext3 so some of this might be wrong. An fsck that takes a few seconds is using the journal, which might not uncover deeper corruption. You should try disabling the journal (I couldn't find the way to do that though), but this will also work: Boot of a LiveCD, mount your root partition somewhere using type "ext2" and fsck it. This will invalidate the journal but that's OK, it gets recreated on the next proper boot. Let the fsck finish - it will take a while on a large fs. When done, reboot as normal and see if the machine boots up properly. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
Am 24.07.2010 23:46, schrieb James Wall: > On 7/24/2010 3:25 PM, Alan McKinnon wrote: >> >> I think you might need to fsck without the journal. I know there's a >> way to do >> this but a cursory glance at the man page didn't reveal it. Maybe an >> ext user >> will chip in with the correct method > > Run e2fsck -f /dev/hda3 to force check a partition. I have had to do > that when my kids yanked all the drives out of a server that I was > setting up. :-) Hi again, # e2fsck -fv /dev/sde3 e2fsck 1.41.11 (14-Mar-2010) Durchgang 1: Prüfe Inodes, Blocks, und Größen Durchgang 2: Prüfe Verzeichnis Struktur Durchgang 3: Prüfe Verzeichnis Verknüpfungen Durchgang 4: Überprüfe die Referenzzähler Durchgang 5: Überprüfe Gruppe Zusammenfassung 356415 inodes used (36.63%) 10396 non-contiguous files (2.9%) 236 non-contiguous directories (0.1%) # von Inodes mit ind/dind/tind Blöcken: 7917/121/0 2191858 blocks used (56.32%) 0 bad blocks 1 large file 315130 regular files 31986 directories 1051 character device files 4089 block device files 1 fifo 2397 links 4147 symbolic links (4027 fast symbolic links) 2 sockets 358803 files Well this does not look bad, does it? Regards kh > No trees were harmed in the sending of this message. However, a large > number of electrons were terribly inconvenienced. cool sig!
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
Am 24.07.2010 22:21, schrieb Alan McKinnon: > On Saturday 24 July 2010 21:57:38 KH wrote: >> Hi there, [...] >> Anyway the box won't boot anymore. grub starts up. Kernel boots. Then >> there is checking root file system (or something like that).The message >> is that my ext2 file system can not be read. That I might want to try >> the alternativ superblock by running #e2fsck -b 8193 >> >> Well, I put the hdd in an external usb and conected it to my >> workstation. As I thought hda3 (is /dev/sde3) is an ext3 filesystem. >> Also badblocks and e2fsck did not show any problem with the hdd. >> >> /etc/fstab is corect (i hope), too. >> >> What am I missing? How can I get the server running, again? > > You said you ran e2fsck and it was OK. What was the command? > > Normally with an e2fsck on a journalled fs, the app will replay the journal > and make a few minor checks. This takes about 4 seconds, not the 40 minutes > it > takes to do a ful ext2 check. > > I think you might need to fsck without the journal. I know there's a way to > do > this but a cursory glance at the man page didn't reveal it. Maybe an ext user > will chip in with the correct method > > > Hi, I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3 /dev/sde3 . Yes, it only took some seconds. Regards kh
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On Sat, Jul 24, 2010 at 9:21 PM, Alan McKinnon wrote: > I think you might need to fsck without the journal. I know there's a way to do > this but a cursory glance at the man page didn't reveal it. Maybe an ext user > will chip in with the correct method "e2fsck -f" should run the full system check after replaying the journal. RobbieAB
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On 7/24/2010 3:25 PM, Alan McKinnon wrote: On Saturday 24 July 2010 21:57:38 KH wrote: Hi there, my server was running strait for 8 month now. I did updates regularly but still used an 2.6.2x kernel. Never switched it of. Now someone from houskeeping pulled the plug for the vacuum cleaner ... Anyway the box won't boot anymore. grub starts up. Kernel boots. Then there is checking root file system (or something like that).The message is that my ext2 file system can not be read. That I might want to try the alternativ superblock by running #e2fsck -b 8193 Well, I put the hdd in an external usb and conected it to my workstation. As I thought hda3 (is /dev/sde3) is an ext3 filesystem. Also badblocks and e2fsck did not show any problem with the hdd. /etc/fstab is corect (i hope), too. What am I missing? How can I get the server running, again? You said you ran e2fsck and it was OK. What was the command? Normally with an e2fsck on a journalled fs, the app will replay the journal and make a few minor checks. This takes about 4 seconds, not the 40 minutes it takes to do a ful ext2 check. I think you might need to fsck without the journal. I know there's a way to do this but a cursory glance at the man page didn't reveal it. Maybe an ext user will chip in with the correct method Run e2fsck -f /dev/hda3 to force check a partition. I have had to do that when my kids yanked all the drives out of a server that I was setting up. :-) -- No trees were harmed in the sending of this message. However, a large number of electrons were terribly inconvenienced.
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On Saturday 24 July 2010 21:57:38 KH wrote: > Hi there, > > my server was running strait for 8 month now. I did updates regularly > but still used an 2.6.2x kernel. Never switched it of. Now someone from > houskeeping pulled the plug for the vacuum cleaner ... > > Anyway the box won't boot anymore. grub starts up. Kernel boots. Then > there is checking root file system (or something like that).The message > is that my ext2 file system can not be read. That I might want to try > the alternativ superblock by running #e2fsck -b 8193 > > Well, I put the hdd in an external usb and conected it to my > workstation. As I thought hda3 (is /dev/sde3) is an ext3 filesystem. > Also badblocks and e2fsck did not show any problem with the hdd. > > /etc/fstab is corect (i hope), too. > > What am I missing? How can I get the server running, again? You said you ran e2fsck and it was OK. What was the command? Normally with an e2fsck on a journalled fs, the app will replay the journal and make a few minor checks. This takes about 4 seconds, not the 40 minutes it takes to do a ful ext2 check. I think you might need to fsck without the journal. I know there's a way to do this but a cursory glance at the man page didn't reveal it. Maybe an ext user will chip in with the correct method -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
On Saturday 24 July 2010 21:57:38 KH wrote: > Hi there, > > my server was running strait for 8 month now. I did updates regularly > but still used an 2.6.2x kernel. Never switched it of. Now someone from > houskeeping pulled the plug for the vacuum cleaner ... > > Anyway the box won't boot anymore. grub starts up. Kernel boots. Then > there is checking root file system (or something like that).The message > is that my ext2 file system can not be read. That I might want to try > the alternativ superblock by running #e2fsck -b 8193 > > Well, I put the hdd in an external usb and conected it to my > workstation. As I thought hda3 (is /dev/sde3) is an ext3 filesystem. > Also badblocks and e2fsck did not show any problem with the hdd. > > /etc/fstab is corect (i hope), too. > > What am I missing? How can I get the server running, again? You said you ran e2fsck and it was OK. What was the command? Normally with an e2fsck on a journalled fs, the app will replay the journal and make a few minor checks. This takes about 4 seconds, not the 40 minutes it takes to do a ful ext2 check. I think you might need to fsck without the journal. I know there's a way to do this but a cursory glance at the man page didn't reveal it. Maybe an ext user will chip in with the correct method -- alan dot mckinnon at gmail dot com
[gentoo-user] Problems booting my server - ext2 - e2fsck
Hi there, my server was running strait for 8 month now. I did updates regularly but still used an 2.6.2x kernel. Never switched it of. Now someone from houskeeping pulled the plug for the vacuum cleaner ... Anyway the box won't boot anymore. grub starts up. Kernel boots. Then there is checking root file system (or something like that).The message is that my ext2 file system can not be read. That I might want to try the alternativ superblock by running #e2fsck -b 8193 Well, I put the hdd in an external usb and conected it to my workstation. As I thought hda3 (is /dev/sde3) is an ext3 filesystem. Also badblocks and e2fsck did not show any problem with the hdd. /etc/fstab is corect (i hope), too. What am I missing? How can I get the server running, again? Regards kh
Re: [gentoo-user] Problems Booting
Something very similar happened to me. baselayout-1.12.0_pre1-r1 was emerged in the past day or two, and the next time I rebooted, it hung up on what at first seemed to be having issues loading alsa. The boot did get into runlevel 3, so I was able to get in remotely and mess around. After pruning various things from the startup routine, it turned out to be sys-apps/dbus causing the problem for me. I removed that from the init sequence, rebooted, and everything is back to normal (or seems to be). I'm not familiar with dbus, but it was a dependency of evolution, and the very simple description of the "dbus" use flag seemed innocuous enough. I'm still running on baselayout-1.12.0_pre1-r1. Regards, Chris -- /*** *Chris Woods || [EMAIL PROTECTED]* *AIM: gnarrlybob || ICQ: 21740987 * *Yahoo: cjwoods || MSN: [EMAIL PROTECTED]* * Jabber: [EMAIL PROTECTED] || http://bitspace.org * **/ -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Problems Booting
Rumen Yotov wrote: [EMAIL PROTECTED] wrote: I'm ~x86 on a dell laptop. I'm having some fun this morning. Everything was working this morning, but I shut down the system for my daily commute and now it won't boot. I seem to Hi, As there are problems with latest baselayout (2-3 persons) on boot check for "baselayout-1.12.0_pre1-r1" and go to the stable/previous version: 1.11.13. HTH. Rumen So Kurt, here is your friendly tip/clue that you should have email sent from both "[EMAIL PROTECTED]" and "[EMAIL PROTECTED]" include your name! Cheers, -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Problems Booting
[EMAIL PROTECTED] wrote: I'm ~x86 on a dell laptop. I'm having some fun this morning. Everything was working this morning, but I shut down the system for my daily commute and now it won't boot. I seem to remember a few gnome emerges last night, but everything emerged cleanly and ran etc-update. I have some failing init scripts such as xfs (ie, X Font Server) and net.eth0. I did a 'rc-update del' on these and xdm, so that I'd have a starting point from which to work from. However, it sill won't give me a bash shell. It literally hangs after starting the last script. Does anybody know which rock to turn over to find out why this is the case? --Kurt PS- I can boot off the Gentoo Live CD. I did a new 'emerge sync', but I can't find anything that would fix this. I also checked bugs.gentoo.com, but nada. I'm running fsck on all my file partitions to see if there is an error. Hi, As there are problems with latest baselayout (2-3 persons) on boot check for "baselayout-1.12.0_pre1-r1" and go to the stable/previous version: 1.11.13. HTH. Rumen smime.p7s Description: S/MIME Cryptographic Signature
[gentoo-user] Problems Booting
I'm ~x86 on a dell laptop. I'm having some fun this morning. Everything was working this morning, but I shut down the system for my daily commute and now it won't boot. I seem to remember a few gnome emerges last night, but everything emerged cleanly and ran etc-update. I have some failing init scripts such as xfs (ie, X Font Server) and net.eth0. I did a 'rc-update del' on these and xdm, so that I'd have a starting point from which to work from. However, it sill won't give me a bash shell. It literally hangs after starting the last script. Does anybody know which rock to turn over to find out why this is the case? --Kurt PS- I can boot off the Gentoo Live CD. I did a new 'emerge sync', but I can't find anything that would fix this. I also checked bugs.gentoo.com, but nada. I'm running fsck on all my file partitions to see if there is an error. -- gentoo-user@gentoo.org mailing list
[gentoo-user] problems booting from sata raid
hi everybody, i'm a new gentoo user and i encountered following problem: my computer is amd64 on abit ax8 mobo, installation started at stage2. i put root on mirrored sata (raid1) disks. kernel compiled ok, i performed all steps described in the installation guide with the modifications described in the wiki: http://gentoo-wiki.com/HOWTO_Gentoo_Install_on_Software_RAID i am quite sure that all the necessary drivers (namely raid1) are compiled into the kernel. after reboot, kernel detects the hw. sets up the raid drives, but then: checking root file system ... ext2fs_check_if_mount: No such file or directory while determining whether /dev/md0 is mounted fsck.ext3:No such file or directory while trying to open /dev/md0 /dev/md0: The superblock could not be read or does not describe a correct ext2 filesystem... Filesystem couldn't be fixed. after it, it asks for root password for maintenance. i checked /dev and it doesn't have any of the md* nodes. i found similar error while googling the web, but no solution to the problem was given... few lines above the error i can see: Configuring system to use udev Populating /dev with device nodes /sbin/rc: line 248: cannot redirect standard input from /dev/null: No such file or directory can this be related? mounted filesystems in my fstab are in the following order: proc tmpfs swap1 swap2 hda cdrom fd0 floppy md0 / md1 /home i'd be very grateful if someone could help me with this... thanks in advance. regards, -- Lubos [EMAIL PROTECTED]" -- gentoo-user@gentoo.org mailing list
