Changes

===Backup/Restore===

===Backup/Restore===

*Using a combination of hardware and software compression for tape backup causes errors

====Using a combination of hardware and software compression for tape backup causes errors====

You should use only one of software or hardware compression. Doing both may exercise bugs, and won't reduce the size of data on the tape - it is more likely to increase it.  

You should use only one of software or hardware compression. Doing both may exercise bugs, and won't reduce the size of data on the tape - it is more likely to increase it.  

<!--[[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1276860&amp;group_id=96750]]-->

<!--[[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1276860&amp;group_id=96750]]-->

    

    

*Backup to desktop 4GB limit

====Backup to desktop 4GB limit====

As in previous versions of SME Server, the backup to desktop function has a limit of 4GB. It's not fixable until we know where the limit or limits are. All these components are involved in transferring the backup file, and at least one of them is truncating at 4GB: tar, perl, mod_proxy, apache, TCP stack, browser at desktop end. See this bug listing for details [[bugzilla:701]]

As in previous versions of SME Server, the backup to desktop function has a limit of 4GB. It's not fixable until we know where the limit or limits are. All these components are involved in transferring the backup file, and at least one of them is truncating at 4GB: tar, perl, mod_proxy, apache, TCP stack, browser at desktop end. See this bug listing for details [[bugzilla:701]]

*Losing too many ticks

*Losing too many ticks

A kernel bug with Athlon64 processors may cause the system to run slowly, possibly fixed with a later kernel

A kernel bug with Athlon64 processors may cause the system to run slowly, possibly fixed with a later kernel

*VGA problem with VIA EPIA board

*VGA problem with VIA EPIA board

Once the installer loads the VGA display loses sync and it is impossible to read what is being displayed. There is a workaround, see this bug report for details: [[ Bugzilla:236 ]]

Once the installer loads the VGA display loses sync and it is impossible to read what is being displayed. There is a workaround, see this bug report for details: [[ Bugzilla:236 ]]

*VIA EPIA CL1000 (dual LAN, single processor)

*VIA EPIA CL1000 (dual LAN, single processor)

The smp kernal fails to boot - non-smp works like a charm...

The smp kernal fails to boot - non-smp works like a charm...

 

====Slow Disk Format====

*Slow Disk Format

Installing 2 discs as Primary and Secondary on the same IDE channel may cause

Installing 2 discs as Primary and Secondary on the same IDE channel may cause

slow formatting and is not a very good idea because:

slow formatting and is not a very good idea because:

1-May hamper system performance.

# May hamper system performance.

# Does not provide system redundancy if you loose the IDE channel.

====Why does my clock run too fast in SME Server under VMware?====

 

 

*Why does my clock run too fast in SME Server under VMware?

If you are testing SME Server on VMware, you may notice the clock doen't keep time accurately. <!--- See this bug report for details and a possible fix.  

If you are testing SME Server on VMware, you may notice the clock doen't keep time accurately. <!--- See this bug report for details and a possible fix.  

[[http://sourceforge.net/tracker/index.php?func=detail&amp;aid=1303401&amp;group_id=96750&amp;atid=615772]] --->

[[http://sourceforge.net/tracker/index.php?func=detail&amp;aid=1303401&amp;group_id=96750&amp;atid=615772]] --->

Perhaps this might be of use: [http://synapticsolutions.com.au/?page_id=28 <nowiki>Synaptic: Clock Running fast in CentOS 4.3 [SME7] Guest</nowiki>]

Perhaps this might be of use: [http://synapticsolutions.com.au/?page_id=28 <nowiki>Synaptic: Clock Running fast in CentOS 4.3 [SME7] Guest</nowiki>]

    

    

*Boot failure after install if you have enabled hardware raid

====Boot failure after install if you have enabled hardware raid====

There sometimes seem to be conflicts with the SME Server automatic software raid setup in combination with hardware raid. Disabling the hardware raid in your motherboard or controller card's bios is the suggested fix. <!--- See these bug reports for details:  

There sometimes seem to be conflicts with the SME Server automatic software raid setup in combination with hardware raid. Disabling the hardware raid in your motherboard or controller card's bios is the suggested fix. <!--- See these bug reports for details:  

[[https://sourceforge.net/tracker/index.php?func=detail&amp;aid=1286560&amp;group_id=96750&amp;atid=615772]]

[[https://sourceforge.net/tracker/index.php?func=detail&amp;aid=1286560&amp;group_id=96750&amp;atid=615772]]

[[https://sourceforge.net/tracker/index.php?func=detail&amp;aid=1304784&amp;group_id=96750&amp;atid=615772]] -->

[[https://sourceforge.net/tracker/index.php?func=detail&amp;aid=1304784&amp;group_id=96750&amp;atid=615772]] -->

 

====Booting in SMP mode results in kernel panic with certain hardware====

*Booting in SMP mode results in kernel panic with certain hardware

The combination of a 2MB Cache P4 3.0GHZ CPU, and a Giga-byte GA-81848P775-G (Intel 848P chipset) motherboard produces this problem. Other simialar hardware may be affected. <!-- If you encounter this problem, see this bug report for a workaround.  

The combination of a 2MB Cache P4 3.0GHZ CPU, and a Giga-byte GA-81848P775-G (Intel 848P chipset) motherboard produces this problem. Other simialar hardware may be affected. <!-- If you encounter this problem, see this bug report for a workaround.  

[[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1325350&amp;group_id=96750]]-->

[[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1325350&amp;group_id=96750]]-->

    

    

 

====Legacy ~MegaRAID driver is no longer included====

*Legacy ~MegaRAID driver is no longer included

Certain raid cards that worked under SME Server 6, do not work under SME Server 7.  

Certain raid cards that worked under SME Server 6, do not work under SME Server 7.  

[[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1274199&amp;group_id=96750]] -->

[[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1274199&amp;group_id=96750]] -->

*Raid on HP server Proliant ML330 with adaptec RAID is unsupported

Raid on HP server Proliant ML330 with adaptec RAID is unsupported

*aic7xxx driver hangs on installation boot

====aic7xxx driver hangs on installation boot====

On some Compaq Proliant servers (specifically an ML370 G2), &amp; possibly others, the aic7xxx driver will hang if there is nothing connected to the adaptor or if it is not terminated correctly. On most Proliants you can tell the BIOS to not allocate an IRQ to the device which effectively disables it; the ML370 G2 uses an AIC-7899 chip on the motherboard. This problem also exists in the ~CentOS 4.3 base. SME 6.0 loads fine which would seem to indicate that the newer driver in ~CentOS 4.3 can't handle the older system (this Proliant is probably 5 years old). [[Bugzilla:373]]

On some Compaq Proliant servers (specifically an ML370 G2), &amp; possibly others, the aic7xxx driver will hang if there is nothing connected to the adaptor or if it is not terminated correctly. On most Proliants you can tell the BIOS to not allocate an IRQ to the device which effectively disables it; the ML370 G2 uses an AIC-7899 chip on the motherboard. This problem also exists in the ~CentOS 4.3 base. SME 6.0 loads fine which would seem to indicate that the newer driver in ~CentOS 4.3 can't handle the older system (this Proliant is probably 5 years old). [[Bugzilla:373]]

 

====Anaconda doesn't support >2Tb====

*Anaconda doesn't support >2Tb

Installing on large storage devices will take a significant amount of work. see [[Bugzilla:1963]]

Installing on large storage devices will take a significant amount of work. see [[Bugzilla:1963]]

 

====Older systems stop at reboot====

*Older systems stop at reboot

This may be an issue from the older P2 and early P3 era BIOS'es but the problem may also occur on some newer chipsets, that don't follow the "specs" for power saving features. Also, this problem seems to be more prevalent in multi-CPU machines. Only a kernel change could provide a real fix to this issue.

This may be an issue from the older P2 and early P3 era BIOS'es but the problem may also occur on some newer chipsets, that don't follow the "specs" for power saving features. Also, this problem seems to be more prevalent in multi-CPU machines. Only a kernel change could provide a real fix to this issue.

For some motherboards, there may be a workaround by adding appropriate text to the grub config.

For some motherboards, there may be a workaround by adding appropriate text to the grub config.

The addition of the noapic and acpi=off to etc/grub.conf might solve the problem of reboots failing.

The addition of the noapic and acpi=off to etc/grub.conf might solve the problem of reboots failing.

 

*I'm burning the SMESERVER cd. When I check the md5sum on this burner, it returns an *incorrect* value. What gives?

I'm burning the SMESERVER cd. When I check the md5sum on this burner, it returns an *incorrect* value. What gives?

Try a different cd burner. We've found in the past that some drives provide an extra garbage block when reading back the image. This results in an incorrect md5sum value.

Try a different cd burner. We've found in the past that some drives provide an extra garbage block when reading back the image. This results in an incorrect md5sum value.

====My Adaptec DPT raid controller is not migrated on upgrade. What gives?====

 

 

*My Adaptec DPT raid controller is not migrated on upgrade. What gives?

The Adaptec DPT raid controller won't work for upgrades. However, the Adaptec DPT raid controller works on new installs. For details visit: [[bugzilla:833]]

The Adaptec DPT raid controller won't work for upgrades. However, the Adaptec DPT raid controller works on new installs. For details visit: [[bugzilla:833]]

 

*I've loaded the SMESERVER into my hardware without problems. Now my SMESERVER freezes when I reboot. What gives?

I've loaded the SME Server on my hardware without problems. Now my SME Server freezes when I reboot. What gives?

Most likely this is a problem with the video card or sound card. The best fixes are to replace the video/sound card, disable the video/sound in the bios (if it's integrated on the motherboard) or remove the video/sound card altogether. Video/sound isn't needed on the SMESERVER and can be managed via the SERVER-MANAGER.  

Most likely this is a problem with the video card or sound card. The best fixes are to replace the video/sound card, disable the video/sound in the bios (if it's integrated on the motherboard) or remove the video/sound card altogether. Video/sound isn't needed on the SME Server and can be managed via the server-manager.  

Please note that other hardware devices such as CD-ROM drives as well as mismatched IDE cables may cause a problem, (i.e. kernel panic on reboot after installation). For details, visit: [[bugzilla:985]]

Please note that other hardware devices such as CD-ROM drives as well as mismatched IDE cables may cause a problem, (i.e. kernel panic on reboot after installation). For details, visit: [[bugzilla:985]]

 

*My SMESERVER suddenly stopped working. I look in the log messages I see: kernel: ata1: command 0x35 timeout, stat 0x50 host_stat 0x1. Any ideas what could be causing this?

My SME Server suddenly stopped working. I look in the log messages I see: kernel: ata1: command 0x35 timeout, stat 0x50 host_stat 0x1. Any ideas what could be causing this?

Most likely, this is either a hardware or BIOS problem or a kernel bug. It's very unlikely we can fix any of those. However, you can try editing /etc/grub/grub.conf. In this file, close to the top, you'll see the latest kernel. It looks like this:  

Most likely, this is either a hardware or BIOS problem or a kernel bug. It's very unlikely we can fix any of those. However, you can try editing /etc/grub/grub.conf. In this file, close to the top, you'll see the latest kernel. It looks like this:  

  kernel /vmlinuz-2.6.9-42.0.10.EL ro root=/dev/vg_primary/lv_root

  kernel /vmlinuz-2.6.9-42.0.10.EL ro root=/dev/vg_primary/lv_root

Then reboot. Hopefully the problem goes away.

Then reboot. Hopefully the problem goes away.

 

====Is there a problem installing SME Server with my NFORCE motherboard?====

*Is there a problem installing SMESERVER with my NFORCE motherboard?

Submitted reports claim that nForce boards based on the 410 or 430 chipset won't work [[bugzilla:1240]].

Submitted reports claim that nForce boards based on the 410 or 430 chipset won't work [[bugzilla:1240]].

*Is there a problem installing SMESERVER with my ZIP drive?

====Is there a problem installing SME Server with my laptop?====

 

 

*Is there a problem installing SMESERVER with my laptop?

SME Server has never supported laptop PCMCIA network adaptors.  This being said, some possible workarounds have been identified in [[bugzilla:1246]]

SME Server has never supported laptop PCMCIA network adaptors.  This being said, some possible workarounds have been identified in [[bugzilla:1246]]

 

====Symbios 53c895 scsi raid card====

*Symbios 53c895 scsi raid card

This is a hardware issue. It worked with SME6 but doesn't work with SME7.

This is a hardware issue. It worked with SME6 but doesn't work with SME7.

===Installation (not hardware related) &amp; Initial Configuration===

===Installation (not hardware related) &amp; Initial Configuration===

*Why is there a delay after verifying administrator password?

====Why is there a delay after verifying administrator password?====

On "slow" system, there is a delay (2-5 seconds) after verifying administrator password. This is because the password is actually set and checked at this point. Everything else we wait until the script is done to perform any actions.  

On "slow" system, there is a delay (2-5 seconds) after verifying administrator password. This is because the password is actually set and checked at this point. Everything else we wait until the script is done to perform any actions.  

<!--[[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1264659&amp;group_id=96750]]-->

<!--[[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1264659&amp;group_id=96750]]-->

 

====Use /server-manager, not /e-smith-manager====

*Use /server-manager, not /e-smith-manager

In previous versions, both aliases worked, but in SME Server 7 you must use /server-manager to access the server manager.  

In previous versions, both aliases worked, but in SME Server 7 you must use /server-manager to access the server manager.  

<!--[[https://sourceforge.net/tracker/?func=detail&atid=615772&aid=1275334&group_id=96750]]-->

<!--[[https://sourceforge.net/tracker/?func=detail&atid=615772&aid=1275334&group_id=96750]]-->

 

====Why can the system not be named 'mail', 'ftp' or 'www'?====

*Why can the system not be named 'mail', 'ftp' or 'www'?

If you choose one of these for the hostmane of your server, the atalk (Appletalk) service will have errors and fail. <!--See these bug listings for details:  

If you choose one of these for the hostmane of your server, the atalk (Appletalk) service will have errors and fail. <!--See these bug listings for details:  

[[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1223012&amp;group_id=96750]] [[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1264588&amp;group_id=96750  -->

[[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1223012&amp;group_id=96750]] [[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1264588&amp;group_id=96750  -->

 

====Why is there no option to create reinstallation disk?====

*Why is there no option to create reinstallation disk?

There is no option to create a reinstallion disk during installation or later from the Administration section of the server-manager.   

There is no option to create a reinstallion disk during installation or later from the Administration section of the server-manager.   

This is intentional, since it required too much effort to keep it up-to-date as kernels change. The CD contains a rescue mode, which is a better environment for fixing problems, and a reinstall followed by a restore of the configuration works well without us supporting another method.  

This is intentional, since it required too much effort to keep it up-to-date as kernels change. The CD contains a rescue mode, which is a better environment for fixing problems, and a reinstall followed by a restore of the configuration works well without us supporting another method.  

*4 disk install - md1 is raid1 and md2 is raid5

====4 disk install - md1 is raid1 and md2 is raid5====

Even if you have 4 (or more) disks, which are supported by your motherboard and ~CentOS, md1 is always set up as a 4 disk raid1. This is, because you can't boot off a raid-5. md1 is the boot partition and must either be non-raid or raid-1. md2 will be set up as a 4 disk raid5 as expected.  

Even if you have 4 (or more) disks, which are supported by your motherboard and ~CentOS, md1 is always set up as a 4 disk raid1. This is, because you can't boot off a raid-5. md1 is the boot partition and must either be non-raid or raid-1. md2 will be set up as a 4 disk raid5 as expected.  

More information can be found in [[bugzilla:759]].

More information can be found in [[bugzilla:759]].

 

====Anaconda crash from rescue mode when starting network interfaces====

*Anaconda crash from rescue mode when starting network interfaces

There is a problem with the installer and as networking is not essential for a rescue function it won't be fixed any time soon.  Note however that this is no longer an issue with version 7.2. [[bugzilla:712]]

There is a problem with the installer and as networking is not essential for a rescue function it won't be fixed any time soon.  Note however that this is no longer an issue with version 7.2. [[bugzilla:712]]

 

====On first boot after installation, system name appears on terminal 1 while on terminal 2 and 3 it shows as "localhost". ====

*On first boot after installation, system name appears on terminal 1 while on terminal 2 and 3 it shows as "localhost".  

This is because the gettys on tty2 and tty3 are started before the configuration wizard runs, and therefore before the system name has been set. Also note that the correct system name is displayed after someone logs out from VT2 or VT3?)

This is because the gettys on tty2 and tty3 are started before the configuration wizard runs, and therefore before the system name has been set. Also note that the correct system name is displayed after someone logs out from VT2 or VT3?)

 

====The installation gave an exception when trying to format already formatted disks====

*The installation gave an exception when trying to format already formatted disks.

In some cases, you may have to manually wipe re-used disks.

In some cases, you may have to manually wipe re-used disks.