Samba Server Configuration in Centos 6.2

@Lakshmana said:

@scottalanmiller said:
My Senior Engineer got scolding from Manager because of me in RAID rebuilding at one company.

What happened there to cause that though?

scottalanmiller

@thanksajdotcom said:

@Mike-Ralston is not your average intern.

Nope, he's much younger than your average intern

thanksajdotcom

@scottalanmiller said:

@thanksajdotcom said:

@Mike-Ralston is not your average intern.

Nope, he's much younger than your average intern

Still WAY more qualified than most of the guys I work with in L1 at my current full-time job.

scottalanmiller

@Lakshmana said:

@scottalanmiller said:
My Senior Engineer got scolding from Manager because of me in RAID rebuilding at one company.So he was trying to protect himself and he gives me the work to confirm the status of the RAID as well as Data

No, he is giving you tasks that are distracting you from those things. He's confused and is causing problems, rather than fixing them. He's not responding logically to the scolding. He should be learning what RAID is, not stopping you from fixing problems.

Lakshmana

@thecreativeone91 said:
The motherboard at one company is not working and it was fired.Now I tested with the motherboard A and configured RAID 1 in hard A1 and A2.Then I tested the hard disk in the other motherboard B and inserted the hard disk A1 and A2.So the RAID is working properly.So I need to suggest them the motherboard to be buyed them.So now I finished checking RAID.But my senior engineer said me to check the SAMBA server also to verify the sharing of Data

scottalanmiller

@thanksajdotcom said:

@scottalanmiller said:

@thanksajdotcom said:

@Mike-Ralston is not your average intern.

Nope, he's much younger than your average intern

Still WAY more qualified than most of the guys I work with in L1 at my current full-time job.

Most of them probably didn't intern. Interns or people who did internships tend to be the top end of the field because they are the ones able to and interested in getting into the field earliest and in the most productive way.

thanksajdotcom

@scottalanmiller said:

@thanksajdotcom said:

@scottalanmiller said:

@thanksajdotcom said:

@Mike-Ralston is not your average intern.

Nope, he's much younger than your average intern

Still WAY more qualified than most of the guys I work with in L1 at my current full-time job.

Most of them probably didn't intern. Interns or people who did internships tend to be the top end of the field because they are the ones able to and interested in getting into the field earliest and in the most productive way.

I started my career at an internship. My first real IT job started as an internship, which was how I first met @scottalanmiller and @Minion-Queen.

thanksajdotcom

@Lakshmana said:

@thecreativeone91 said:
The motherboard at one company is not working and it was fired.Now I tested with the motherboard A and configured RAID 1 in hard A1 and A2.Then I tested the hard disk in the other motherboard B and inserted the hard disk A1 and A2.So the RAID is working properly.So I need to suggest them the motherboard to be buyed them.So now I finished checking RAID.But my senior engineer said me to check the SAMBA server also to verify the sharing of Data

Yes, but what does setting up SAMBA prove? It proves you can setup SAMBA. It proves you have a network connection. It doesn't prove anything more than you already have by testing the disks on a new motherboard and accessing everything locally.

thanksajdotcom

@scottalanmiller, I understand the situation @Lakshmana is in. He reads it here and it makes sense, but trying to take what you read here and then regurgitate it to someone else who then fires questions you're not necessarily prepared for is another thing. He probably has tried relaying this to his boss and/or the senior engineer. Then they say something that frazzles him and it makes him feel stupid (not that he is) and his boss/senior engineer feel superior/right. Been there many a time with discussions with coworkers about a plethora of topics.

scottalanmiller

@thanksajdotcom said:

Yes, but what does setting up SAMBA prove? It proves you can setup SAMBA. It proves you have a network connection. It doesn't prove anything more than you already have by testing the disks on a new motherboard and accessing everything locally.

This is very important. The client could easily be left with no working RAID and your senior engineer will claim that he has tested it without having tested anything. He's avoiding knowing his job and hoping to cover up that he doesn't understand what is going on.

@Lakshmana said:

@thecreativeone91 said:
The motherboard at one company is not working and it was fired.Now I tested with the motherboard A and configured RAID 1 in hard A1 and A2.Then I tested the hard disk in the other motherboard B and inserted the hard disk A1 and A2.So the RAID is working properly.So I need to suggest them the motherboard to be buyed them.So now I finished checking RAID.But my senior engineer said me to check the SAMBA server also to verify the sharing of Data

Is the server suppose to be a file server and you need to setup shares? if so that makes sense. But it is unrelated to checking the raid or motherboard replacement. Infact why would all the config not still be there that was from before the replacement. There should be no reason to reimage with a motherboard replacement (especially of the same model).

scottalanmiller

@thecreativeone91 said:

There should be no reason to reimage with a motherboard replacement (especially of the same model).

Even of a different model since there is no connection between the board and the RAID. Only issue is if the drives re-identify themselves. Same issue you have on every reboot of a Cisco UCS - a great reason to avoid that garbage.

PSX_Defector

@scottalanmiller said:

@thecreativeone91 said:

There should be no reason to reimage with a motherboard replacement (especially of the same model).

Even of a different model since there is no connection between the board and the RAID. Only issue is if the drives re-identify themselves. Same issue you have on every reboot of a Cisco UCS - a great reason to avoid that garbage.

Whaaaaaaaa? I've never seen a drive blow off a profile in UCS. What in the world have you been doing?

scottalanmiller

@PSX_Defector said:

Whaaaaaaaa? I've never seen a drive blow off a profile in UCS. What in the world have you been doing?

I've seen it a lot. VMAX over FCoE to large UCS blade chassis. Drive IDs flipped constantly. One of many, many complications that made the UCS just the crappiest gear I've ever seen a business duped into buying in the last decade.

@scottalanmiller said:

@PSX_Defector said:

Whaaaaaaaa? I've never seen a drive blow off a profile in UCS. What in the world have you been doing?

I've seen it a lot. VMAX over FCoE to large UCS blade chassis. Drive IDs flipped constantly. One of many, many complications that made the UCS just the crappiest gear I've ever seen a business duped into buying in the last decade.

Uh Oh. a local datacenter I do contract work with is looking to replace the AS/400's (or whatever they call it now since they keep changing the name) with Cisco UCS gear.

thanksajdotcom

@Lakshmana, the point is that if the data is there, the data is there. Proving you can access it over a network vs accessing it locally proves nothing in terms of the reliability of the data. If it's all good from a local connection, sharing it so a Windows system can access it makes it sound like your Engineer 1. doesn't know Linux, and doesn't want to admit it and 2. is too lazy to walk to wherever the physical machine is and sit down in front of it, so he wants to make you run around setting up shares so he doesn't have to leave his desk.

@scottalanmiller is right. You need to find a job you can actually learn something from.

scottalanmiller

@thecreativeone91 said:

Uh Oh. a local datacenter I do contract work with is looking to replace the AS/400's (or whatever they call it now since they keep changing the name) with Cisco UCS gear.

One bad decision after another I see. The IBM i (hopefully they don't actually run on AS/400s from the 1990s) is solid, but a pretty poor business decision. It was obvious that it made no sense for any workload even when it first released. Someone was getting IBM kickbacks. Even IBM doesn't use those. Not even the departments that build them.

Cisco UCS is more of the "proprietary, unnecessarily convoluted" garbage. It requires special knowledge and training with no upsides - and that means risk and cost. I can't even fathom letting Cisco in the door to discuss that stuff. Blades have been a known bad idea from day one. Cisco takes the bad idea of blades to an absurd level.

It blows my mind that any company would let a decision maker choose those and keep their job. I've never heard of anyone come up with a reason to have chosen them. No one ever has a technical benefit and I've never seen a shop that used them and didn't get burned in the end.

@scottalanmiller said

I've never heard of anyone come up with a reason to have chosen them. No one ever has a technical benefit and I've never seen a shop that used them and didn't get burned in the end.

That's pretty much my opinion of most anything from Cisco expect their switches. I don't care for their routers.

thanksajdotcom

I have to keep my opinions of Cisco in check because I work for one of their biggest support partners. There are people on staff here who WROTE protocols Cisco uses. Dual-CCIE level guys and above.

@thanksajdotcom said:

I have to keep my opinions of Cisco in check because I work for one of their biggest support partners. There are people on staff here who WROTE protocols Cisco uses. Dual-CCIE level guys and above.

They used to be the only ones who made decent gear. Now there are plenty of others Juniper etc. yet Cisco still charges a high price for the name of yester year.