Looong story short. Power Outage, 2 drives "red balled" all data is there. Can read and write to both drives. Rebuilt array to have it fail after it was all done (couldn't write config to flash drive)

I'm not sure how to run smart tests on the drives in the raid array, which would be helpful. I've tried guides using smartctl but, alas, i'm too stupid to figure it out. (not real familiar with linux)

 

System Specs:

 

Lenovo TS440

3Ware Raid card for all but parity and cache drives.

2 Parity drives, 10 Data drives.  Parity drives on SATA Interface of TS440. Data drives run on raid card. Data drives are in a seperate san enclosure.

 

Trying to fix the flash drive.

 

Unmounted /boot. 

ran fsck -v /dev/sda1

 

Getting the following error:

root@Tower:~# fsck.fat 3.0.28 (2015-05-16)
-bash: syntax error near unexpected token `('
root@Tower:~# /CONFIG/PLUGINS/Sabnzbd
-bash: /CONFIG/PLUGINS/Sabnzbd: No such file or directory
root@Tower:~#   ".." is missing. Can't fix this yet.
> /dev/sda1: 150 files, 8928/59183 clusters

 

Every time i reboot, the dirty bit is set, the filesystem is read only, and even if i rebuild the parity, it won't keep and shows it missing the drives! WTF do i do?? The system is located about 1 hour away in my server rack. I have access remotely, and can remote into the system via intel AMT all day long.

 

What gives? I can't get my array to work right, and i can't get my flash drive to stop being retarded!

 

Notes: I'm not a linux expert, but i try to fix things on my own, and have been messing with this over the course of almost a week now, as the rebuild process takes TWO days.
 

Thanks

 

 

Edited April 2, 20179 yr by lazerusrm

Ok, So after thinking about it for a bit longer... I did the following:

 

 

Unmounted Boot drive: umount /dev/sda1

Checked the drive:        fsck /dev/sda1

Dirty Bit Set... Unset the Dirty bit... 

Deleted the folder that was giving grief: rm /boot/CONFIG/PLUGINS/Sabnzbd

Checked the drive:        fsck /dev/sda1

No errors this time...

Remounted Drive:         mount /dev/sda1 /boot

Rebooted from the dashboard.

 

After  a reboot, i'm now rebuilding the array, and it looks to be working this time... Fingers Crossed.

Edited April 3, 20179 yr by lazerusrm

Sounds like you are probably on the way, but if you need more advice, go to Tools - Diagnostics and post the complete zip.

 

Trurl:

 

     Thanks so much. I managed to get it figured out, the array is back online, and all drives have recovered, no lost data. Whew!   Seems to be all working normally again. I made sure to enable push notifications so i can be alerted quicker in the future!! Also hooked it up to the UPS so it can shut down before a power loss in the future.