View Single Post
Unread 07-16-2008, 04:57 AM   #71
blue68f100
Thermophile
 
blue68f100's Avatar
 
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
Default Re: Guardian OS units

If you have a copy of SpinRite, I would shut it down and run it on all the drives. If there is a drive problem it will correct it. Otherwise you may need to reload the GSU file. It's has an error on loading one part. Like maybe all the markers did not get changed.

Have you checked to see if the bios settings have not changed? May be time to replace the Battery. But this is down Phoenix32 line.

Quote:
EXT2-fs warning: checktime reached, running e2fsck is recommended

VFS: Mounted root (ext2 filesystem).

kmod: failed to exec /sbin/modprobe -s -k char-major-10-152, errno = 2

kmod: failed to exec /sbin/modprobe -s -k char-major-10-152, errno = 2

/dev/Qhwmon: No such device
/dekmod: failed to exec /sbin/modprobe -s -k char-major-10-152, errno = 2

v/Qhwmon: No suckmod: failed to exec /sbin/modprobe -s -k char-major-10-152, errno = 2

h device
/dev/Qhwmon: No such device
/dev/Qhwmon: No such device
Using /lib/modules/i2c-core.o
i2c-core.o: i2c core module

Using /lib/modules/i2c-dev.o
i2c-dev.o: i2c /dev entries driver module

Using /lib/modules/i2c-proc.o
i2c-proc.o version 2.6.1 (20010825)

Using /lib/modules/i2c-piix4.o
Install SMBus adapter driver (i2c-piix4)

i2c-dev.o: Registered 'SMBus OSB4/CSB5 adapter at 0580' as minor 0

i2c-piix4.o: PIIX4 bus detected and initialized

Using /lib/modules/Qhwmon-Modulekmod: failed to exec /sbin/modprobe -s -k char-major-10-152, errno = 2

.o
kmod: failed to exec /sbin/modprobe -s -k char-major-10-152, errno = 2

/dev/Qhwmon: No such device
/dekmod: failed to exec /sbin/modprobe -s -k char-major-10-152, errno = 2

v/Qhwmon: No such device
/dev/Qhwmon: No such device
Qhwmon: proc entries installed OK

Qhwmon: Hardware monitor driver successfully loaded as Manta driver

Using /lib/modules/mtdcore.o
Using /lib/modules/mtdchar.o
Using /lib/modules/chipreg.o
Using /lib/modules/gen_probe.o
Using /lib/modules/cfi_probe.o
Using /lib/modules/cfi_cmdset_0001.o
Using /lib/modules/amd_flash.o
Using /lib/modules/quantumsnap.oGuardian: Found no Flash device


Using /lib/modules/mii.o
Platform = MANTARAY
Using /lib/modules/qinfo_i2c.o
Using /lib/modules/qinfo.o
qinfo: version 2.2 (20020709)

mdctl: fail to stop array /dev/md100root: No such device
starting raid: md100root containing drive /dev/hda2
mdctl: /dev/md100root has been started with 3 drives.
mdctl: fail to stop array /dev/md101swap: No such device
starting raid: md101swap containing drive /dev/hda5
mdctl: /dev/md101swap has been started with 4 drives.
>> root FS exists
***** Running on HARD DISK *****
Not on Clipper: Returning from Linuxrc
Kernel panic: No init found. Try passing init= option to kernel.

Oops: 0002

CPU: 0

EIP: 0010:[<c0230009>] Not tainted

EFLAGS: 00010206

eax: 00000007 ebx: c02f7ee0 ecx: 00000000 edx: 00000488

esi: 00000000 edi: 00000000 ebp: 0008e000 esp: dfde7f84

ds: 0018 es: 0018 ss: 0018

Process swapper (pid: 1, stackpage=dfde7000)

Stack: c02f7ee0 00000000 00000000 0008e000 00000246 00000000 c02304de 00000000

00000000 c02f7ee0 c011c9ee c02f7ee0 00000000 00000000 c02a8900 0000000e

c0105000 c0113c6a c0317f14 00000000 00000000 00000000 c02a88f6 c010539a

Call Trace: [<c02304de>] [<c011c9ee>] [<c0105000>] [<c0113c6a>] [<c010539a>]

[<c01056f3>]

Code: ff 01 0f 8e 25 05 00 00 31 c0 5b 5e 5f 5d 59 5a c3 89 f6 31

<0>Kernel panic: Attempted to kill init!
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5,
1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5,
1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy

Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820
blue68f100 is offline   Reply With Quote