Teaching yourself about the "fsck" command by running it on the company's firewall, because it refuses to boot and nobody else is in the office. Woo-hoo!
I got to work this morning before anyone else did. The Internet was broken. The computer that makes it work (aka "the firewall", which also does some other stuff) wouldn't boot and said that there were problems with its disk. The other computers were all off, meaning we probably had a power failure.
I called around to get the superuser password for the firewall. Then, with the least little bit of trepidation (because I'd never done this before and it's an important system), I ran the fsck command to fix the disk (which had a lot of errors on it). Then I rebooted the system, turned on the main Windows machine and the mail server, and had everything working happily a few minutes later. It's not rocket science or anything, but it's really the sort of thing one prefers not to learn on systems that do important stuff.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
blinker
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2002-02-22 02:20 pm (UTC)no subject
Date: 2002-02-22 02:42 pm (UTC)I called around to get the superuser password for the firewall. Then, with the least little bit of trepidation (because I'd never done this before and it's an important system), I ran the fsck command to fix the disk (which had a lot of errors on it). Then I rebooted the system, turned on the main Windows machine and the mail server, and had everything working happily a few minutes later. It's not rocket science or anything, but it's really the sort of thing one prefers not to learn on systems that do important stuff.
no subject
Date: 2002-02-22 03:34 pm (UTC)