similar to: Help/Advice needed

Graham Bentley wrote: > Recently swapped out my Sony for a HP DAT and > got this first time in dmesg > > (sa0:ahc0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 0 0 > (sa0:ahc0:0:6:0): CAM Status: SCSI Status Error > (sa0:ahc0:0:6:0): SCSI Status: Check Condition > (sa0:ahc0:0:6:0): UNIT ATTENTION asc:28,0 > (sa0:ahc0:0:6:0): Not ready to ready change, medium may

Hello, I am trying to use a 1.5TB Eonstor raid array with FreeBSD 7.0, but I don't understand whether it is the raid or the scsi card or something else that is causing the computer problems when accessing the raid. My problem is that soon after recognizing the attached disk during boot, FreeBSD appears to hang for about 10 seconds and then says ahd0: Recovery Initiated - Card

Hi folks, I''ve been asked to post my experiences here, so... well, here goes :) (in no particular order). We can view bugs in kernel/xen via bugs.opensolaris.org, but not file them against kernel/xen. Could that be added to the list of categories for submission? There''s kind of a composite set of problems with bootadm(1M). While the modified bootadm will update

Greetings, I sent the message below to the developer of the contributed R package "sspir", but have yet to receive any response. I would be very grateful for any advice people have on the matter. Thanks, Mark -------- Original Message -------- Subject: possible bug in sspir? Date: Tue, 19 May 2009 16:08:41 -0700 From: Mark Scheuerell <mark.scheuerell at noaa.gov> To:

I have one thing happening now at boot which must have happened during the migration to zfs boot. I get an error message about /dev/random: "No randomness provider enabled for /dev/random. Use cryptoadm to provide one." Does anyone know how to fix this? Another thing: Is it possible to upgrade to a higher build when using zfs boot? Is this what LiveUpgrade does? And is there a step by

Hello ,,,, can liveupgrade be done zfs i am running snv_35 on sparc if so how tks art This message posted from opensolaris.org

Hello ,,,, can liveupgrade be done zfs i am running snv_35 on sparc if so how tks art This message posted from opensolaris.org

Hi, Yesterday I got all my disks in two zpool disconected. They are not real disks - LUNS from StorageTek 2530 array. What could that be - a failing LSI card or a mpt driver in 2009.06? After reboot got four disks in FAILED state - zpool clear fixed things with resilvering. Here is how it started (/var/adm/messages) Feb 23 12:39:03 nexus scsi: [ID 365881 kern.info] /pci at 0,0/pci10de,5d at

I''m curious about if there are any potential problems with using LVM metadevices as ZFS zpool targets. I have a couple of situations where using a device directly by ZFS causes errors on the console about "Bus and lots of "stalled" I/O. But as soon as I wrap that device inside an LVM metadevice and then use it in the ZFS zpool things work perfectly fine and smoothly (no

Hello I have a strange issue, I''m having a setup with 24 disk enclosure connected with LSI3801-R. I created two pools. Pool have 24 healthy disks. I disabled LUN persistency on the LSI adapter. When I cold boot the server (power off by pulling all power cables), a warning is shown on the console during boot: .... WARNING: /pci/path/ ... (mpt0): wwn for traget has changed

This patch implements a checker to detect instructions which should be paravirtualized instead of direct writing raw instruction. This patch does rough check so that it doesn't fully cover all cases, but it can detects most cases of paravirtualization breakage of hand written assembly codes. Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: "Luck, Tony"

This patch implements a checker to detect instructions which should be paravirtualized instead of direct writing raw instruction. This patch does rough check so that it doesn't fully cover all cases, but it can detects most cases of paravirtualization breakage of hand written assembly codes. Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: "Luck, Tony"

Hello All, I 've gotten myself into trouble by running out of disk space. On an all-in-one Ovirt system some users have filled up a Windows7 virtual machine and in doing so filled up an nfs mount and in doing so filled up a root partition: B estandssysteem Grootte Gebruikt Besch Geb% Aangekoppeld op /dev/mapper/centos-root 50G 46G 4,8G 91% / devtmpfs 7,9G 0 7,9G 0% /dev tmpfs 7,9G 0

After a liveupgrade and luactivate I can login to the -new- BE. My question is: do I have to luactive the -old- BE again if I want to chose that one from the grub menu or can I just run it if I want to. -- Dick Hoogendijk -- PGP/GnuPG key: 01D2433D + http://nagual.nl/ | SunOS sxce snv107 ++ + All that''s really worth doing is what we do for others (Lewis Carrol)

Maybe not a good assumption afterall -- I can no longer boot using kernel 3.10.0-514 or 3.10.0-862. boot.log shows: Dependency failed for /mnt/data Dependency failed for Local File Systems Dependency failed for Mark the need to relabel after reboot. Dependency failed for Migrate local SELinux policy changes from the old store structure to the new structure. Dependency failed for Relabel all

I posted a thread on this once long ago[1] -- but we''re still fighting with this problem and I wanted to throw it out here again. All of our hardware is from Silicon Mechanics (SuperMicro chassis and motherboards). Up until now, all of the hardware has had a single 24-disk expander / backplane -- but we recently got one of the new SC847-based models with 24 disks up front and 12 in the

Dear List The UKgas data is stored as an object of class 'ts'. I am trying to use "UKgas" in a formula as argument to a function. However, I do not know how to access the 'time series' information in the response (such as start() end() etc.). Here is a boiled down example. ssm <- function(formula, data = list(),subset=NULL) { cl <- match.call() if

Hi, Xiantao a comments is below. >+// 0x3000 Entry 12 (size 64 bundles) External Interrupt (4) >+ENTRY(kvm_interrupt) >+ mov r31=pr // prepare to save predicates >+ mov r19=12 >+ mov r29=cr.ipsr >+ ;; >+ tbit.z p6,p7=r29,IA64_PSR_VM_BIT >+ tbit.z p0,p15=r29,IA64_PSR_I_BIT >+ ;; >+(p7) br.sptk kvm_dispatch_interrupt >+ ;; >+ mov

Hi, Xiantao a comments is below. >+// 0x3000 Entry 12 (size 64 bundles) External Interrupt (4) >+ENTRY(kvm_interrupt) >+ mov r31=pr // prepare to save predicates >+ mov r19=12 >+ mov r29=cr.ipsr >+ ;; >+ tbit.z p6,p7=r29,IA64_PSR_VM_BIT >+ tbit.z p0,p15=r29,IA64_PSR_I_BIT >+ ;; >+(p7) br.sptk kvm_dispatch_interrupt >+ ;; >+ mov

When I change /etc/fstab from /dev/mapper/lvol001 to /dev/lvm_pool/lvol001, kernel 3.10.0-514 will boot. Kernel 3.10.0-862 hangs and will not boot. On Sat, Jul 14, 2018 at 1:20 PM Mike <1100100 at gmail.com> wrote: > > Maybe not a good assumption afterall -- > > I can no longer boot using kernel 3.10.0-514 or 3.10.0-862. > > boot.log shows: > > Dependency failed for