Phas3L0ck

Have an old phone that's served me well for many years, and earlier this year 3G got cut for good. What can I sensibly do with this to prevent it from being e-waste? It doesn't use a SIM card since the ID is built in (proprietary device for Sprint CDMA only) and it pre-dates the adoption of WiFi in phones, so the only useful signal it works with is Bluetooth (I'm not even sure which version) Storage space is limited but it does have a MicroSD slot for expansion... and the software is extremely basic, something called "BrewMP" (NO, it's NOT android) I can't even figure out if it has an admin mode to flash custom firmware or not. But DO NOT say things like "use it for the camera" or "voice recorder" or anything to do with the internet. The video quality is horrible, it doesn't have the software to make a decent audio recorder, and the built-in web browser (surprisingly it does have one) won't work with ANY modern websites.

Not sure if this helps, but double check the power connections to the GPU and the motherboard. - And have you tried any other screens, or do you only have the one? - Try switching input modes on the monitor. - If you have different RAM modules, particularly of a lower frequency, try using that instead. (I literally just solved this same problem on a friend's system and it was bad RAM)

Close, but not quite it. After an exhaustive search, it seems you have the size right, but mine is closer to the Philmore-255... not 100% sure, but then I found their 48-420 part, which looks a lot more like my cable. Either way, I think my plug is an EIAJ-04 type. What you found is close, but the barrel length (from the image you attached) looks a little too long to fit in just right.

If the install itself was disrupted, then reinstalling to the nvme is the only real way to go.

The outer, as I stated in my initial post, is 5mm. The inner diameter is about 3mm. That's as accurately as I can measure with nothing but a typical slim ruler. I found something on a foreign website that looks close, but specifies the size is 7.9mm length by 5.5mm OD. It has the center pin, so I'll be looking into that as a possibility.

Oh dude, ConnectX-2 is obsolete. The V3 is already getting old, but V2... That thing has serious issues from the inside out. I've seen and heard errors and complaints on the V2 series for years now. UEFI compatibility with newer boards is questionable at best, and I would be amazed if any OS newer than Win8.1 would even boot much less recognize and use the V2 series. You could try doing a firmware update, but I have no idea if firmware for V2 cards is available anymore...

That doesn't help at all. I tried looking for plugs in both known sizes and what I measured, and all I ever find is generic junk! This sort of thing happens so often, it's like the entire world is completely pathologically backwards and everyone only ever has the exact opposite of what I need!

I'm doing a minor upgrade to integrate 12v power to my desk in a semi-industrial way, and with a new power brick comes the need for connections-- but I can't power my speakers due to the odd style of plug it takes... I have a very old pair of Yamaha speakers, and this just happens to be the one thing that uses a reverse DC barrel plug, and I can't find it anywhere! I have the original power adapter, a PA-M7, but I don't want to cut the cord off and lose the ability to use it again. The plug measures at 5mm outer diameter and 8mm length (at least that's as accurately as I can measure) and I need an open-ended cable with this exact plug. The problem is that I can't find this style of DC barrel plug anywhere no matter hard hard I look or what I search for. Can anyone find this?

I guess that makes sense, especially knowing Lenovo. Anyhow I found a partial solution; the CRA4448 from Gigabyte has an identical board design and all the standard features-- except it's not a common part and is twice the overall cost of the M5210 including the CV addon.

That's exactly what I'm starting to think. Lenovo mentions that you can add adapters later and they will be given the new feature even after it's been added to the IMM, but the feature will not exist on the adapter if it's moved to another server... So we're basically on the same page in guessing that the mainboard acts as a hardware feature key of it's own to the adapter... I just haven't seen anything like this before. What really gets me is why this would work if RAID-6 is supposed to be hardware default in SAS3108 chips. Maybe it has something to do with the firmware from IBM/Lenovo being several Meagbytes larger than the one from LSI, and might contain code that makes this "floating default" possible.

I thought of that. And so have dozens of other people. In light of a recent disaster (which I recovered from surprisingly easily), I now know of many ways to flash firmware, so that's not a problem. What becomes a problem, however, is the data in NVRAM, which can't be touched. As evidence (and experience) suggests, hardware feature keys are like separate NVRAM augmentations that can be used to add (or transfer) feature options, whereas features stored in NVRAM are permanent and can't be removed or changed no matter what firmware is flashed. In fact, I accidentally used their firmware to update my own proprietary SAS3108 adapter from a different OEM, and it works just fine without affecting the available features. What I don't understand is the structure of Lenovo's FoD, which is what a user in the forum I referenced was grappling with, to determine whether or not there is an underlying code (or variation) of the activation key that would result from the authorization code Lenovo asks for to generate such a key that could possibly be used in LSI's MSM interface. I can believe that hardware activation keys enable more than one feature, as the one in the eBay link suggests, but where is the PROOF? I need someone who owns such a key to explain if this is a thing or not-- but that's gonna be even harder seeing as RAID-6 is standard on most LSI 9361-8i variants and few people have this issue... I find it interesting that, in some cases, adding a CacheVault module may enable the MegaRaid SafeStore option (which is surprising as there is a hardware key for that feature as well).

Okay, I have a kind of loaded question about the M5210 SAS card, which is the IBM/Lenovo equivalent of the LSI 9361-8i... *but first, a little explanation; I'm researching this model both for technical reasons and because I need something modern and extremely compact that can do RAID-6 and has vertical ports like this one does.* My question is; regarding RAID-6, I see it has to be activated as a separate feature, and while the software activation code is available, if I can't use it in the LSI MSM interface, then is it true what so many people are suggesting-- that the hardware CacheCade 2.0 key (found here: https://www.ebay.com/itm/132592996052 ) can actually activate RAID-6 functionality? Does anyone else know about this? I know it's been an issue before but very little detail was given. I last saw a reference at servethehome: https://forums.servethehome.com/index.php?threads/lsi-9361-8i-no-raid-5-6-licence-where-to-get-lsi-advanced-software-option.17548/ And to answer to the readers of this post who are wondering, I intend to use the M5210 with a CacheVault module in my Tyan GN70 server due to the mechanical layout. ---------- Additional details: RAID-6 for the M5210 is referred to by Lenovo as a "Feature on Demand" (FoD) that must be entered in the Integrated Management Module which ONLY exists in Lenovo servers! Controller Datasheet: https://lenovopress.com/tips1069.pdf (See page 2) FoD Documentation: https://lenovopress.com/redp4895.pdf (Look at pages 38-41 and 163-165 for a quick read) Activation website: https://fod2.lenovo.com/lkms/angular/app/pages/index.htm#/welcome

I get what you meant, but tolerances are already maxed out by my calculations, and I'm kinda OCD about mechanical uniformity. Big CFM may sound good, but 40-100CFM from the average fan means nothing without pressure. The San Ace fan I'm looking into combines airflow, pressure, and a far more predictable flow pattern in a dense area where the high air volume must be focused. In other words, it's not what I had planned, but San Ace's C133 series shows a great deal of respect for common 2U equipment layouts (by a great deal of coincidence in it's design) although requiring a 3U enclosure. Funny how the fan itself looks like it was intended to be mounted in a position slightly above the surface of a motherboard, and hang just under a chassis roof so as to fully cover multiple 2U CPU heatsinks with the most effective use of space! Finding a screen model with a decent image quality and reasonable pixel size that would actually fit onto the front of a 3U chassis was a nightmare! The only good Full-HD model known to be available requires a proprietary adapter to use the full display area, and most other models are too basic.

First of all, YUCK. Second, the last thing I need is bezel-shock in which an extra part needlessly extends the front of the chassis beyond the uniform borders of what is currently present and intended to be installed. And third... well... after a cascade of conflicting ideas on how to use the top 3U of space efficiently, (the only space to be fully available in the end) I decided to try putting them all together and see what happened. At first it wasn't going to work because of mechanical conflicts between available hardware, but then I found a few things that happened to fall in line with most of my ideas extremely narrowly and pushing the boundaries of what can be assembled without a major issue. And you won't believe the motherboard I chose to use in the event I'm able to design a full chassis and have it manufactured. One other thing-- the fans I found are surprisingly efficient, and I'm interested to see what kind of cooling capacity they have to offer on a tremendously powerful system (or maybe I'll be lazy in testing and do something with watercooling stuff... meh.)

Hardware side; yes. Software side, well, depending on your OS, half yes/half no. Best way to go is keep your drivers updated, and configure the full setup through the NVidia software, NOT in Windows.

It really doesn't matter. Dual channel or not is irrelevant unless you're running an SQL server all the time. And speed isn't as big as people make it out to be either, except for the few who run dedicated systems with RDMA as part of their infrastructure. RAM is RAM. As long as it's compatible, run it!

Two points; we all know that the 3U rack size is the least liked by many server enthusiasts and manufacturers, and even hated by some for its odd size; many large servers use axial fans in 80, 92, and 120mm sizes, but very few beyond the 1U format will have squirrel-cage/blower fans for full system cooling. Even in the rare case which such fans are used, the air is always drawn in from the front of the chassis for obvious reasons. I have a random idea to design a chassis in 3U form factor that dedicates all of it's front-panel space to a pair of 8" HD (old HD, not 1080) screens for system telemetry, maintenance, and casually observing running workloads... but how to cool it? Through the top, of course! (my rack has an open 3U space in the top, so this works perfectly) But I couldn't just pick an axial fan to mount on the top and blindly believe it would work, no, I needed a more strategic approach to the issue-- so I looked at datasheets from the few manufacturers known to make high-speed fans, and found something perfectly fitting as well as energy efficient from San-Ace under their C133 line, model 9TJ48P0H01. To those of you wondering why I'd do such an odd configuration and with powerful centrifugal fans, the simple answer is; I was bored. (and I have a mad obsession with fans!) Because the fans I intend to use are proprietary in shape, the only way to mount them and effectively direct the airflow in a full-scale server chassis is to design a custom base and shroud to affix the fans and the inlet nozzle uniformly to the target chassis. I ran the numbers several times, and while at first I didn't think it would all fit, I made it work just barely staying within mechanical tolerances. Needless to say this is going to be ludicrously dense. Overall dimensions are 420mm wide, 140mm deep, and 107mm total height. Each fan (133mm wheel diameter) is separated at the midpoint by 140mm, leaving effectively 2mm of running space between each wheel and the walls of the shroud. Vertically it has about 5mm from the base plate to the bottom of the wheel, and some odd 12-13mm from underneath the cover plate to the top of the wheel. Am I concerned about the fan wheel rubbing against the side walls? Well first off that's what the screw holes on the base plate are for since that's how the fan is expected to be mounted, and second, as Linus would say; YOLO! Also a little side comment here; the numbers weren't quite what I expected, so I plan to split my 3U design idea internally; the system itself will live on a 2U upper-deck area (the effective cooling path for this fan model only covers 2U vertical area) inline with the custom fan assembly, while the power supply and other components will be in the bottom 1U of the chassis' usable space, making it possible to create a monster of a system! Here are renderings of the semi-final assembly I've made so far:

Been there, done that. Only got a partial result, and not the level of complexity I'm looking for.

As much as I like the idea, I don't have a real need for SMB3. If I truly wanted or required those features in-transit, I would be using Linux. And yes, I did read the link, and it's really nothing but a summary of what ABE can do. If I managed to get it to do what I want, I wouldn't be posting this on a forum right now. And MY point is that I need to figure out how to do what I described exactly as it was, and without auto-mount or using extended UNC paths. So tell me, do you know how to configure a file share to do exactly what I described or not?

Hell no! Windows 7 is more stable and reliable than anything "newer" from M$. And what "modern features" could it possibly be missing? And BTW, YES, it does get security updates! ESU updates are out left and right, and they all just work. But how is automount relevant if I can see the restricted directory under the name of the main/root share without even mounting it? No, I don't want AD, and most definitely don't need it. Between servers? No, I only have 1 server that I use for everything. Yeah I looked at that link, but it's not a guide, it just says what ABE is. It doesn't tell me how to use it. You still don't get it, do you? The config I experienced was so advanced there was NO NEED for the "full UNC path" or deeper folder mounting. That was what the admins tried to do and FAILED to make it work before the configuration was finalized to work as I know it. Let me clarify this at the level of the full drive path, this is an example of exactly what's going on as a result of the config and how I know it works for them; Imagine drive H:\ is a master share, and I want a user to only be able to enter folder "user1" upon authenticating to the file server... The user sees the share under \\server\share, but this is where things get weird... On a normal system, what would happen is the user sees the directory as \\server\share\user1 and is able to see other folders next to it on the drive, but unable to access them... What ACTUALLY HAPPENED is that, after entering login credentials, the server knows who the user is and which folders are assigned, so when the share is accessed, the server's H:\user1 folder becomes \\server\share as if the user1 folder were the master share! No AD, no extended UNC path, and no GPO.

NO, IT'S NOT GONE, WINDOWS 7 STILL WORKS JUST FINE! Anything in the realm of Windows 8, 10, or otherwise NEEDS TO BURN! Automount has nothing to do with it, what I experienced is something much deeper and more organized. I don't know what you have, but it sounds like the end systems are all linked in to make it look like it auto-redirected, but that's just a facade put on by AD and GPO tweaks. I'm not running a co-dependent client/server config like most do, and I managed to see and experience what I did by connecting to their network with a personal system NOT registered on AD and NOT affected by GPO! Seriously, does anyone read what's actually been written? I already concluded that root/folder authentication like this has something to do with NFS and Access Based Enumeration, but I can't figure out how. I got as far as a folder-level lock, but I still can't get a dedicated folder under the root drive share to mount as a root directory on a client end.

What you want is called VLP RAM. Often used in high-density servers and blades, I'm not sure if it's made or available for desktops though. VLP modules are usually ECC (for servers only) and depending on size and frequency they're very rare.

I've been trying to figure this one out for years but no one could explain it properly and I never heard back from the few who did it. The closest I got was recognizing that there is a way to configure NFS with Access-Based-Enumeration, but I haven't been able to make it work at folder-level. And before anyone asks, yes I tried talking to the people who did it and managed the servers, yes I looked it up, and yes I've tried everything I know how already, and no I never got an answer. Here's what I know: At the schools in my area, there is a central file server where people store their files and other stuff for easy use throughout the district. But because there are so many people using it, modifications had to be made to prevent users from accessing each other's files and stealing or deleting work. The files themselves were never at risk, but people were able to look at and inside of every users' sub-directory and even see what was there or how many files they had. In the early years, students who were accessing the network file storage system could view the folders and usernames of other students, but they could only enter their own assigned folder for storing and retrieving files. Once the problem became well known, the network file share authentication was modified so that each student and teacher could only access their assigned directory (well, teachers could still see everything, but that's because they had different viewing permissions) on the network file server, and the directory assigned to them would appear as a designated network hard drive. In other words, after the fix, there would no longer be a folder or sub-folder to enter for a person to access their files once they authenticate to the network drive; all their files would simply be right there when they entered the network drive shortcut. (except for some cases involving staff access) In other words, a sub-directory stored on a shared root hard drive BECAME ROOT upon mounting the file share!!! Now here's what I don't get; I can something similar happening through a simple permissions fix in the Active Directory controls, or perhaps even assign every single student and teacher file directory it's own network share path so that the shared directory would appear as a straight network drive to prevent others' folders and usernames being visible as sub-directories under the communal network-shared drive, but neither of these is the case. Upon close examination during my network/system analysis a few years back, I discovered something that I now realize is extremely impressive... I found that, upon logging into the main network file server, even on a personal system, only the shared paths with a sub-folder that correspond to my username (or have shared access permissions) were available to view, let alone log into; I was able to access on a personal system exactly what I would see logged into a district system, and even map the shares as network drives. Any other available file shares on that server which didn't have a single folder accessible to my username were properly hidden! Let's focus on the drive mapping for a second; I can view the shared directories available on the network server under my username, and map these directories as network drives, but upon entering the mapped network drive, I didn't need to select the folder with my username, nor did I see sub-directories with others' named folders, because the mapped network drive and the file share itself is rooted to my assigned directory. It works the exact same way with other students' accounts, and even for most of the staff. This prevents other users' directories from being seen and/or potentially breached by only allowing the folder that corresponds to a specific username to be accessed. Normally I would think that some sort of "folder hiding" method is being used to do this, but what absolutely baffles me is the fact that, like I said, a user's designated directory (their named folder) does not need to be entered after opening the network drive share (no sub-dir) because the share directory that can be seen on the file server after entry of a user's credentials is the exact directory that corresponds to that user, displayed as it's own file share. I've been trying to accomplish this for years on my personal systems, but I didn't have the hardware to run either a physical or virtual machine for file server experiments back then. So now, keeping in mind everything I just described, my burning question is; how can I implement this exact file/folder share authentication method on a regular Windows Server system? I intend to configure my Windows Server 2008 R2 system (same OS the district's server used) to authenticate network file share access in this unique way. *And don't say Active Directory, because that's never gonna happen. AD doesn't really work for me and it shouldn't be necessary anyway.

This is a little more than just a review, it's a look at the inside with details on the sensor it uses. **dust everywhere**