|
Post by fajo on Dec 16, 2007 6:05:56 GMT 7
Thecus just (Dec 14th) released a new GPL source package at www.thecus.com/Downloads/GPL/The package has a version of 2.00.04 so it's most likely that the next FW release will be available before Christmas. Since the source package has been stripped down in some parts it is not possible to tell much about the next FW release but it looks like some applications have been upgraded (compared to 2.00.01): - iSCSI kernel driver from 1.0-485 to 1.1-648 (confirmed)
- Samba from 3.0.22 to 3.0.26a (confirmed)
- Busybox from 1.1.0 to busybox-1.7.2 (not confirmed)
There are also some applications new to the source tree - part of them may have been missing in previous source packages only: - MPlayer 1.0rc1 (confirmed)
- reiserfsprogs 3.6.19 (confirmed)
- util-linux-ng 2.13.0.1
- wget 1.10.2 (confirmed)
MPlayer seems to be new and includes a command line video encoder (confirmed). Lets see what it will be used for if included in the FW package The source code itself did not reveal much: - the iSCSI target kernel drivers vendor/product IDs have changed from THECUS/N5200-VDISK to NAS/iSCSI-VDISK
- the USB kernel driver (UB - low performance driver) no longer gets compiled in (confirmed)
- the flash layout /dev/hdaX) seems to have changed (confirmed)
- the MD kernel driver has been modified (/fixed?). It seems to distinguish between DEGRADED and DAMAGED now
- other small changes
/Falk
|
|
|
Post by midknight on Dec 16, 2007 9:56:16 GMT 7
hopefully we'll be getting new firmware for the 5200 soon then
|
|
|
Post by funkstar on Dec 17, 2007 2:39:34 GMT 7
With MPlayer inthe firmware, i guess it can be dropped from the Slimserver module. It was being used for the AlienBBC plugin.
|
|
|
Post by fajo on Dec 18, 2007 19:27:29 GMT 7
|
|
|
Post by cyrilix on Dec 19, 2007 20:58:33 GMT 7
I tried this firmware as an upgrade from "Broken Modules" (i.e. 2.00.03), and it has worked well so far. I'm also glad that I got some 70 GB of space back with my 4 drive RAID5, which made me very happy. I haven't been able to observe performance as of yet (I'm hoping Vista SP1 networking performance increases will be the icing on the cake later on).
|
|
|
Post by midknight on Dec 19, 2007 21:03:30 GMT 7
same here, so far all is great, and im sure the box seems to operate faster. havent had a chance to try and read/write performance tests.
i didnt gain any disc space myself though
|
|
|
Post by cyrilix on Dec 19, 2007 21:25:24 GMT 7
Well, the disk space I gained back was as a result of the 5% reserved, which is no longer (and was needlessly) there, so it's more of a bug fix that ended up well, than any kind of magical gain.
|
|
|
Post by midknight on Dec 19, 2007 21:33:14 GMT 7
im not sure if thats the reserved for usb or something, but when i made up my raid i chose to use all. if thats what your talking about?
otherwise the system here says i have a total Capacity of 2788.9gb and data capacity is 2700.1gb
always been that way and never changed on this firmware upgrade. kinda annoying as thats alot of space that i dont know whats using it, if anything
|
|
|
Post by cyrilix on Dec 19, 2007 21:42:55 GMT 7
I don't think so. The USB is another piece of space (which I don't use). The fix is this one here listed under the fixes for 2.00.04:
file systems created with (-m 0) now -> no reserved space
...where I believe it used to be -m 5. omega created a thread on it, and gave instructions as to how to recover this. It seems like Thecus has simply integrated it into their fixes.
|
|
|
Post by midknight on Dec 19, 2007 22:36:39 GMT 7
so does your total Capacity match your data capacity?
|
|
|
Post by cyrilix on Dec 19, 2007 23:24:42 GMT 7
Nope, it does not.
Total Capacity: 1394.4 GB Data Capacity: 688.3 GB / 1349.3 GB USB Capacity: N/A
So I assume it means that it needs 45.1 GB allocated for the RAID array itself, which is what it has been like since I got this unit with 1.00.08.
|
|
|
Post by kniteowl on Dec 19, 2007 23:49:46 GMT 7
You will NEVER see the full capacity of your drives. Even with the fix from Omega, as there is a part of the drive that is reserved for system files.
After the firmware creates the raid, it automatically creates two (2) partition. \raid\data & \raid\system.
\raid\data is where your data is saved, with the addition of a few items like the DNLA software, any added modules, etc.
\raid\system stores the system settings, like your SAMBA shares information, the sqlight DB that stores the iSCSI settings, etc.
On my system, my \raid\system partition is 100 Megs in size. I am not sure if it is a static size for all, or if it is a percentage of overall raid size.
Teng
|
|
|
Post by pellicle on Dec 20, 2007 5:12:21 GMT 7
:)I have installed successfully. I was unable to expand my Raid size after adding a new disk and doing a Raid 5 to Raid 5 migration.
While I could have fiddled around and fixed this I opted to wait for the promised fix in the new firmware.
I can report that the issue is resolved and I was successful in expanding the raid array to recover the space lost to the snapshot.
|
|
glo8al
Junior Member
Posts: 95
|
Post by glo8al on Dec 21, 2007 4:28:58 GMT 7
I noticed there are changes to Quote management. Anyone had any new problems with quote management? Do you have to re-format the Drives like you did when you went from V1.x.x toV2.x.x? (well you didn't have to but the format changed something from memory)
|
|
|
Post by satanko on Dec 21, 2007 17:54:52 GMT 7
Well, the disk space I gained back was as a result of the 5% reserved, which is no longer (and was needlessly) there, so it's more of a bug fix that ended up well, than any kind of magical gain. Do you need to delete and then rebuild your RAID5 array? Or can you on-the-fly adjust USB/iSCSI reserved space?
|
|