SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264
Anonymous | Login | 2021-01-22 18:50 UTC | ![]() |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
0003524 | Endian Firewall | Installation | public | 2011-03-08 03:51 | 2011-03-25 15:27 | ||||||
Reporter | narikki | ||||||||||
Assigned To | lorenzo-endian | ||||||||||
Priority | normal | Severity | major | Reproducibility | always | ||||||
Status | feedback | Resolution | open | ||||||||
Platform | OS | OS Version | |||||||||
Product Version | 2.4.1 | ||||||||||
Target Version | Fixed in Version | ||||||||||
Summary | 0003524: Endless looping of usbhid messages as reported | ||||||||||
Description | Installation of efw 2.4/2.4.1 DL380G4: Unsuccessful as the aforementioned problem persisted. Endless looping of usbhid messages as reported above: ... FATAL: Module usbhid not found Running command: /bin/mount -t usbfs none /proc/bus/usb ... failed: device or resource busy running command /bin/mountsource.sh scanning source media ... | ||||||||||
Tags | No tags attached. | ||||||||||
Attached Files | |||||||||||
![]() |
|
(0005867) lorenzo-endian (manager) 2011-03-08 07:22 |
Hi narikki, are you using any hardware/software raid? in that case, can you try to disable it and run the installer again? If you have 2 hdd, the installer creates a software raid (RAID1) during the installation. Thanks a lot Lo |
(0005995) bacanol (reporter) 2011-03-20 12:29 |
Hi all! I have got the same issue with 2.4 and 2.4.1 on Fujitsu Siemens Futro S400. I did a bit of research and it seems to me that this is due a missing driver. If I proceed I will try to give additional feedback on this. Best regards, Nico |
(0006012) lorenzo-endian (manager) 2011-03-25 10:17 |
Hi all, the driver could be a feasible source of this problem :/ I will wait for a feedback from you! Thanks in advance! Lo |
(0006016) bacanol (reporter) 2011-03-25 15:27 |
Hi Lorenzo, I did a little bit of investigation and I found that an installation from internal CDROM with the nousb boot option is working. I think there might be a missing module for the kernel. After installation on the target drive the system is booting ok, without any errors. So there must be a difference in the install environment and the installed environment. I hope this helps. Best regards, Nico |
![]() |
|||
Date Modified | Username | Field | Change |
2011-03-08 03:51 | narikki | New Issue | |
2011-03-08 07:22 | lorenzo-endian | Note Added: 0005867 | |
2011-03-08 07:22 | lorenzo-endian | Assigned To | => lorenzo-endian |
2011-03-08 07:22 | lorenzo-endian | Status | new => feedback |
2011-03-20 12:29 | bacanol | Note Added: 0005995 | |
2011-03-25 10:17 | lorenzo-endian | Note Added: 0006012 | |
2011-03-25 15:27 | bacanol | Note Added: 0006016 |
Copyright © 2000 - 2012 MantisBT Group |