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
MantisBT - Endian Firewall | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000882 | Endian Firewall | Hardware related (kernel, drivers, hardware) | public | 2008-05-28 19:35 | 2008-07-27 20:18 |
| Reporter | peter-endian | ||||
| Assigned To | peter-endian | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | 2.2-rc2 | Fixed in Version | 2.2-rc2 | ||
| Customer Importance | |||||
| Customer Occurrences | |||||
| Queue | |||||
| Summary | 0000882: RAID: reinstallation causes raid to block installation until sync is finished | ||||
| Description | when a system will be reinstalled which has disks which have been within a raid before, the installer will block during installation and wait until the raid have been completely rebuild. (may take about 70 hours, with 160G disks) When this happens, the kernel gives this error: md: created mdX md: bind <hdaX> md: bind <hdcX> md: running: <hdcX><hdaX> md: mdX: raid array is not clean -- starting background reconstruction md: personality for level 1 is not loaded! md: do_md_run() returned -22 md: mdX: stopped. md: unbind<mdX> i think this is the following bug: http://lkml.org/lkml/2007/12/27/45 [^] .. page includes kernel-patch which seems to fix the problem. Probably it is also sufficient to do the following within installer before creation of the new md devices: mdadm --zero-superblock /dev/hda1 mdadm --zero-superblock /dev/hda3 mdadm --zero-superblock /dev/hda4 mdadm --zero-superblock /dev/hdc1 mdadm --zero-superblock /dev/hdc3 mdadm --zero-superblock /dev/hdc4 After this the disks should be non-raid disks and no kernel should start reconstruction of the raid .. (?) | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2008-05-28 19:35 | peter-endian | New Issue | |||
| 2008-06-03 10:07 | peter-endian | Target Version | 2.2 => 2.2-rc2 | ||
| 2008-06-03 15:40 | peter-endian | Issue cloned: 0000904 | |||
| 2008-06-03 15:47 | peter-endian | Status | new => resolved | ||
| 2008-06-03 15:47 | peter-endian | Fixed in Version | => 2.2-rc2 | ||
| 2008-06-03 15:47 | peter-endian | Resolution | open => fixed | ||
| 2008-06-03 15:47 | peter-endian | Assigned To | => peter-endian | ||
| 2008-06-03 15:47 | peter-endian | Note Added: 0001282 | |||
| 2008-07-27 20:18 | peter-endian | Status | resolved => closed | ||
| Notes | |||||
|
|
|||||
|
|
||||