• Main INDEX
  • Monthly INDEX
  • PREV
  • NEXT
    Make New Entry, Make Followup Entry

    User name Ole Hansen

    Log entry time 23:01:49 on November 14, 2009

    Entry number 299913

    keyword=adaql1 recovery

    It looks like the shift crew managed to restart adaql1 after all. Good job, and good news: only one disk is bad (/dev/sdb), and it seems to be only one bad spot on the disk (one bad partition) instead of a total failure. The other disk (/dev/sda) dropped out of the arrays because of a lockup of the SCSI bus, not because of an I/O failure. We can probably run the machine like this for the weekend.

    I restored the degraded RAID-1 (mirror) arrays of the system disk except for /dev/md3 (/usr partition), which has the bad spo on /dev/sdb and is therefore no longer redundant.

    I have made a backup of the crontabs that are set up on adaql1: /adaql3/work2/adaql1/crontabs. This would at least allow the halog to come back quickly. I don't know what else is running there, though, which would be critical for DAQ. Bob or another DAQ expert should prepare adaql3 as a backup machine just in case.



    A copy of this log entry has been emailed to: rom, riordan