As it was the purpose to have the 1.04RC3 being released officially I’ve decided not to release it through the official channel. I have just received an important bugfix which was finished earlier than expected. So probably early next week this version will be released.
In this release only the following has been fixed:
- The samba server time setting is not synchronized with FTP server and device web time setting.
This means that in certain conditions you could see time differences when uploading / copying files to the CH3SNAS. Download the 1.04RC4 here
Note: the PS3 issue is still under debugging. Playing a 7GB .ts media file can show the correct size, but it can only be played for 2 hours.
Hi Dennis,
I encountered the following problem with FW release 1.4RC2 and the same with RC3. RC4 I have’nt already tested.
The problem does NOT occur with 1.4RC1 !!
After some time after having booted the device (maybe after 24-36 hours) the following happens:
I use fun_plug 0.5
— i enabled logging
root@CH3SNAS:~# cat /log/fan_ctrl.log
…
2008-07-04 22:01:22 : 122F 50C — 3180rpm
2008-07-04 22:03:22 : 122F 50C — 3180rpm
2008-07-04 22:05:22 : 122F 50C — 3180rpm
2008-07-04 22:07:22 : 32F 0C — 0rpm
2008-07-04 22:09:21 : 32F 0C — 0rpm
2008-07-04 22:11:21 : 32F 0C — 0rpm
… (does not change anymore)
root@CH3SNAS:~# fanspeed g
2533
root@CH3SNAS:~# temperature g 0
Temperature type : Fahrenheit
: get temperature = 32
root@CH3SNAS:~# dmesg
TWSI: mvTwsiStartBitSet ERROR – Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR – Start Clear bit TimeOut .
… (continued, always the same)
After trying to reboot, the device does not boot anymore. It seems to be in a loop during the bootup-process, LEDs are flickering (as during normal boot), then they get dark and the boot-process begins from scratch. After doing a power-reset (disconnect and reconnect power cord) the device boot up normally.
As already mentioned – this did never happen with RC1 ?
I can reproduce it only with RC2/RC3 …
After reapplying RC1, all works fine again
Any idea what causes this issue ?
best Regards PeterJ
I forgot to mention, that e.g.
root@CH3SNAS:~# fanspeed w 4000
does not have any effect on the previous setting – it does not change it
root@CH3SNAS:~# fanspeed g
2533
root@CH3SNAS:~# temperature g 0
Temperature type : Fahrenheit
: get temperature = 32
So I think it does not have to do anything with funplug.
The fan is running slowly, but does not increase speed after issuing command above.
Strange thing – I went back to RC1 now to have stable condition for my device
best regards
Peter J
fun_plug is not supported. So is your issue related to fun_plug settings / fan_script or native ?
Thanks! I noticed this morning a 2 hr time difference in my files on my NAS. I hope this release will solve this.
For the TWSI error you could check this site:
http://forum.source.pri.ee/p9812-2008-01-25-15:30:21.html
It seems to be related to a kernel error. To me it looks that when this is the case, the fans are not controlled anymore, thus a potential risk of overheating the NAS.
@Enrico
thanks for your information – that’s exactly what I am experiencing. Overheating can take place and I had this issue already (not OVERheating, but i was quite hot – 65C due to “# temperature g 0” shows 32F :-( )
@Dennis:
sorry for misunderstanding – I use a very easy to handle “fancontrol script” FROM fun_plug website that uses “normal” unix shell commands, including “temperature” (to get temp) and “fanspeed” (to get and set fanspeed). The original “fancontrol” process is not running. But these commands are supported, i guess.
NO OTHER CHANGES have been made to the box – the ONLY intention was to power down the the fan that does some bothersome noise even if temp is low and disks are spinned down (this might be an enhancement request for new firmware releases :-) )
I check with “# temperature g 0” if temperature is below a defined value (108F), then the fan is turned off (# fanspeed w 0), if temperature increases, fan will be turned on again, starting at 2300rpm. If temp still increases, fanspeed also is increased and so on
=> is this a supported way ?
If yes – there is some malfunction, because i get this TWSI error
If no – sorry for bothering you (and i will continue using the well working 1.4RC1)
best regards
PeterJ
PS: last idea would be running the original “fancontrol” process for some time (2 days) instead of working with “temperature” and “fanspeed” commands, but I will be able to do this not until 15.07.
It seems that trying to enable the iTunes server on a non-root direcory causes the internal webserver to crash (and restart after a while). More info available if needed.
@peterJ: if things do not work with Fun_Plug anymore you have to go to the author of that fun_plug
@Hertog: yes, please give more info
Thanks for your answer
Sorry, I did not know that some the commands I use in “my” script (if, then, else, fi, “temperature g 0”, “fanspeed g” and “fanspeed w “, some variable assignments) are NOT originally from CH3SNAS and usage is not supported.
Will test default beviour (original “fancontrol”) with new FW after my holiday trip ;-))
btw: what do you think about the idea of implementing that feature in a new FW release (power down fan if disks are spinned down and temp is below a specified value) ?
This would save power consumption and would also be helpful regarding the fan’s “standby-noise”
many thx
Will there be a patch for the dns security issue?
http://www.security.nl/article/19053/1/Microsoft%2C_Sun_en_Cisco_redden_Internet_van_ernstig_DNS-lek.html
since when acts the ch3snas as a dns server?
I think this does not apply, but you can proof otherwise of course
I seem to be having problems with playing xvids on the playstation3 from the CH3SNAS, using firmware 1.4rc3.
I’m not 100% sure if this is caused by the nas or the playstation, because when I copy it to the playstation they still won’t play: “Data type is not supported”….
Another problem I seem to get quite often is this error message:
Media Server Error
A DLNA Error protocol error (2114) has occured.
Any help would be greatly appreciated, as half of my videos are xvid ..
2110 and 2101 sometimes happens too.
1.04RC4 solves most PS3 issues, but files >4GB will have problems being played by the UPnP Server
I updated to 1.04RC4, and now xvid seems to be working indeed. Thanks!
I hadn’t realised something had changed for this release on the PS3 issues.
By the way, when I ‘browse’ on the PS3 in “Folders”, I always get a directory “-“. Like this:
“\Media\Movies\-\something”
“\Media\Movies\-\something”
It appears impossible to format drives under firmware 1.3 or the new 1.4RC4.
My setup is raid 0 2 times 320 GB harddisks(WD3200AAKS-00YGA).
When downgrading to 1.2 I can format drives again, and then re-upgrade to 1.3 or 1.4 But formatting in 1.3 or 1.4rc4 hangs at around 10% and gives a format failure.
Will swissknife be a solution?
@ michiel, I have no idea ..
we have no issue here.
Sometimes putty give “connection refused”, after spinning up the drives bij the web interface i can log in with putty.
When using putty to connect ch3snas let me log in without asking for a password.
all systems who use dns in one way or another, should patch there client.
Microsoft released a patch this thuesday, http://support.microsoft.com/kb/951748
So all dns-servers should patch, but also all clients should patch.
I don’t know if ch3snas uses dns. If it does, then you should bring out a patch.
Strange. You haven’t had other reports about format failures?
BTW in the support/help tab of the new firmware scandisk is still mentioned.
Formating raid1 with rc3 with 2X500 gigs just gave me a 489 raid1
The leftover should be a bunch of disk like earlier releases
Jbod did not show up i only have 1 raid 1 and no jbod space
status page only give (see below)
HARD DRIVE INFO
Volume Name: Volume_1
Volume Type: RAID 1
Sync Time Remaining: Completed
Total Hard Drive Capacity: 490402 MB
Used Space: 249841 MB
Unused Space: 240560 MB
Upgraded from 1.03beta3. My right drive doesn’t go in powersave mode. This behaviour is exactly the same as in 1.03B4 and up. What can cause the problem? There is no activity.
I encountered a problem with the UPnP server today. It used to work fine, but I decided to organize my media in a different way. I just created some new folders and moved the content around.
I stopped the UPnP server, rebooted, and started it back up again.
As a result of this, the database seems to be messed up. When I look at “All tracks” on my PS3, I see all the files, but they can’t be played. When I look in Folders, it gives the media folder, but after that “No tracks available”.
My folder structure looks like this:
Volume_1/Media/
Volume_1/Media/Audio/
Volume_1/Media/Video/
Volume_1/Media/Video/Movies/
etc.
Are there any specific rules when it comes to folder names (For example audio files only a folder “Audio”) ? Or can I just use anything I want?
the tag of this post is misspelled
After formatting the drives and putting the media content back on it, I am now getting the following error on the PS3:
A DLNA protocol error (2114) has occured.
To make matters worse, the NAS seems to lock up completely after a minute or two of inactivity. The only thing left is to pull the power plug and restart.
I’m seriously starting to doubt whether buying this piece of hardware was such a good idea….
I’m unable to change the harddisk raid-configuration. I use 1.4-RC4. No matter what i choose, Standard, JBOD, RAID-0, RAID-1, it always gives a format error in the pop-up window. After clicking the restart button in the pop-up window and it comes up again, it always starts again with the format window. This does not result in an error. After restarting again, in the status window, it always shows 2 volumes, no matter what i choose as configuration. I tried swapping the drives, formatting with one drive installed. No help. Looks like formatting the first drive always failes.
I have 2 identical 320GB WD drives.
I’ll downgrade tomorrow to 1.3 and try again. I have no computer with sata connectors (only laptops) so i cannot format the drives in an another computer.
@Joris: The Upnp-Server is accessing the Harddrive all the Time…perhaps dennis could review the upnp-Server as it also runs, if it is turned off in the Webinterface! I had a lot of enquiries concerning this issue!
@dennis: I think the Error in Comment 33934 is a serious issue! Please make “fanspeed” and “temperature” working again! Your new Kernel seems to be broken! Please have a look at the Link in Comment 33938!
btw: The tag chd3snas should be ch3snas…
Good morning,
for few days i bought the Conceptronic CH2SNAS with two Seagate HDD (ST3750330AS) with 750 gb each.
My CH3SNAS was shipped with Firmware 1.02 and i configurated the system as JABOD to get the full size of 1.5 tb.
All wents fine.
After a visit of the homepage from Conceptronic i see the new firmware 1.04 RC4 and installed them.
The system reboot and ask to re-format?! I have no date on disc and therefore i confirmed. But i was very surprised to see only on HDD was available.
I cancel the wizard and reboot again.
During the starup the right channel indicate for a second the orange light (problem?) and changed back to blue.
After this only one HDD (left) is available. Therefore i turn off and change the HDD (left to right) and start again. Same is happend. Startup, one second orange led on right and only 750 gb (one disk) available.
I was little bit shocked and flashed back to 1.03.
With this firm all went fine. Startup without any problem and i can format both HDDs with the wizard.
After this i changed again to 1.04 and the same thinks happend. Sometime during the startup no orange led appears but if i start the format it breaks up about 8 – 10% with error “failed” – no error code or more information.
flashed back to 1.03 and all runs fine.
i copy about 350 gb data to the device and no problem appears.
Have somebody a idea why i got some problems with 1.04? later i learned the “RC” means “release-canidate” and means it is a BETA?!?
Maybe it is better to wait until the 1.04 FINAL is available.
Thank you for help.
best regards
Mag
P.S. Sorry for my bad english.
Summary: 1.04RC indeed (see “Mag” and “Uli” postings) has a problem with formatting. Scary.
================================================
I have almost the same issue with upgrading from 1.02 to 1.04RC4 as Mag. By coincidence on the same day.
> for few days i bought the Conceptronic CH2SNAS [typo: CH3SNAS] with two Seagate HDD (ST3750330AS) with 750 gb each.
Me: picked up the CH3SNAS today and installed 2 new Samsung 1 TByte drives.
> My CH3SNAS was shipped with Firmware 1.02 and i configurated the system as JABOD to get the full size of 1.5 tb.
Me: Firmware also 1.02. Configured the system for one volume of 750 MByte of Raid 1 and rest for 500 MByte of JBOD. 2×750+500 = 2 x 1 TByte. So far so good.
> All wents fine.
> After a visit of the homepage from Conceptronic i see the new firmware 1.04 RC4 and installed them.
Me: same.
> The system reboot and ask to re-format?! I have no date on disc and therefore i confirmed. But i was very surprised to see only on[e] HDD was available.
Me: I did not get an explicit request to reformat, but thought that would be safer (and the drive was empty anyway). But RAID Wizard said “Hard Drive(s) formatting failure” – and it took suspiciously little time (but I missed the status bar setting where it failed).
Then RAID Wizard offered to make the second (right side) drive consistent with the left one. During that process, the left drive light turned orange. Then the Raid Wizard now listed 2x Volume_1 (sic) formatted in Ext2 and with format result = Success for each volumes.
> I cancel the wizard and reboot again.
Me: a restart of the CH3NAS resulted in
* orange lamp was gone. Both drives Blue (an improvement).
* but only a 750 MB Volume_1
* Tools>Raid indicating that the firmware was synchronizing the drives (and that this would take about 120 minutes, argggh). This isn’t nice as the firmware is now creating a copy of a drive which was (almost certainly) incompletely formated.
* no sign of the 500 MB JBOD Volume_2 anymore
> I was little bit shocked and flashed back to 1.03.
For now I am waiting with going back to 1.03 (but thanks for the tip, Mag) because I assume that v1.04RC should be able to do something this basic somehow. Will probably try another reformat of the drives via the CH3SNAS (or worst case, using a PC). To be continued.
Peter (located in the Netherlands)
@Dennis:
I can confirm the devices’ behaviour and the problem that “Peter” and “Mag” are facing. I had the same experience, but after a few retries (reboot, wizard and so on) I succeeded to format the two Samsung 1GB drives as RAID 1, so I thought it’s not so important !
@Uli
Thanks for confirming the problems with “temperature” and “fanspeed”
Due to at least these two reasons I would ask Dennis for a FW review BEFORE releasing it as a final version
Thanks in advance
Why do you think I am releasing RC’s ? They are not public yet .. until I get feedback. Only the last 2 weeks I get more and more reports about the latest RC’s ..
all input is valuable and will be taken into consideration
Sorry for that – It came to my mind because you wrote:
> at the start of this page “So probably early next week this version will be released” (this was on July, 4th)
and some more comments about “soon release on official website without anymore changes” on your 1.04RC3 postings site
=> sorry again, I’m convinced you will do what you can to release the most stable version
an update on my previous posting. I downgraded to firmware 1.03 and tried again to create a raid-1 setup. Worked right out of the box without errors.
I wrote earlier today:
> For now I am waiting with going back to 1.03 (but thanks for the tip, Mag) because I assume that v1.04RC should be able to do something this basic somehow.
Unfortunately I gave up getting a stable reformat using v1.04RC4 after a few attempts (and a few hours). And am now running version 1.03 instead.
Summary of what I learned: a drive (re)format of fails with an error message under firmware 1.04RC4 after 2-5% have been formatted. I didn’t test if this also applied when the drives have not been formated under CH3SNAS before. The error occurs using JBOD (says Mag) and RAID 1 (me) and seems pretty repeatable.
Probably the problem doesn’t show up if you just continue using a validly formatted drive.
Possibly relevant detail: freshly formatted shares under v1.02 and v1.03 show that the system uses 24 kB of space (valid for RAID 1 and JBOD). Under 1.04rc4 this becomes 32 kB. Related?
Peter
Hi,
you have a typo in the tag for this message: ch*d*3snas -> ch3snas!?!
Regards, Tom
I had the craziest thing just now. I was watching a .avi on my PS3, using the NAS, and suddenly playback stops, and it turns out the NAS is simply switched off.
So I checked the power plug, all fine, and turn it back on again. It booted and immediately switched off again!
Booted it up once again and now it seems to be working fine…..
to Pjanssen: some basic ideas on what can cause your CH3SNAS to turn off. 1) it can be turned off via the Web interface (prank?). 2) There is a feature to send an E-mail notification and turn off the NAS if it gets above an adjustable temperature. 3) according to the FAQ, if the power is removed, the device does not automatically reboot.
to Dennis/all: Is there a way to find out known bugs/limitations of the firmware (except study the release notes of 1.04 release candidates and maybe 1.05 release notes for the DLink DNS323)? Is there a systematic way to submit bugs (other than posting them here, and hoping it gets on a list somewhere)?
Peter
@uli upnp is also disabled. There is absolute nothing running on the ch3snas. The problem occurs even with the ethernet cable disconnected. Strange problem…..
FYI: the link to v1.04rc4 for CH3SNAS have been removed from the Conceptronics.net site. I think this was sensible as there have been too many problems with it.
Question: I am running CH3SNAS in RAID 1 to reduce the chance of data loss due to drive failure. Questions about RAID 1 reliability and how to test that:
1) Is there a way to test if the two mirrored drive partitions are error free and hold the same data?
2) Can a single operational Ext2 drive partition (of a RAID 1 pair) be _easily_ read from a Linux PC? E.g. as a last resort if the firmware fails.
3) Is it safe to pull out one drive and do read-only tests? What happens when I install the 2nd drive again (with hopefully no reads)? A link to how Ext2 does RAID 1 would be fine.
4) Bottom line question: would you recommend using CH3SNAS for data which cannot be recreated/redownloaded like your own fotos? (Yes, I know that RAID 1 does not replace backup)
Thanks for any help,
PeterH (previously Peter)
@dennis
any comment on Peter’s statement above regarding “know issues” and “submitting bugs” (“to Dennis/all:”) ?
@Joris: If you have a look into the processlist, you will probably see a process called “upnp” even if you switched the UPNP-Server off. This is a Bug in the Firmware, which will probably be solved in the next release (dennis is already working on this problem)
@PeterH: My thoughts: Submitting Bugs should be done via Conceptronic Support (Please write in English!). Submitting them here is also good solution as dennis can forward the bugs to the developers.
@PeterJ: Known Bugs are afaik not listed at the moment. But you can find them all in the comments on the entrys on RC1-RC4.
Peter, there are many forums where you can discuss the status of the CH3SNAS. I have too many projects to handle during my daytime job. So I will not always be able to give extra information or keep lists with issues yes/no
Right now the focus is on fixing the UPnP AV server, some wierd stuff on kernel level submitted by some guys.
Removing at conceptronic site; Yep, due to the issues raised here and at support I’ve advised to remove the link and wait for a new release. (unknown when)
For raid questions”
the scandisk feature is not ok, there are alternative ways through fun_plug which can check the disk(s).
Yes, you can use the disks in a linux machine ..
There is no backup medium which is fail safe, so I always make multiple backups.
(copy to DVD, multiple HDD’s etc. etc. etc.)
So… apparently there is no issue/defect list for the CH3SNAS firmware. For another project, users maintained an online spreadsheet.
This was about a commercial PC tool ($150 or so) used by amateur and professional photographers to convert RAW digital (SLR) images to JPG while correcting various lens errors like vignetting and chromatic abberation.
Such a spreadsheet (or wiki?) can be quite some work (unless there are few issues), but the work can be distributed (multiple people with write/modify access, requires an account with Google/Picasa/etc). Would somebody or sombodies be willing to coordinate the content of such a list? Can we convince PeterJ to help? Would Dennis feel this is helpful (to collect issues, their claimed urgency, and collect user feedback on issues)?
I could help with an empty (simplified) spreadsheet but am not willing to moderate the list. Mainly because I did that for the above spreadsheet. And also because I am not experienced enough with Linux/Unix matters.
A short history of the google docs spreadsheet on the photography tool:
* The vendor had a very (VERY) buggy release 5.0
* Users got (VERY) upset with the vendor (slow bug fixing, vendor essentially denying there was a major problem).
* One user in California set up the spreadsheet (I took over later)
* We managed to get a reasonably high quality spreadsheet. It became a standard reference for serious users and for the vendor (customer support and maybe development team). Note that these users are largely non-IT folks: just people trying to get the tool to work reliably and productively.
* Vendor starting helping by providing info (e.g. “this bug will be fixed in next release”)
* Vendor created its own web-based bug tracking tool which has become operational since version 5.1 of their software. So the spreadsheet was more or less frozen a few months ago.
* Vendor’s software became stable around version 5.2. And they all lived happily ever after (sort of).
In the case of the CH3SNAS firmware, the relationship between users and vendor seem to be pretty ok (probably largely thanks to Dennis). And there seem to be the usual issues (bugs, enhancement requests), but no serious frustration as far as I can see. But a single location of info may help see what the bugs are, whether there are workarounds, whether they have been confirmed by others, etc: “a known bug is a lot less painful than an unknown bug”…
PeterH
@PeterH:
This is a very good idea, i like the idea to maintain all this stuff in a wiki (probably as i have no access to google spreadsheets from my employer). I’d help to maintain and even host (I’m running own servers) such a wiki as i’m already working with the CH3SNAS and it’s “Problems” every day. I can see the advantages of consolidating all those bugs of the different Firmwares together into a list, would be a nice feature.
On the one hand it would be helpful to Conceptronic (Complete Lists of Bugs) and on the other hand it would be nice if the developers could also add the/their known bugs (Perhaps also the workarounds for them).
=> Shall i set something up?
PS: I’m already running a German Tutorial-Page for the CH3SNAS with some helpful tutorials (at least around 200 Visitors a day seem to need it).
@Uli:
The Google spreadsheets use http protocol but probably they use some client-side scripting (as well as service-side processing). Maybe somebody indeed blocks the client side scripting for security reasons – but this is the first time somebody mentioned that there are problems. But never mind…
IMO the person who takes the initiative has the main say in how it should be implemented ;-) So unless we find another volunteer in a few days, I suggest you proceed with your proposal. I will provide support in the form of submitting my bugs (and suggestions on the format/process before/during setup of the Wiki – see below).
Some ideas and lessons-learned from my previous project (maybe half are not useful for you;-):
* Format freedom not always good
I don’t know if a Wiki can provide the structure of a spreadsheet or database or HTML forms. “Forcing” people to provide certain info for a bug report sounds unnice but is useful: you want people to provide info on their version, whether the bug was reproducible, whether it has been fixed in a newer release, etc.
* English
The Wiki “shall” be in English. I have no idea where the CH3SNAS firmware is developed, but English is the only safe option.
* Bugs versus enhancement/change requests
With my previous project, we had religious issues where the vendor wanted these to be submitted/listed separately. My position was “this is an internal distinction for the developers”: they distinguish between “this is not what we intended” and “this is what we intended, but users want something else/more”. So allow users to submit both. If the vendor wants an extra attribute to distinguish bug/changerequest, fine.
* “bug” -> “issue”
I tended to avoid the word “bug” (see previous point). And developers have bosses/customers too. Managers feel “bugs” are defects that have to be fixed under existing maintenance contracts. As users we don’t care: we just have improvemet which we feel are needed (regardless of the bug/enhancement distinction).
* Issue ownership
I tried to get the submitter to feel obligated to help check if the bug disappeared in future versions. Needed to keep the work scaleable. “Adopt-an-issue”.
* Info needed per issue
– who submitted
– version where it occured
– fixed in a newer release?
– how important (nit=small detail, minor, major). I tried keeping the number of Majors down to about 10% to avoid inflation of classification.
– description/relevance
– discussion
– are others able to reproduce the issue?
– is issue acknowledged by vendor, and any comments by vendor (e.g. plans). Vendor has 100% control over this info.
* Dennis buy-in
No (positive or negative) comments from Dennis yet. It is obviously important at some point to get Dennis positive about this initiative. Its value increases significantly if the vendor sees it as relevant/useful info. If you/we are successful in this, the vendor will ultimately create its own initiative to handle simple communications between- and with users ;-) Which is good: you don’t want to be assisting Conceptronic with customer support forever ;-)
* Scope?
CH3SNAS only? What about the “verrrrry similar” DNS323? I don’t know enough about who-develops-what to judge.
* Findability in Google
Obviously important to get people to find the site.
I will have a closer look at your u-li website. It seems to contain info which I need (e.g. family member complaining about the fan). And I am adding a (Sharkoon Quickport-based) driver in a few days to backup the content of the NAS – which allows me to be a bit wilder in exploring options like the fun-plug ;-)
Too much text (again). Sorry.
@PeterH:
The hole Spreadsheets-Page is blocked besides a lot of the Rest of the Internet ;) I think my employer wants us to “work” and not to “surf” or something like that ;)
Thanks for your List of proposals, these are very helpful.
I thought of some structure for this:
CH3SNAS
-> Issues
–> Firmware – Version
—> Headline of a Bug
—-> Detailed Description for a Bug
-> Tutorials (I’d translate my Tutorials)
and so on.
Scope: I think, that the DNS-323 already has a wiki with some bugs. And i think the Scope should be Products of Conceptronic as these are different from the D-Link-Products.
Google: Should not be the problem
English: That’s clear, such a Page needs to reach a lot of people. My Page reaches only German-reading People at present.
Conceptronic: This is my main point. Will Conceptronic accept such a Page or not? Will i run into Problems with Conceptronic?
Forums: Would it be useful to setup some forums for discussions around the CH3SNAS?
If Conceptronic is okay with this, i am definitely willing to setup such a Page!
Uli,
I have no objection. but I cannot speak 100% for my employer of course.
There are many forums / sites discussing products also ours and we read them and use feedback if we can see the product will be better and improved..
So if this is one of them, there is no problem to create such site
@Uli,
Good to hear that Dennis is OK with this. Strictly speaking users can create a web site with facts/opinions about a product regardless of what the vendor says. But we should only invest the energy to make a difference (e.g. help fellow users, improve the software and maybe the hardware), and goodwill by a key Conceptronic representative is really helpful.
Re: “DNS-323 already has a wiki with some bugs. And i think the Scope should be Products of Conceptronic as these are different from the D-Link-Products.” Fine. I wasn’t sure there was a technical difference. Just for clarity: “scope should be products of Conceptronics” hopefully means “Concentronics CH3NAS and any future products which might be sufficiently technical similar” (e.g. a successor or hardware update). I assume you don’t want the new wiki become a Conceptronic-in-General fan site ;-) They make a wide range of devices with cables sticking out and in…
Will look at the tree structure later.
PeterH
fan sites I like ;-)
@Dennis: Thanks for your reply.
@PeterH: The scope was exactly planned like that. The CH3WNAS might be one of the Candidates for the Wiki as it has some things in common (e.g. possibility of a fun_plug) but also some things that differ (e.g. fun_plug differs a little from the CH3SNAS). It was not planned as a fan-site for ALL Conceptronic-Products, but for only some of their Products. I want to improve the little NAS, not all other products ;)
@Uli
If I understand correctly (3 different types of dash symbols confused me), you are thinking of an issue documenting structure like:
CH3SNAS
. . IssueList
. . . . CH3SNAS version 1.04r5
. . . . . . Issue #17 = Setting Time doesn’t work
. . . . . . . . text
. . Tutorials (great! maybe I can help translate one or two)
Note that Issue #17 may (and does) also occur in earlier version and probably later versions of the firmware. How about
CH3SNAS Wiki (can change the title when needed)
. . IssueList
. . . . Issue #17 = Setting Time doesn’t work
. . . . . . Occurs in: CH3SNAS 1.02-1.05. Fixed in: 1.06
. . . . . . Description: When you set the time in the … menu, it …
. . . . . . Workaround: you can run an extra daemon using fun-plug which etc.
. . Tutorials and how-to’s
Alternatively the “Occurs in” could be represented as a table. Rows=issues (gives room for issue title). Columns=firmware versions. Most recent firmware version to the left (only need to scroll if you want to see really old versions).
PeterH (if you want my direct E-mail address let me know)