All my syncs to Box, DropBox, etc. are handled by my Synology NAS. Since it still supports SMB1, the shared folders are easily mounted on the ol' PPC systems.
All my syncs to Box, DropBox, etc. are handled by my Synology NAS. Since it still supports SMB1, the shared folders are easily mounted on the ol' PPC systems.
This sounds interesting. Is it easy to set up?All my syncs to Box, DropBox, etc. are handled by my Synology NAS. Since it still supports SMB1, the shared folders are easily mounted on the ol' PPC systems.
You just need to buy the Synology NAS (Network Attached Storage) first. That'll set you back from about $200 to more than $1200 depending on which NAS you want to buy.This sounds interesting. Is it easy to set up?
I'm thinking of going this way...I know it's costly since we try to maintain our old powerful machine that has a little backward compatibilityAll my syncs to Box, DropBox, etc. are handled by my Synology NAS. Since it still supports SMB1, the shared folders are easily mounted on the ol' PPC systems.
What about setting up an FTP server on one of the machines?
Those LaCie d2 drives look super-cool with their blue eyes
Those LaCie d2 drives look super-cool with their blue eyes
Drive failure is the number one reason I make a daily and weekly backup of drives. One goes to my NAS (the daily), but I realized that this could fail too (as you found out with the LaCIE). All my RAIDed drives are RAID 0, so one drive goes the whole thing goes. That's why I do a weekly backup which goes right up to Dropbox. Sure, the drive that has Dropbox on it could also fail, but I'm paying Dropbox monthly for 4.1TB. They'd better have their own backups, redundancy, etc or we're going to have problems.Aaaaaaaaaaaaa that nebulous blue eye button glow… post-traumatic flashbacks of my LaCie 1TB 301369U devouring itself just a year after getting it new (specifically, we think the embedded linux kernel which managed the xfs formatting of the 2x500GBJBODRAID 0 (striping) and served as a layer between Mac and the physical HDDs corrupted the directory) — not losing the data, per se, but making it nearly impossible to find individual files, even harder to retrieve them without content loss, and impossible to preserve directory hierarchy).
The several hours I spenton the phonevolleying email with the impressively unhelpful, borderline hostile LaCie help desk (which insisted I send them the drive, to fulfil the 3-year warranty replacement, but I wouldn’t be permitted to open it to extract/recover the data[!!!], nor would they offer or refer a LaCie-approved service for data recovery) changed overnight the way I handled local storage. Ever since, I’ve set up my own hardware or software RAID volumes, and they are not handled by an embedded kernel layer within the external RAID device (critical archives get copied to an additional drive, which is promptly disconnected and put into deep storage).
Whatever reverence I felt for LaCie in the mid ’90s, during the late 68040/early PPC 601 days, was obliterated by the ominous blue eye of doom. However unfairly to much better systems out there nowadays, like QNAP or Synology, I have an extremely hard time putting stock in an intermediary layer of file server handling which is handled, principally (if not solely), through a web interface. Thanks, but I’ll save the web interface for my router.
BRB wiping the panicked sweat from my brow…
UPDATE to add: there was a whole thread about this on MR starting about six weeks before mine failed.
Do you need the speed of RAID 0 or is there another reason for that setup rather than e.g. RAID 5 or JBOD?All my RAIDed drives are RAID 0, so one drive goes the whole thing goes.
The device enclosures I have use either RAID 0, 1 or JBOD. I use RAID 0 because I want the capacity of two (or more) drives combined. JBOD means I have multiple drives. Backing up is my compensation for not using RAID 1.Do you need the speed of RAID 0 or is there another reason for that setup rather than e.g. RAID 5 or JBOD?
Hm. I thought JBOD concatenates several disks into one logical disk, combining the capacity, but writing data sequentially, filling one disk after another. That still means things (can) get nasty if one drive fails though.JBOD means I have multiple drives.
RAID 0 spreads all data over all drives. Say you have a file that can be broken into six chunks labelled A, B, C, D, E and F: a two-drive RAID 0 puts chunks A, C and E on the first drive and chunks B, D and F on the second drive. When accessing the file, it's read from two drives simultaneously, increasing transfer rates.@Amethyst1 yeah, at least in my Raid it does that, but its not clear to me what is the difference with a Raid 0,
I may have misread things, it's been a while since I set these up.RAID 0 spreads all data over all drives. Say you have a file that can be broken into six chunks labelled A, B, C, D, E and F: a two-drive RAID 0 puts chunks A, C and E on the first drive and chunks B, D and F on the second drive. When accessing the file, it's read from two drives simultaneously, increasing transfer rates.
AFAIK, a JBOD also combines several drives into one but simply writes data sequentially, filling the first drive first and only moving to the other drive once the first drive is full.
A FoxBox or Fluid app was one way I was accessing Dropbox before Czo began maintaining the Dropbox app for us way back when.Could a FoxBox work? Just throwing out ideas.
I managed to get things working using nfs instead of smb. I don't use Windows so I don't care about smb. I can now connect to the file server using nfs://path from the PowerPC Mac and from Linux machines. I've turned off samba on the server and will probably uninstall samba going forward.
In the past, I setup nfs shares on a PowerPC Mac. It seems that there are lots of options.
Tiger and Leopard use SMB, which is SMB2 (at the very least in Leopard's case). You can also force SMB1 by using CIFS.
Are you saying that Apple has completely removed SMB1 and SMB2 from the M1 Macs? There is no backwards compatibility on this?