HELP, System is Read Only

Discuss Applications

HELP, System is Read Only

Postby Basher52 » Fri Jun 18, 2010 11:07 am

data from dmesg:

rr2340:channel [0,0] started successfully
rr2340:channel [0,1] started successfully
rr2340:channel [0,2] started successfully
rr2340:channel [0,3] started successfully
rr2340:channel [0,4] started successfully
rr2340:channel [0,5] started successfully
rr2340:channel [0,6] started successfully
rr2340:channel [0,7] started successfully
rr2340:channel [1,4] started successfully
rr2340:channel [1,5] started successfully
rr2340:channel [1,6] started successfully
rr2340:channel [1,7] started successfully
scsi4 : rr2340
scsi 4:0:0:0: Direct-Access HPT DISK_4_0 4.00 PQ: 0 ANSI: 5
sd 4:0:0:0: Attached scsi generic sg2 type 0
sd 4:0:0:0: [sdb] 21487026176 512-byte logical blocks: (11.0 TB/10.0 TiB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 2f 00 00 00
sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb: unknown partition table
sd 4:0:0:0: [sdb] Attached SCSI disk
parport_pc 00:06: reported by Plug and Play ACPI
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP]
udev: renamed network interface eth0 to eth1
udev: renamed network interface eth1_rename to eth0
ppdev: user-space parallel port driver
VIA 82xx Audio 0000:00:11.5: PCI INT C -> GSI 22 (level, low) -> IRQ 22
VIA 82xx Audio 0000:00:11.5: setting latency timer to 64
EXT3 FS on sda2, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 1052248k swap on /dev/sda3. Priority:-1 extents:1 across:1052248k
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
r8169: eth1: link up
r8169: eth1: link up
p4-clockmod: P4/Xeon(TM) CPU On-Demand Clock Modulation available
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
eth0: no IPv6 routers present
w83627hf: Found W83697HF chip at 0x290
eth1: no IPv6 routers present
nf_nat_ftp: kernel >= 2.6.10 only uses 'ports' for conntrack modules
EXT4-fs (sdb): mounted filesystem with ordered data mode
type=1305 audit(1276532053.928:22378): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 res=1
rr2340:[1,5] completion error, flags=a4

rr2340:ATA regs: error 40, sector count f4f4, LBA low 100, LBA mid 1f, LBA high 25, device 40, status 41

rr2340:start channel [1,5]
rr2340:channel [1,5] started successfully
end_request: I/O error, dev sdb, sector 2928104896
Aborting journal on device sdb-8.
EXT4-fs error (device sdb): ext4_journal_start_sb: Detected aborted journal
EXT4-fs (sdb): Remounting filesystem read-only
rr2340:[1,5] completion error, flags=84

rr2340:ATA regs: error 40, sector count fcfc, LBA low 180, LBA mid d, LBA high 35, device 40, status 41

rr2340:start channel [1,5]
rr2340:channel [1,5] started successfully
rr2340:[1,5] completion error, flags=84

rr2340:ATA regs: error 40, sector count fcfc, LBA low 180, LBA mid 1e, LBA high 35, device 40, status 41

rr2340:start channel [1,5]
rr2340:channel [1,5] started successfully


after I did a umount and mount, I got this:

EXT4-fs error (device sdb): ext4_put_super: Couldn't clean up the journal
EXT4-fs warning (device sdb): ext4_clear_journal_err: Filesystem error recorded from previous mount: IO failure
EXT4-fs warning (device sdb): ext4_clear_journal_err: Marking fs in need of filesystem check.
EXT4-fs (sdb): warning: mounting fs with errors, running e2fsck is recommended
EXT4-fs (sdb): recovery complete
EXT4-fs (sdb): mounted filesystem with ordered data mode


Should I restart the server and see what happens or is there something I should do before that.

Right now I took it offline.

I know it's not easy for anyone to know the error codes of the RAID card, but I need to know if there's anything I can do besides that.
Check the disks or anything?


Getting back later with a 'e2fsck -n -v /dev/sdb' log...

log:

[root@unknown /]# e2fsck -n -v /dev/sdb
e2fsck 1.41.9 (22-Aug-2009)
/dev/sdb contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

284188 inodes used (0.04%)
5794 non-contiguous files (2.0%)
36 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 281479/2691
1290302124 blocks used (48.04%)
0 bad blocks
16 large files

262802 regular files
21369 directories
0 character device files
0 block device files
0 fifos
0 links
8 symbolic links (8 fast symbolic links)
0 sockets
--------
284179 files
[root@unknown /]#

this shows no error, so what is going on here?

a new umount/mount won't give any new errors or into in dmesg
User avatar
Basher52
guru
guru
 
Posts: 907
Joined: Wed Oct 22, 2003 5:57 am
Location: .SE

Postby Basher52 » Fri Jun 18, 2010 2:27 pm

been snooping around the disks and now it seems that one older 1Tb disk is getting bad blocks. The funny part is that I had the same problem some older 500G HDDs and that was no problem, it just fixed it, as now, and no problem with sabotaging the FAT :(
User avatar
Basher52
guru
guru
 
Posts: 907
Joined: Wed Oct 22, 2003 5:57 am
Location: .SE

Postby Basher52 » Fri Jun 18, 2010 2:49 pm

I finally dared to do the e2fsck with changes and I got the same result...

[root@unknown /]# e2fsck -v /dev/sdb
e2fsck 1.41.9 (22-Aug-2009)
/dev/sdb contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

284188 inodes used (0.04%)
5794 non-contiguous files (2.0%)
36 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 281479/2691
1290302124 blocks used (48.04%)
0 bad blocks
16 large files

262802 regular files
21369 directories
0 character device files
0 block device files
0 fifos
0 links
8 symbolic links (8 fast symbolic links)
0 sockets
--------
284179 files
[root@unknown /]# e2fsck --help
e2fsck: invalid option -- '-'
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device

Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
[root@unknown /]# e2fsck -v -n /dev/sdb
e2fsck 1.41.9 (22-Aug-2009)
/dev/sdb: clean, 284188/671473664 files, 1290302124/2685878272 blocks
[root@unknown /]#

as you see, still no error found, not even bad blocks as I could see using the RAID card, but after that I did another e2fsck and all of a sudden it's OK


que?
User avatar
Basher52
guru
guru
 
Posts: 907
Joined: Wed Oct 22, 2003 5:57 am
Location: .SE

Postby Basher52 » Fri Jun 18, 2010 5:05 pm

...more tests done and still the /dev/sdb/ is OK, but can I really trust it?


Can anyone tell me why it shows no error when I test it and when I do a 'e2fsck -v' WITHOUT '-n' so it can do changes in case there are some, still nothing in those logs and after that, all seems fine.
???
User avatar
Basher52
guru
guru
 
Posts: 907
Joined: Wed Oct 22, 2003 5:57 am
Location: .SE


Return to Applications

Who is online

Users browsing this forum: No registered users and 3 guests

cron