B09_-_140F1S24Q0051_0001.pdf

(x)

140F1S24Q0051 x x copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted ; or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGEMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR

OFFER. If by virtue of this amendment you desire to change an offer already submitted , such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

x

F1S

Falls Church VA 22041 5275 Leesburg Pike FWS, IT Services FWS IT Services

04/22/20240001

13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS. IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

12. ACCOUNTING AND APPROPRIATION DATA (If required) is not extended.is extended, Items 8 and 15, and returning

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended , by one of the following methods: (a) By completing

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

FACILITY CODE CODE

10B. DATED (SEE ITEM 13)

10A. MODIFICATION OF CONTRACT/ORDER NO.

9B. DATED (SEE ITEM 11)

9A. AMENDMENT OF SOLICITATION NO.

CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)

7. ADMINISTERED BY (If other than Item 6)CODE 6. ISSUED BY

PAGE OF PAGES

4. REQUISITION/PURCHASE REQ. NO.3. EFFECTIVE DATE2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO. (If applicable)

1. CONTRACT ID CODE

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

04/22/2024

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority) appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

E. IMPORTANT: Contractor is not is required to sign this document and return __________________ copies to the issuing office.

ORDER NO. IN ITEM 10A.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

The purpose of this amendment is to provide the Q&A received for this request as well as extend the posting period. The solicitation will now have a close date of 4/30/2024 5PM EST.

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)15A. NAME AND TITLE OF SIGNER (Type or print)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 15B. CONTRACTOR/OFFEROR 16C. DATE SIGNED

(Signature of person authorized to sign) (Signature of Contracting Officer)

Lorenzo Aragon

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

Previous edition unusable

Except as provided herein, all terms and conditions of the document referenced in Item 9 A or 10A, as heretofore changed, remains unchanged and in full force and effect .

Data Recovery

RFQ# 140F1S24Q0051

Q&A

1. Was the disk configured on RAID system? If so hardware or software RAID?

Hardware RAID (RAID5)

2. Please explain the disk type (ATA/SCSI etc) and the hardware interface PCIe etc

SATA Standard Drives | PERC H330 Adapter

3. What was host side storage network configuration (such as NAS, DAS, iSCSI, SATA etc) –

SATA (Virtual Disks as RAID5)

4. When the drive is inaccessible, was it logical or physical:

Logical – The Disks; Physical 4, 5, and 7 for the RAID5 failed – it looks to be due to age of the drives and bad luck with 2/3 of the drives failing (likely due to shutdown from frequent power failure). PhyDisk7 was likely the hot spare (this I am not certain as when I helped out with the non access issue, the disks were already bad and the RAID5 details was not showing with good details due to the failure of the ‘DATA’ Virtual Disk (the DATA RAID5 pool).

a. Logical - Was configured on RAID but got corrupted meta data or file system (Logical Block Address - LBA level)

b. Physical - Disk physically damaged so some physical reconstruction required for data recovery

5. Are there multiple disks involved during the project timeline? If so, what are they monolithic or different types of drives/hardware interfaces/host systems/file systems etc.

There are a total of 6 physical disks (all SATA, same disk space), same RAID5 pool (failure being the ones that is label as 4,5 and 7.

6. when the disks are shipped to us and if there are multiple, is there a design/configuration document for the setup/configuration to aid?

We can ship the disks with numbers attached to each disk (2,3,4,5,6,7)

7. How many drives are in the RAID? (6 drives)

8. What is the size capacity of each of the drives? Example: 2 TB per HDD.

9. Is for 1 (one) RAID 5 Hard Drive Data recovery or multiple? This is for (1) RAID5 recovery.

10. Data Storage Hardware Specification:

• What Happened? On August 23, 2023 (Wednesday), we encountered a shared drive access issue and determined that the DATA/RAID5 was corrupted. Attempts to recover the data were unsuccessful due to more than 2 HDD failures on a RAID5.

• When? August 23, 2023.

• What is the current state of the hardware? The physical server is still ONLINE and active with its OS volume operational.

• Make and model of the hardware? Dell PowerEdge T630

• How many disks in the unit? A total of 8 physical drives, (0 and 1 being the OS RAID1-----and 2,3,4,5,6, and 7 being the RAID5 for the Virtual DATA volume (D:\).

• How many disks make up the Volume? 6 disks

• What is the RAID configuration? RAID5 (with 1 hot spare? Being disk 7?)

• Type of disks, size, interface, make, manufacturer?

Will provide a picture of the physical disks after taken them out.

• File System for the volume? NTFS

• Is there any virtualization present? NO

• If yes, what are the names and sizes of the virtual machines in question? Not applicable

11. Are these virtual machines static or dynamic? Not applicable

12. Are there any deltas? Not applicable

13. How was this hardware primarily used? Not applicable

14. What happened after the initial failure? Not applicable

• Any disk replacements / rebuild / re-initialization attempted on the system since initial failure? (DO NOT PERFORM ANY) No

15. What specific actions have been taken / if any (please be as detailed as possible)? Not applicable