Page 1 of 1

Error after installing Vicibox 3.1

PostPosted: Sun Dec 04, 2011 7:02 pm
by obregonjose3
Hi everybody

I installed Vicibox 3.1 64bit on a Dell poweredge 6800, with 2 Xeon processors 64bit, 8Gb in RAM, and 4 hard drives SCSI, in RAID.

Everything is ok when the installation is finished. But when I reboot the system, wow:

Code: Select all
Boot logging starded on /dev/tty1(/dev/console)
resume device not found (ignoring)
Waiting for device /dev/sda1 to appear:..........................................could not find /dev/sda1.
Want me to fall back to /dev/sda1? (y/n)


Happens after execute this:

Code: Select all
#zypper refresh && zypper up
#reboot


Ok, Because this is optional I try to obviate. And again it is the same error when rebooting.

Here are some facts:

Disk partitions:
Code: Select all
Disk /dev/sda 440GB
255 heads, 63 sectors, 53504 cylinders
Units = sectors of 1 * 512 bytes
Sector size (logical/physical): 512 bytes/512 bytes
I/O size (minimun/optimal): 512 bytes/512 bytes

Device       Boot        Start         End          Block        ID   System
/dev/sda1     *          63        858529664  429264801   83   Linux
/dev/sda2           858529665   859541759   506047+     82   Linux/swap


GRUB entries:

Code: Select all
ViciBox 3.1.....
Kernel (hd0, 0)/boot/vmlinuz-2.6.34.10-0.4-default root=/dev/sda1 disk=/dev/sda vga=0x314 splash=silent showopts resume=/dev/sda2
initrd  (hd0, 0)/boot/initrd-2.6.34.10-0.4-default
Failsafe ........
Kernel (hd0, 0)/boot/vmlinuz-2.6.34.10-0.4-default root=/dev/sda1 disk=/dev/sda vga=0x314 splash=silent showopts ide=nodma apm=off acpi=off noresume selinux=0 nosmp noapic maxcpu=0 edd=off
initrd  (hd0, 0)/boot/initrd-2.6.34.10-0.4-default


thanks and I hope your valuable help

PostPosted: Sun Dec 04, 2011 9:06 pm
by Michael_N
it might be some raiddrivers that gives you trouble.
Have you tried a reinstall?

You could search for solution on opensuse forums providing your raid-data.

PostPosted: Mon Dec 19, 2011 3:13 pm
by williamconley
Turn off RAID and use a stock HD setup instead. If that fixes it, you'll need to wait until the RAID drivers are added the base OpenSuSE or investigate having someone install them for you.

Also: You did not mention your actual version, there is no "3.1", there is, however, "3.1.XX" .. and the question is whether you are using the latest .iso (3.1.13? 14? Dunno, haven't looked today) which will have the most recent drivers added from the SuSE Studio .iso creator by Kumba.

PostPosted: Fri Feb 17, 2012 5:26 am
by nkasoff
I just switched from to GoAutodial to Vicibox at the recommendation of somebody who shall remain nameless, and had the same problem on my Dell PowerEdge 2850. Strange thing is, it worked fine at my office, then decided to stop working at my customer site. So I brought the system back to my office, reinstalled, and had the problem as soon as I rebooted. So now, I'm reinstalling GoAutodial in hopes that I can resolve the "8168 not working" problem by some other means than moving to Vicibox. Grrrr.

PostPosted: Fri Feb 17, 2012 6:31 pm
by williamconley
which version of Vicibox?