limetech Posted November 18, 2010 Author Share Posted November 18, 2010 There seems to be allot of change to the interface driver's output. Does mdVersion still exist? Does it change when the interface changes? That could be a tell tale sign for future validation. Guess it depends on what you think is "allot" The 'kernel oops' bug fix was actually found and fixed in 5.0-beta, so I am using that driver in 4.6-rc1. There are a few other changes in the driver done during 5.0 development (such as elimination of diskNumber variable). I have always considered the driver interface to be "private" though in practice it's used (via mdcmd) obviously by 3rd party add-ons. The intent is that with 5.0 I can make the driver interface truly private (because I'm planning big changes), but I guess this is a 5.0 discussion. In the meantime, I desire to restore any functionality necessary to get 4.6 100% backward compatible. Link to comment
limetech Posted November 18, 2010 Author Share Posted November 18, 2010 Other things I noticed is that mdresyncpros, mdresyncprcnt, mdresyncfinish, mdresyncspeed, rdevNumreads and rdevnumwrites has been added with the rc1. Also, cmdoper and cmdresult has been removed. mdResync* variables used to only be present when a parity check/sync was in operation, now they are always present but with values 0 if no check/sync operation in progress. rdevNum* have come and go in various revisions. cmdOper and cmdResult are no longer necessary due to way communication is handled with driver (i.e., the bug fix). These last two I really do not want to add back in unless it breaks an existing 3rd party add-on. Link to comment
Joe L. Posted November 18, 2010 Share Posted November 18, 2010 Other things I noticed is that mdresyncpros, mdresyncprcnt, mdresyncfinish, mdresyncspeed, rdevNumreads and rdevnumwrites has been added with the rc1. Also, cmdoper and cmdresult has been removed. cmdOper and cmdResult are no longer necessary due to way communication is handled with driver (i.e., the bug fix). These last two I really do not want to add back in unless it breaks an existing 3rd party add-on. I don't know of anything using those two cmd* variables Joe L. Link to comment
NAS Posted November 18, 2010 Share Posted November 18, 2010 Yeah, however it wasnt, Possibly a glitch in the matrix and I was silly enough not to backup first. Minutes of work to rectify though once I had found a KB and monitor If you only copied over bzimage/bzroot, it's not possible for the other settings to be lost, unless perhaps you have a bad Flash device. Either A: I had a brain fart and i copied over the raw files or B: i had a flash funny. This box hasnt be rebooted for a long time and is used constatly. It highly possible it was A but either way its no big deal. Something to ponder, perhaps the defauly config file should be created if they are not there on boot allowing them not to be included in the distribution removing any chance of this happening. Failrly typical for that procedure to be used. Anyways ta for the support. Link to comment
limetech Posted November 18, 2010 Author Share Posted November 18, 2010 Something to ponder, perhaps the defauly config file should be created if they are not there on boot allowing them not to be included in the distribution removing any chance of this happening. Failrly typical for that procedure to be used. That's a good idea. Link to comment
limetech Posted November 18, 2010 Author Share Posted November 18, 2010 4.6-rc2 now available. Link to comment
abs0lut.zer0 Posted November 18, 2010 Share Posted November 18, 2010 If you only copy over bzimage/bzroot files from download to your Flash, everything else should be preserved. sorry, just to confirm to upgrade from working v4.5.6 to 4.6rc1 i just need 2 files from the whole download? thanks and all SHOULD be well....? Link to comment
Joe L. Posted November 18, 2010 Share Posted November 18, 2010 If you only copy over bzimage/bzroot files from download to your Flash, everything else should be preserved. sorry, just to confirm to upgrade from working v4.5.6 to 4.6rc1 i just need 2 files from the whole download? thanks and all SHOULD be well....? correct. bzroot, and bzimage. Link to comment
abs0lut.zer0 Posted November 18, 2010 Share Posted November 18, 2010 If you only copy over bzimage/bzroot files from download to your Flash, everything else should be preserved. sorry, just to confirm to upgrade from working v4.5.6 to 4.6rc1 i just need 2 files from the whole download? thanks and all SHOULD be well....? correct. bzroot, and bzimage. Thanks Joe L Lets hope all goes well and i don't have another incident...!! Link to comment
bubbaQ Posted November 18, 2010 Share Posted November 18, 2010 For the folks looking for cpufreq support.... On my AMD bench, cold unRAID boot showed: CPU type : AMD Athlon II X2 260 Processor CPU speed : 3214.576 MHz The driver for my system is powernow-k8, so run: modprobe powernow-k8 Now it reports: CPU type : AMD Athlon II X2 260 Processor Min/Max frequency : 800/3200 MHz Current frequency : 800 MHz Frequency governor : ondemand Freq. scaling driver : powernow-k8 The available drivers are in: /lib/modules/2.6.32.9-unRAID/kernel/arch/x86/kernel/cpu/cpufreq/ Here’s description for the kernel drivers: * acpi-cpufreq: uses ACPI Processor P-States, common to many modern motherboards/CPU’s. * cpufreq-nforce2: uses FSB changing on motherboards using the nForce2 chipset. * p4-clockmod: cpufreq driver for Pentium 4/Xeon (and possibly the Core2) * powernow-k6: PowerNow! driver for AMD K6-2+ / K6-3+ processors. * powernow-k7: Powernow driver for AMD K7 processors. * powernow-k8: AMD Athlon 64 and Opteron processor frequency driver. * speedstep-lib: Library for Intel SpeedStep 1 or 2 cpufreq drivers. so pick the right one for your system, and modprobe it. Link to comment
Kewjoe Posted November 18, 2010 Share Posted November 18, 2010 Just installed 4.6-rc2, so far so good. Link to comment
Kewjoe Posted November 18, 2010 Share Posted November 18, 2010 For the folks looking for cpufreq support.... On my AMD bench, cold unRAID boot showed: CPU type : AMD Athlon II X2 260 Processor CPU speed : 3214.576 MHz The driver for my system is powernow-k8, so run: modprobe powernow-k8 Now it reports: CPU type : AMD Athlon II X2 260 Processor Min/Max frequency : 800/3200 MHz Current frequency : 800 MHz Frequency governor : ondemand Freq. scaling driver : powernow-k8 The available drivers are in: /lib/modules/2.6.32.9-unRAID/kernel/arch/x86/kernel/cpu/cpufreq/ Here’s description for the kernel drivers: * acpi-cpufreq: uses ACPI Processor P-States, common to many modern motherboards/CPU’s. * cpufreq-nforce2: uses FSB changing on motherboards using the nForce2 chipset. * p4-clockmod: cpufreq driver for Pentium 4/Xeon (and possibly the Core2) * powernow-k6: PowerNow! driver for AMD K6-2+ / K6-3+ processors. * powernow-k7: Powernow driver for AMD K7 processors. * powernow-k8: AMD Athlon 64 and Opteron processor frequency driver. * speedstep-lib: Library for Intel SpeedStep 1 or 2 cpufreq drivers. so pick the right one for your system, and modprobe it. Bubba, if i get a "FATAL: Module acpi_cpufreq.ko not found" does that mean my processor isn't supported? I have an Atom 330 Link to comment
bubbaQ Posted November 18, 2010 Share Posted November 18, 2010 Bubba, if i get a "FATAL: Module acpi_cpufreq.ko not found" does that mean my processor isn't supported? Yup. Link to comment
limetech Posted November 18, 2010 Author Share Posted November 18, 2010 AFAIK Atoms don't support CPU freq scaling. Link to comment
flixxx Posted November 18, 2010 Share Posted November 18, 2010 Ok, well things do look better. I hate doing this but now it's acting similar to your version 4.5.6 where it mdcmd display a status for all 20 disks (wether installed or not). It's not a big deal because your interface hides them and so does unraid notify but Bubba's shows them all: sbName=/boot/config/super.dat sbVersion=0.95.4 sbCreated=1279688098 sbUpdated=1290115134 sbEvents=121 sbState=0 sbNumDisks=7 sbSynced=1290029380 sbSyncErrs=0 mdVersion=1.1.0 mdState=STARTED mdNumProtected=7 mdNumDisabled=0 mdDisabledDisk=0 mdNumInvalid=0 mdInvalidDisk=0 mdNumMissing=0 mdMissingDisk=0 mdNumNew=0 mdResync=0 mdResyncPos=0 mdResyncPrcnt=0 mdResyncFinish=0 mdResyncSpeed=0 diskNumber.0=0 diskName.0= diskSize.0=1953514552 diskState.0=7 diskModel.0=WDC WD20EARS-00M diskSerial.0=WD-WMAZ20043234 diskId.0=WDC_WD20EARS-00M_WD-WMAZ20043234 rdevActive.0=1 rdevNumber.0=0 rdevStatus.0=DISK_OK rdevName.0=sdc rdevSize.0=1953514552 rdevModel.0=WDC WD20EARS-00M rdevSerial.0=WD-WMAZ20043234 rdevId.0=WDC_WD20EARS-00M_WD-WMAZ20043234 rdevNumReads.0=0 rdevNumWrites.0=0 rdevNumErrors.0=0 rdevLastIO.0=1290115135 rdevSpinupGroup.0=0 diskNumber.1=1 diskName.1=md1 diskSize.1=488386552 diskState.1=7 diskModel.1=Maxtor 6H500R0 diskSerial.1=H80J9HGH diskId.1=Maxtor_6H500R0_H80J9HGH rdevActive.1=1 rdevNumber.1=1 rdevStatus.1=DISK_OK rdevName.1=hda rdevSize.1=488386552 rdevModel.1=Maxtor 6H500R0 rdevSerial.1=H80J9HGH rdevId.1=Maxtor_6H500R0_H80J9HGH rdevNumReads.1=0 rdevNumWrites.1=0 rdevNumErrors.1=0 rdevLastIO.1=1290115162 rdevSpinupGroup.1=0 diskNumber.2=2 diskName.2=md2 diskSize.2=488386552 diskState.2=7 diskModel.2=WDC WD5000AAKS-7 diskSerial.2=WD-WMASY4103612 diskId.2=WDC_WD5000AAKS-7_WD-WMASY4103612 rdevActive.2=1 rdevNumber.2=2 rdevStatus.2=DISK_OK rdevName.2=sdd rdevSize.2=488386552 rdevModel.2=WDC WD5000AAKS-7 rdevSerial.2=WD-WMASY4103612 rdevId.2=WDC_WD5000AAKS-7_WD-WMASY4103612 rdevNumReads.2=0 rdevNumWrites.2=0 rdevNumErrors.2=0 rdevLastIO.2=1290115467 rdevSpinupGroup.2=0 diskNumber.3=3 diskName.3=md3 diskSize.3=976762552 diskState.3=7 diskModel.3=WDC WD1001FALS-0 diskSerial.3=WD-WMATV5570723 diskId.3=WDC_WD1001FALS-0_WD-WMATV5570723 rdevActive.3=1 rdevNumber.3=3 rdevStatus.3=DISK_OK rdevName.3=sda rdevSize.3=976762552 rdevModel.3=WDC WD1001FALS-0 rdevSerial.3=WD-WMATV5570723 rdevId.3=WDC_WD1001FALS-0_WD-WMATV5570723 rdevNumReads.3=0 rdevNumWrites.3=0 rdevNumErrors.3=0 rdevLastIO.3=1290115475 rdevSpinupGroup.3=0 diskNumber.4=4 diskName.4=md4 diskSize.4=1465138552 diskState.4=7 diskModel.4=WDC WD15EARS-00S diskSerial.4=WD-WCAVY1930651 diskId.4=WDC_WD15EARS-00S_WD-WCAVY1930651 rdevActive.4=1 rdevNumber.4=4 rdevStatus.4=DISK_OK rdevName.4=sdf rdevSize.4=1465138552 rdevModel.4=WDC WD15EARS-00S rdevSerial.4=WD-WCAVY1930651 rdevId.4=WDC_WD15EARS-00S_WD-WCAVY1930651 rdevNumReads.4=0 rdevNumWrites.4=0 rdevNumErrors.4=0 rdevLastIO.4=1290115472 rdevSpinupGroup.4=0 diskNumber.5=5 diskName.5=md5 diskSize.5=625131832 diskState.5=7 diskModel.5=WDC WD6400AAKS-0 diskSerial.5=WD-WCASY0373935 diskId.5=WDC_WD6400AAKS-0_WD-WCASY0373935 rdevActive.5=1 rdevNumber.5=5 rdevStatus.5=DISK_OK rdevName.5=sdb rdevSize.5=625131832 rdevModel.5=WDC WD6400AAKS-0 rdevSerial.5=WD-WCASY0373935 rdevId.5=WDC_WD6400AAKS-0_WD-WCASY0373935 rdevNumReads.5=0 rdevNumWrites.5=0 rdevNumErrors.5=0 rdevLastIO.5=1290115190 rdevSpinupGroup.5=0 diskNumber.6=6 diskName.6=md6 diskSize.6=488386552 diskState.6=7 diskModel.6=Hitachi HTS54505 diskSerial.6=100410PBN40017CZKJXE diskId.6=Hitachi_HTS54505_100410PBN40017CZKJXE rdevActive.6=1 rdevNumber.6=6 rdevStatus.6=DISK_OK rdevName.6=sdg rdevSize.6=488386552 rdevModel.6=Hitachi HTS54505 rdevSerial.6=100410PBN40017CZKJXE rdevId.6=Hitachi_HTS54505_100410PBN40017CZKJXE rdevNumReads.6=0 rdevNumWrites.6=0 rdevNumErrors.6=0 rdevLastIO.6=1290115149 rdevSpinupGroup.6=0 diskNumber.7=7 diskName.7= diskSize.7=0 diskState.7=0 diskModel.7= diskSerial.7= diskId.7= rdevActive.7=0 rdevNumber.7=7 rdevStatus.7=DISK_NP rdevName.7= rdevSize.7=0 rdevModel.7= rdevSerial.7= rdevId.7= rdevNumReads.7=0 rdevNumWrites.7=0 rdevNumErrors.7=0 rdevLastIO.7=0 rdevSpinupGroup.7=0 diskNumber.8=8 diskName.8= diskSize.8=0 diskState.8=0 diskModel.8= diskSerial.8= diskId.8= rdevActive.8=0 rdevNumber.8=8 rdevStatus.8=DISK_NP rdevName.8= rdevSize.8=0 rdevModel.8= rdevSerial.8= rdevId.8= rdevNumReads.8=0 rdevNumWrites.8=0 rdevNumErrors.8=0 rdevLastIO.8=0 rdevSpinupGroup.8=0 diskNumber.9=9 diskName.9= diskSize.9=0 diskState.9=0 diskModel.9= diskSerial.9= diskId.9= rdevActive.9=0 rdevNumber.9=9 rdevStatus.9=DISK_NP rdevName.9= rdevSize.9=0 rdevModel.9= rdevSerial.9= rdevId.9= rdevNumReads.9=0 rdevNumWrites.9=0 rdevNumErrors.9=0 rdevLastIO.9=0 rdevSpinupGroup.9=0 diskNumber.10=10 diskName.10= diskSize.10=0 diskState.10=0 diskModel.10= diskSerial.10= diskId.10= rdevActive.10=0 rdevNumber.10=10 rdevStatus.10=DISK_NP rdevName.10= rdevSize.10=0 rdevModel.10= rdevSerial.10= rdevId.10= rdevNumReads.10=0 rdevNumWrites.10=0 rdevNumErrors.10=0 rdevLastIO.10=0 rdevSpinupGroup.10=0 diskNumber.11=11 diskName.11= diskSize.11=0 diskState.11=0 diskModel.11= diskSerial.11= diskId.11= rdevActive.11=0 rdevNumber.11=11 rdevStatus.11=DISK_NP rdevName.11= rdevSize.11=0 rdevModel.11= rdevSerial.11= rdevId.11= rdevNumReads.11=0 rdevNumWrites.11=0 rdevNumErrors.11=0 rdevLastIO.11=0 rdevSpinupGroup.11=0 diskNumber.12=12 diskName.12= diskSize.12=0 diskState.12=0 diskModel.12= diskSerial.12= diskId.12= rdevActive.12=0 rdevNumber.12=12 rdevStatus.12=DISK_NP rdevName.12= rdevSize.12=0 rdevModel.12= rdevSerial.12= rdevId.12= rdevNumReads.12=0 rdevNumWrites.12=0 rdevNumErrors.12=0 rdevLastIO.12=0 rdevSpinupGroup.12=0 diskNumber.13=13 diskName.13= diskSize.13=0 diskState.13=0 diskModel.13= diskSerial.13= diskId.13= rdevActive.13=0 rdevNumber.13=13 rdevStatus.13=DISK_NP rdevName.13= rdevSize.13=0 rdevModel.13= rdevSerial.13= rdevId.13= rdevNumReads.13=0 rdevNumWrites.13=0 rdevNumErrors.13=0 rdevLastIO.13=0 rdevSpinupGroup.13=0 diskNumber.14=14 diskName.14= diskSize.14=0 diskState.14=0 diskModel.14= diskSerial.14= diskId.14= rdevActive.14=0 rdevNumber.14=14 rdevStatus.14=DISK_NP rdevName.14= rdevSize.14=0 rdevModel.14= rdevSerial.14= rdevId.14= rdevNumReads.14=0 rdevNumWrites.14=0 rdevNumErrors.14=0 rdevLastIO.14=0 rdevSpinupGroup.14=0 diskNumber.15=15 diskName.15= diskSize.15=0 diskState.15=0 diskModel.15= diskSerial.15= diskId.15= rdevActive.15=0 rdevNumber.15=15 rdevStatus.15=DISK_NP rdevName.15= rdevSize.15=0 rdevModel.15= rdevSerial.15= rdevId.15= rdevNumReads.15=0 rdevNumWrites.15=0 rdevNumErrors.15=0 rdevLastIO.15=0 rdevSpinupGroup.15=0 diskNumber.16=16 diskName.16= diskSize.16=0 diskState.16=0 diskModel.16= diskSerial.16= diskId.16= rdevActive.16=0 rdevNumber.16=16 rdevStatus.16=DISK_NP rdevName.16= rdevSize.16=0 rdevModel.16= rdevSerial.16= rdevId.16= rdevNumReads.16=0 rdevNumWrites.16=0 rdevNumErrors.16=0 rdevLastIO.16=0 rdevSpinupGroup.16=0 diskNumber.17=17 diskName.17= diskSize.17=0 diskState.17=0 diskModel.17= diskSerial.17= diskId.17= rdevActive.17=0 rdevNumber.17=17 rdevStatus.17=DISK_NP rdevName.17= rdevSize.17=0 rdevModel.17= rdevSerial.17= rdevId.17= rdevNumReads.17=0 rdevNumWrites.17=0 rdevNumErrors.17=0 rdevLastIO.17=0 rdevSpinupGroup.17=0 diskNumber.18=18 diskName.18= diskSize.18=0 diskState.18=0 diskModel.18= diskSerial.18= diskId.18= rdevActive.18=0 rdevNumber.18=18 rdevStatus.18=DISK_NP rdevName.18= rdevSize.18=0 rdevModel.18= rdevSerial.18= rdevId.18= rdevNumReads.18=0 rdevNumWrites.18=0 rdevNumErrors.18=0 rdevLastIO.18=0 rdevSpinupGroup.18=0 diskNumber.19=19 diskName.19= diskSize.19=0 diskState.19=0 diskModel.19= diskSerial.19= diskId.19= rdevActive.19=0 rdevNumber.19=19 rdevStatus.19=DISK_NP rdevName.19= rdevSize.19=0 rdevModel.19= rdevSerial.19= rdevId.19= rdevNumReads.19=0 rdevNumWrites.19=0 rdevNumErrors.19=0 rdevLastIO.19=0 rdevSpinupGroup.19=0 diskNumber.20=20 diskName.20= diskSize.20=0 diskState.20=0 diskModel.20= diskSerial.20= diskId.20= rdevActive.20=0 rdevNumber.20=20 rdevStatus.20=DISK_NP rdevName.20= rdevSize.20=0 rdevModel.20= rdevSerial.20= rdevId.20= rdevNumReads.20=0 rdevNumWrites.20=0 rdevNumErrors.20=0 rdevLastIO.20=0 rdevSpinupGroup.20=0 On the other hand it might be impacting "cache_dir". when I try to stop the array, cache_dir does not get killed. I can't access my logs just yet, i'll do that when I get home but if anyone else can replicate it with only cache_dir running, let us know. Link to comment
theone Posted November 18, 2010 Share Posted November 18, 2010 AFAIK Atoms don't support CPU freq scaling. You are correct. It doesn't. Link to comment
lewcass Posted November 18, 2010 Share Posted November 18, 2010 Installed 4.6-rc2 and now unMENU (1.3) reports there is a parity check underway, when there actually is not. The official unRAID web menu indicates there is no parity check in progress. Tried rebooting. Killing unMenu and restarting it. Stopping the array from the official unRAID menu. Attempted to cancel the alleged parity check within unMENU. Nothing worked. unMENU still indicates Parity Check in progess. Though the unMENU parity check progress indicators all remain at zero. Maybe this topic belongs in the unMENU thread but I thought I should post it here since the problem coincided with installing 4.6-rc2 and hadn't occurred with previous versions. Link to comment
Joe L. Posted November 18, 2010 Share Posted November 18, 2010 Installed 4.6-rc2 and now unMENU (1.3) reports there is a parity check underway, when there actually is not. The official unRAID web menu indicates there is no parity check in progress. Tried rebooting. Killing unMenu and restarting it. Stopping the array from the official unRAID menu. Attempted to cancel the alleged parity check within unMENU. Nothing worked. unMENU still indicates Parity Check in progess. Though the unMENU parity check progress indicators all remain at zero. Maybe this topic belongs in the unMENU thread but I thought I should post it here since the problem coincided with installing 4.6-rc2 and hadn't occurred with previous versions. It is how the output of mdcmd is being interpreted. Once rc3 is out I'll fix whatever is needed to get the display on the top of unMENU back in sync. Right now, too much of a moving target. Link to comment
lewcass Posted November 18, 2010 Share Posted November 18, 2010 It is how the output of mdcmd is being interpreted. Once rc3 is out I'll fix whatever is needed to get the display on the top of unMENU back in sync. Right now, too much of a moving target. OK. Thanks Joe. Just as long as I know it is nothing wrong that I need to fix myself. Link to comment
limetech Posted November 18, 2010 Author Share Posted November 18, 2010 Installed 4.6-rc2 and now unMENU (1.3) reports there is a parity check underway, when there actually is not. The official unRAID web menu indicates there is no parity check in progress. Tried rebooting. Killing unMenu and restarting it. Stopping the array from the official unRAID menu. Attempted to cancel the alleged parity check within unMENU. Nothing worked. unMENU still indicates Parity Check in progess. Though the unMENU parity check progress indicators all remain at zero. Maybe this topic belongs in the unMENU thread but I thought I should post it here since the problem coincided with installing 4.6-rc2 and hadn't occurred with previous versions. It is how the output of mdcmd is being interpreted. Once rc3 is out I'll fix whatever is needed to get the display on the top of unMENU back in sync. Right now, too much of a moving target. The idea here is for me to identify what broke, so you don't have to make changes to existing code. Link to comment
lewcass Posted November 18, 2010 Share Posted November 18, 2010 For the folks looking for cpufreq support.... The driver for my system is powernow-k8, so run: modprobe powernow-k8 ...so pick the right one for your system, and modprobe it. Thanks for this how-to bubbaQ, and to Tom for enabling it in unRAID. Seems to work OK with my old Opteron 185. Cuts the clock from 2.6GHz to 1.0 when idling. Been wanting this ever since I built my unRAID box last year. Should save a significant amount of electricity. I assume I can put the modprobe command in my go script so it will enable automatically after rebooting? Link to comment
bubbaQ Posted November 19, 2010 Share Posted November 19, 2010 Should save a significant amount of electricity. Not really... I'd guess about 6 Watts. I assume I can put the modprobe command in my go script so it will enable automatically after rebooting? Yup. Link to comment
jazzysmooth Posted November 19, 2010 Share Posted November 19, 2010 Installed 4.6-rc2 and now unMENU (1.3) reports there is a parity check underway, when there actually is not. The official unRAID web menu indicates there is no parity check in progress. Tried rebooting. Killing unMenu and restarting it. Stopping the array from the official unRAID menu. Attempted to cancel the alleged parity check within unMENU. Nothing worked. unMENU still indicates Parity Check in progess. Though the unMENU parity check progress indicators all remain at zero. Maybe this topic belongs in the unMENU thread but I thought I should post it here since the problem coincided with installing 4.6-rc2 and hadn't occurred with previous versions. I had the same thing happen when I installed 4.5.8. Editing the Send Status Alert package (changed "Send mail even if status is normal" to no) and restarting UnMenu fixed it for me - not sure if I had to do both things, but I no longer get the hourly parity emails (parity wasn't running, like yours the progress was always at 0%) I've since upgraded to 4.6.1 RC and it didn't come back. Link to comment
gbdesai Posted November 19, 2010 Share Posted November 19, 2010 I came home to an unresponsive Unraid, I have been running this new build (move from my old server) for about 3 weeks with no problems. I have IPMI so I logged into and saw this: Is that a server crash? I rebooted and server is coming up and disks still show as mounting and writes are taking place and slowly they are mounting one by one... I'll upgrade to RC2 shortly, but want to make sure I know what the problem was... Thanks. G Link to comment
Romeo Posted November 19, 2010 Share Posted November 19, 2010 Install acpitool from: http://www.software-mirror.com/linuxpackages/Slackware-12.0/Console/acpitool/acpitool-0.4.7-i486-1goa.tgz and run: acpitool -c That will tell you what's cooking, and we can go from there. bubbaQ, could you please explain in details how to install acpitool and how to run? Link to comment
Recommended Posts