A mounting failure doesn't always result in a VM entering emergency mode.SmartUpdate ISOs (firmware cd's) can be downloaded from the HP support site. scexe program) failed, so I had to boot from the SmartUpdate iso, through ILO Virtual Media, as getting physical access to the box is somewhat of a hassle. Updating the firmware from a running box (running the downloaded. I found that HP SmartAray identifications are very confusing, and the same controller can be referred to under at least three different names. However, if you haven't done so yet, before anything else, my first line of action would be to backup any valuable data from the still readable disk, as it may still be the disk that's failing. You may also get some indications when you go into the SmartArray's BIOS on boot, and see if it has any issues with drive statuses.
Although your symptoms are not the same (and you're not on 5.6 but 5.5), you may be suffering from similar firmware issues, and it doesn't hurt to check/try. Somewhere during startup you must see messages as to why the filesystem is placed in read-only mode. All of them were fixed by updating the SmartArray firmware to the latest level, though. Ensure that firmware is up to date.but the others did not. One of these boxes had a line in DMESGcciss 0000:04:01.0: Controller reports max supported commands of 0, an obvious lie. After upgrading a couple of problem-free boxes from RHEL 5.2 / 5.4 to RHEL 5.6 I had three of them failing (after some hours or days) on cciss I/O writing to the disks timed out, causing infinite hang.
#Extfs list orphaned inodes update#
If my assessment that you're on an HP SMartArray (ProLiant server) is correct, I suggest you have a look at DMESG and search for any complaints about the cciss driver you may need to update the SmartArray firmware. I had a go on one of my boxes but got 'A mandatory SMART command failed' all the time. Not sure you can request SMART data from hardware raid, or even from a SmartArray. Judging from the 'cciss'-bit it would appear your disks are on an HP SmartArray (just guessing, I only have HP boxes here), which begs the question whether you run that in RAID or not. Inode 183369745 was part of the orphaned inode list.
Inode 183369742 was part of the orphaned inode list. Inode 183369738 was part of the orphaned inode list. Inode 183369737 was part of the orphaned inode list. Inodes that were part of a corrupted orphan linked list found. Pass 1: Checking inodes, blocks, and sizesĭeleted inode 183369735 has zero dtime. dev/VolGroup00/LogVol01 swap swap defaults 0 ~]# fsck -yvf /dev/VolGroup00/LogVol00 dev/VolGroup00/LogVol00 / ext3 defaults 1 1ĭevpts /dev/pts devpts gid=5,mode=620 0 0 Need help on doing FSCK, tried running it since yesterday afternoon but it seems to be hanging forever? Am I doing the correct method? Or this is just normal for a 1TB disk? Are there other ways to execute fsck? And also how do I see valuable results logs of FSCK ~]# uname -a
Got this problem when starting my db having 'Linux Error: 30 : Read only Filesystem'
0 kommentar(er)
