Alternative SMD (Sunday Morning Drive), pushing up some IOPS
Comments (0) 
Category: Others (其它)
Comments (0) 
前蘇聯米格MiG戰鬥機的設計
By admin, January 30, 2016 1:46 pm
很喜歡Mikoyan設計的米格戰鬥機，因為感覺很流線形，在現在看來一點也不落伍，還是很時尚。
MiG-15 (1950s)
MiG-29 (1970s)
另外昨天看到了美國最新公佈的主力F35隱形戰鬥機，感覺跟中國的那台殲敵J20差不多。
F35
J20
Gifts from Equallogic
By admin, January 16, 2016 7:14 pm
Professional compensation from Dell for their previous very unprofessional services.
It’s a bit different than the one back in 2011, which has Firmware version EN03 and Made in China.
Blocked by Hotmail.com: 550 SC-001 (BAY004-MC4F44)
By admin, January 8, 2016 10:31 am
Recently my client has encountered problem that all their email sent to hotmail.com got bounced back immediately with the following error message.
Server response to MAIL FROM:
550 SC-001 (BAY004-MC4F44) Unfortunately, messages from xxx.xxx.xxx.xx weren’t sent. Please contact your Internet service provider since part of their network is on our block list. You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors.
It turns out their email server IP got blacklisted by hotmail.com due to suspicious spam activities, given the fast even their IP isn’t listed on any of the RBL anti-spam database.
The solution is quite straight forward but does with a bit of luck, simply fill in the form and PRAY Microsoft will get back to you shortly. (and they did recently, average reply time is about 10-30 mins)
The following is the actual reply from Microsoft:
We have completed reviewing the IP(s) you submitted. The following table contains the results of our investigation.
Conditionally mitigated
xxx.xxx.xxx.xxx, xxx.xxx.xxx.xxx, xxx.xxx.xxx.xxx,Our investigation has determined that the above IP(s) qualify for conditional mitigation. These IP(s) have been unblocked, but may be subject to low daily email limits until they have established a good reputation.
Please note that mitigating this issue does not guarantee that your email will be delivered to a user’s inbox.
Ongoing complaints from users will result in removal of the mitigation.
Mitigation may take 24 – 48 hours to replicate completely throughout our system.
If you feel your issue is not yet resolved, please reply to this email and one of our support team members will contact you for further investigation.
Regardless of the deliverability status, Outlook.com recommends that all senders join two free programs that provide visibility into the Outlook.com traffic on your sending IP(s), the sending IP reputation with Outlook.com and the Outlook.com user complaint rates.
Of course, the above is just the normal scenario. Worst case, your email to hotmail.com could be never bounced back but disappeared totally in darkness.
After filled in the above form, you get a very discouraging reply from Microsoft saying your IP cannot be unblocked.
Not qualified for mitigation
xxx.xxx.xxx.xxx
Our investigation has determined that the above IP(s) do not qualify for mitigation.Please ensure your emails comply with the Outlook.com policies, practices and guidelines found here: http://mail.live.com/mail/policies.aspx.
To have Deliverability Support investigate further, please reply to this email with a detailed description of the problem you are having, including specific error messages, and an agent will contact you.
Don’t worry, the next step is to reply to that particular email and explain the situation in detail and politely, normally, Microsoft will grand you the rights to unblock your IP again.
My name is xxx and I work with the Outlook.com Deliverability Support Team.
Recent activity coming from your IP (xxx.xxx.xxx.xxx) has been flagged by our system as suspicious, causing your IP to become blocked. I have conducted an investigation into the emails originating from your IP space and have implemented mitigation for your deliverability problem. This process may take 24 – 48 hours to replicate completely throughout our system.
Please note that lifting the block does not guarantee that your email will be delivered to a user’s inbox. However, here are some things that can help you with delivery:
次次見到人哋砌Rack都會好High!
By admin, January 7, 2016 11:37 am
Design + Mechanical + Hardware + Network, simply love this kind of stuff.
New York New York
NO STOCK of this Equallogic 600GB 15K SAS Disk!!!
By admin, December 28, 2015 7:07 pm
This is the 4th time Equallogic 15K SAS failed (previous failed record was on April 30, 2015), but this time comes with another surprise the local Dell logistic and inventory department called me saying they don’t have any stock currently!!! ARE YOU KIDDING ME? There are at least 50-60 Equallogic boxes running 600GB 15K SAS in Hong Kong and they don’t have the most failed parts in stock? and we paid for 4 hours Pro-Support replacement service…to be updated!
The RAID reconstruction took 3 hours and 40 mins to complete this time.
Update: Jan-15, 2016
5th time Equallogic 15K SAS failed.
Update: Jan-18, 2016
6th time Equallogic 15K SAS failed.
Whenever you see predicative failure kicks-in (ie, Copying to Spare), then you know it’s time to call Dell service, as all previous 3 predicative failures, none of it worked, the process always failed at half way.
Update: Jan-30, 2016
7th time Equallogic 15K SAS failed
4 disks failed one after another in 30 days is a Wow!!!
It seems the 5 years + SAS disks do have a life span of around 5 years warranty time, that’s why you need to extend your warranty for another 2 years as Dell gives maximum 7 years warranty for their enterprise products.
Update: Jul-15, 2016
8th time Equallogic 15K SAS failed
Don’t think predicative failure will help, so called pro-support right away to replace the failed disk.
Update: Oct-1, 2018
9th time Equallogic 15K SAS failed
After more than 2 years, finally it comes another disk failure, but this time the copy to spare was successful!
—————————————–
Level Received Member Message
Info 10/01/2018 04:43:05 AM eql01 Completed copying-to-spare operation from drive 4 to drive 15.
—————————————–
One interesting fact I found out, when I re-insert the failed disk, EQL produced the following error that I’ve never seen before.
—————————————–
History-of-Failures
ERROR event from storage array eql01
subsystem: SP
event: 14.4.18
time: Mon Oct 1 11:00:43 2018
0:Orphan disk drive: Disk drive LUN 4 (26bc078a0900-779214cc-8) no longer belongs to RAID LUN 0 (3be078a0900-b0e5c22b-92d39732). This disk has a history of failure and will not be used.
Update: Dec-2, 2018
10th time Equallogic 15K SAS failed, more than half of the disks are replaced, firmware EN03 from EN01.
Update: Dec-31, 2018
11th time Equallogic 15K SAS failed just before the end of 2018, this time is the first disk with firmware EN03.
Update: May-23, 2019
12th time Equallogic 15K SAS failed, firmware EN03 (TB EN03, Disk 0:0)
Update: Nov-15, 2020
13th time Equallogic 15K SAS failed, firmware EN03 (TB EN03, Disk 0:3)
Update: Jul-19, 2023
14th time Equallogic 15K SAS failed, firmware EN03 (TB EN01, Disk 0:5)
Update: Mar-1, 2024
15th time Equallogic 15K SAS failed, firmware EN00 (TB EE06, Disk 0:13)
=========================
Update: Jan-23, 2023
1st time Equallogic02 10K SAS failed (TB FE10, Disk 0:11)
Update: Feb-28, 2023
2nd time Equallogic02 10K SAS failed (TB FE10, Disk 0:12)
Update: Mar-13, 2023
3rd time Equallogic02 10K SAS failed (TB FE10, Disk 0:2)
Update: Mar-26, 2023
4th time Equallogic02 10K SAS failed (TB FE10, Disk 0:3)
Update: Mar-27, 2023
5th time Equallogic02 10K SAS failed (TB FE10, Disk 0:2)
Update: Mar-28, 2023
6th time Equallogic02 10K SAS failed (TB FE10, Disk 0:4)
Update: Mar-30, 2023
7th time Equallogic02 10K SAS failed (TB FE10, Disk 0:6)
Update: Apr-08, 2023
8th time Equallogic02 10K SAS failed (TB FE10, Disk 0:11)
Update: Apr-16, 2023
9th time Equallogic02 10K SAS failed (TB FE10, Disk 0:3)
10th time Equallogic02 10K SAS failed (TB FE10, Disk 0:10)
Update: Apr-17, 2023
11th time Equallogic02 10K SAS failed (TB FE10, Disk 0:7)
Update: Apr-24, 2023
12th time Equallogic02 10K SAS failed (TB FE10, Disk 0:15)
Update: May-6, 2023
13th time Equallogic02 10K SAS failed (TB FE10, Disk 0:3)
Update: May-20, 2023
14th time Equallogic02 10K SAS failed (TB FE10, Disk 0:0)
Update: Jun-8, 2023
15th time Equallogic02 10K SAS failed (TB FE10, Disk 0:21)
Update: Jul-14, 2023
16th time Equallogic02 10K SAS failed (TB FE10, Disk 0:11)