mpt2sas: SATA Initialization Failed - Linux does not create any block devices for PUIS drives behind SAS expander

2012-12-21 Thread CrashPlan Pro
kernel 2.6.32-5-amd64 linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=61dd0022-387c-4fb8-9532-a4af17aa4af3 ro clocksource=hpet hpet=force raid=noautodetect scsi_mod.scan=async selinux=0 noisapnp verbose MPT2BIOS-07.29.00.00 (loading of this BIOS is disabled in Ami PC BIOS) SAS2008-IT 15.00.00.00

What does scsi IO state flag 0x0C (= 0x08 && 0x04 == terminated && no scsi status) mean?

2012-12-31 Thread CrashPlan Pro
mpi2_init.h contains: #define MPI2_SCSI_STATE_TERMINATED (0x08) #define MPI2_SCSI_STATE_NO_SCSI_STATUS (0x04) What does it mean when for each SCSI IO (REPORT_LUNS, TEST_UNIT_READY) the state flag 0x0C (= 0x08 && 0x04) is returned? -- To unsubscribe from this list: send the

Re: Disk spin-up optimization during system resume

2014-01-20 Thread CrashPlan Pro
Dan Williams wrote at 18-01-14 05:09: Larger systems are less likely to ever sleep. I have to agree with this. There is almost no storage server that will be suspended to sleep. Users of storage servers rather see an improvement at reboot time. For example by not re-enumerating all 40 / 80