drrehak - You said you selected the front USB location for active database media. On reboot, the drive was formatted to EXT4 (linux) so MB can use it for the active database. Therefore the USB drive no longer contains a FAT32 partition, which is needed for database backups. So MB can't find the required FAT32 partition to use. It's the same scenario as using the internal drive for database media but without an
external FAT32 USB connected, and trying to do a backup. Backup fails because there isn't a FAT32 partition. And it doesn't make any sense to make a backup to the SAME drive as the active database.
TonvG - You originally selected to use the
external drive for database media as well, so your drive was also formatted to EXT4. Both Windows and macOSx cannot interact with EXT4 drives unless a 3rd party tool is used. Windows won't even recognize the drive. On macOSx you will get a pop up saying it can't read the disk and do you want to initialize it? Only after you initialize it can you see the drive in disk utility. Now you have 3 selections: Name, Partition, and Scheme. Name doesn't matter, partition HAS to be FAT32, and scheme HAS to be Master Boot Record (MBR). MacOSx defaults to GUID partition scheme, so you have to be careful and change this. While GUID will work in theory, macOSx will always create a hidden EFI partition, in addition to the one you are trying to create. The EFI partition is FAT32, about 196 mb in size, and given the #1 label (sda1 or sdb2, etc). It also will not automount on the macOSx desktop. And as far as I can tell, MB always mounts the #1 partition, so the EFI partition is the one that is mounted and used for backups. You have to go into disk utility, and as Bart mentions, select the drive volume, not the partition, in the side bar and use the "erase" function. The drive volume usually shows the vendor name in it, hit cmd2 if you dont see it. This is why you are only seeing the 196 mb available in the log message during MB backup, and why I showed the screenshot in your other post comparing backups on GUID and MBR formatted drives using macOSx.
As I said, GUID scheme will work, but you need to use a 3rd party tool, or 'gparted' in linux to avoid unknowingly creating the EFI FAT32 partition that macOSx automatically creates.
OK, now back to the original OP post.
Bart wrote: ↑Sat Jan 22, 2022 2:48 pm
But I like to know if anyone knows the answer to the question above...
Bart - There was post in another forum where the user mentioned that Boris said that ATP Nanodura SLC USB drives would work, as a replacement for a failing internal drive (P# ATP AF1GUFNDNC(I)-AABXX or ATP AF1GUFNDNC(I)-AAAXX). Both Boris and mattK also responded in the thread, and didn't take issue with those p#'s. Here is the thread:
https://www.wxforum.net/index.php?topic=38937.0
After a bit of googling, I found a very similar drive on Digikey ATP Nanodura SLC P#AF8GUFNDNC(I)-OEM-ND for ~ $140 US. I assume the difference between AF1 and AF8 in the first part is just 1GB vs 8gb drives, but no idea if that's correct. Also I have no idea if the difference in the last part after the dash matters. But there doesn't seem to be a lot of ATP Nanodura SLC options available, at least here in the US.
I'm not recommending you replace the internal drive (that will void your warranty), or even you should use one of these drives in the front USB port. Just wanted to point out some SLC drives that appear to meet the needs of more frequent database writes.
I'm a little intrigued by Gyvate using a SLC SD card and USB adapter. But I'm still a little on the fence about the benefit of using that, especially if it takes up the front USB port, as it makes database backups a lot less convenient. And a USB adapter is just another piece to fail. But seems like he is having good success with it. SD SLC cards are a lot more affordable, and if they're good enough to use in a PI and Nano, maybe the Pro too? There is a list of recommended/required SD cards for the NANO SD and MBRPi on the main meteobridge website.
I've had my MBPRO red for just over 2 yrs, and my internal drive shows :Internal 864 MB total, 759 MB free (12% used, 1.2 yrs) and the latest database backup is only 80mb. So I'm wondering how big a database could possibly get? Up until recently, I was just using the MBPro to upload real time data to another website template, and that would do a lot of the logging. So I never really paid much attention to the database size and maybe I don't actually have 2yrs worth of data? I am only just now discovering the capabilities of generating nice HTML charts, and these are quickly filling up the drive. I'm also running out of 'events' to offload / upload, so looking for a solution. Maybe a bigger drive would be nice, or maybe figure out a way to back these up to the
external FAT32 drive?