Subj : What to do with a gia To : Ky Moffet From : Barry Martin Date : Thu Aug 29 2019 19:32:00 Hi Ky! > > And yes, I sort of figured you had found the information I did, just > > sometimes I'll put the search terms in a different sequence or add or > > leave out a phrase and find something unique. > KM> You never know, especially what with all the stupid custom > KM> results. No, Goo-duck, I want the exact thing I searched for, not > KM> what you think I wanted!!@*&^@@@##!! > There are times when I do misspell/mistype something and Google will > offer the right one. There are also times when I try to type what I > want, with the plus and minus options, and still get what I didn't want. KM> Duck is pretty good about that, but often as not I want MY KM> spelling! Frequently, yes. > And sometimes just fun to help someone, like with the Adrian can't be > shut off in the previous message (or at least my reading sequence!). ^C > is the answer, or at least supposed to be the answer -- now you get to > find out why it didn't work. And maybe you knew about > www.TheAdrianProject.com, maybe not. KM> Hadn't heard of it, tho I suppose it had to come from somewhere! KM> But when I was quick-testing distros, the whole didn't impress me KM> so much that I cared enough to chase after it. That makes sense. I've done testing and didn't like the way a utility worked, or didn't work, ow was the same utility as what I had tested and dumped before just renamed. > > Interesting on the USB Boot. That is one way to do an installation with > > 'regular' computers, though I'm still using DVDs. > KM> You're supposed to use the embedded management engine, which I > KM> haven't entirely figured out yet. I read the fine manual and was > KM> not enlightened. I watched a video and began to have a glimmer. > KM> Perhaps I'll experiment and hope nothing explodes. One of the > KM> SSDs will be used as the OS drive (it has two 2.5" internal drive > KM> bays for this very purpose). > I'll admit to (maybe too freqently!) want it NOW. The DVD installation KM> Last week would be nice. :D And I would like this knowledge to KM> just magically appear in my head; I have little patience with KM> pursuing it. Maybe next year I won't be so busy, and will also be KM> officially an Old Fogey eligible for free tuition, so maybe I'll KM> go take a networking course at the college... Or teach it! ...I have spent a lot of time 'learning on the fly' stuff that's probably halfway common knowledge to the Computer Science graduates but for me, never heard of it! > just about always seems to work -- there are two computers where the DVD > seems to have been software-disconnected and so they have been sitting > gathering dust - literally. Used to work, for some reason don't work > now, or the last time I tried. KM> It doesn't have a DVD drive. I'd have to use the USB DVD (which I KM> happen to have) or hook a loose drive to the internal SATA port. I can't recall if I tried an external USB DVD or not. Recall spent a lot of time with seems like five different drivers. Maybe didn't have the external DVD then (those two computers have been hanging around that long??!!!). > Thumbdrive installation probably is no big deal and probably is a little > faster, though doesn't give me the flashing LED indicator like a DVD > does to say something is happening even though the screen is just > sitting there. KM> Flash drive install is a LOT faster, probably 10x faster for the KM> average install, and better yet if it's USB3. Optical drive is KM> severely limited by low rotational speed (have you seen the demos KM> of CDs flying apart in shards at speeds above 52x?). Haven't seen but have heard of some nasty occurrences. KM> And most flash drives have a busy-LED, tho commonly it points at KM> the floor if plugged into the mainboard port. This is solved by KM> using a cable (be sure it supports USB3) so it can flap around in KM> sight. :) ?? What have I been buying? I haven't seen a LED on a thumbdrive/flash drive/USB stick in years. Might see some soon: I bought a bunch of small (capcacity) ones (8 GB IIRC) for a picture project for my Mother and Aunt specifically because they said they had a LED indicator. As for the LED indicator being pointed wrong, yes, the old-old ones I have here with an LED always seemed to be pointing the wrong direction and here were times I used an extension cable to flip 'em over. > Never tried a network install. KM> Me neither. Seemed the ones done at the store took d-a-y-s. And seems like someone always fiddled with the system while it was upgrading/being rebuilt/whatever and so the process had to be restarted. > > Now for the "what would I do with 53 pounds of server?". And what was > KM> Boat anchor? :) > I wonder if that's enough for the current on the Mississippi River? > (It's only about a dozen blocks from the house.) KM> Probably not :) Have friends across the river in Davenport, only KM> a block from the river (EEEK!) tho they tell me behind good KM> levees. (whew!) Ah! They're on the good side too! (I'm in Bettendorf.) > KM> 24TB straight up. Plus I'll probably hunt down some used SAS > KM> (cheaper than used SATA) HDs to fill the vacated bays. > Wasn't familar with the term and probably others aren't either so here: KM> Yeah, you pretty much never see SAS drives unless you have a KM> server! Never thought I'd own one, let alone eight. Or twelve KM> once I get it refilled (need to check how large it supports). Right: almost seems as logical to fill it to the max even though have no idea what with. That'll come along! And always better too much than not enough. > SAS SSD vs. SATA SSD > A SSD delivers faster data transfer rates than a serial ATA (SATA) SSD. > ... SAS drives use a higher signal voltage than SATA drives and can > reliably transmit data -- with better overall data integrity end to > end -- at twice the speed of SATA drives. > > https://searchstorage.techtarget.com/definition/SAS-SSD-Serial-Attached- > SCSI-solid-state-drive > > OK, may as well go with the super-speed while you're at it! KM> Yep. And they're HGST 7200rpm so I expect the speed is KM> impressive, and this particular drive, per Backblaze stats, KM> almost never fails. Even better: lasts forever, or at least until you're done with them. > "Ytch!" I've got a bunch of JPGs from my first visit to Vienna which > somehow became corrupted on the camera (cell phone) memory card -- have > been able to recover some and others are still need to be worked on - > just hadn't looked around for better/other repair utilities plus wanted > a faster computer (like this one which I built in the interim) to > hopefully get things done quicker. KM> There is no repair utility as such, other than extracting 'em KM> from whatever sectors were recoverable, then hand-editing the KM> resulting file. You have to learn what is and isn't data by KM> sight, and hand-delete what's not. Foreign junk will always be KM> some multiple of a sector, or the slack space at the end of a KM> cluster. (Yet another reason to defrag early and often!!) OK, so possibly I've done all that can be done. I was able to recover some of the pictures from the corrupted files; some had two pictures (or most of the picture) and I think one even had three partial pictures. KM> When you see a JPG with the bottom part tutti-fruiti, but KM> otherwise the displayed size looks right, you've got some garbage KM> in the middle of the file (it can only decode and display down to KM> the garbage). Delete that garbage with your handy hex editor KM> (Frhed in my case), making sure there are no leftover bytes, and KM> assuming the rest of the data is intact, the file should look KM> normal again. OK. (Need to keep this for reference!). I had used a utility which extracted automatically and then went back and manually looked for the header and tail information and extracted some more that way. KM> IIRC Frhed lets you jump down N-many bytes, so I'd find the bad KM> spot, then jump down by sector (selecting as I went) and after KM> one or more jumps landing right on the next good byte. Delete, KM> done. Got so my average processing time for ordinary corruption KM> was about 30 seconds. I think that was sometimes the time it took just to load here with the old system! > RAID and JBOD do seem a little 'dangerous'. I will admit to using JBOD > with my backup NAS in the basement. So far so good. Know with JBOD if > one drive fails essentially all fail, as far as the data component is > concerned. KM> Oy. KM> https://blog.storagecraft.com/jbod-care/ Scanned through that -- seems like with anything there are good points and bad. KM> I don't know why I'd want the One Big Disk effect. I'm perfectly KM> good with drives named \\Bullet\Easystore and \\Bullet\H and... KM> okay, it does get a little windy... KM> Shared resources at \\bullet KM> Share name Type Used as Comment KM> ------------------------------------------------------------------ KM> ------------- KM> Bullet_C_W98 Disk KM> Bullet_D Disk KM> Bullet_E Disk (UNC) KM> Bullet_F_XP Disk (UNC) KM> Bullet_WD500 Disk (UNC) KM> CitizenG Print Citizen GSX-230 KM> E2B (J) Disk (UNC) KM> EasyStore Disk (UNC) KM> Epson3250 Print Epson AP-3250 ESC/P 2 KM> G_MAIL (G) Disk KM> H Disk (UNC) KM> HP2100TN Print HP LaserJet 2100 PCL6 KM> HPLaserJet2100 Print HP LaserJet 2100 KM> L-XD-Fuji Disk KM> Lexar (J) Bullet Disk KM> M-SD-card Disk KM> My Book (O) Disk (UNC) KM> My Documents Disk KM> My Pictures Disk KM> Printer Print HP LaserJet IIIP KM> Printer3 Print HP LaserJet 4P/4MP PS KM> SharedDocs Disk KM> Shared resources at \\silver KM> SILVER KM> ------------------------------------------------------------------ KM> ------------- KM> E-Scratch Disk KM> G-Hitachi320 Disk KM> HPLaserJ Print HP LaserJet 1020 KM> Mail (M) Disk KM> SD120 (F) Disk KM> SILVER-RAMdisk (Z) Disk KM> SILVER-WD1000 Disk KM> SILVER-WD250 Disk KM> Shared resources at \\dell-pc KM> Share name Type Used as Comment KM> ------------------------------------------------------------------ KM> ------------- KM> !SHARED Disk (UNC) KM> C Disk (UNC) KM> Users Disk KM> The Dell's C and Users shares exist but do not work. Apparently KM> one must do ugly hoop-jumping to share the root on Win7 and KM> above, so I just dump everything I want to share in !SHARED. XP KM> lets me share the root at my convenience. And tho the linux box KM> can see everyone else, hell if I can figure out how to GET it to KM> share (SAMBA did not help). If - well, more like when -- one of the drives in the NSA unit downstairs fails I'll probably go with two separate drives rather than the one combined drive now (with JBOD). At the time I added the second hard drive it must have made sense to combine the original 2 TB with the new 3 TB (to get 5 TB), though in hindsight it makes just as much sense to have some files one drive and another set of files on the other. > KM> On the scattered PCs I have about 8-10 TB, > KM> not counting semi-random duplications, er, I mean backups of > KM> disks-in-use. > I'll have to allow ballpark as I know I have duplicated duplicates here. > Working on combining the various 'storages' here. A lot of duplicate KM> Yeah, someday I need to make one consolidated backup. Real Soon KM> Now! Think 25 TB will be sufficient?! > filenames but enough where the filename is the same but the data is > different I don't want to just click the automatic overwrite or skip KM> Not me, I've got way too many same names different file. Uh, that's what I said! Or meant to say. A lot of the 'common filename problem' was due to the MS-DOS 8.3 limitation; I used subdirectories to make some bulk differentiation: could have CABLE.001, CABLE.002, etc., in PRINTER, MONITOR, TV, TELEPHON (ran out of characters!) -- all the CABLE files dealing with cabling, just specific to that device. (And probably a horrible example, though I did make some of my cables and had to learn about RTS/CTS vs. Xon/Xoff protocols.) > options. Also had an issue like you with all the files got dumped into > a common directory, so loss of the subdirectories. I don't want the > computer stuff mixed with the car stuff mixed with the house stuff, so > that is being separated. KM> Erk, that would be all sorts of fun... So if I flip this 3-way switch the car wipers start! > KM> I'm thinkin' backup server and maybe occasional media server... > It'll look impressive stating you have 18 TB (or whatever) of storage! > Just don't display the "free space = 16.2 TB" part!! KM> Haha.. likely I'll assign each disk a particular backup job, and KM> maybe make a redundant copy on another disk. That makes sense. ...And isn't 'redundant copy' one of the RAIDs?! > KM> ...if I ripped all the DVDs, which I should for backup purposes > KM> anyway, it'd be... well, there go the rest of those TBs... > KM> http://www.the-sandpit.com/misc/dvdlist.htm > KM> Who buys all this crap? Worse, who watches all this crap? :) > KM> Junk fills the brain cells allotted. :D > Well there are some I'd find interesting. If the "Becker DVD" is the KM> Becket. Excellent film. KM> https://en.wikipedia.org/wiki/Becket_(1964_film) Uh, yeah! Becket would be interesting too. Some very good actors which helps. KM> ...Teenage Mutant Ninja Turtles??!! KM> One of many from Walmart's $3 bin. But I liked the animated KM> series, so what the heck. Haven't watched 'em yet. I knew there was a whimsical side to you! :) KM> Alice to Nowhere is exceedingly rare (and not on DVD other than KM> crappy bootlegs)... tripped over it for cheap on eBay, guy did KM> not know what he had... One man's junk is another's treasure! KM> Had quite a bit of that luck in the past year. One was a KM> reference book I thought I'd never even SEE, let alone own... KM> there are only 8, maybe 9 copies known to exist. And someone had KM> it up for $25. GIMME!!! Probably another instance of "hmpf! Probably won't get a nibble for this old text but may as well:. ¯ ® ¯ Barry_Martin_3@ ® ¯ @Q.COM ® ¯ ® .... Error: Error finding error not found error. --- MultiMail/Win32 v0.47 þ wcECHO 4.2 ÷ ILink: The Safe BBS þ Bettendorf, IA --- QScan/PCB v1.20a / 01-0462 * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1) .