limetech Posted April 3, 2008 Share Posted April 3, 2008 Download. Fixes 'hang' that can happen during start-up if no WINS server on network. Please refer to the 4.3-beta4 announcement regarding description of new features. unRAID Server 4.3-beta5 Release Notes Upgrade Instructions (Please Read Carefully) -------------------------------------------- If you are currently running unRAID Server 4.2-beta1 or higher (including 4.2.x 'final'), please copy the following files from the new release to the root of your Flash device: bzimage bzroot If you are currently running unRAID server 4.0 or 4.1, please copy the following files from the new release to the root of your Flash device: bzimage bzroot syslinux.cfg menu.c32 memtest This can be done either by plugging the Flash into your PC or, by copying the files to the 'flash' share on your running server. The server must then be rebooted. If you are currently running unRAID Server 3.0-beta1 or higher, please follow these steps to upgrade: 1. Referring to the System Management Utility 'Main' page, make a note of each disks's model/serial number; you will need this information later. 2. Shut down your server, remove the Flash and plug it into your PC. 3. Right-click your Flash device listed under My Computer and select Properties. Make sure the volume label is set to "UNRAID" (without the quotes) and click OK. You do NOT need to format the Flash. 4. Copy the files from the new release to the root of your Flash device. 5. Right-click your Flash device listed under My Computer and select Eject. Remove the Flash, install in your server and power-up. 6. After your server has booted up, the System Management Utility 'Main' page will probably show no devices; this is OK, navigate to the 'Devices' page. Using the model/serial number information gathered in step 1, assign each of your hard drives to the correct disk slot. 7. Go back to the 'Main' page and your devices should appear correctly. You may now Start the array. If you are installing this release to a new Flash, please refer to instructions on our website at: http://www.lime-technology.com/wordpress/?page_id=19 Changes from 4.3-beta4 to 4.3-beta5 ----------------------------------- Bug Fix: Fix 'hang' that may occur starting syslogd. Improvement: Add 'sync' as last step in 'mover' script Changes from 4.3-beta3 to 4.3-beta4 ----------------------------------- New feature: cache disk support. Improvement: enable SMART before reading disk temperature. Improvement: upgrade from linux kernel 2.6.24.3 to 2.6.24.4 (refer to http://lwn.net/Articles/274741). Improvement: upgrade from Samba 3.0.28 to Samba 3.0.28a (addresses some Vista issues, refer to http://us1.samba.org/samba/history/samba-3.0.28a.html). Improvement: added back a few more missing libraries needed for certain user customizations. Bug Fix: Support normal expansion of array when Parity is not installed. Quote Link to comment
RobJ Posted April 3, 2008 Share Posted April 3, 2008 Improvement: enable SMART before reading disk temperature. Thank you for this. For others, this should help avoid certain tech support issues, where a few drives were not responding to 'get temperature' requests. Quote Link to comment
ReneV Posted April 3, 2008 Share Posted April 3, 2008 I've lost the temperatures on the two SATA-II drives I've got sitting on a Promise TX4 with this beta. Quote Link to comment
RobJ Posted April 3, 2008 Share Posted April 3, 2008 If you could attach a syslog, I think Tom would find that useful. Quote Link to comment
ReneV Posted April 3, 2008 Share Posted April 3, 2008 I've lost the temperatures on the two SATA-II drives I've got sitting on a Promise TX4 with this beta. syslog: Apr 4 00:31:40 unRAID kernel: ata13.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Apr 4 00:31:40 unRAID kernel: ata13.00: cmd b0/d8:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Apr 4 00:31:40 unRAID kernel: res 50/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) Apr 4 00:31:40 unRAID kernel: ata13.00: status: { DRDY } Apr 4 00:31:40 unRAID kernel: ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Apr 4 00:31:40 unRAID kernel: ata14.00: cmd b0/d8:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Apr 4 00:31:40 unRAID kernel: res 50/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) Apr 4 00:31:40 unRAID kernel: ata14.00: status: { DRDY } Quote Link to comment
limetech Posted April 3, 2008 Author Share Posted April 3, 2008 ReneV- If you don't mind, please download this bzroot zip file, unzip and replace your current bzroot file on the Flash & let me know if this fixes the problem. Quote Link to comment
BLKMGK Posted April 3, 2008 Share Posted April 3, 2008 I seem to have lost temp on my Parity drive - comes up with an asterisk. All other drives are coming up fine to include other drives from same manufacturer - Seagate. root@BEAST:~# tail -f /var/log/syslog Apr 3 17:20:40 BEAST kernel: sd 1:0:0:0: [sdb] 976773168 512-byte hardware sect ors (500108 MB) Apr 3 17:20:40 BEAST kernel: sd 1:0:0:0: [sdb] Write Protect is off Apr 3 17:20:40 BEAST kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Apr 3 17:20:40 BEAST kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache : enabled, doesn't support DPO or FUA Apr 3 17:20:40 BEAST kernel: sd 1:0:0:0: [sdb] 976773168 512-byte hardware sect ors (500108 MB) Apr 3 17:20:40 BEAST kernel: sd 1:0:0:0: [sdb] Write Protect is off Apr 3 17:20:40 BEAST kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Apr 3 17:20:40 BEAST kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache : enabled, doesn't support DPO or FUA What's DPO and FUA? Edit: Whoops! Just tried to go into the Shares area, which I've never enabled, and now the WEB interface no longer responds! Segfault it looks like - doh! Apr 3 17:20:40 BEAST kernel: sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB) Apr 3 17:20:40 BEAST kernel: sd 1:0:0:0: [sdb] Write Protect is off Apr 3 17:20:40 BEAST kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Apr 3 17:20:40 BEAST kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 3 17:20:40 BEAST kernel: sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB) Apr 3 17:20:40 BEAST kernel: sd 1:0:0:0: [sdb] Write Protect is off Apr 3 17:20:40 BEAST kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Apr 3 17:20:40 BEAST kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 3 17:21:45 BEAST in.telnetd[1905]: connect from 192.168.1.149 (192.168.1.149) Apr 3 17:21:48 BEAST login[1906]: ROOT LOGIN on `pts/0' from `zippy' Apr 3 17:24:39 BEAST kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Apr 3 17:24:39 BEAST kernel: ata1.00: cmd b0/d8:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Apr 3 17:24:39 BEAST kernel: res 50/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) Apr 3 17:24:39 BEAST kernel: ata1.00: status: { DRDY } Apr 3 17:24:39 BEAST kernel: ata1: soft resetting link Apr 3 17:24:39 BEAST kernel: ata1.00: configured for UDMA/133 Apr 3 17:24:39 BEAST kernel: ata1: EH complete Apr 3 17:24:39 BEAST kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Apr 3 17:24:39 BEAST kernel: ata1.00: cmd b0/d8:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Apr 3 17:24:39 BEAST kernel: res 50/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) Apr 3 17:24:39 BEAST kernel: ata1.00: status: { DRDY } Apr 3 17:24:39 BEAST kernel: ata1: soft resetting link Apr 3 17:24:39 BEAST kernel: ata1.00: configured for UDMA/133 Apr 3 17:24:39 BEAST kernel: ata1: EH complete Apr 3 17:24:39 BEAST kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Apr 3 17:24:39 BEAST kernel: ata1.00: cmd b0/d8:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Apr 3 17:24:39 BEAST kernel: res 50/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) Apr 3 17:24:39 BEAST kernel: ata1.00: status: { DRDY } Apr 3 17:24:39 BEAST kernel: ata1: soft resetting link Apr 3 17:24:39 BEAST kernel: ata1.00: configured for UDMA/133 Apr 3 17:24:39 BEAST kernel: ata1: EH complete Apr 3 17:24:39 BEAST kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Apr 3 17:24:39 BEAST kernel: ata1.00: cmd b0/d8:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Apr 3 17:24:39 BEAST kernel: res 50/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) Apr 3 17:24:39 BEAST kernel: ata1.00: status: { DRDY } Apr 3 17:24:39 BEAST kernel: ata1: soft resetting link Apr 3 17:24:40 BEAST kernel: ata1.00: configured for UDMA/133 Apr 3 17:24:40 BEAST kernel: ata1: EH complete Apr 3 17:24:40 BEAST kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Apr 3 17:24:40 BEAST kernel: ata1.00: cmd b0/d8:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Apr 3 17:24:40 BEAST kernel: res 50/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) Apr 3 17:24:40 BEAST kernel: ata1.00: status: { DRDY } Apr 3 17:24:40 BEAST kernel: ata1: soft resetting link Apr 3 17:24:40 BEAST kernel: ata1.00: configured for UDMA/133 Apr 3 17:24:40 BEAST kernel: ata1: EH complete Apr 3 17:24:40 BEAST kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Apr 3 17:24:40 BEAST kernel: ata1.00: cmd b0/d8:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Apr 3 17:24:40 BEAST kernel: res 50/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) Apr 3 17:24:40 BEAST kernel: ata1.00: status: { DRDY } Apr 3 17:24:40 BEAST kernel: ata1: soft resetting link Apr 3 17:24:40 BEAST emhttp: disk_temperature: ioctl (smart_enable): Input/output error Apr 3 17:24:40 BEAST kernel: ata1.00: configured for UDMA/133 Apr 3 17:24:40 BEAST kernel: ata1: EH complete Apr 3 17:24:40 BEAST kernel: sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB) Apr 3 17:24:40 BEAST kernel: sd 1:0:0:0: [sdb] Write Protect is off Apr 3 17:24:40 BEAST kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Apr 3 17:24:40 BEAST kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 3 17:24:40 BEAST kernel: sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB) Apr 3 17:24:40 BEAST kernel: sd 1:0:0:0: [sdb] Write Protect is off Apr 3 17:24:40 BEAST kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Apr 3 17:24:40 BEAST kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 3 17:24:43 BEAST kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Apr 3 17:24:43 BEAST kernel: ata1.00: cmd b0/d8:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Apr 3 17:24:43 BEAST kernel: res 50/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) Apr 3 17:24:43 BEAST kernel: ata1.00: status: { DRDY } Apr 3 17:24:43 BEAST kernel: ata1: soft resetting link Apr 3 17:24:43 BEAST kernel: ata1.00: configured for UDMA/133 Apr 3 17:24:43 BEAST kernel: ata1: EH complete Apr 3 17:24:43 BEAST kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Apr 3 17:24:43 BEAST kernel: ata1.00: cmd b0/d8:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Apr 3 17:24:43 BEAST kernel: res 50/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) Apr 3 17:24:43 BEAST kernel: ata1.00: status: { DRDY } Apr 3 17:24:43 BEAST kernel: ata1: soft resetting link Apr 3 17:24:43 BEAST kernel: ata1.00: configured for UDMA/133 Apr 3 17:24:43 BEAST kernel: ata1: EH complete Apr 3 17:24:43 BEAST kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Apr 3 17:24:43 BEAST kernel: ata1.00: cmd b0/d8:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Apr 3 17:24:43 BEAST kernel: res 50/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) Apr 3 17:24:43 BEAST kernel: ata1.00: status: { DRDY } Apr 3 17:24:43 BEAST kernel: ata1: soft resetting link Apr 3 17:24:44 BEAST kernel: ata1.00: configured for UDMA/133 Apr 3 17:24:44 BEAST kernel: ata1: EH complete Apr 3 17:24:44 BEAST kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Apr 3 17:24:44 BEAST kernel: ata1.00: cmd b0/d8:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Apr 3 17:24:44 BEAST kernel: res 50/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) Apr 3 17:24:44 BEAST kernel: ata1.00: status: { DRDY } Apr 3 17:24:44 BEAST kernel: ata1: soft resetting link Apr 3 17:24:44 BEAST kernel: ata1.00: configured for UDMA/133 Apr 3 17:24:44 BEAST kernel: ata1: EH complete Apr 3 17:24:44 BEAST kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Apr 3 17:24:44 BEAST kernel: ata1.00: cmd b0/d8:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Apr 3 17:24:44 BEAST kernel: res 50/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) Apr 3 17:24:44 BEAST kernel: ata1.00: status: { DRDY } Apr 3 17:24:44 BEAST kernel: ata1: soft resetting link Apr 3 17:24:44 BEAST kernel: ata1.00: configured for UDMA/133 Apr 3 17:24:44 BEAST kernel: ata1: EH complete Apr 3 17:24:44 BEAST kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Apr 3 17:24:44 BEAST kernel: ata1.00: cmd b0/d8:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Apr 3 17:24:44 BEAST kernel: res 50/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) Apr 3 17:24:44 BEAST kernel: ata1.00: status: { DRDY } Apr 3 17:24:44 BEAST kernel: ata1: soft resetting link Apr 3 17:24:44 BEAST emhttp: disk_temperature: ioctl (smart_enable): Input/output error Apr 3 17:24:44 BEAST kernel: ata1.00: configured for UDMA/133 Apr 3 17:24:44 BEAST kernel: ata1: EH complete Apr 3 17:24:44 BEAST kernel: sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB) Apr 3 17:24:44 BEAST kernel: sd 1:0:0:0: [sdb] Write Protect is off Apr 3 17:24:44 BEAST kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Apr 3 17:24:44 BEAST kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 3 17:24:44 BEAST kernel: sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB) Apr 3 17:24:44 BEAST kernel: sd 1:0:0:0: [sdb] Write Protect is off Apr 3 17:24:44 BEAST kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Apr 3 17:24:44 BEAST kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 3 17:24:44 BEAST emhttp: shareSplitLevel.1046770735 not found Apr 3 17:24:44 BEAST emhttp: shareInclude.1046770735 not found Apr 3 17:24:44 BEAST emhttp: shareExclude.1046770735 not found Apr 3 17:24:44 BEAST kernel: emhttp[1534]: segfault at d9965854 eip 0804bb97 esp bf82aac4 error 5 Now what? Anyway to restart the interface from commandline? Glad this isn't my media server! Can still access shares... Quote Link to comment
erikatcuse Posted April 3, 2008 Share Posted April 3, 2008 One last question on the cache drive. I have an IDE only 12 drive system right now. Can I add the cache drive as a SATA? Also since it's not part of the array it could be any size correct? Quote Link to comment
limetech Posted April 3, 2008 Author Share Posted April 3, 2008 BLKMGK- For the segfault problem, you might need to manually edit the 'config/share.cfg' file on the Flash (/boot/config/share.cfg via telnet), and disable user shares. Change the line that reads: shareUser=e to shareUser=- Next, reboot and system should come up again without user shares enabled. Now, I need to see the top level directories of your disks. From a telnet session, type this: ls /mnt There will be an entry in there for each of your data disks. You need to do this for each disk: ls -a /mnt/disk1 ls -a /mnt/disk2 etc. Do this for each disk. Capture the screen output and send to me: [email protected] For your parity disk temperature problem, please try the 'bzroot' test file in the post above to ReneV & let me know if that solves it for you. DPO and FUA are bits in a SCSI write command that give "hints" to the disk drive about the nature of the data being written. These are just informational messages of no consequence. Quote Link to comment
limetech Posted April 3, 2008 Author Share Posted April 3, 2008 One last question on the cache drive. I have an IDE only 12 drive system right now. Can I add the cache drive as a SATA? Also since it's not part of the array it could be any size correct? Yes and yes. Quote Link to comment
ReneV Posted April 3, 2008 Share Posted April 3, 2008 ReneV- If you don't mind, please download this bzroot zip file, unzip and replace your current bzroot file on the Flash & let me know if this fixes the problem. We seem to be good. Cheers. Apr 4 07:18:42 unRAID kernel: ata13: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Apr 4 07:18:42 unRAID kernel: ata13.00: ATA-7: HDT722525DLA380, V44OA9BA, max UDMA/133 Apr 4 07:18:42 unRAID kernel: ata13.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 0/32) Apr 4 07:18:42 unRAID kernel: ata13.00: configured for UDMA/133 Apr 4 07:18:42 unRAID kernel: ata14: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Apr 4 07:18:42 unRAID kernel: ata14.00: ATA-8: WDC WD5000AAKS-00YGA0, 12.01C02, max UDMA/133 Apr 4 07:18:42 unRAID kernel: ata14.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32) Apr 4 07:18:42 unRAID kernel: ata14.00: configured for UDMA/133 Quote Link to comment
BLKMGK Posted April 3, 2008 Share Posted April 3, 2008 Copied file, modified the share entry. Any chance I could be given the command to restart the WEB interface so I do not do a hardboot and be forced to rebuild parity? Quote Link to comment
Joe L. Posted April 4, 2008 Share Posted April 4, 2008 Copied file, modified the share entry. Any chance I could be given the command to restart the WEB interface so I do not do a hardboot and be forced to rebuild parity? BLKMGK, You should be able to cleanly stop the array with this series of commands /etc/rc.d/rc.samba stop /bin/sync for disk in /mnt/disk* do umount ${disk} done /root/mdcmd stop Then, I think you can restart emhttp with this: nohup /usr/local/sbin/emhttp >/dev/null 2>/dev/null & Once started, I'd stop the array and reboot to clean up everything. Joe L. Quote Link to comment
BLKMGK Posted April 4, 2008 Share Posted April 4, 2008 Seems to have worked, thanks! Bringing up the HTTP interface the array is still up but at least I can now cleanly kill it off Rebooted fine! Tom, you have mail! Quote Link to comment
SuperW2 Posted April 4, 2008 Share Posted April 4, 2008 Looks like I lost the Temp Readings on the drives connected to my SUPERMICRO AOC-SAT2-MV8 card as well... Cache Disk Comes up now and I hope to give that a little testing this evening and see how the Mover thing functions overnight tonight... Without going back to the Beta4 description Post, am I correct in remebering that the Mover will not remove the empty folders from the Cache Disk once it's moved the stuff from the Cache Drive to the individual drives from the user share. Thanks SW2 Quote Link to comment
erikatcuse Posted April 4, 2008 Share Posted April 4, 2008 Without going back to the Beta4 description Post, am I correct in remebering that the Mover will not remove the empty folders from the Cache Disk once it's moved the stuff from the Cache Drive to the individual drives from the user share. Thanks SW2 No the empty directories stay on the cache disk. Quote Link to comment
RobJ Posted April 4, 2008 Share Posted April 4, 2008 ReneV- If you don't mind, please download this bzroot zip file, unzip and replace your current bzroot file on the Flash & let me know if this fixes the problem. Very impressive looking fix! The first syslog that ReneV attached is 6000 lines, and over 5200 are error related. After trying the replacement bzroot, his syslog was about 740 lines, essentially identical EXCEPT for the loss of over 5200 error related lines! This newer version of bzroot seems to have completely fixed the problem. It may not have taken 12 hours like the other problem, but is no less dramatic in syslog improvement. Of course, a failure to boot is a bit more important than minor SMART related errors... For any who have lost temp readings, try the new bzroot. Quote Link to comment
tillkrueger Posted April 4, 2008 Share Posted April 4, 2008 i also lost temperature readout on all drives hooked up to the Promise TX4 controllers (everything attached to the mobo is fine). i downloaded the "renev_bzroot.zip" file, but when i extract it, it first writes a "bzimage" file, then begins to extract *that* file and creates a "bzroot 2" file, but end with an error message saying "Unable to expand "bzroot 2" - it is an unsupported format." the "bzroot 2" file is 66.8MB, significantly larger than the current "bzimage" file (27.2MB) from the 4.3-beta5 archive. am i not doing something right? i haven't had any beer and tried 3 times already...hmmm. PS: nevermind...i know i could have not even posted this at all, now that i got it to work, but for educational purposes: actually i *did* drink beer...27 of them...no, just kidding...for some reason the OSX native de-archive function exhibited this double-extract behavior...when i de-archived same file with 7zip, it did it correctly...beats me. Quote Link to comment
limetech Posted April 5, 2008 Author Share Posted April 5, 2008 4.3-beta6 should fix these problems reading drive temps. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.