Re: fixing a debian system: which RTFM to start?
Can you run find /dev -type l and then run an ls -al on anything that
looks like it's pointing at hda?
I can't remember how to get find to exec an ls -al on each file it finds
and -follow won't really work here I think to get the target of the link
AND please run ls -al /dev/ |grep 3,
and look for anything with major 3 and minor 0 which would be pointing
at hda without having the hda name necessarily.
--mike
On 08 Aug 2001 10:33:52 +0700, Rahmat M. Samik-Ibrahim wrote:
> Hello Karsten,
>
> I will rewrite the problem to avoid context confusion.
>
> First some background: My (prior) DNS server's disk went
> out of order, and it was moved to an "unused" backup server.
> I noticed that the "named" at that system crashed once in
> a while, and therefore I tried to find out about what
> was going on. Then, I failed to "dselect|upadate" and
> "apt-get".
>
> Problems:
> - how to fix the lilo problem?
> - which manual to read?
> - any other clue what to do?
>
> Good news:
> - I can reboot it, and I have full remote access to the
> system.
> - ssh/sshd is available
> - the named does not crash so often (about 1-2 times a week).
>
> Bad news:
> - the owner of that system is very busy. I have no idea
> on why the CD-ROM is on IDA primary/master.
> But I guess, that there was only a SCSI disk in the
> beginning; the two additional IDE disks have been added
> later.
> - the system is 10000 miles away; I have no idea how
> it looks like, or if the CD-ROM drive is still
> attached.
> - The system is "as is"; it was not me who compiled the kernel.
> The problem: apparently it is still running 2.0.36;
> thus lilo can not be updated?
>
> Files:
> --- message after running "dselect|update" --------------------
> mount: the kernel does not recognize /dev/hda as a
> block device
> (may be `insmod driver'?)
> update available list script returned error status 1.
>
> --- sources.list ----------------------------------------------
> deb http://http.us.debian.org/debian woody main contrib non-free
> deb http://non-us.debian.org/debian-non-US woody non-US/main non-US/contrib non-US/non-free
>
> --- fstab ---------------------------------------------
> /dev/sda1 / ext2 defaults,errors=remount-ro 0 1
> /dev/sda6 none swap sw 0 0
> proc /proc proc defaults 0 0
> /dev/sda2 /usr ext2 defaults 0 2
> /dev/sda5 /var ext2 defaults 0 2
> /dev/sda7 /h1 ext2 defaults 0 2
> /dev/hdc1 /b1 ext2 defaults 0 2
> /dev/hdd1 /b2 ext2 defaults 0 2
>
> ---- part of messages ----------------------------------------
> kernel: Memory: 256440k/262144k available (1136k kernel code, 384k reserved, 4184k data)
> kernel: Linux version 2.0.36 (root@gondor) (gcc version 2.7.2.3) #2 Sun Feb 21 15:55:27 EST
> 1999
> kernel: ide: i82371 PIIX (Triton) on PCI bus 0 function 57
> kernel: ide0: BM-DMA at 0xffa0-0xffa7
> kernel: ide1: BM-DMA at 0xffa8-0xffaf
> kernel: hdc: Maxtor 53073U6, 29311MB w/2048kB Cache, CHS=59554/16/63, UDMA
> kernel: hdd: Maxtor 53073U6, 29311MB w/2048kB Cache, CHS=59554/16/63, UDMA
> kernel: ide1 at 0x170-0x177,0x376 on irq 15
> kernel: (scsi0) <Adaptec AHA-294X Ultra SCSI host adapter> found at PCI 16/0
> kernel: Failed initialization of WD-7000 SCSI card!
> kernel: <Adaptec AHA-294X Ultra SCSI host adapter>
> kernel: Module inserted $Id: cdrom.c,v 0.8 1996/08/10 10:52:11 david Exp $
>
> --- lilo.conf --------------------------------------
> disk=/dev/sda
> bios=0x81
> disk=/dev/hdc
> bios=0x80
> boot = /dev/hdc
> root = /dev/sda1
> compact
> delay = 5
> vga = normal
>
> # (extra note: /vmlinuz is a symlink of /boot/vmlinuz-2.4.6)
> # (no error complain when running "lilo")
> # (is this a BIOS problem?)
> image = /vmlinuz
> label = linux
> read-only
>
> image = /boot/vmlinuz-2.0.36
> label = 2036
> read-only
>
>
> -----------------------------------------------------------
> regards,
>
> --
> Rahmat M. Samik-Ibrahim - VLSM-TJT - http://rms46.vlsm.org
> - AWAS IBRAHIM[tm] PALSU :^) Patent and Trade Mark Pending
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
Reply to: