This is likely a firmware bug on this device. target_core_get_fabric() failed for test_mkdir systemd: Unit rvice entered failed state. systemd-modules-load: Module 'sunrpc' is builtin systemd-modules-load: Module 'crc_itu_t' is builtin systemd-modules-load: Module 'firewire_core' is builtin systemd-modules-load: Module 'firewire_ohci' is builtin systemd-modules-load: Module 'libcrc32c' is builtin firewire_core 0000:05:09.3: refreshed device fw0 tsc: Refined TSC clocksource calibration: 2793.181 MHz usb 4-2: new low-speed USB device number 2 using uhci_hcd firewire_core 0000:05:09.3: created device fw0: GUID xxxxxxGUIDxxxxxx, S400 input: GenPS/2 Genius Mouse as /devices/platform/i8042/serio1/input/input2 ehci-pci 0000:00:1d.7: setting latency timer to 64
CONFIGURE JBOD IN DISK GENIUS DRIVER
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
firewire_ohci 0000:05:09.3: added OHCI v1.0 device as card 0, 4 IR + 8 IT contexts, quirks 0x41 | grep -B1 -A3 -iE '(firewire|1394|sbp|configfs|Configuration File System|targetcore|targetd|tcm|tgt|iblock|iscsi|pscsi|corehba|T10|VPD|targetcli)' # CONFIG_FIREWIRE_OHCI_REMOTE_DMA is not set # Supported FireWire (IEEE 1394) Adapters | grep -B1 -A2 -iE '(firewire|1394|sbp|configfs|Configuration File System|targetcore|targetd|tcm|tgt|iblock|iscsi|pscsi|corehba|T10|VPD|targetcli)' Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-Ĭat /boot/config-3.11.686 Region 0: Memory at fc511000 (32-bit, non-prefetchable) Ĭapabilities: Power Management version 2įlags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2+,D3hot+,D3cold+) Latency: 64 (8000ns max), Cache Line Size: 64 bytes Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- It's an HP Pentium-4 minitower PC with a VIA-chip Firewire+USB PCI-card fitted.įedora-19-LXDE with plenty of yum-installed extra tools, all updated. The dearth of detail around targetcli + Firewire IEEE1394 is worrying. Worth asking, has anyone actually achieved a JBOD set-up with current software? I'll only be able to help troubleshoot if instructions are explicit and comprehensive.īut I'm willing to do my best, as far as my circumstances and abilities allow. I grasp certain ideas, but know nothing of the nut-and-bolts which you guys deal with. Sadly, although I can cobble Bash scripts together, I'm neither a coder nor CS graduate. I wish I could offer more than just ignorant questions. Something exposing some other deeper kernel/driver issues? Is targetcli (installed using yum) involved at all in that set-up?Īs you yourselves mused in the links above, maybe Fedora's CONFIGFS_FS=y is somehow culpable?Ĭompounded by dracut/systemd voodoo? Hyper-threading SMP complications? PCI-card quirks? So I wonder whether the set-up of the configfs is somehow not quite right. Mind you, mkdir will not create for me anything higher up the /sys/kernel/config tree either. Which seems odd, given the (2012-vintage Linux-3.4, sans-targetcli) direct strategy here : Mkdir: cannot create directory '/sys/kernel/config/target/sbp/eui.xxxxxxGUIDxxxxxx': Invalid argument # mkdir -pvm777 /sys/kernel/config/target/sbp/eui.xxxxxxGUIDxxxxxxCONFIGURE JBOD IN DISK GENIUS PC
0 kommentar(er)
