[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-developers] Fwd: Unavailable storage
- Subject: Re: [cobalt-developers] Fwd: Unavailable storage
- From: Barry Titmarsh <barry@xxxxxxxxxxxxxx>
- Date: Thu Feb 3 18:08:14 2000
At 01:48 04/02/00 +0000, you wrote:
At 01:26 04/02/00 +0000, you wrote:
Well good Job this box is a test box The only way to recover this problem
was to manually mount the disk then delete the disk in the storage panel
and then re-add it which means reformat the disk ;-(
resulting in total loss of all data.
not a good fix hi. Now I get to test the cobalt restore stuff and see if
that works hi ;)
Barry
Ok heres the good news after install of the RAQ3E-OS-2.0 upgrade and a
total loss of my storage disk1
Telnet monitor now says its not in use - correct
My /vol/home1 is back but all data lost - okay I can restore
The Box is back working but for me and my virtual test sites back to
factory defaults.
If I was an operational box here I would be a bit worried by now. but since
Im only a developer with a test box I am not..
I hope this experience tonight helps some one figure out what went wrong.
before some one out there makes a big booboo and gets into some serious
doodoo hi.
Barry
PS here are some logs stuff
Feb 4 00:42:43 boobox upsd[235]: Host 127.0.0.1 disconnected
Feb 4 00:42:44 boobox smartups[224]: SIGTERM: Shutting down
Feb 4 00:42:44 boobox smartups[224]: Detaching from shared memory
Feb 4 00:42:45 boobox kernel: Kernel logging (proc) stopped.
Feb 4 00:42:45 boobox kernel: Kernel log daemon terminating.
Feb 4 00:42:47 boobox exiting on signal 15
Feb 4 00:43:45 boobox syslogd 1.3-3: restart.
Feb 4 00:43:45 boobox modprobe: can't locate module block-major-22
Feb 4 00:43:46 boobox modprobe: can't locate module block-major-22
Feb 4 00:43:46 boobox modprobe: can't locate module block-major-33
Feb 4 00:43:46 boobox modprobe: can't locate module block-major-33
Feb 4 00:43:46 boobox modprobe: can't locate module block-major-34
Feb 4 00:43:46 boobox modprobe: can't locate module block-major-34
Feb 4 00:43:46 boobox modprobe: can't locate module block-major-8
Feb 4 00:43:46 boobox last message repeated 4 times
Feb 4 00:43:46 boobox modprobe: can't locate module block-major-13
Feb 4 00:43:46 boobox modprobe: can't locate module block-major-13
Feb 4 00:43:47 boobox kernel: klogd 1.3-3, log source = /proc/kmsg started.
Feb 4 00:43:47 boobox kernel: Inspecting /boot/System.map
Feb 4 00:43:47 boobox kernel: Loaded 6537 symbols from /boot/System.map.
Feb 4 00:43:47 boobox kernel: Symbols match kernel version 2.2.12.
Feb 4 00:43:47 boobox kernel: Loaded 104 symbols from 1 module.
Feb 4 00:43:47 boobox kernel: Linux version 2.2.12C3 (root@freakshow) (gcc
version egcs-2.91.66 19990314
/Linux (egcs-1.1.2 release)) #1 Tue Oct 5 15:42:47 PDT 1999
and more
Feb 4 00:43:47 boobox kernel: Uniform Multi-Platform E-IDE driver
Revision: 6.20
Feb 4 00:43:47 boobox kernel: ALI15X3: IDE controller on PCI bus 00 dev 78
Feb 4 00:43:47 boobox kernel: ALI15X3: 100% native mode on irq 14
Feb 4 00:43:47 boobox kernel: ide0: BM-DMA at 0xf000-0xf007, BIOS
settings: hda:DMA, hdb:DMA
Feb 4 00:43:47 boobox kernel: ide1: BM-DMA at 0xf008-0xf00f, BIOS
settings: hdc:DMA, hdd:DMA
Feb 4 00:43:47 boobox kernel: hda: QUANTUM FIREBALLlct08 08, ATA DISK drive
Feb 4 00:43:47 boobox kernel: hdb: QUANTUM FIREBALLlct08 26, ATA DISK drive
Feb 4 00:43:47 boobox kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Feb 4 00:43:47 boobox kernel: ALI15X3: Ultra DMA enabled
Feb 4 00:43:47 boobox kernel: hda: QUANTUM FIREBALLlct08 08, 8063MB
w/418kB Cache, CHS=16383/16/63, (U)D
MA
Feb 4 00:43:47 boobox kernel: ALI15X3: Ultra DMA enabled
Feb 4 00:43:47 boobox kernel: hdb: QUANTUM FIREBALLlct08 26, 24833MB
w/418kB Cache, CHS=50456/16/63, (U)
DMA
Feb 4 00:43:47 boobox kernel: md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
and more
Feb 4 00:43:47 boobox kernel: Uniform Multi-Platform E-IDE driver
Revision: 6.20
Feb 4 00:43:47 boobox kernel: ALI15X3: IDE controller on PCI bus 00 dev 78
Feb 4 00:43:47 boobox kernel: ALI15X3: 100% native mode on irq 14
Feb 4 00:43:47 boobox kernel: ide0: BM-DMA at 0xf000-0xf007, BIOS
settings: hda:DMA, hdb:DMA
Feb 4 00:43:47 boobox kernel: ide1: BM-DMA at 0xf008-0xf00f, BIOS
settings: hdc:DMA, hdd:DMA
Feb 4 00:43:47 boobox kernel: hda: QUANTUM FIREBALLlct08 08, ATA DISK drive
Feb 4 00:43:47 boobox kernel: hdb: QUANTUM FIREBALLlct08 26, ATA DISK drive
Feb 4 00:43:47 boobox kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Feb 4 00:43:47 boobox kernel: ALI15X3: Ultra DMA enabled
Feb 4 00:43:47 boobox kernel: hda: QUANTUM FIREBALLlct08 08, 8063MB
w/418kB Cache, CHS=16383/16/63, (U)D
MA
Feb 4 00:43:47 boobox kernel: ALI15X3: Ultra DMA enabled
Feb 4 00:43:47 boobox kernel: hdb: QUANTUM FIREBALLlct08 26, 24833MB
w/418kB Cache, CHS=50456/16/63, (U)
DMA
Feb 4 00:43:47 boobox kernel: md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
bla bla....
Looks like after the update something was wrong or changed in the file
system some modules failed to load that drive the disks ?
ah well some data to ponder over another time
Barry
----------------------------------------------------------------------------
------------------------------
Barry Titmarsh BMT1-RIPE Nacamar Ltd (Sheringham Office)
Knole House 38 Cromer Rd
Sheringham Norfolk NR268RR
e-mail: barry@xxxxxxxxxxxxxx voice: +44-1263-821-844
www: www.nacamar.net.uk
----------------------------------------------------------------------------
------------------------------