개월에 1번씩 접속하는 스토리지 서버가 있습니다. 네트워크 플로우 데이터를 저장용입니다.
우분투 15.04 64비트
어느 순간 루트사용자로 파일을 생성하려고 했는데 아래와 같은 나오네요.
sys-bash: cannot create temp file for here-document: Read-only file system
다행히 데이터영역은 다른 파티션입니다.
os는 /dev/sda , 데이터는 /dev/sdb
구글검색하니까
https://jellybeanz.medium.com/ubuntu-%EC%97%90%EC%84%9C-%EA%B0%91%EC%9E%90%EA%B8%B0-read-only-file-system-%EC%97%90%EB%9F%AC%EA%B0%80-%EB%B0%9C%EC%83%9D-%ED%95%98%EB%8A%94-%EA%B2%BD%EC%9A%B0-9284bff8b92b
근데 언마운트롤 하라고 하면 /boot를 해야하는지 아니면 / 영역 자체를 해야 하는지 궁금합니다.
만약 싱글모드?로 부팅해서 해야 할 것 같기도 한데요. 싱글모드 진입 후 언마운트 하고 e2fsck 명령어로 복구 가능하다고 하는데 정말 잘될런지 모르겠네요.
혹시 경험있으신 분 계신가요?
sudo mount -no remount,rw /
߿Ѱ, read-only ٲ ˾ƾ Ѵٴ .
ذ ȵǸ read-only մϴ.
ũ 뷮 ְų, ̰ų..
Ÿ ٸ ..
https://yumserv.tistory.com/17
urló ۾Ϸ մϴ.
߰ syslog Ϻ 뵵 ֽϴ.
Jan 19 04:26:31 flow-storage kernel: [13398460.209172] megaraid_sas: FW detected to be in faultstate, restarting it...
Jan 19 04:26:34 flow-storage kernel: [13398463.221343] pcidata = 0
Jan 19 04:26:34 flow-storage kernel: [13398463.221346] megaraid_sas: FW restarted successfully,initiating next stage...
Jan 19 04:26:34 flow-storage kernel: [13398463.221348] megaraid_sas: HBA recovery state machine,state 2 starting...
Jan 19 04:27:04 flow-storage kernel: [13398493.344144] megasas: Waiting for FW to come to ready state
Jan 19 04:27:04 flow-storage kernel: [13398493.344148] megasas: FW in FAULT state!!
Jan 19 04:51:04 flow-storage kernel: [13399933.606050] FW state [-268435456] hasn't changed in 180 secs
Jan 19 04:51:04 flow-storage kernel: [13399933.606054] megaraid_sas:adapter not ready
Jan 19 04:51:06 flow-storage kernel: [13399935.614139] megaraid_sas: pending cmds after reset
Jan 19 04:51:06 flow-storage kernel: [13399935.614142]
Jan 19 04:51:06 flow-storage kernel: [13399935.614142] megasas[2]: Dumping Frame Phys Address of all pending cmds in FW
Jan 19 04:51:06 flow-storage kernel: [13399935.645807] megasas[2]: Total OS Pending cmds : 0
Jan 19 04:51:06 flow-storage kernel: [13399935.657099]
Jan 19 04:51:06 flow-storage kernel: [13399935.657099] megasas[2]: 64 bit SGLs were sent to FW
Jan 19 04:51:06 flow-storage kernel: [13399935.678702] megasas[2]: Pending OS cmds in FW :
Jan 19 04:51:06 flow-storage kernel: [13399935.689737] megasas[2]: Frame addr :0x366c2000 :
Jan 19 04:51:06 flow-storage kernel: [13399935.690008] megasas[2]: frame count : 0x1, Cmd : 0x2, Tgt id : 0x0, lba lo : 0x13018330, lba_hi : 0x0, sense_buf addr : 0x366bf480,sge count : 0x2
Jan 19 04:51:06 flow-storage kernel: [13399935.719622]
Jan 19 04:51:06 flow-storage kernel: [13399935.728899]
Jan 19 04:51:06 flow-storage kernel: [13399935.728899] megasas[2]: Pending Internal cmds in FW :
Jan 19 04:51:06 flow-storage kernel: [13399935.746899] megasas[2]: Dumping Done.
Jan 19 04:51:06 flow-storage kernel: [13399935.746899]
Jan 19 04:51:06 flow-storage kernel: [13399935.763664] megasas: failed to do reset
Jan 19 04:51:06 flow-storage kernel: [13399935.772096] sd 2:2:0:0: [sda] megasas: RESET cmd=2a retries=0
Jan 19 04:51:06 flow-storage kernel: [13399935.772097] megasas: cannot recover from previous reset failures
Jan 19 04:51:06 flow-storage kernel: [13399935.780359] sd 2:2:0:0: [sda] megasas: RESET cmd=2a retries=0
Jan 19 04:51:06 flow-storage kernel: [13399935.780360] megasas: cannot recover from previous reset failures
Jan 19 04:51:06 flow-storage kernel: [13399935.788424] sd 2:2:0:0: Device offlined - not ready after error recovery
Jan 19 04:51:06 flow-storage kernel: [13399935.788430] sd 2:2:0:0: [sda] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
Jan 19 04:51:06 flow-storage kernel: [13399935.788432] sd 2:2:0:0: [sda] CDB:
Jan 19 04:51:06 flow-storage kernel: [13399935.788433] Write(10): 2a 00 13 01 83 30 00 00 10 00
Jan 19 04:51:06 flow-storage kernel: [13399935.788438] blk_update_request: I/O error, dev sda, sector 318866224
Ư SSD ѹ濡 ϴ.
߿ ʹ ־ ʴ° ϴ.
.. ⵿غ ֽð.....
ϴ
̱۸ . .. unmount Ŀ FSCK ...
Ƴ.. Ƴ...
DD copy ð...
ٸ ũ Ʈ Ʈؼ ũ ˻غð, SMART Ȯغ