I believe something is wrong with your RAM. Heard kind of the same beeping sequence when booting the Mobo without any RAM stick inserted. Try it without the stick, if it's the same beep sequence, you have your answer.
12gen N-series Nas motherboard (topton, cwwk, ... )
- Thread starter Steffe
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
So, update on my purple board build:
Has anyone managed to control the CPU/SYSFAN headers through Linux CLI ? sensors-LM does not detect them, and bios options for the fan control seem to do nothing.
- bios: CW-NAS-ADLN-KV10_noBootSATA_20240624
- using a intel stock cooler works perfectly over the coper plate, does not interfere with nothing
- Crucial 32GB 4800, no problems
- Pci-e x4 works fine, I have a bootable x4 NVME adaptor+1TB SSD plugged in to get that max speed.
- Additional nvme m.2 ASM1166 6xSATA adaptor also works fine.
- PCI-E ASPM is bios default, disabled, even if put to auto it reverts to disabled, but.. image hosted at ImgBB this shows that ASPM is working, the board reports C10 state with powertop ( image hosted at ImgBB only shows C1 C6 C8 C10, so I'm not sure how accurate this is )
- Real power consumption reported by smart power-plug With 2 HDD and around 20 dockers running, 24 idle / 32 W with hdd spinning /64W in full stresstest ( using a 550W gold power supply, was hard to find a PSU that does not cost an arm and fits in a N3.. )
Has anyone managed to control the CPU/SYSFAN headers through Linux CLI ? sensors-LM does not detect them, and bios options for the fan control seem to do nothing.
Last edited:
Have the CWWK I3-N306 non-dc board and I am able to access/read the fans in lmsensors by emulating another chipset - modprobe it87 force_id=0x8620 && /etc/init.d/kmod start. I did attempt to make a profile, but upon first attempt the fans stopped and the PC rebooted :/
Following this one, I think.
Please do let me know if you make it work. I am quite annoyed by either have 0 or 100% fan speed.
We're getting conflicting reports on the screws vs the Jonsbo cases, but only this last week! The board seems to be drilled for M3 screws. (one of the two standards that exist). So you will need M3 screws from somewhere.I got my CW-NAS-ADLN-K a couple of days ago. (I had to wait a month before the actually shipped it) but now it's here its a very nice board and totally stable so far.
Working fine with 32GB Crucial.
I did notice straight away that the mouting holes were to small as it wouldn't fit on my testbench.
I have received the correct IO shield but just double checked and I did not receive any special screws. (how much of a problem is this?)
Still waiting on Jonsbo N1 to be delivered and didn't think it would be a problem until I started reading this thread.
The least clarity is the standoffs in the case. Some have said they are UNC 6-32 female rather than M3. If that's true then you'd also need to buy standoffs that are UNC 6-32 male and M3 female. Fairly common on amazon/ebay/etc. These should then screw into the holes in the case, but provide M3 holes to the board. You'd fit these instead of the supplied ones, and assumes the case holes are 6-32.
If you can find an M3 screw and a 6-32 screw you can gently test the holes in the standoffs. M3 have a fine thread whereas the others are quite course. Don't force a larger screw as it will mash the threads and could also damage the motherboard.
Ok thanks for the info. I am still waiting on my case... starting to wonder if that £15 discount on local pricing is worth a several week wait
.I have lots of screws and stuff kicking about so I am sure I will find something that works. Bit strange the size of the holes on the mobo. I have never built ITX before so don't know if that’s common. Built my fair share of ATX and MATX over the last 30 years and I have not come across these tiny holes before. I am sure they are part of a standard but must not be the common one.
What settings did you set the ASPM mode the bios? There is an Auto option and then I think a C1-C10. Do you set it to C10 for the max? Many thanks!
305
I set it to auto the first time I booted after bios update, but after checking the next day, it was set again to disable, however, it works as shown in the picture, there is also an L1 option in the bios, I'm not sure if the reverse to disable state is only visual or the board has ASPM on even with the setting disabled.
Last edited:
I know that guide, the board has fan control in bios but they don't work so I asked Cwwk for some clarification/help.
I will try some more. I'm assuming this is the one that should control the fans: image hosted at ImgBB . IT87 should actually support the 86
If nothing works I'll probably just get a 5$ multi-channel PCI knob fan controller and power it from Sata and call it a day. ( image hosted at ImgBB )
Last edited:
Little update on my N100 purple board with wrong I/O shield, and very rude seller rep who told me to pay them $50 to ship the correct I/O shield.
went through the dispute, and requested partial refund/keep item, and they actually gave me a full refund.
went through the dispute, and requested partial refund/keep item, and they actually gave me a full refund.
Can anyone let me know the correct way to update the bios? Have the original CWWK board (pre-purple) and am trying to install the latest 2024.03.05 BIOS.
The instructions below don’t seem to work. Typing 1.nah I get “1.nsh is not recognised as an internal or external command, operable program or batch file’.
The instructions below don’t seem to work. Typing 1.nah I get “1.nsh is not recognised as an internal or external command, operable program or batch file’.
The procedure is more or less the same:
- Create a bootable usb stick with Ventoy
- Copy the iso file in the empty partition created by Ventoy
- Boot "server" from usb stick
- Select the iso file
- When countdown comes, press any key to stop it
- At this point there is a different from the video (minute 1:50), probably there is a problem in our script: the procedure doesn't start, you have to launch it manually (type 1.nsh and it starts).
- Wait the end
- When prompt comes back, type "reset"
- Remove the usb stick during reboot
- Enjoy!
I figured it out - I needed to let the startup.sh run (i.e. not press any key to stop the countdown) and then run 1.nsh.
Running 2024.03.04 and proxmox (latest version/latest kernel). Tried enabling C-states, however, still get the proxmox boot process stuck at 'Loading initial ramdisk'.
Has anyone actually got c-states + proxmox booting under 2024.03.04 on the original N305 black CWWK board? Boots fine with BIOS 'optimized defaults' only (which has C-states disabled...).
Update: I also tried booting unraid 7 beta and debian 12.6 live iso. No boot if c-states enabled on either of those either. Boots fine with c-states disabled.
Running 2024.03.04 and proxmox (latest version/latest kernel). Tried enabling C-states, however, still get the proxmox boot process stuck at 'Loading initial ramdisk'.
Has anyone actually got c-states + proxmox booting under 2024.03.04 on the original N305 black CWWK board? Boots fine with BIOS 'optimized defaults' only (which has C-states disabled...).
Update: I also tried booting unraid 7 beta and debian 12.6 live iso. No boot if c-states enabled on either of those either. Boots fine with c-states disabled.
Last edited:
update on this, the last build of it87 mantained by frankcrawford supports the 8613E sensor ( can control CPU and SYSfan1 only, info from cwwk ) so:
Code:
apt-get install build-essential dkms git
cd /home/
git clone https://github.com/frankcrawford/it87
cd it87/
make dkms ( mine errored out first time and asked for linux-headers-6.1.0-22-amd64 so you may need to also apt install linux-headers-XXX-amd64 )
modprobe -v it87 ( start probe manualy )
sensors ( to see if it works, may have to do a " yes | sensors-detect " first )
echo "it87" | sudo tee -a /etc/modules ( to autostart )
To update rm -rf /var/lib/dkms/it87 and run dkms again ( also update the linux-headers package to your kernel version before DKMS comand)The next phase is to test if PWM can be controlled once I get home and plug in some fans, in stress-test fan2 ramps from 0 to 2000+ so the CPU fan seems to at least report correctly
Last edited:
i have the purple N100 2 NICs version with 16GB RAM and 128GB SSD. Initially there was powering up issue as all i got was blank screen. But after removing the CMOS battery and reinsert it and let it boot for a long while it started to boot. I added 2 HDDs and I've been using it for a while as my Proxmox + Jellyfin + Truenas server. It was working fine until recently.
Initially I couldn't launch the Web UI for my Proxmox/Jellyfin/Truenas. I tried pinging those IPs and did get a response. so i rebooted the system and it works, but this behaviour keeps repeating. I later hook a monitor to see what's going on and I realise that i keep getting "EXT4-FS Delayed block allocation failed for inode" error.
Some research online seems to suggest a disk failure or disk full. Anyone has theirs with the cheap 128GB Shiji SSD the vendor provides that is failing? I checked the that the VMs disks are not full. tried to run fstrim and it did clear some data but soon enough run into the same EXT4-FS delayed block allocation faliure again..
Any clue what i should check next? or Should i update the bios to the latest one? is this the link for the purple N100 board?
Initially I couldn't launch the Web UI for my Proxmox/Jellyfin/Truenas. I tried pinging those IPs and did get a response. so i rebooted the system and it works, but this behaviour keeps repeating. I later hook a monitor to see what's going on and I realise that i keep getting "EXT4-FS Delayed block allocation failed for inode" error.
Some research online seems to suggest a disk failure or disk full. Anyone has theirs with the cheap 128GB Shiji SSD the vendor provides that is failing? I checked the that the VMs disks are not full. tried to run fstrim and it did clear some data but soon enough run into the same EXT4-FS delayed block allocation faliure again..
Any clue what i should check next? or Should i update the bios to the latest one? is this the link for the purple N100 board?
@NinjaHub, is that an issue on the boot disk or one of the HDDs? I would try running e2sck to check the EXT4 partitions in question for any issues - ‘e2fsck -vfn /dev/sdXX’ will check the partitions in read only mode so you can see if anything wrong with any of them, whilst ‘e2fsck -vf /dev/sdXX’ will run and fix the problems (you can do -vfy instead of -vf to auto accept all corrections instead of agreeing to each of them one by one). If the issue is on the boot disk, these may need to be run from an alternative boot disk (maybe live debian or something).
Sorry for my slow reply. I got it to work. The reason for the blak/blank screen was that it was connecting the monitor using HDMI, and when I tried with a DisplayPort to HDMI adatper, still black screen. But with a DisplayPort cable directly to the monitor, I got I a screen. Afterwards evrything worked fine. And I guess that the beeps where when the post process was done, I had to disable it in the BIOS.
Ok so some good news I think, my case has still not arrived but I have found some screws that fit through the holes and screw into the standard size standoff! So thats a problem sorted for now I hope. I think they are both the M3 size. The standoffs are m3 for sure and the screws screw in with no force or anything and the slide through the holes in the mobo.
Thanks for responding!
It is the OS drive, so when that happens, everything is read only.. i cannot run any command such as fsck, e2csk, df.. but system did not freeze. i can still do basic things like ls and change directory.
I search and found some older (4-5 years) post and seems to suggest this could be due to IOMMU or NVME ASPT ASPM issues. When i disabled ASPM in grub, my NIC port stop working as well. So i have to re-enable that. I'm trying without IOMMU, but would have to update my TrueNAS VM as i used that for my HDD passthrough.
Since the indications are on IOMMU or ASPM and only happens post Proxmox update, i'm thinking to update the BIOS. but before that I wanted to check if anyone else have similar issues with the Shiji SSD that came with the hardware. Was tempted to get a SSD from a more popular brand such as Crucial or Samsung or WD, but those older post that came up from search seems to indicate similar issues on those NVME SSD. Perhaps it's resolved now...
fixes to the SATA chip, update.
Regarding this, by default fancontrol is unable to control the speed, it will ramp it up to max rpm but won't turn it down again, however, the bios settings for the sysfan seem to work so I chained 4 fans, set the PWM to 120 and call it a day for now.
There is a pwm2 and pwm3 file with pwm values set from the bios but they are locked, I'm unable to directly edit them. ( odroid-h3:application_note:fan_speed_control_with_temp [ODROID Wiki] for reference )
Last edited: