Recommended Posts

If that is the case then  yeah I would expect bad things to happen.

 

FAA certification only goes to 150% .I know the FAA doesn't have jurisdiction here, but is NASA requiring 200%?  Is this for that ###### LOC rate they require? 

 

4 hours ago, Skiver said:

Still no news on this? I'm so used to SpaceX's quick and open explanations on some of the "failures" they've had in the past, the lack of information on this makes it feel worse than it probably is.

Government is involved.  Could be why it's taking longer?

SpaceX's Hans Koenigsmann re: Crew Dragon test failure. Sounds like plumbing.

Powered up nominally.

Completed 2 Draco thruster firings, 5 seconds each. 

Just before the SDs fired there was an anomaly which destroyed the vehicle.

Indications this happened while the SDs were "activating". Too soon to speculate about root cause.

COPVs are not pressurized during SD activation

Confidence in SDs - 600 tests including integrated;  pad abort and hovers.

Large amount of data; high speed film, sensors and telemetry. 

 

Video does not include the Q&A

 

Edited by DocM
9 hours ago, Skiver said:

Still no news on this? I'm so used to SpaceX's quick and open explanations on some of the "failures" they've had in the past, the lack of information on this makes it feel worse than it probably is.

Well....when the Falcon blew up on the launch pad it took about three weeks before a lengthy statement (aside from ones apologizing for loss of the AMOS-6) and preliminary speculation on the cause.  About 4 months before everything was done...with updates about every month.

 

I wouldn't read too much into them not giving out information at this point.  

 

Just hoping it isn't a design flaw...but we'll know eventually.

  • Like 2

From the above article...

Quote

///

In the company's most expansive comments to date, Koenigsmann said the "anomaly" occurred during a series of tests with the spacecraft, approximately one-half second before the firing of the SuperDraco thrusters. At that point, he said, "There was an anomaly and the vehicle was destroyed."

 

During the activation phase, the SuperDraco thruster system is pressurized, and valves are opened and closed. Since the accident there has been speculation that there may have been some issue with the composite overwrap pressure vessels, or COPVs, which store rocket fuels at extremely high pressures. The COPVs on Crew Dragon are different from those on the Falcon 9, and they would not have been overly stressed at that moment, Koenigsmann said. "I'm fairly confident that the COPVs are going to be fine," he said.

///

He also went on to say that  "We have no reason to believe there’s an issue with the SuperDracos themselves,"

  • 4 weeks later...
  • 4 weeks later...
  • 4 weeks later...

WRT the Crew Dragon explosion

 

https://twitter.com/SpaceflightIns/status/1150825006663897088

 

SpaceFlight Insider @SpaceflightIns
SpaceX has a teleconference set for later today. Most agencies / companies give a couple days notice @SpaceX gave less than 3 hours. Topic is explosion of their @CommercialCrew offering @CrewDragon2

 

SpaceX press release

 


On Saturday, April 20, 2019 at 18:13 UTC, SpaceX conducted a series of static fire engine tests of the Crew Dragon In-Flight Abort test vehicle on a test stand at SpaceXs Landing Zone 1, Cape Canaveral Air Force Station in Florida.

Crew Dragons design includes two distinct propulsion systems  a low-pressure bi-propellant propulsion system with sixteen Draco thrusters for on-orbit maneuvering, and a high-pressure bi-propellant propulsion system with eight SuperDraco thrusters for use only in the event of a launch escape. After the vehicles successful demonstration mission to and from the International Space Station in March 2019, SpaceX performed additional tests of the vehicles propulsion systems to ensure functionality and detect any system-level issues prior to a planned In-Flight Abort test.

The initial tests of twelve Draco thrusters on the vehicle completed successfully, but the initiation of the final test of eight SuperDraco thrusters resulted in destruction of the vehicle. In accordance with pre-established safety protocols, the test area was clear and the team monitored winds and other factors to ensure public health and safety.

Following the anomaly, SpaceX convened an Accident Investigation Team that included officials from the National Aeronautics and Space Administration (NASA), and observers from the Federal Aviation Administration (FAA) and the National Transportation Safety Board (NTSB), and began the systematic work on a comprehensive fault tree to determine probable cause. SpaceX also worked closely with the U.S. Air Force (USAF) to secure the test site, and collect and clean debris as part of the investigation. The site was operational prior to SpaceXs Falcon Heavy launch of STP-2 and landing of two first stage side boosters at Landing Zones 1 and 2 on June 25, 2019.

Initial data reviews indicated that the anomaly occurred approximately 100 milliseconds prior to ignition of Crew Dragons eight SuperDraco thrusters and during pressurization of the vehicles propulsion systems. Evidence shows that a leaking component allowed liquid oxidizer  nitrogen tetroxide (NTO) to enter high-pressure helium tubes during ground processing. A slug of this NTO was driven through a helium check valve at high speed during rapid initialization of the launch escape system, resulting in structural failure within the check valve. The failure of the titanium component in a high-pressure NTO environment was sufficient to cause ignition of the check valve and led to an explosion.

In order to understand the exact scenario, and characterize the flammability of the check valves titanium internal components and NTO, as well as other material used within the system, the accident investigation team performed a series of tests at SpaceXs rocket development facility in McGregor, Texas. Debris collected from the test site in Florida, which identified burning within the check valve, informed the tests in Texas. Additionally, the SuperDraco thrusters recovered from the test site remained intact, underscoring their reliability.

It is worth noting that the reaction between titanium and NTO at high pressure was not expected. Titanium has been used safely over many decades and on many spacecraft from all around the world. Even so, the static fire test and anomaly provided a wealth of data. Lessons learned from the test  and others in our comprehensive test campaign  will lead to further improvements in the safety and reliability of SpaceXs flight vehicles.

SpaceX has already initiated several actions, such as eliminating any flow path within the launch escape system for liquid propellant to enter the gaseous pressurization system. Instead of check valves, which typically allow liquid to flow in only one direction, burst disks, which seal completely until opened by high pressure, will mitigate the risk entirely. Thorough testing and analysis of these mitigations has already begun in close coordination with NASA, and will be completed well in advance of future flights.

With multiple Crew Dragon vehicles in various stages of production and testing, SpaceX has shifted the spacecraft assignments forward to stay on track for Commercial Crew Program flights. The Crew Dragon spacecraft originally assigned to SpaceXs second demonstration mission to the International Space Station (Demo-2) will carry out the companys In-Flight Abort test, and the spacecraft originally assigned to the first operational mission (Crew-1) will launch as part of Demo-2.

  • Like 2

This is why testing happens. :yes: It'll be a far safer vehicle with this new change.

 

Apollo used the "burst disk" methodology as a safety feature too on its' engines. ALL of them. I'm surprised that SpaceX hadn't employed them also; but hey -- experience becomes the best teacher and this kind of thing won't be overlooked in the future.

 

Better that this happened now rather than later. (Y) 

  • Like 3

Yep, saw this.

 

Crew Dragon does have the capability to land anywhere, but of course won't be allowed to land anywhere but water unless it's an emergency. Frankly I think ocean landings are "old school" and need to be rethought. Big waste of resources for recovery not to mention refurbishing the spacecraft (considering how much havoc seawater causes).

 

Seriously, set up a 50 x 200 mile touchdown area in the Western or Southern U.S. (or both) designated as a Recovery Area so that Commercial Crew spacecraft can land on land. I've disliked the idea that we must use the ocean since I've been a kid following space stuff. No, really -- Crew Dragon especially; those four parachutes are overkill. Touching down on land is gonna be easy peasy. Scuff the heat shield up a bit ... so what. Better than seawater.

 

/shrug

16 minutes ago, Unobscured Vision said:

Yep, saw this.

 

Crew Dragon does have the capability to land anywhere, but of course won't be allowed to land anywhere but water unless it's an emergency. Frankly I think ocean landings are "old school" and need to be rethought. Big waste of resources for recovery not to mention refurbishing the spacecraft (considering how much havoc seawater causes).

 

Seriously, set up a 50 x 200 mile touchdown area in the Western or Southern U.S. (or both) designated as a Recovery Area so that Commercial Crew spacecraft can land on land. I've disliked the idea that we must use the ocean since I've been a kid following space stuff. No, really -- Crew Dragon especially; those four parachutes are overkill. Touching down on land is gonna be easy peasy. Scuff the heat shield up a bit ... so what. Better than seawater.

 

/shrug

Boeing agrees that seawater is no good for their Starliner capsule, there are better ways to get them down :) 

 

 

https://en.wikipedia.org/wiki/Boeing_CST-100_Starliner

9 hours ago, Steven P. said:

Boeing agrees that seawater is no good for their Starliner capsule, there are better ways to get them down :) 

 

 

https://en.wikipedia.org/wiki/Boeing_CST-100_Starliner

 

Assuming the heat shield separates so the bags can inflate. If not, things get bumpy.

  • Like 1
  • Thanks 1
  • 4 weeks later...
  • 3 weeks later...
  • 3 weeks later...

The Crew Dragon In-Flight Abort test FCC permit is in.

 

Pad LC-39A

Simulated second stage

 

The start date further indicates the Starship pad mods should be done by then.

 

Start date: November 23, 2019
End date: May 23, 2020

 

Quote


Please explain in the area below why an STA is necessary:

This application uses information from previous grant, 1829-EX-ST-2019. This STA is necessary to authorize launch vehicle communications for SpaceX Mission 1357, a launch from Complex 39a, Kennedy Space Center. The application includes a sub-orbital first stage, and a simulated orbital second stage. Trajectory data shall be provided directly to NTIA, USAF, and NASA. All downrange Earth stations are receive-only. Launch licensing authority is FAA Office of Commercial Space Transportation.

  • 2 weeks later...

SpaceX now has TWO vessels capable of recovering Crew Dragon; GO Searcher and GO Navigator. 

 

And in a rather ambiguous tweet Musk simply said "A Shortfall Of Gravitas." Will it still be a droneship? "Yes" 

 

Starship capable? We'll see.

 

 

 

 

 

  • Like 1
On 10/9/2019 at 2:08 PM, DocM said:

SpaceX now has TWO vessels capable of recovering Crew Dragon; GO Searcher and GO Navigator. 

 

And in a rather ambiguous tweet Musk simply said "A Shortfall Of Gravitas." Will it still be a droneship? "Yes" 

 

Starship capable? We'll see.

 

 

 

 

 

What do you mean by "Starship capable"?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Russia was able to invade Crimea because of those people. But my point is that I've personally heard how great it was to be "back in Russia" right afterwards - look how great it is now. I've asked you a question in another comment which you haven't answered, so I'll ask it again: is it better now without "Europrats"?
    • ZimaBoard 2 1664 Starter Kit review: it's a cool and affordable DIY NAS by Steven Parker IceWhale Technology reached out to me asking if I was interested in testing the ZimaBoard 2, and after convincing them to send me the Starter Kit, it arrived at my doorstep in May. A bit of background: it is a Shanghai-based Chinese company founded in 2020, which specializes in single-board servers and personal cloud solutions. From searching around online, user feedback on the company and ZimaOS is mostly positive, so we're off to a good start. In addition, I should probably point out that although they do not have a large portfolio of NAS devices, with just four of what they do offer, they seem to have covered everything from a relatively low-priced entry point with the ZimaBoard 2, right up to the high end, with the ZimaCube 2 Creator Pack that even includes an NVIDIA RTX PRO 2000. Anyway, as already mentioned, what we have today is the ZimaBoard 2 Starter Kit, and here are the full specifications: ZimaBoard 2 Model 832, 1664 CPU Intel Core N150 (4x E Cores/Threads, Max burst up to 3.6 GHz) TDP: 6W (Base) 10W (Max) Graphics Intel UHD Graphics 24 EUs (1.00 GHz) Memory 8 GB, 16 GB DDR5 4800MT/s non ECC SODIMM (soldered) Disk Capacity 60 TB (30 TB x 2) Supported RAID Types TRAID, TRAID +, RAID0, RAID1, RAID5, RAID 6, RAID 10 Storage 2 x SATA 3.0 6Gb/s Ports with Power Bootloader 32 GB, 64 GB eMMC Network 2x RJ-45 2.5 GbE PCIe 1 x PCIe 3.0 (via LPC) USB Ports 2 x USB-A 3.1 (5 Gbps) Display Mini-DisplayPort 1.4 (4K@60Hz) Hardware Transcoding Engine H.264, H.265, MPEG-4, VC-1 Maximum resolution: 4K (4096 x 2160); Maximum FPS: 60 Virtualization Intel® AES New Instructions Intel® Virtualization Technology (VT-x) Intel® Virtualization Technology for Directed I/O (VT-d) Size (H/W/D) 140mm x 83mm x 31mm Weight 0.4 kg (only ZimaBoard 2 device) Power 12v 5A Power Supply Warranty 1 year (Global) 2 Years (EU) OS ZimaOS v1.6.1 MSRP $339, $399 ($548.60) As you can see above, there are two variants of the ZimaBoard 2. The lesser variant has half the eMMC storage and 8 GB less RAM, although it also costs $60 less than the top variant we are testing today. The above pricing is only for the ZimaBoard 2. I put the MSRP of the Starter Kit next to it in brackets, although as of publishing, it is discounted to $534.50. The ZimaBoard 2 started life on Kickstarter and shipped to backers in August last year. It became available via the official website in late 2025 and Q1 2026. This hobbyist NAS contains the still relatively new N150 Intel CPU released in the first quarter of 2025, with support for DisplayPort 1.4, HDMI 2.1, although in this case, the memory is integrated into the board itself, so it will not be possible to upgrade or expand the amount. It also supports AV1 decoding, as well as H.264, VP8, VP9, H.265 (8 bit), and H.265 (10 bit). The different capabilities in the Alder Lake-N (and Twin Lake) series are listed below. Processor E-cores L3-cache Turbo clock GPU GPU-clock TDP Intel N355 8 6 MB 3.9 GHz 32 EUs 1.35 GHz 9 W Intel Core 3 N350 3.9 GHz 1.35 GHz 7 W Intel Core i3-N305 3.8 GHz 1.25 GHz 9 W Intel Core i3-N300 3.8 GHz 1.25 GHz Intel N250 4 3.8 GHz 1.25 GHz 6 W Intel Processor N200 3.7 GHz 0.75 GHz Intel N150 3.6 GHz 24 EUs 1 GHz Intel N97 1.2 GHz 12 W Intel Processor N100 3.4 GHz 0.75 GHz 6 W The CPU is part of the Twin Lake series that sits near the bottom of the N-series, designed for low- powered systems and entry-level laptops, and as such has a base level TDP of just 6W. As I have noted before, we are seeing another NAS with a great amount of RAM. It's important to mention that the ZimaBoard 2's memory is integrated into the base board (which is why they have two variants of it). As a reminder, up until a couple of years ago, it was commonplace to only get 2 or 4GB max on a flagship Synology or QNAP home NAS. Ever since the likes of TerraMaster and more have entered the market with ample RAM sizes included in their NAS offerings, it has gone a long way in forcing the hands of the traditional makers to up their game a bit. First impressions The Starter Kit came in one outer box with several packages inside it (shown above). I forgot to take pics of it because when it arrived, it wasn't clear what was inside, and I had to confirm with my contact that I received the entire Starter Kit. In the box ZimaBoard 2 ZimaBoard 2 HDD Expansion Bracket + PCIe card frame Zimaboard Mini DisplayPort Male to HDMI Female Cable 4K 60Hz Zimaboard PCIe 3.0 x4 to Dual NVMe M.2 SSD Adapter Card Quick guide [full online guide] Limited warranty notice Screws Design Where to start? You'd be forgiven for mistaking it as an SSD enclosure if not for all the ports on it. It is completely made out of metal, and the top is an entire heatsink. It has a premium feel about it, but it definitely looks like a hobby device. As you will see, the completed build looks like it belongs in a server or meter closet rather than as a showpiece on someone's desk. On what I am calling the rear, there's a Mini DisplayPort (1.4), two 2.5 GbE ports, with Type A 3.1 USB ports, and then the barrel connector port. Around the front, there are two SATA6 ports with a power connector in the middle. Left side Right side One side is completely free of ports. On the other there's a slit that allows for the feed of a CPU fan cable, and a PCIe 3.0 X4 slot. Top Bottom The top is entirely made up of a heatsink except for the extended height for the I/O on the rear. Around the other side, you can find the ZIMA branding and some regulatory information stamped near the bottom. As you may see from the bottom of the ZimaBoard 2, it scratches quite easily from just moving it around on my Ikea island. Teardown Before we get started, let's have a look at this thing on the inside. The steps to get to the board are as follows: Remove the four smaller Torx screws on the bottom of the ZimaBoard 2; Remove the four larger Torx screws on the sides of the device; Carefully unstick the CMOS battery from the PCB; Remove two Phillips screws on the PCB; Lift out the PCB. Yes, as you can tell from the instructions, you need three different tools to remove Torx and Phillips screws (10 in total), and unhelpfully, one of the screws is located under the CMOS battery, which is stuck onto the PCB. Building Now comes the fun part. Because the ZimaSpace website does not provide any guidance on how to put the Starter Kit together. They only have guidance for connecting the CPU fan. However, they did upload a video to their YouTube channel that shows the entire process. To install the fan, first remove the four screws on the bottom of the ZimaBoard 2, then on the inside, there is a CPU FAN connector where you can attach the fan, reattach the ZimaBoard 2 frame, and feed the fan cable through the provided slit. Then remove the nearest screw on the side and attach the fan frame to the side of the device using the same screw. ZimaBard 2 screws Aligning the screws Bottom view Remember those four screws we removed to access the CPU FAN? Longer screws are provided in the box with the HDD Expansion Bracket, which is what you will now need to attach the ZimaBoard 2 to it. Helpfully, the orientation on how to attach it is made obvious when the frame can only be screwed on at the same overall length as the ZimaBoard 2. If you do it the wrong way around (which is what I did initially) one side hangs off the frame, and it becomes difficult to attach the PCIe Adapter Card cable. PCIe card frame Other side PCIe slot connector Next, it's time to attach the PCIe card frame, which is fastened with the help of 3.5-inch SATA HDD (3 screws). These are toolless screws that you can just use your fingers to fasten them with. Then it is time to connect the provided PCIe cable with the slot connector on one side of the ZimaBoard 2, feed it through the bottom of the HDD frame, and fasten it with two standoffs. Both bracket options 2280 standoffs with 2x 4TB MP44Q The PCIe 3.0 X4 card comes with a short bracket option, handy if you decide to place it inside a different NAS or rack server, but here we need the long bracket. Oddly enough, the M.2 standoffs were preinstalled into the 22110 position, but extra standoffs are included in the box, which I installed at the 2280 position for our use. I added a couple of MP44Q M.2 PCIe 4.0 SSDs (2 x 4TB) that can be availed on Amazon for $478.99 (the lowest price for 3 months) that TEAMGROUP supplied us with Then we have the almost completed build, you just need to push the card into the PCIe slot. Unfortunately, IceWhale Technologies did not provide a screw for the PCIe card frame (this is also apparent in their own video). Here it is at several different angles, with the last pic showing the SATA Y-Cable connected to the two WD Red Plus 4TB drives. Setup and Usage Next, you connect your cables to the I/O, and the ZimaBoard 2 powers on automatically, as there is no power button on the device. Power is controlled through the Settings in ZimaOS. BIOS The ZimaBoard 2 includes an Aptio BIOS from American Megatrends [1, 2, 3], and you can setup pretty much everything here including the boot order, which is locked to the UEFI OS, however above that choice you can enable or disable booting to a SATA/USB bootloader so this would still allow you to switch to an alternative bootloader and boot from it, or disable it to instead always start from the first disk with an OS installed on it. Initial Setup Upon connecting to the LAN and booting up, the ZimaBoard 2 can be reached by navigating to the IP address (shown if you have a monitor connected), or you can find it using the ZIMA Client desktop application, which is essentially a Zima device finder. Initializing the ZimaBoard 2 The ZimaOS setup process is pretty straightforward, through a wizard, and in full above, it basically consists of setting up an account and some handy tips, and that's that! Post Setup (ZimaOS update) Upon first boot, you are alerted that there is a ZimaOS update from 1.5.0 to 1.6.1, which I applied; the full process is shown above with the changelog. ZimaBoard 2 Storage Setup Next, it is time to set up the storage. ZimaOS actually throws everything onto the eMMC flash drive; it is also the default location of AppData, which is definitely something to be wary about, as the 45GB available storage could fill up quickly. HDDs I first attempted to create a Storage Pool using the two 4TB WD Red Plus NAS drives, and got an error message: After several attempts and then looking online, I discovered it was a bug with ZimaOS where the fix was simply to reboot ZimaOS and then try again, this time I was able to create a RAID mirror using the two drives. SSDs I did the same for the SSDs, as you will see in the above gallery, when I created the second Storage Pool, it only allowed me to select available drives. ZimaBoard 2 AppData ZimaOS comes with an App Store that includes a repository of almost 400 apps, so you will be able to find most of what you'll need for a NAS (although after a quick search, I wasn't able to find a Surveillance Manager), and now comes the important part: moving the default AppData location off the 45GB eMMC and onto a larger volume: Open Settings Then Apps Then, in the Select a new location field, click on the new Storage volume you want to move it to (in my case, the Apps Storage Pool), which is the SSD RAID mirror. Confirm the Migration warning Be praised! You can also do this for Docker (which by default installs onto the 45GB eMMC flash drive) and the User database. Plex Setup Next, I tested the configuration by installing the Plex Server app from the App Store. The library folders must already exist (which I placed into the Storage Pool). Plex Server setup is straightforward and requires very little configuration. In my case, all I had to do was add the media path I just created, which you can also browse to using the folder icon in the path field. In addition, you can now map the new Media library in Windows Explorer using the Zima Client. Oddly enough, it is not possible to access the ZimaBoard 2 over the Network Neighborhood; you must map drives using the client, which is shown in the last image in the above gallery. I watched one of my Blu-Ray rips, which is Dolby Vision with Dolby Atmos, and the content played fine with no stuttering or buffering, which is what anyone needs in this scenario. ZimaBoard 2 Zima Client mobile app There's also a client for mobile. It is pretty barebones, as shown in the above gallery, for example, the Apps screen launches the WebUI for that app, and the Backup must be done manually. On opening Backup, you can select internal storage folders on your phone to backup to the ZimaBoard 2's storage, and although this is constantly scanned, the backup action itself must be manually triggered. There is an option to allow foreground backup (last image in the above gallery), but this basically means the queued backup gets triggered when you manually open the app. Benchmarking SATA PCIe 3.0 X4 A CrystalDiskMark test on a mapped network drive from within a Windows 11 25H2 PC (image above) connected over a 2.5 GbE was well within acceptable ranges. Writes were generally better on the SSD RAID mirror. SATA PCIe 3.0 X1 I also ran the NAS Performance tester, which tests the link speed performance. As you can see, it pretty much maxes out the 2.5GbE connection. Of course, you can also opt to bond the two 2.5 GbE connections for a bit more umph, but I didn't do that. Thermals Top PCIe card SATA HDDs Next, I measured some hotspots while playing content on Plex. It's fair to say this will perform better than a NAS that is enclosed in a metal or plastic case, as almost everything storage-wise is exposed! Anyway, the ZimaBoard 2 did not break a sweat with Plex streaming or disk benchmarks. ZimaOS Factory Reset ZimaOS does not include a factory reset option. Instead, you have to download the ZimaOS image and flash it to the eMMC manually. The flashing process is shown in the above gallery. The steps to do so are listed below: Download the ZimaOS image here; Open BalenaEtcher (Run as Administrator) and select the image; Select your inserted USB drive (min 8 GB) Flash to it; Connect your USB drive, monitor, keyboard, USB hub (optional), mouse (optional), and network cable (recommended) to the ZimaBoard 2; Connect power and press F11 continuously; Select your USB drive starting with UEFI in the boot device menu; Press Enter on the Install ZimaOS option; Select /dev/mmcblk0 (MMC) flash drive as target; Confirm with (three times) to wipe the target disk; Wait a couple of minutes while ZimaOS installs; Remove the USB drive and confirm with a reboot; Your ZimaBoard 2 has been factory reset. However, you don't have to stick with ZimaOS, in fact the company also offers official CasaOS images, that are based on Debian; or as they say themselves, put anything you want on this "hackable single board server" it's up to you. Conclusion I had a lot of fun putting this together. I've custom-built all my own PCs and servers since the 90s, and this is the first time I have had to put a NAS together. Even if the actual base ZimaBoard 2 was already a completed build, it still feels pretty custom. I just wish that IceWhale Technology included a getting-started guide in the box for the Start Kit, which would have really completed this kit. Instead, I had to search for the official video on the YouTube channel to make sure I wasn't doing anything wrong. So who is this for? Definitely the hobbyist who is comfortable building their own PC and servers. It also has a much smaller footprint than its nearest equivalent (in terms of specs), like the Beelink Me Pro, which is another NAS I will be testing soon. Although the Beelink does not come with the PCIe 3.0 X4 expansion, the ZimaBoard 2 Starter Kit suddenly looks to be a great bargain, even if it only offers the two 3.5-inch bays over the four in the other example. It makes a lot of sense to use Intel's N150 chip inside a NAS; it is more than capable of doing what the ZimaBoard 2 is intended for, media streaming and backup. It also looks like the IceWhale Technology staff are quite active in the official forums helping people with issues they come across with ZimaOS and the devices, peer support seems to be good as well, I was quickly able to find why I was not able to create a new Storage Pool in ZimaOS v1.6.1 even though that is quite a serious bug, hopefully it will be fixed in the next update. If you are comfortable with the command line and Docker, you'll be fine. You can do great things with this hardware. This was my first time with ZimaOS. It seems a bit barebones in comparison to the likes of Synology DSM, TOS, and UGOS, but it has a ton of apps to get you started with your home or small business NAS. Where to buy As of publishing, IceWhale Technology is running a discount of up to 5% for the Starter Kit. If you opt to get just the ZimaBoard 2 itself, it does come with a SATA Y-Cable, so you will be able to connect up to two 3.5-inch HDDs to it. ZimaBoard 2 1668 Starter Kit for $534.50 on Amazon US (was $548.60) ZimaBoard 2 832 Starter Kit for $372.88 on Amazon US (was $390.60) Zimaboard 2 1668 (16GB+64GB) for $419.90 on Amazon US Zimaboard 2 832 (8GB+32GB) for $359.90 on Amazon Disclosure: IceWhale Technology provided a free sample without any editorial input or review pre-approval. Good to know The Amazon link is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, when you purchase through links on our site, we earn from qualifying purchases.
    • It's in the Insider's group so yes it's technically beta, though these days it's hard to see much of a difference unless you opt for the most extreme beta builds, which I don't. When I moved here from the Release Preview channel I did so primarily because I wanted to see how well the restored taskbar functionality (restored from Win10, and earlier) is working and whether it was time to finally abandon SAB--and it is--working fine, so far. Not as polished as SAB, but it'll do for me.
    • I've been using MWB Premium for a number of years so that along with Windows updates and updated browser should be fine. Thanks for that.
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      488
    2. 2
      +Edouard
      222
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      Steven P.
      74
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!