File system check recs on new ASAs

Just curious if anyone knows why I'd be seeing these on a new ASAs. The last two I received had these fsck records:
f-monona-1# sh flash
--#-- --length-- -----date/time------ path 182 16275456 Dec 13 2010 16:46:02 asa821-k8.bin 223 15962112 Feb 01 2011 16:40:15 asa832-k8.bin 183 49152 Jan 01 1980 00:00:00 FSCK0000.REC 13 2048 Dec 13 2010 16:47:20 coredumpinfo 14 43 Feb 01 2011 16:47:11 coredumpinfo/coredump.cfg 184 11348300 Dec 13 2010 16:47:54 asdm-621.bin 3 2048 Dec 13 2010 16:51:36 log 12 2048 Dec 13 2010 16:51:44 crypto_archive 224 15841428 Feb 01 2011 16:43:34 asdm-641.bin 186 2048 Jan 01 1980 00:00:00 FSCK0001.REC 187 12105313 Dec 13 2010 16:52:00 csd_3.5.841-k9.pkg 188 2048 Dec 13 2010 16:52:02 sdesktop 225 0 Dec 13 2010 16:52:02 sdesktop/data.xml 189 2857568 Dec 13 2010 16:52:02 anyconnect-wince-ARMv4I-2.4.1012-k9.pkg 190 3203909 Dec 13 2010 16:52:04 anyconnect-win-2.4.1012-k9.pkg 191 4832344 Dec 13 2010 16:52:06 anyconnect-macosx-i386-2.4.1012-k9.pkg 192 5209423 Dec 13 2010 16:52:08 anyconnect-linux-2.4.1012-k9.pkg 193 2048 Jan 01 1980 00:00:00 FSCK0002.REC 194 2048 Jan 01 1980 00:00:00 FSCK0003.REC 195 92160 Jan 01 1980 00:00:00 FSCK0004.REC 196 2048 Jan 01 1980 00:00:00 FSCK0005.REC 197 2048 Jan 01 1980 00:00:00 FSCK0006.REC 198 2048 Jan 01 1980 00:00:00 FSCK0007.REC 199 675840 Jan 01 1980 00:00:00 FSCK0008.REC 200 2048 Jan 01 1980 00:00:00 FSCK0009.REC 201 677888 Jan 01 1980 00:00:00 FSCK0010.REC 202 30720 Jan 01 1980 00:00:00 FSCK0011.REC 203 30720 Jan 01 1980 00:00:00 FSCK0012.REC 204 2048 Jan 01 1980 00:00:00 FSCK0013.REC 205 2048 Jan 01 1980 00:00:00 FSCK0014.REC 206 4096 Jan 01 1980 00:00:00 FSCK0015.REC 207 4096 Jan 01 1980 00:00:00 FSCK0016.REC 208 4096 Jan 01 1980 00:00:00 FSCK0017.REC 209 4096 Jan 01 1980 00:00:00 FSCK0018.REC 210 6144 Jan 01 1980 00:00:00 FSCK0019.REC 211 6144 Jan 01 1980 00:00:00 FSCK0020.REC 212 6144 Jan 01 1980 00:00:00 FSCK0021.REC 213 22528 Jan 01 1980 00:00:00 FSCK0022.REC 214 38912 Jan 01 1980 00:00:00 FSCK0023.REC 215 34816 Jan 01 1980 00:00:00 FSCK0024.REC 216 43008 Jan 01 1980 00:00:00 FSCK0025.REC 217 2048 Jan 01 1980 00:00:00 FSCK0026.REC 218 26624 Jan 01 1980 00:00:00 FSCK0027.REC 219 2048 Jan 01 1980 00:00:00 FSCK0028.REC 220 26624 Jan 01 1980 00:00:00 FSCK0029.REC 221 2048 Jan 01 1980 00:00:00 FSCK0030.REC

I have seen the same issues on many multiple NEW ASA's and DON'T think this is a problem with the received ASA's flash card or file structure. I have deleted and reformatted many of these flash cards and not experienced any new FSCK files. The flash cards from new ASA's have all passed.
This leads me to belive that the master flash card used in manufacturing, that was used for the creation of the imaged flash cards, in final production had corruption at times. And these FSCK files that were on the master used for duplicating, were then copied with its FSCK files, to the flash of the shipping ASA's.

Similar Messages

BSD Root - File System Check

My 2.8Ghz iMac has being running very slow recently.
I performed a File System Check and noted that my hard drive had the following message against it.
Major 14 Minor 2
Does that mean it is about to fail?

yes.
Have backups for ALL your data.
Take to nearest Apple Authorized Repair Center for new drive.

[SOLVED] Systemd stuck at "Starting File system check"

Hi all
Backstory
My hardware:
Mobo: Gigabyte X99 2011v3 with UEFI and dual bios.
GFX: MSI GTX 970 4GB Gaming OC
HDD: Samsung 850 Pro 1TB SSD
CPU: intel 5820k
I have been using arch for about 2 years now. I recently bought new hardware, Gigabyte X99 motherboard uefi dual bios. I have tried a couple of times to install arch the old way, i.e. legacy mode or normal bios mode, however after a successful install, when I reboot my bios says "Select Proper Boot Device". Then I decided to put everything in UEFI mode and install arch using the uefi install disc. At first, I was not very successful, because I followed the arch wiki to the bone but when it comes to UEFI, instructions are a bit vague. In any case, I managed to install Arch and get uefi to work 100% by using this guide http://jorisvandijk.com/2014/installing … pt-system/ .
Problem
After installing arch successfully using UEFI mode, arch starts booting up, everything shows [OK] at the side, no errors, however, it hangs after a line that reads "Starting File system check ". I am not at home right now, however I thought I could start troubleshooting and maybe get some ideas.
I have tried the following.
- Chrooted back into my arch install using the live cd and mounting my partitions.
- Updated and synced pacman.
- Removed all journal log files.
- reinstalled Systemd.
- rebuilt kernel modules.
none of the above worked. It still hangs at "Starting fiel system check"
Any ideas.
SOLUTION
Solved by using
nolapic
Still had other problems after that, however, the initial problem was solved.
Last edited by janpansa (2015-02-26 20:04:24)

jasonwryan wrote:Taking the time to read through the relevant pages and working through the Beginners' Guide methodically is the best (and only) way to both install Arch and also bed in a sound understanding of how your system is put together. It is an investment that will continue to pay you back as long as you run a Linux/UNIX box.
Hi Jason,
thx for your help so far. I have printed out the Arch beginners install and followed it to the bone and focusing on the UEFI parts. Arch installed without a single error, everything went smooth. Aftwerwards, I exited from the chroot environmount, unmount and reboot and again, it hangs on the startup. This time I took screenshots.
I present to the board, exhibit A, arch starting up after a fresh install :
http://oi61.tinypic.com/2m4x82o.jpg
I now present to the board, exhibit B, arch starting up for a second time, after restarting the pc :
http://oi59.tinypic.com/10ehvki.jpg
Afterwards, I restarted again. Went into bios setup and checked my boot priorities. This is what I saw:
I now present exhibit C, my bios boot options :
http://oi62.tinypic.com/24ys0bd.jpg
I tried all the options listed for my Samsung SSD, with and without UEFI as well as the option that was the default aka Linux boot manage". Each one did exactly the same.
I have a few ideas :
1.) Leave out swap.
2.) Disable fscheck.
3.) I have a feeling that my SSD is reading/writing too fast and that fscheck is having trouble ?
I am now trying option 1. In other words, I am reinstalling arch, again, following the beginners guide to the bone and focusing specifically on the UEFI parts. This time, I am leaving out swap. (I have 16GB of DDR4 memory). I have about a 70% feeling that the outcome will be the same. However, I will be back after that to comment on the outcome. Please leave feedback and help me through this where you can ! Thanks
Last edited by jasonwryan (2015-02-23 19:34:21)

File system checking exit code 8

Hi guys ... after done a filesystem checking I've got:
+0100: Incorrect number of file hard links
+0100: Checking catalog hierarchy.
+0100: Checking extended attributes file.
+0100: Checking volume bitmap.
+0100: Checking volume information.
+0100: The volume Macintosh HD was found corrupt and needs to be repaired.
+0100: File system check exit code is 8.
+0100: Error: This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility.
After restart the machine as suggested, my filesystem check exit without finding any problem, so ... what is the problem in fact? ...
By the way: I do not have any strange behaviour on my mac, I normally run filesystem and permissions repairs in order to keep "him" clean and healthy.
Thanks in advanced,
Jorge

This seems to be a bug. You may be able to work around it by starting up from another physical device. Make sure you have a current backup before doing anything.
If you have a "clone" backup on another drive—not a partition on the same drive—start up from it by holding down the option key at the startup chime and selecting its icon in the Startup Manager display. Launch Disk Utility and repair your primary startup volume—not the one you started from.
If you have a Time Machine backup on a locally-attached storage device—not a network device such as a Time Capsule—there should already be a Recovery system on that device. Start up from it and repair in the same way as above.
Otherwise, use Recovery Disk Assistant to create a Recovery system on a spare storage device, such as a USB flash drive, and start up from that device. All existing data on the Recovery device will be permanently erased.

File system check fails "FATAL"

Dear all,
after about three of years of running, one of my Xsan filesystems died. The fsm process stops running after about 2 minutes in running state. A filesystem check with cvfsck -w -v <Name> ends with:
Creating Daten allocation check file.
Stripe Group Daten ( 0) 0xe8def800 blocks.
Building Inode Index Database 91458560 ( 52%).
Fatal: rf_relblk write failed - Input/output error
Building Inode Index Database 91459584 ( 52%).
Fatal: Cannot insert inotab for [0x32a9e378800]! -No such file or directory
Fatal: Cannot build inode tracking tree - Input/output error.
I cannot see any misbehaviour of the hardware itself. RAID Admin is green everywhere.
The filesystem size is about 17 TB and the data is quite important. Is there any way to proceed without re-formatting?
Some more information I found in the log files:
[0923 16:26:42] 0xa000ed88 (debug) FSS 'Experiments' REGISTERED -> DYING, next e
vent in 60s
[0923 16:26:43] 0x1802e00 INFO Disk rescan found 10 disks
[0923 16:26:43] 0xa000ed88 INFO NSS: Active FSS 'Experiments[0]' at 192.168.100.
10:49275 (pid 354) - dropped.
[0923 16:26:45] 0x1801600 ERR Portmapper: FSS 'Experiments' (pid 354) exited on
signal 4
[0923 16:26:45] 0x1801600 ERR FSS 'Experiments' appears unstable (2 failures in
60 minutes or less), halting restarts
[0923 16:26:45] 0x1801600 (debug) FSS 'Experiments' DYING -> STOPPED (corefile l
imit exceeded)
Any hint is really appreciated.
Best regards,
Torsten

Thanks for the hint. Well, the cvfsck -j command succeeded rather quickly. But the -w afterwards fails again:
Super Block information.
FS Created On : Wed Aug 31 13:24:34 2005
Inode Version : '2.3'
File System Status : Clean
Allocated Inodes : 173699072
Free Inodes : 37814385
FL Blocks : 9309
Next Inode Chunk : 0x2c05d400
Windows Security Indx Inode : 0x4
Windows Security Data Inode : 0x5
Quota Database Inode : 0x6
ID Database Inode : 0xb
Client Write Opens Inode : 0x7
Creating Daten allocation check file.
Stripe Group Daten ( 0) 0xe8def800 blocks.
Building Inode Index Database 91363328 ( 52%).
Fatal: Cannot insert inotab for [0x8261a053f400]! -No such file or directory
Fatal: Cannot build inode tracking tree - Input/output error.
Is there anything else I can do?
Thanks,
Torsten

How can I search a file system and only return newer files?

Sorry the title didn't give me much room to work with. I'm writing a tool which needs to track all the files in an OS. What I'd like to do is make it so my program will only return files that have been modified/created since the last search to add to my program. I was wondering if there's an efficient way to do this other than checking each file's timestamps? Also is there a way to tell from a parent directory whether any files in its directory have been modified/created? I'm looking for ways for Windows and Linux.

I have no problem checking timestamps but it can be rather time consuming doing this. I don't know if this is quicker but I'd like to sort by modified date and check the time stamps for newer timestamps than the last time I ran. This way if I hit a time stamp equal to my last run I know to stop there. I checked Windows and the folder does tell you whether any file was created/modified in it's directory. However, if a file is created in one of its children's directories it won't update the time stamp. It's unfortunate because I could've avoided the search at a higher level directory otherwise. Without this I'll have to walk the whole structure one way or another. I can still improve the speed but I can't make it as efficient as I'd like.

Disk utility can't repair time machine disk - File system check exit code is 8

i have a WD My Passport 2Tb external hard drive that is split in to 2 volumes (1.5 & .5 TB). I use the smaller volume as my Time Machine disk. A couple of days ago I started getting an error that the Time Machine back up had failed and to use Disk Utility to repair the disk. So I launched DU and ran Verify Disk in the Time Machine volume. It quit verifying and told me to run Repair Disk EXCEPT the Repair Disk button was still greyed out. If I select the physical drive, Repair Disk becomes available but gives me the above error. The other (larger) volume continues to work just fine.
The he Time Machine volume is read only now.
I'm running Yosemite 10.10.1.
Hoping ting someone has a fix because I would prefer not to lose a years worth of Time Machine data.
Mahalo for for any help.
Steve Hudson

i'm afraid that the disk is too corrupt to repair. This could be because the drive is failing or you will need to erase the partition (which may not succeed unless you also repartition the drive.) If you must repartition the drive then you will lose data on both partitions. This is an important reason why you should not mix storage and backup on the same drive.
You will need to erase your Time Machine volume to see if that fixes the problem. You will lose all the backup data unless you get another external drive to which you can clone the backup volume before erasing it.

IX4-300d I/O error, check file system, now stuck at software restart

Good morning!
I have a brand new IX4-300d. Was uploading files with sftp yesterday, which kept giving me errors, so I enable support access and checked the logs while uploading. Got a lot of:
end_request: I/O error, dev sde, sector 16384
sd 16:0:0:0: [sde] Unhandled error code
sd 16:0:0:0: [sde] Result: hostbyte=0x07 driverbyte=0x00
sd 16:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 01 00
end_request: I/O error, dev sde, sector 0
sd 16:0:0:0: [sde] Unhandled error code
sd 16:0:0:0: [sde] Result: hostbyte=0x07 driverbyte=0x00
sd 16:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 3a 38 17 c0 00 00 01 00
end_request: I/O error, dev sde, sector 7814036992
sd 16:0:0:0: [sde] Unhandled error code
sd 16:0:0:0: [sde] Result: hostbyte=0x07 driverbyte=0x00
sd 16:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 3a 38 17 d3 00 00 01 00
end_request: I/O error, dev sde, sector 7814037144
sd 16:0:0:0: [sde] Unhandled error code
sd 16:0:0:0: [sde] Result: hostbyte=0x07 driverbyte=0x00
sd 16:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 01 00
end_request: I/O error, dev sde, sector 0
sd 16:0:0:0: [sde] Unhandled error code
sd 16:0:0:0: [sde] Result: hostbyte=0x07 driverbyte=0x00
sd 16:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 00 00 00 01 00 00 01 00
end_request: I/O error, dev sde, sector 8
sd 16:0:0:0: [sde] Unhandled error code
sd 16:0:0:0: [sde] Result: hostbyte=0x07 driverbyte=0x00
sd 16:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 01 00
end_request: I/O error, dev sde, sector 0
sd 16:0:0:0: [sde] Unhandled error code
sd 16:0:0:0: [sde] Result: hostbyte=0x07 driverbyte=0x00
sd 16:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 3a 38 17 c0 00 00 01 00
end_request: I/O error, dev sde, sector 7814036992
sd 16:0:0:0: [sde] Unhandled error code
sd 16:0:0:0: [sde] Result: hostbyte=0x07 driverbyte=0x00
sd 16:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 3a 38 17 d3 00 00 01 00
end_request: I/O error, dev sde, sector 7814037144
So I requested a offline file system check from diagnose page. That was as off now 23 hours ago, from what I can see, the fs check did not take long, but has been stuck at DEvice software restarting for at least 22 hourse. I use less then 200Gig on it, setup as raid 10.
This device is not 1 month old. I had it freeze on my once already, not while restarting, just froze up. So that is the second time.
Status in the web console said all is fine, I had to go in through ssh and look at the os logs to find out what is happening.
What should I do?
Solved!
Go to Solution.

Hello CollegeMathieu
Please contact support using the below support links so we can have the issue properly diagnosed. There is a good chance that the unit may have shipped with a defective drive (if it is a diskless model one of your hard disks may be defective). This could be causing the strange firmware behavior.
A couple of things to try :
-power down the unit and re-seat all disks then try booting again to see if there is any change.
-If the above does not work, try swapping disk 1 with any of the other hard disks while powered off and then try booting again.
LenovoEMC Contact Information is region specific. Please select the correct link then access the Contact Us at the top right:
US and Canada: https://lenovo-na-en.custhelp.com/
Latin America and Mexico: https://lenovo-la-es.custhelp.com/
EU: https://lenovo-eu-en.custhelp.com/
India/Asia Pacific: https://lenovo-ap-en.custhelp.com/
http://support.lenovoemc.com/

Resized partitions how to fix file system to new size.

So I had to resize my /boot partition which required me to resize my root partition. How do I fix the file system to match the new size of the partition?

I do not understand why this was moved? This is not a new install, I was tuning my hooks to use systemd replaceing udev, autodetect and base.
running
mkinitcpio -p Linux
resulted in an error that said there was not enough space. and that the image was probably not correctly made.
I based my decision on the placement of the post by the following post which seemed to be in the same category.
https://bbs.archlinux.org/viewtopic.php?id=173359
Is there a place that provides a more narrow definition of topics that are acceptable for fourm categories?

Read only file system

One of my Parabola installations has started to always mount the / partition read-only. I've booted into a different install on the same machine, and can mount the affected partition without problems. I've done a fsck, and run the SMART disk checks. No problems. I've touched /forcefsck so a file system check is done every time I boot, but still the partition is read-only when it finishes booting.
This is the output of 'mount':
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=1024388k,nr_inodes=256097,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sdb10 on / type ext4 (ro,relatime,data=ordered)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime)
/dev/sdb9 on /boot type ext4 (rw,relatime,data=ordered)
/dev/sdb1 on /media/Stuff type fuseblk (rw,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
binfmt on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
This is the output of 'dmesg':
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.6.3-1-LIBRE (nobody@root) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Tue Oct 23 00:29:01 UYST 2012
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux-libre root=UUID=f0206707-f1ca-4bea-9eb3-c5d3713e4a4e ro resume=UUID=5b4248ba-30c3-48e5-a090-3a9c9f49d9c4 quiet
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000e4000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000007ff8ffff] usable
[ 0.000000] BIOS-e820: [mem 0x000000007ff90000-0x000000007ff9dfff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x000000007ff9e000-0x000000007ffcffff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000007ffd0000-0x000000007ffddfff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000007ffe0000-0x000000007fffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fff00000-0x00000000ffffffff] reserved
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] DMI present.
[ 0.000000] DMI: System manufacturer System Product Name/P5KPL-CM, BIOS 0702 08/27/2010
[ 0.000000] e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] No AGP bridge found
[ 0.000000] e820: last_pfn = 0x7ff90 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-DFFFF write-protect
[ 0.000000] E0000-EFFFF write-through
[ 0.000000] F0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask F80000000 write-back
[ 0.000000] 1 disabled
[ 0.000000] 2 disabled
[ 0.000000] 3 disabled
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [ffff8800000ff780]
[ 0.000000] initial memory mapped: [mem 0x00000000-0x1fffffff]
[ 0.000000] Base memory trampoline at [ffff880000099000] 99000 size 24576
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x7ff8ffff]
[ 0.000000] [mem 0x00000000-0x7fdfffff] page 2M
[ 0.000000] [mem 0x7fe00000-0x7ff8ffff] page 4k
[ 0.000000] kernel direct mapping tables up to 0x7ff8ffff @ [mem 0x1fbfd000-0x1fffffff]
[ 0.000000] RAMDISK: [mem 0x37a10000-0x37cfffff]
[ 0.000000] ACPI: RSDP 00000000000fb6a0 00014 (v00 ACPIAM)
[ 0.000000] ACPI: RSDT 000000007ff90000 0003C (v01 A_M_I_ OEMRSDT 08001027 MSFT 00000097)
[ 0.000000] ACPI: FACP 000000007ff90200 00084 (v02 A_M_I_ OEMFACP 08001027 MSFT 00000097)
[ 0.000000] ACPI: DSDT 000000007ff905c0 07BFA (v01 A0968 A0968000 00000000 INTL 20060113)
[ 0.000000] ACPI: FACS 000000007ff9e000 00040
[ 0.000000] ACPI: APIC 000000007ff90390 0006C (v01 A_M_I_ OEMAPIC 08001027 MSFT 00000097)
[ 0.000000] ACPI: MCFG 000000007ff90400 0003C (v01 A_M_I_ OEMMCFG 08001027 MSFT 00000097)
[ 0.000000] ACPI: OEMB 000000007ff9e040 00080 (v01 A_M_I_ AMI_OEM 08001027 MSFT 00000097)
[ 0.000000] ACPI: HPET 000000007ff981c0 00038 (v01 A_M_I_ OEMHPET 08001027 MSFT 00000097)
[ 0.000000] ACPI: GSCI 000000007ff9e0c0 02024 (v01 A_M_I_ GMCHSCI 08001027 MSFT 00000097)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000007ff8ffff]
[ 0.000000] Initmem setup node 0 [mem 0x00000000-0x7ff8ffff]
[ 0.000000] NODE_DATA [mem 0x7ff8c000-0x7ff8ffff]
[ 0.000000] [ffffea0000000000-ffffea0001ffffff] PMD -> [ffff88007d600000-ffff88007f5fffff] on node 0
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x00010000-0x00ffffff]
[ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
[ 0.000000] Normal empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00010000-0x0009efff]
[ 0.000000] node 0: [mem 0x00100000-0x7ff8ffff]
[ 0.000000] On node 0 totalpages: 524063
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 6 pages reserved
[ 0.000000] DMA zone: 3913 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 8127 pages used for memmap
[ 0.000000] DMA32 zone: 511953 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
[ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[ 0.000000] smpboot: Allowing 4 CPUs, 2 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 40
[ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000e4000
[ 0.000000] PM: Registered nosave memory: 00000000000e4000 - 0000000000100000
[ 0.000000] e820: [mem 0x80000000-0xfedfffff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff88007fc00000 s84608 r8192 d21888 u524288
[ 0.000000] pcpu-alloc: s84608 r8192 d21888 u524288 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1 2 3
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 515866
[ 0.000000] Policy zone: DMA32
[ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-linux-libre root=UUID=f0206707-f1ca-4bea-9eb3-c5d3713e4a4e ro resume=UUID=5b4248ba-30c3-48e5-a090-3a9c9f49d9c4 quiet
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] __ex_table already sorted, skipping sort
[ 0.000000] Checking aperture...
[ 0.000000] No AGP bridge found
[ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
[ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[ 0.000000] Memory: 2048780k/2096704k available (4726k kernel code, 452k absent, 47472k reserved, 4144k data, 772k init)
[ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
[ 0.000000] RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
[ 0.000000] NR_IRQS:4352 nr_irqs:712 16
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] allocated 8388608 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] hpet clockevent registered
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 1613.131 MHz processor
[ 0.003338] Calibrating delay loop (skipped), value calculated using timer frequency.. 3227.68 BogoMIPS (lpj=5377103)
[ 0.003342] pid_max: default: 32768 minimum: 301
[ 0.003391] Security Framework initialized
[ 0.003397] AppArmor: AppArmor disabled by boot time parameter
[ 0.003643] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 0.004961] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.005580] Mount-cache hash table entries: 256
[ 0.005927] Initializing cgroup subsys cpuacct
[ 0.005933] Initializing cgroup subsys memory
[ 0.005946] Initializing cgroup subsys devices
[ 0.005949] Initializing cgroup subsys freezer
[ 0.005951] Initializing cgroup subsys net_cls
[ 0.005953] Initializing cgroup subsys blkio
[ 0.005995] CPU: Physical Processor ID: 0
[ 0.005998] CPU: Processor Core ID: 0
[ 0.006000] mce: CPU supports 6 MCE banks
[ 0.006010] CPU0: Thermal monitoring enabled (TM2)
[ 0.006015] process: using mwait in idle threads
[ 0.006021] Last level iTLB entries: 4KB 128, 2MB 4, 4MB 4
Last level dTLB entries: 4KB 256, 2MB 0, 4MB 32
tlb_flushall_shift is 0xffffffff
[ 0.008169] ACPI: Core revision 20120711
[ 0.013350] ftrace: allocating 18348 entries in 72 pages
[ 0.026962] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.059974] smpboot: CPU0: Intel(R) Celeron(R) CPU E1200 @ 1.60GHz stepping 0d
[ 0.059996] Performance Events: PEBS fmt0+, 4-deep LBR, Core2 events, Intel PMU driver.
[ 0.059996] perf_event_intel: PEBS disabled due to CPU errata
[ 0.059996] ... version: 2
[ 0.059996] ... bit width: 40
[ 0.059996] ... generic registers: 2
[ 0.059996] ... value mask: 000000ffffffffff
[ 0.059996] ... max period: 000000007fffffff
[ 0.059996] ... fixed-purpose events: 3
[ 0.059996] ... event mask: 0000000700000003
[ 0.083501] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 0.096681] smpboot: Booting Node 0, Processors #1
[ 0.109825] Brought up 2 CPUs
[ 0.109825] smpboot: Total of 2 processors activated (6455.37 BogoMIPS)
[ 0.110104] devtmpfs: initialized
[ 0.112186] PM: Registering ACPI NVS region [mem 0x7ff9e000-0x7ffcffff] (204800 bytes)
[ 0.112186] NET: Registered protocol family 16
[ 0.112186] ACPI: bus type pci registered
[ 0.112186] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000)
[ 0.112186] PCI: not using MMCONFIG
[ 0.112186] PCI: Using configuration type 1 for base access
[ 0.113367] bio: create slab <bio-0> at 0
[ 0.113401] ACPI: Added _OSI(Module Device)
[ 0.113401] ACPI: Added _OSI(Processor Device)
[ 0.113401] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.113401] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.114233] ACPI: EC: Look up EC in DSDT
[ 0.116040] ACPI: Executed 1 blocks of module-level executable AML code
[ 0.122816] ACPI: SSDT 000000007ffa00f0 001D2 (v01 AMI CPU1PM 00000001 INTL 20060113)
[ 0.122816] ACPI: Dynamic OEM Table Load:
[ 0.122816] ACPI: SSDT (null) 001D2 (v01 AMI CPU1PM 00000001 INTL 20060113)
[ 0.122816] ACPI: SSDT 000000007ffa02d0 00143 (v01 AMI CPU2PM 00000001 INTL 20060113)
[ 0.122816] ACPI: Dynamic OEM Table Load:
[ 0.122816] ACPI: SSDT (null) 00143 (v01 AMI CPU2PM 00000001 INTL 20060113)
[ 0.122816] ACPI: Interpreter enabled
[ 0.122816] ACPI: (supports S0 S1 S3 S4 S5)
[ 0.122816] ACPI: Using IOAPIC for interrupt routing
[ 0.122816] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000)
[ 0.122816] PCI: MMCONFIG at [mem 0xf0000000-0xf3ffffff] reserved in ACPI motherboard resources
[ 0.136077] ACPI: No dock devices found.
[ 0.136086] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.136182] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 0.136328] pci_root PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[ 0.136382] PCI host bridge to bus 0000:00
[ 0.136387] pci_bus 0000:00: busn_res: [bus 00-ff] is inserted under domain [bus 00-ff]
[ 0.136390] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.136394] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
[ 0.136397] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
[ 0.136400] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[ 0.136403] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000dffff]
[ 0.136406] pci_bus 0000:00: root bus resource [mem 0x80000000-0xffffffff]
[ 0.136420] pci 0000:00:00.0: [8086:29c0] type 00 class 0x060000
[ 0.136478] pci 0000:00:01.0: [8086:29c1] type 01 class 0x060400
[ 0.136533] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 0.136587] pci 0000:00:1b.0: [8086:27d8] type 00 class 0x040300
[ 0.136606] pci 0000:00:1b.0: reg 10: [mem 0xfe9fc000-0xfe9fffff 64bit]
[ 0.136697] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.136723] pci 0000:00:1c.0: [8086:27d0] type 01 class 0x060400
[ 0.136803] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.136831] pci 0000:00:1c.1: [8086:27d2] type 01 class 0x060400
[ 0.136910] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
[ 0.136941] pci 0000:00:1d.0: [8086:27c8] type 00 class 0x0c0300
[ 0.136986] pci 0000:00:1d.0: reg 20: [io 0xc480-0xc49f]
[ 0.137022] pci 0000:00:1d.1: [8086:27c9] type 00 class 0x0c0300
[ 0.137067] pci 0000:00:1d.1: reg 20: [io 0xc800-0xc81f]
[ 0.137108] pci 0000:00:1d.2: [8086:27ca] type 00 class 0x0c0300
[ 0.137153] pci 0000:00:1d.2: reg 20: [io 0xc880-0xc89f]
[ 0.137190] pci 0000:00:1d.3: [8086:27cb] type 00 class 0x0c0300
[ 0.137235] pci 0000:00:1d.3: reg 20: [io 0xcc00-0xcc1f]
[ 0.137282] pci 0000:00:1d.7: [8086:27cc] type 00 class 0x0c0320
[ 0.137304] pci 0000:00:1d.7: reg 10: [mem 0xfe9fbc00-0xfe9fbfff]
[ 0.137395] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[ 0.137419] pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401
[ 0.137491] pci 0000:00:1f.0: [8086:27b8] type 00 class 0x060100
[ 0.137581] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0294 (mask 0003)
[ 0.137630] pci 0000:00:1f.1: [8086:27df] type 00 class 0x01018a
[ 0.137645] pci 0000:00:1f.1: reg 10: [io 0x0000-0x0007]
[ 0.137656] pci 0000:00:1f.1: reg 14: [io 0x0000-0x0003]
[ 0.137667] pci 0000:00:1f.1: reg 18: [io 0x08f0-0x08f7]
[ 0.137678] pci 0000:00:1f.1: reg 1c: [io 0x08f8-0x08fb]
[ 0.137689] pci 0000:00:1f.1: reg 20: [io 0xffa0-0xffaf]
[ 0.137730] pci 0000:00:1f.2: [8086:27c0] type 00 class 0x01018f
[ 0.137747] pci 0000:00:1f.2: reg 10: [io 0xc400-0xc407]
[ 0.137757] pci 0000:00:1f.2: reg 14: [io 0xc080-0xc083]
[ 0.137767] pci 0000:00:1f.2: reg 18: [io 0xc000-0xc007]
[ 0.137777] pci 0000:00:1f.2: reg 1c: [io 0xbc00-0xbc03]
[ 0.137786] pci 0000:00:1f.2: reg 20: [io 0xb880-0xb88f]
[ 0.137827] pci 0000:00:1f.2: PME# supported from D3hot
[ 0.137845] pci 0000:00:1f.3: [8086:27da] type 00 class 0x0c0500
[ 0.137901] pci 0000:00:1f.3: reg 20: [io 0x0400-0x041f]
[ 0.137974] pci_bus 0000:01: busn_res: [bus 01] is inserted under [bus 00-ff]
[ 0.137991] pci 0000:01:00.0: [1002:68f9] type 00 class 0x030000
[ 0.138008] pci 0000:01:00.0: reg 10: [mem 0xe0000000-0xefffffff 64bit pref]
[ 0.138021] pci 0000:01:00.0: reg 18: [mem 0xfeac0000-0xfeadffff 64bit]
[ 0.138031] pci 0000:01:00.0: reg 20: [io 0xd000-0xd0ff]
[ 0.138047] pci 0000:01:00.0: reg 30: [mem 0xfeaa0000-0xfeabffff pref]
[ 0.138085] pci 0000:01:00.0: supports D1 D2
[ 0.138109] pci 0000:01:00.1: [1002:aa68] type 00 class 0x040300
[ 0.138125] pci 0000:01:00.1: reg 10: [mem 0xfeafc000-0xfeafffff 64bit]
[ 0.138195] pci 0000:01:00.1: supports D1 D2
[ 0.138231] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.138236] pci 0000:00:01.0: bridge window [io 0xd000-0xdfff]
[ 0.138240] pci 0000:00:01.0: bridge window [mem 0xfea00000-0xfeafffff]
[ 0.138246] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xefffffff 64bit pref]
[ 0.138291] pci_bus 0000:03: busn_res: [bus 03] is inserted under [bus 00-ff]
[ 0.138295] pci 0000:00:1c.0: PCI bridge to [bus 03]
[ 0.138347] pci_bus 0000:02: busn_res: [bus 02] is inserted under [bus 00-ff]
[ 0.138372] pci 0000:02:00.0: [1969:1026] type 00 class 0x020000
[ 0.138398] pci 0000:02:00.0: reg 10: [mem 0xfebc0000-0xfebfffff 64bit]
[ 0.138412] pci 0000:02:00.0: reg 18: [io 0xec00-0xec7f]
[ 0.138519] pci 0000:02:00.0: PME# supported from D3hot D3cold
[ 0.138544] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
[ 0.138555] pci 0000:00:1c.1: PCI bridge to [bus 02]
[ 0.138560] pci 0000:00:1c.1: bridge window [io 0xe000-0xefff]
[ 0.138565] pci 0000:00:1c.1: bridge window [mem 0xfeb00000-0xfebfffff]
[ 0.138595] pci_bus 0000:04: busn_res: [bus 04] is inserted under [bus 00-ff]
[ 0.138642] pci 0000:00:1e.0: PCI bridge to [bus 04] (subtractive decode)
[ 0.138654] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
[ 0.138657] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
[ 0.138660] pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
[ 0.138663] pci 0000:00:1e.0: bridge window [mem 0x000d0000-0x000dffff] (subtractive decode)
[ 0.138666] pci 0000:00:1e.0: bridge window [mem 0x80000000-0xffffffff] (subtractive decode)
[ 0.138689] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.138794] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
[ 0.138867] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT]
[ 0.138903] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT]
[ 0.138963] pci0000:00: ACPI _OSC support notification failed, disabling PCIe ASPM
[ 0.138967] pci0000:00: Unable to request _OSC control (_OSC support mask: 0x08)
[ 0.145009] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *11 12 14 15)
[ 0.145073] ACPI: PCI Interrupt Link [LNKB] (IRQs *10)
[ 0.145128] ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 7 11 12 14 15)
[ 0.145187] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *11 12 14 15)
[ 0.145246] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 11 12 14 15) *0, disabled.
[ 0.145306] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 11 12 14 15) *0, disabled.
[ 0.145365] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 11 12 14 15) *0, disabled.
[ 0.145425] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 11 12 14 15)
[ 0.146698] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.146703] vgaarb: loaded
[ 0.146705] vgaarb: bridge control possible 0000:01:00.0
[ 0.146775] PCI: Using ACPI for IRQ routing
[ 0.147301] PCI: pci_cache_line_size set to 64 bytes
[ 0.147387] e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
[ 0.147389] e820: reserve RAM buffer [mem 0x7ff90000-0x7fffffff]
[ 0.147545] NetLabel: Initializing
[ 0.147548] NetLabel: domain hash size = 128
[ 0.147550] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.147571] NetLabel: unlabeled traffic allowed by default
[ 0.147588] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
[ 0.147593] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.147599] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
[ 0.166686] Switching to clocksource hpet
[ 0.177018] pnp: PnP ACPI init
[ 0.177044] ACPI: bus type pnp registered
[ 0.177174] pnp 00:00: [bus 00-ff]
[ 0.177179] pnp 00:00: [io 0x0cf8-0x0cff]
[ 0.177182] pnp 00:00: [io 0x0000-0x0cf7 window]
[ 0.177186] pnp 00:00: [io 0x0d00-0xffff window]
[ 0.177189] pnp 00:00: [mem 0x000a0000-0x000bffff window]
[ 0.177192] pnp 00:00: [mem 0x000d0000-0x000dffff window]
[ 0.177195] pnp 00:00: [mem 0x80000000-0xffffffff window]
[ 0.177279] pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active)
[ 0.177295] pnp 00:01: [mem 0xfed14000-0xfed19fff]
[ 0.177363] system 00:01: [mem 0xfed14000-0xfed19fff] has been reserved
[ 0.177369] system 00:01: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 0.177419] pnp 00:02: [dma 4]
[ 0.177423] pnp 00:02: [io 0x0000-0x000f]
[ 0.177426] pnp 00:02: [io 0x0081-0x0083]
[ 0.177429] pnp 00:02: [io 0x0087]
[ 0.177431] pnp 00:02: [io 0x0089-0x008b]
[ 0.177434] pnp 00:02: [io 0x008f]
[ 0.177437] pnp 00:02: [io 0x00c0-0x00df]
[ 0.177478] pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active)
[ 0.177494] pnp 00:03: [io 0x0070-0x0071]
[ 0.177508] pnp 00:03: [irq 8]
[ 0.177544] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.177557] pnp 00:04: [io 0x0061]
[ 0.177595] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
[ 0.177609] pnp 00:05: [io 0x00f0-0x00ff]
[ 0.177617] pnp 00:05: [irq 13]
[ 0.177654] pnp 00:05: Plug and Play ACPI device, IDs PNP0c04 (active)
[ 0.178000] pnp 00:06: [irq 6]
[ 0.178004] pnp 00:06: [dma 2]
[ 0.178007] pnp 00:06: [io 0x03f0-0x03f5]
[ 0.178010] pnp 00:06: [io 0x03f7]
[ 0.178096] pnp 00:06: Plug and Play ACPI device, IDs PNP0700 (active)
[ 0.178501] pnp 00:07: [irq 7]
[ 0.178504] pnp 00:07: [dma 3]
[ 0.178508] pnp 00:07: [io 0x0378-0x037f]
[ 0.178511] pnp 00:07: [io 0x0778-0x077f]
[ 0.178686] pnp 00:07: Plug and Play ACPI device, IDs PNP0401 (active)
[ 0.178731] pnp 00:08: [io 0x0000-0xffffffffffffffff disabled]
[ 0.178735] pnp 00:08: [io 0x0000-0xffffffffffffffff disabled]
[ 0.178738] pnp 00:08: [io 0x0290-0x0297]
[ 0.178815] system 00:08: [io 0x0290-0x0297] has been reserved
[ 0.178821] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.178918] pnp 00:09: [io 0x0010-0x001f]
[ 0.178922] pnp 00:09: [io 0x0022-0x003f]
[ 0.178925] pnp 00:09: [io 0x0044-0x005f]
[ 0.178928] pnp 00:09: [io 0x0062-0x0063]
[ 0.178934] pnp 00:09: [io 0x0065-0x006f]
[ 0.178937] pnp 00:09: [io 0x0072-0x007f]
[ 0.178939] pnp 00:09: [io 0x0080]
[ 0.178942] pnp 00:09: [io 0x0084-0x0086]
[ 0.178945] pnp 00:09: [io 0x0088]
[ 0.178948] pnp 00:09: [io 0x008c-0x008e]
[ 0.178951] pnp 00:09: [io 0x0090-0x009f]
[ 0.178953] pnp 00:09: [io 0x00a2-0x00bf]
[ 0.178956] pnp 00:09: [io 0x00e0-0x00ef]
[ 0.178959] pnp 00:09: [io 0x04d0-0x04d1]
[ 0.178962] pnp 00:09: [io 0x0800-0x087f]
[ 0.178965] pnp 00:09: [io 0x0000-0xffffffffffffffff disabled]
[ 0.178968] pnp 00:09: [io 0x0480-0x04bf]
[ 0.178971] pnp 00:09: [mem 0xfed1c000-0xfed1ffff]
[ 0.178974] pnp 00:09: [mem 0xfed20000-0xfed8ffff]
[ 0.179068] system 00:09: [io 0x04d0-0x04d1] has been reserved
[ 0.179072] system 00:09: [io 0x0800-0x087f] has been reserved
[ 0.179076] system 00:09: [io 0x0480-0x04bf] has been reserved
[ 0.179080] system 00:09: [mem 0xfed1c000-0xfed1ffff] has been reserved
[ 0.179083] system 00:09: [mem 0xfed20000-0xfed8ffff] has been reserved
[ 0.179089] system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.179173] pnp 00:0a: [mem 0xfed00000-0xfed003ff]
[ 0.179219] pnp 00:0a: Plug and Play ACPI device, IDs PNP0103 (active)
[ 0.179280] pnp 00:0b: [mem 0xffb00000-0xffbfffff]
[ 0.179284] pnp 00:0b: [mem 0xfff00000-0xffffffff]
[ 0.179332] pnp 00:0b: Plug and Play ACPI device, IDs INT0800 (active)
[ 0.179387] pnp 00:0c: [mem 0xffc00000-0xffefffff]
[ 0.179460] system 00:0c: [mem 0xffc00000-0xffefffff] has been reserved
[ 0.179466] system 00:0c: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.179524] pnp 00:0d: [mem 0xfec00000-0xfec00fff]
[ 0.179528] pnp 00:0d: [mem 0xfee00000-0xfee00fff]
[ 0.179608] system 00:0d: [mem 0xfec00000-0xfec00fff] could not be reserved
[ 0.179612] system 00:0d: [mem 0xfee00000-0xfee00fff] has been reserved
[ 0.179617] system 00:0d: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.179660] pnp 00:0e: [io 0x0060]
[ 0.179663] pnp 00:0e: [io 0x0064]
[ 0.179673] pnp 00:0e: [irq 1]
[ 0.179734] pnp 00:0e: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
[ 0.179796] pnp 00:0f: [irq 12]
[ 0.179852] pnp 00:0f: Plug and Play ACPI device, IDs PNP0f03 PNP0f13 (active)
[ 0.180166] pnp 00:10: [irq 4]
[ 0.180170] pnp 00:10: [dma 0 disabled]
[ 0.180173] pnp 00:10: [io 0x03f8-0x03ff]
[ 0.180292] pnp 00:10: Plug and Play ACPI device, IDs PNP0501 (active)
[ 0.180342] pnp 00:11: [mem 0xf0000000-0xf3ffffff]
[ 0.180427] system 00:11: [mem 0xf0000000-0xf3ffffff] has been reserved
[ 0.180433] system 00:11: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.180636] pnp 00:12: [mem 0x00000000-0x0009ffff]
[ 0.180640] pnp 00:12: [mem 0x000c0000-0x000cffff]
[ 0.180643] pnp 00:12: [mem 0x000e0000-0x000fffff]
[ 0.180646] pnp 00:12: [mem 0x00100000-0x7fffffff]
[ 0.180649] pnp 00:12: [mem 0x00000000-0xffffffffffffffff disabled]
[ 0.180743] system 00:12: [mem 0x00000000-0x0009ffff] could not be reserved
[ 0.180747] system 00:12: [mem 0x000c0000-0x000cffff] could not be reserved
[ 0.180751] system 00:12: [mem 0x000e0000-0x000fffff] could not be reserved
[ 0.180754] system 00:12: [mem 0x00100000-0x7fffffff] could not be reserved
[ 0.180760] system 00:12: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 0.180916] pnp: PnP ACPI: found 19 devices
[ 0.180919] ACPI: ACPI bus type pnp unregistered
[ 0.188605] pci 0000:00:1c.0: bridge window [io 0x1000-0x0fff] to [bus 03] add_size 1000
[ 0.188613] pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000
[ 0.188617] pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 03] add_size 200000
[ 0.188628] pci 0000:00:1c.1: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000
[ 0.188646] pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 200000
[ 0.188650] pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
[ 0.188653] pci 0000:00:1c.1: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
[ 0.188657] pci 0000:00:1c.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
[ 0.188664] pci 0000:00:1c.0: BAR 14: assigned [mem 0x80000000-0x801fffff]
[ 0.188668] pci 0000:00:1c.0: BAR 15: assigned [mem 0x80200000-0x803fffff 64bit pref]
[ 0.188673] pci 0000:00:1c.1: BAR 15: assigned [mem 0x80400000-0x805fffff 64bit pref]
[ 0.188678] pci 0000:00:1c.0: BAR 13: assigned [io 0x1000-0x1fff]
[ 0.188683] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.188687] pci 0000:00:01.0: bridge window [io 0xd000-0xdfff]
[ 0.188693] pci 0000:00:01.0: bridge window [mem 0xfea00000-0xfeafffff]
[ 0.188697] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xefffffff 64bit pref]
[ 0.188703] pci 0000:00:1c.0: PCI bridge to [bus 03]
[ 0.188707] pci 0000:00:1c.0: bridge window [io 0x1000-0x1fff]
[ 0.188713] pci 0000:00:1c.0: bridge window [mem 0x80000000-0x801fffff]
[ 0.188718] pci 0000:00:1c.0: bridge window [mem 0x80200000-0x803fffff 64bit pref]
[ 0.188725] pci 0000:00:1c.1: PCI bridge to [bus 02]
[ 0.188729] pci 0000:00:1c.1: bridge window [io 0xe000-0xefff]
[ 0.188735] pci 0000:00:1c.1: bridge window [mem 0xfeb00000-0xfebfffff]
[ 0.188740] pci 0000:00:1c.1: bridge window [mem 0x80400000-0x805fffff 64bit pref]
[ 0.188747] pci 0000:00:1e.0: PCI bridge to [bus 04]
[ 0.188784] pci 0000:00:1c.0: enabling device (0104 -> 0107)
[ 0.188805] pci 0000:00:1e.0: setting latency timer to 64
[ 0.188810] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
[ 0.188814] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
[ 0.188817] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
[ 0.188820] pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000dffff]
[ 0.188824] pci_bus 0000:00: resource 8 [mem 0x80000000-0xffffffff]
[ 0.188827] pci_bus 0000:01: resource 0 [io 0xd000-0xdfff]
[ 0.188830] pci_bus 0000:01: resource 1 [mem 0xfea00000-0xfeafffff]
[ 0.188833] pci_bus 0000:01: resource 2 [mem 0xe0000000-0xefffffff 64bit pref]
[ 0.188836] pci_bus 0000:03: resource 0 [io 0x1000-0x1fff]
[ 0.188840] pci_bus 0000:03: resource 1 [mem 0x80000000-0x801fffff]
[ 0.188843] pci_bus 0000:03: resource 2 [mem 0x80200000-0x803fffff 64bit pref]
[ 0.188846] pci_bus 0000:02: resource 0 [io 0xe000-0xefff]
[ 0.188849] pci_bus 0000:02: resource 1 [mem 0xfeb00000-0xfebfffff]
[ 0.188852] pci_bus 0000:02: resource 2 [mem 0x80400000-0x805fffff 64bit pref]
[ 0.188856] pci_bus 0000:04: resource 4 [io 0x0000-0x0cf7]
[ 0.188859] pci_bus 0000:04: resource 5 [io 0x0d00-0xffff]
[ 0.188862] pci_bus 0000:04: resource 6 [mem 0x000a0000-0x000bffff]
[ 0.188865] pci_bus 0000:04: resource 7 [mem 0x000d0000-0x000dffff]
[ 0.188868] pci_bus 0000:04: resource 8 [mem 0x80000000-0xffffffff]
[ 0.188916] NET: Registered protocol family 2
[ 0.189551] TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
[ 0.192082] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 0.192686] TCP: Hash tables configured (established 262144 bind 65536)
[ 0.192758] TCP: reno registered
[ 0.192773] UDP hash table entries: 1024 (order: 3, 32768 bytes)
[ 0.192798] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
[ 0.192949] NET: Registered protocol family 1
[ 0.193147] pci 0000:01:00.0: Boot video device
[ 0.193158] PCI: CLS 32 bytes, default 64
[ 0.193230] Unpacking initramfs...
[ 0.285578] Freeing initrd memory: 3008k freed
[ 0.287514] audit: initializing netlink socket (disabled)
[ 0.287533] type=2000 audit(1351450895.286:1): initialized
[ 0.303689] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.306261] VFS: Disk quotas dquot_6.5.2
[ 0.306342] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.306570] msgmni has been set to 4007
[ 0.306904] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.306951] io scheduler noop registered
[ 0.306955] io scheduler deadline registered
[ 0.307043] io scheduler cfq registered (default)
[ 0.307215] pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
[ 0.307324] pcieport 0000:00:1c.0: irq 41 for MSI/MSI-X
[ 0.307443] pcieport 0000:00:1c.1: irq 42 for MSI/MSI-X
[ 0.307659] intel_idle: does not run on family 6 model 15
[ 0.307698] GHES: HEST is not enabled!
[ 0.307788] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 0.328340] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.349279] 00:10: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.349579] Linux agpgart interface v0.103
[ 0.349708] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
[ 0.352389] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.352444] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 0.352607] mousedev: PS/2 mouse device common for all mice
[ 0.352700] rtc_cmos 00:03: RTC can wake from S4
[ 0.352865] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[ 0.352896] rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
[ 0.352913] cpuidle: using governor ladder
[ 0.352915] cpuidle: using governor menu
[ 0.353088] drop_monitor: Initializing network drop monitor service
[ 0.353195] TCP: cubic registered
[ 0.353379] NET: Registered protocol family 10
[ 0.353609] NET: Registered protocol family 17
[ 0.353626] Key type dns_resolver registered
[ 0.353965] PM: Checking hibernation image partition UUID=5b4248ba-30c3-48e5-a090-3a9c9f49d9c4
[ 0.377050] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[ 0.398600] PM: Hibernation image not present or could not be loaded.
[ 0.398629] registered taskstats version 1
[ 0.399166] rtc_cmos 00:03: setting system clock to 2012-10-28 19:01:35 UTC (1351450895)
[ 0.400807] Freeing unused kernel memory: 772k freed
[ 0.401093] Write protecting the kernel read-only data: 8192k
[ 0.407007] Freeing unused kernel memory: 1408k freed
[ 0.410355] Freeing unused kernel memory: 652k freed
[ 0.424642] systemd-udevd[42]: starting version 194
[ 0.484567] ACPI: bus type usb registered
[ 0.484613] usbcore: registered new interface driver usbfs
[ 0.484629] usbcore: registered new interface driver hub
[ 0.484994] usbcore: registered new device driver usb
[ 0.485924] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.485981] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[ 0.485987] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 0.485997] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
[ 0.489913] ehci_hcd 0000:00:1d.7: debug port 1
[ 0.489922] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
[ 0.489951] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfe9fbc00
[ 0.493550] SCSI subsystem initialized
[ 0.496118] ACPI: bus type scsi registered
[ 0.496720] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 0.497003] hub 1-0:1.0: USB hub found
[ 0.497013] hub 1-0:1.0: 8 ports detected
[ 0.497923] uhci_hcd: USB Universal Host Controller Interface driver
[ 0.497967] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 0.497972] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 0.497982] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
[ 0.498020] uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000c480
[ 0.498143] libata version 3.00 loaded.
[ 0.499305] hub 2-0:1.0: USB hub found
[ 0.499317] hub 2-0:1.0: 2 ports detected
[ 0.499540] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 0.499547] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 0.499557] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
[ 0.499610] uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000c800
[ 0.500253] hub 3-0:1.0: USB hub found
[ 0.500264] hub 3-0:1.0: 2 ports detected
[ 0.500442] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[ 0.500448] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 0.500463] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
[ 0.500512] uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000c880
[ 0.500811] hub 4-0:1.0: USB hub found
[ 0.500822] hub 4-0:1.0: 2 ports detected
[ 0.501016] uhci_hcd 0000:00:1d.3: setting latency timer to 64
[ 0.501022] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[ 0.501039] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
[ 0.501090] uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000cc00
[ 0.502169] hub 5-0:1.0: USB hub found
[ 0.502179] hub 5-0:1.0: 2 ports detected
[ 0.502422] ata_piix 0000:00:1f.1: version 2.13
[ 0.502499] ata_piix 0000:00:1f.1: setting latency timer to 64
[ 0.503963] scsi0 : ata_piix
[ 0.504744] scsi1 : ata_piix
[ 0.505372] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
[ 0.505378] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
[ 0.505429] ata_piix 0000:00:1f.2: MAP [
[ 0.505431] P0 P2 P1 P3 ]
[ 0.505484] ata_piix 0000:00:1f.2: setting latency timer to 64
[ 0.507566] scsi2 : ata_piix
[ 0.508975] scsi3 : ata_piix
[ 0.509624] ata3: SATA max UDMA/133 cmd 0xc400 ctl 0xc080 bmdma 0xb880 irq 19
[ 0.509630] ata4: SATA max UDMA/133 cmd 0xc000 ctl 0xbc00 bmdma 0xb888 irq 19
[ 0.684177] ata3.00: ATA-8: WDC WD6400AAKS-00A7B2, 01.03B01, max UDMA/133
[ 0.684184] ata3.00: 1250263728 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 0.691230] ata3.00: configured for UDMA/133
[ 0.691417] scsi 2:0:0:0: Direct-Access ATA WDC WD6400AAKS-0 01.0 PQ: 0 ANSI: 5
[ 0.699349] sd 2:0:0:0: [sda] 1250263728 512-byte logical blocks: (640 GB/596 GiB)
[ 0.699463] sd 2:0:0:0: [sda] Write Protect is off
[ 0.699468] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 0.699516] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 0.774080] sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 >
[ 0.775132] sd 2:0:0:0: [sda] Attached SCSI disk
[ 1.096765] usb 2-2: new low-speed USB device number 2 using uhci_hcd
[ 1.275214] usbcore: registered new interface driver usbhid
[ 1.275219] usbhid: USB HID core driver
[ 1.276959] input: USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/input/input1
[ 1.277358] hid-generic 0003:04B3:310C.0001: input,hidraw0: USB HID v1.11 Mouse [USB Optical Mouse] on usb-0000:00:1d.0-2/input0
[ 1.290145] tsc: Refined TSC clocksource calibration: 1613.217 MHz
[ 1.290153] Switching to clocksource tsc
[ 1.426263] PM: Starting manual resume from disk
[ 1.426269] PM: Hibernation image partition 8:8 present
[ 1.426271] PM: Looking for hibernation image.
[ 1.426530] PM: Image not found (code -22)
[ 1.426535] PM: Hibernation image not present or could not be loaded.
[ 1.648559] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null)
[ 12.388263] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null)
[ 12.459036] fuse init (API version 7.20)
[ 13.150864] Adding 1951860k swap on /dev/sda8. Priority:-1 extents:1 across:1951860k
[ 0.691798] ACPI: Invalid Power Resource to register!
[ 14.060519] synergys[417]: segfault at 0 ip 0000000000449fa9 sp 00007fff68a19a90 error 4
[ 14.060531] in synergys[400000+cb000]
(I disconnected the second hard drive in the machine to verify that it wasn't causing problems. Hence the sda / sdb discrepancy)
I've been able to mount the partitions and chroot into them, but I don't know what to do from here. Oddly, I've discovered that 'ls' doesn't output anything, although bash completion seems to work ok.
Any ideas on what I should do to get my system running again?
Thanks in advance,
Bernie

Have you read the forum rules? Asking for support for Parabola isn't going to get you very far.
https://wiki.archlinux.org/index.php/Fo … pport_ONLY

EZ file system errors

Hello people!
Today I have a new issue. I received an email from my EZmedia NAS "The file system on your Lenovo EZ has errors and needs to be checked".
But I have not any process tu run.
Options? Solutions???

Hi JoeSRV,
I would recommend doing an offline disk check. Type "<IP address of NAS>/manage/diagnostics.html" into your web browser and select on the Storage tab. Then click on "Perform an offline file system check..." to begin the disk check.
Have questions and need answers?
Search the database for answers to FAQ's, software/driver downloads, tutorials, news, features and more!
LenovoEMC Support & Downloads
LenovoEMC North America Support Contact Page

Essbase file system

Hi,
We ran out of the existing ESSBASE file system( Analytic Service 9.3.0.1) and we added a new file system on different volume. Now when we open a Analytic Admin. service console and check the properties/disk space tab, we are able to see the name of the new file system but all the values are 0's including total space, free space or used space. We are able to see the old file system values but not the new file system. I have verified that 1 TB space is available on the new file system (via putty session.)
Any idea how we can make it visible on AAS console.
Thanks
AA

Have you extended the current file system or created a new file system mount?
Have you tried starting and stopping Essbase?
Brian Chow

File Systen Check Fail

I keep getting a file system check fail after a new install:
The error message states that "/dev/hda3 could not be read or does not describe a correct ext2 filesystem"
/dev/hda3 was setup as ext4 and as /, so I can't really believe this error message.

Thanks rockin turtle, I did a standard reinstall instead of legacy like you suggested:
Even though my system didn't have sata, the correct approach was to do a standard install instead of "Legacy IDE".
This appears to be a bug in the installer right? I couldn't find it in the bug tracker.

How to add more disk space into /   root file system

Hi All,
Linux 2.6.18-128
can anyone please let us know how to add more disk space into "/" root file system.
i have added new hard disk with space of 20GB,
[root@rac2 shm]# df -h
Filesystem            Size Used Avail Use% Mounted on
/dev/hda1             965M 767M 149M 84% /
/dev/hda7             1.9G 234M 1.6G 13% /var
/dev/hda6             2.9G   69M 2.7G   3% /tmp
/dev/hda3             7.6G 4.2G 3.0G 59% /usr
/dev/hda2              18G   12G 4.8G 71% /u01
LABLE=/               2.0G     0 2.0G   0% /dev/shm
/dev/hdb2             8.9G 149M 8.3G   2% /vm
[root@rac2 shm]#

Dude! wrote:
I would actually question whether or not more disks increase the risk of a disk failure. One disk can break as likely as one of two of more disks.
Simple stats. Buying 2 lottery tickets instead of one, gives you 2 chances to win the lottery prize. Not 1. Even though the odds of winning per ticket remains unchanged.
2 disks buy you 2 tickets in The-Drive-Failure lottery.
Back in the 90's, BT (British Telecom) had a 80+ node OPS cluster build with Pyramid MPP hardware. They had a dedicated store of scsi disks for replacing failed disks - as there were disk failure fairly often due to the number of disks. (a Pryamid MPP chassis looked like a Xmas tree with all the scsi drive LEDs, and BT had several)
In my experience - one should rather expect a drive failure sooner, than later. And have some kind of contingency plan in place to recover from the failure.
The use of symbolic links instead of striping the filesystem protects from the complete loss of the enchilada if a volume member fails, but it does not reduce the risk of loosing data.
I would rather buy a single ticket for the drive failure lottery for a root drive, than 2 tickets in this case. And using symbolic links to "offload" non-critical files to the 2nd drive means that its lottery ticket prize is not a non-bootable server due to a toasted root drive.

QFS don�t update File System space after a failover

When I do a fail-over (get down a master node of device QFS) while I delete a file the space on it (FS) is inconsistent (df command show mayor space than du command) and I have to do a file System Check on it to get free space.

Thanks,
The version of QFS is VERSION.4.6
SUN Cluster version 3.2
Solaris 10 8/07
The file "mcf" is
# Equipment Eq Eq Family Device Additional
# Identifier Ord Type Set State Parameters
kml 1 ms kml on shared
/dev/did/dsk/d7s0 10 md kml on
/dev/did/dsk/d8s0 11 md kml on
/dev/did/dsk/d9s0 12 md kml on
/dev/did/dsk/d10s0 13 md kml on
/dev/did/dsk/d11s0 14 md kml on
/dev/did/dsk/d12s0 15 md kml on
/dev/did/dsk/d13s0 16 md kml on
/dev/did/dsk/d14s0 17 md kml on
/dev/did/dsk/d15s0 18 md kml on
/dev/did/dsk/d16s0 19 md kml on
/dev/did/dsk/d21s0 20 md kml on
/dev/did/dsk/d22s0 21 md kml on
/dev/did/dsk/d23s0 22 md kml on
/dev/did/dsk/d24s0 23 md kml on
/dev/did/dsk/d25s0 24 md kml on
/dev/did/dsk/d26s0 25 md kml on
/dev/did/dsk/d27s0 26 md kml on
/dev/did/dsk/d28s0 27 md kml on
/dev/did/dsk/d29s0 28 md kml on
/dev/did/dsk/d30s0 29 md kml on
# samfsinfo kml
samfsinfo: filesystem kml is mounted.
name: kml version: 2 shared
time: Thursday, April 10, 2008 4:48:05 PM PYT
count: 20
capacity: 000000003d064400 DAU: 64
space: 000000003d04e480
ord eq capacity space device
0 10 00000000030d1d00 00000000030d0580 /dev/did/dsk/d7s0
1 11 00000000030d1d00 00000000030d1c00 /dev/did/dsk/d8s0
2 12 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d9s0
3 13 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d10s0
4 14 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d11s0
5 15 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d12s0
6 16 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d13s0
7 17 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d14s0
8 18 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d15s0
9 19 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d16s0
10 20 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d21s0
11 21 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d22s0
12 22 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d23s0
13 23 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d24s0
14 24 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d25s0
15 25 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d26s0
16 26 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d27s0
17 27 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d28s0
18 28 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d29s0
19 29 00000000030d1d00 00000000030d1c40 /dev/did/dsk/d30s0
#df -k |grep kml
kml 1023820800 5384 1023815416 1% /oradata_kml1
#clrs status -g qfs-kml-rg +
Cluster Resources ===
Resource Name Node Name State Status Message
qfs-kml-rs m9ka Online Online - Service is online.
m9kb Offline Offline
Best regasts,
Ivan

File system check recs on new ASAs

Similar Messages

Maybe you are looking for