Listmates, I just got problem with my server, somehow i cant write anything in /home dir, even if I'm root. I try to remount, but still no luck, it said 'device busy'. Then I reboot the system, and I do fsck.ext3. It shows a lot of error with the inodes. I have to type 'y' to fix, and a lot of 'y'... Right now the system is on, I check /var/log/messages, I see this errors.. Dec 23 11:27:26 godsigma smbd[8726]: Error writing 5 bytes to client. -1. (Connection reset by peer) Dec 23 11:29:41 godsigma kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } Dec 23 11:29:41 godsigma kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=45474392, high=2, low=11919960, sector=45474392 Dec 23 11:29:41 godsigma kernel: ide: failed opcode was: unknown Dec 23 11:29:41 godsigma kernel: end_request: I/O error, dev hdb, sector 45474392 Dec 23 11:29:41 godsigma kernel: EXT3-fs error (device hdb7): ext3_get_inode_loc: unable to read inode block - inode=1524082, block=3047623 Dec 23 11:29:41 godsigma kernel: Aborting journal on device hdb7. Dec 23 11:29:41 godsigma kernel: EXT3-fs error (device hdb7) in ext3_reserve_inode_write: Journal has aborted Dec 23 11:29:41 godsigma kernel: EXT3-fs error (device hdb7) in ext3_reserve_inode_write: Journal has aborted Dec 23 11:29:41 godsigma kernel: EXT3-fs error (device hdb7) in ext3_dirty_inode: Journal has aborted Dec 23 11:29:41 godsigma kernel: EXT3-fs error (device hdb7) in ext3_dirty_inode: Journal has aborted Dec 23 11:29:41 godsigma kernel: ext3_abort called. Dec 23 11:29:41 godsigma kernel: EXT3-fs error (device hdb7): ext3_journal_start_sb: Detected aborted journal Dec 23 11:29:41 godsigma kernel: Remounting filesystem read-only Is that means something wrong with my HD ? badsector ? I use UPS so i think it's not because of power failure.. regards, -ARZ- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org