Error on sd* during boot

Hi,
I am using RHEL 5.2
with smart Array
with LVM2
/boot on /dev/cciss/c0d0p1
/, /usr ... on /dev/cciss/c0d0p2 (LVM)
/data on /dev/cciss/c0d1 (LVM)
during boot I have a lot of errors like below
Buffer I/O error on device sda, logical block 0
end_request: I/O error, dev sda, sector 0
it is connected to a SAN
Thanks for your help

I would first verify correct device assignment on the SAN, or Fiber switch if used, correct cabling and check if the disks are perhaps already mounted from another computer. Check what has changed since the last reboot of the system. Perhaps boot into rescue mode from the Linux installation DVD and see if you can mount the volumes in read only mode (mount -r).

Similar Messages

  • VIA Raid 0: Red screen of Death - fatal error during boot sequence

    I have been using two Maxtor 120GB SATA drives in a RAID 0 array on my Athlon 64 MSI MB.  I have occasionally had messages saying "Hard disk error. Can't find drive 0".  I've assumed that this has been a driver issue because if I power down, wait a while I can reboot and continue without issue (other than chkdsk running during boot up).  However after the last such error, when I next tried to reboot I got an error message as the RAID was initialising.  The error message was in a red box on a black screen and stated that there was a fatal error and that the raid relationship and all HHD would be destroyed if I continued.  Naturally I switched off at this point, but on rebooting got exactly the same message.  Eventually, as I have backups, I continued past this point and sure enough the RAID had gone.  So I rebuilt the raid array and everything seems to be OK.
    However, I'd forgotten that my MSI DVD burner was incapacitated due to a failed firmware update so had temporaril;y replace it with a DVD rom drive to get access to my backups.  BUT the drive won't read all my backup discs, in particular it won't read the Drive C backups .
    Has anyone else had this RAID erro.  Is it a driver error or is it a dsik failing (even though they were new at Christmas).
    I am using a Superflower power supply which has 22A on the 12V rail
    1GB PC3200 ram by A-Data (CAS 2.5)
    Elderly HP 9100 CDRW
    MSI DR-8 DVD RW
    Ethernet card
    Radeon 9600 128MB
    AMD64 3000 processor
    Freeflow

    Raids do not really help benchmarks unless you considure hard drive benchmarks. Most games and benchmark proggies load everything they need prior to running. So unless you have a low memory condition that forces the game or benchmark to use the swap file the only place that you would typically see any gain in speed is during the loading of the game or benchmark. That is hard to quantify other than through experience.
    Where a raid shines is in file tranfer situations. When you create and save large files such as movies, Reading or copying large files, defragging, or any other massive file effort. Overall the gains can be very small compaired to the rest of what you do with your system. However that is not to belittle what a Raid does. It does give a finer sheen to the overall computers operations and will make sluggish file transfers seem much more bearable overall.

  • Suddenly "Fatal error during GPU init" during boot - radeon

    Hi,
    after a rather abrupt shutdown my system doesn't boot correctly anymore.
    I have an Asus laptop with an ATI radeon HD 2400 (so the sticker on the laptop says - I'm not really a hardware guy)
    Before:
    While booting, the kernel/console output had bigger, somewhat non-high-resolution letters. Halfway in, the letters changed into a smaller, higher-defined font which was more "beautiful".
    Sorry, I don't know what mechanism that is, so I had to describe it that way.
    After:
    This doesn't happen anymore. Rather, I get this message during boot (this is a copy out of /var/log/errors.log):
    Jun 21 17:59:55 localhost kernel: [    4.081919] radeon 0000:01:00.0: Fatal error during GPU init
    Jun 21 17:59:55 localhost kernel: [    4.082998] radeon 0000:01:00.0: no bo for sa manager
    Jun 21 17:59:55 localhost kernel: [    4.083059] [TTM] Trying to take down uninitialized memory manager type 1
    I already tried the following:
    - reinstall xorg and xf86-video-ati
    - sections "Enable KMS" and "Troubleshoot KMS" from that wiki entry:
      https://wiki.archlinux.org/index.php/ATI
    - scream and slightly hit the side of the laptop
    Nothing worked. Could anyone tell me where to continue searching? I'd hate to reinstall a 1-week old system.
    Thanks in advance,
    Alex

    If you remove the ati drivers, the mesa-drivers are used I think.
    Since the open source drivers don't work, you should try the closed source drivers (ATI Catalyst) from the AUR. Installing this is a bit of a hassle. The catalyst driver does not support Xorg 1.12, so you have to add a repository for Xorg1.11 and downgrade (see the wiki page). Then, you should install either catalyst-utils and catalyst-hook from AUR (as described in the wiki) or catalyst-total (which combines both and is also mentioned in the wiki).
    See the Catalyst Wiki for all information.
    Catalyst Utils in AUR
    Catalyst Hook
    Catalyst Total
    edit: I just read the wiki. It seems like there is an easier way to install things now: https://wiki.archlinux.org/index.php/AT … repository
    Last edited by Terminator (2012-06-25 23:32:39)

  • 3 unable to open '/etc/udev/rules.d/':m error during booting

    After a recent upgrade to the kernel26-2.6.28.5-1-i686, I got the above error during booting in one of the laptop.
    My search did not give any positive solution for this till now. I read that now udev gets its rules from /lib/udev/rules.d.
    But still rules files in /etc/udev/rules.d and /lib/udev/rules.d are different. I know that any symllink work around will not work in this case, I tried but as  expected the error message appears again.
    So, I roll back to kernel26-2.6.28.4-1-i686 and everything back to normal.
    Any Idea to resolve this? (package is not broken as I use the same mirror for another PC and in that I am not getting any error)
    Last edited by kgas (2009-02-19 16:10:23)

    This issue got resolved on its own with the latest kernel (kernel26-2.6.28.6-1-i686) update. I will leave this topic for some more time to see others response...

  • Memory Allocation Error during Boot

    Hi,
    I am posting this on a different computer than the one on which I istalled Java because I can no longer get it to boot.
    Here's the history:
    I am working in Windows 98
    I added a line to the autoexec.bat so that the PATH lines looked like this:
    SET PATH=C:PROGRA~1\UTILIT~1\SYMATEC\PCANYW~1
    PATH=%PATH%;"C:Program Files\Mts";"C:j2sdk1.4.0_02\bin
    I then rebooted and tried the javac and java commands in different folders and everything worked fine. I shut down the computer and tried to reboot a day later. The following are pieces of the message I received (I don't usually go near the autoexec.bat or system settings so I have no idea how to get past these errors, nor fix them):
    SET PATH=C:PROGRA~1\UTILIT~1\SYMATEC\PCANYW~1
    PATH=C:WINDOWS;C:WINDOWS\COMMAND;C:PROGRA~1\UTILIT~1\SYMATEC\PCANYW~1;"C:Program Files\Mts";"C:j2sdk1.4.0_02\bin
    General Protection Fault in C:WINDOWS\SCANDISK.ALT at 0090:1921
    Memory Allocation Error
    Cannot load COMMAND, system halted
    Please help!
    Thanks,
    Julie

    SET PATH=C:PROGRA~1\UTILIT~1\SYMATEC\PCANYW~1
    PATH=C:WINDOWS;C:WINDOWS\COMMAND;C:PROGRA~1\UTILIT~1\SY
    ATEC\PCANYW~1;"C:Program
    Files\Mts";"C:j2sdk1.4.0_02\bin
    General Protection Fault in C:WINDOWS\SCANDISK.ALT at
    0090:1921This shouldn't have been caused by the Java installation. As I understand the situation, at load time scandisk has been called. This is usually due to the computer not having been shut down properly, or a sign of real problems. However, scandisk is unable to run.
    You should try a forum/newsgroup for Windows for more help. My own suggestion would be to load to the command prompt (or try safe mode). (Press F8 during boot to get a menu.) And then run scandisk manually. If it works, try renaming the C:\WINDOWS\SCANDISK.ALT file and rebooting.
    Regards,
    Bhaveet

  • G580 Upgrade to Windows 10 failed in the SAFE_OS phase with an error during BOOT operation

    0xC1900101-0x20017 I could not successfully upgrade from windows update, nor from the straight download site.   The installation failed in the SAFE_OS phase with an error during BOOT operation.  I see w10 bios updates for other models.  Has anyone been successful in upgrading to W10 from W8?

    2015-07-31 21:36:19, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
    2015-07-31 21:36:19, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
    2015-07-31 21:36:21, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >:uspend(1066): Result = 0xC18001042015-07-31 21:36:21, Error MOUPG CSetupManager::ExecuteInstallMode(656): Result = 0x800705BB
    2015-07-31 21:36:21, Error MOUPG CSetupManager::ExecuteDownlevelMode(376): Result = 0x800705BB
    2015-07-31 21:36:21, Error MOUPG CSetupManager::Execute(222): Result = 0x800705BB
    2015-07-31 21:36:21, Error MOUPG CSetupHost::Execute(370): Result = 0x800705BB
    2015-07-31 21:36:21, Error MOUPG CDlpManager::AsyncSerializeDisable(471): Result = 0x80070216
    2015-07-31 21:36:36, Error CallPidGenX: PidGenX function failed on this product key. (hr = 0x8a010101)
    2015-07-31 21:36:40, Error CallPidGenX: PidGenX function failed on this product key. (hr = 0x8a010101)
    2015-07-31 21:37:02, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
    2015-07-31 21:37:03, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
    2015-07-31 21:37:04, Error CDiagnosticsHelper:etDeferredSQMDatapoint: Attempting to set a deferred SQM datapoint in an invalid SQM session[gle=0x000000b7]
    2015-07-31 21:37:04, Error CDiagnosticsHelper:etDeferredSQMDatapoint: Attempting to set a deferred SQM datapoint in an invalid SQM session[gle=0x000000b7]
    2015-07-31 21:37:11, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
    2015-07-31 21:39:15, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
    2015-07-31 21:39:18, Error CDiagnosticsHelper:etDeferredSQMDatapoint: Attempting to set a deferred SQM datapoint in an invalid SQM session[gle=0x000000b7]

  • Errors during boot OEL 5.5 starting a 11.2 instance

    Hello,
    I've installed Oracle 11GR2 on OEL 5.5 and a I created a db instance. How I can see why my db instance is not up? More precisely , how I can get errors messages thrown by procedure that start oracle instance during boot process (I am sure that kind of messages is thrown but I can't see them).
    Many thanks,
    Aurel

    Hi;
    I've installed Oracle 11GR2 on OEL 5.5 and a I created a db instance. How I can see why my db instance is not up? More precisely , how I can get errors messages thrown by procedure that start oracle instance during boot process (I am sure that kind of messages is thrown but I can't see them).For can see your db up or not u can run :
    ps -ef|grep lg
    oracle 6750316 1 0 Feb 28 - 0:03 asm_lgwr_+ASM
    oracle 9437238 14418146 0 16:06:56 pts/3 0:00 grep lg
    oracle 14745644 1 0 15:50:41 - 0:00 ora_lgwr_orcl
    So my asm instance and db instance is up
    For alert or error message you need to create one sh which is cheking alert.log,if you hit ORA error than it can send u email
    Regard
    Helios

  • Error during boot

    When doing tmboot, I have obtained the following error:
    exec siscafrn -A -- -d -l 09 :
    CMDTUX_CAT:819: INFO: Process id=22319 Assume started (pipe).
    exec siscafrn -A -- -d -l 09 :
    CMDTUX_CAT:819: INFO: Process id=22320 Assume started (pipe).
    exec siscafrn -A -- -d -l 09 :
    CMDTUX_CAT:819: INFO: Process id=22321 Assume started (pipe).
    exec siscafrn -A -- -d -l 09 :
    That it means? So that one takes place? The documentation on the error indicates
    that any action is not necessary. And that the servants can have published or
    no. I have verified with tmadmin that the servants estan DEAD. He can be a problem
    of allocation of resources, can be that ipc does not have sufficient resources
    associate? Somebody podria to give an idea me on like acting? Thank you very much

    This error message is normaly printed if the server is directly going down again
    during boot. Don't know what your servers are, but you will see this error message
    e.g. if the server is not able to allocate its resources like database access,
    open config/logfiles, etc.. As the server is not booting you have a problem you
    should investigate. Taking a look to your ULOG and stdout/stderr files may give
    more details.
    "lucia vilar" <[email protected]> wrote:
    >
    >
    When doing tmboot, I have obtained the following error:
    exec siscafrn -A -- -d -l 09 :
    CMDTUX_CAT:819: INFO: Process id=22319 Assume started (pipe).
    exec siscafrn -A -- -d -l 09 :
    CMDTUX_CAT:819: INFO: Process id=22320 Assume started (pipe).
    exec siscafrn -A -- -d -l 09 :
    CMDTUX_CAT:819: INFO: Process id=22321 Assume started (pipe).
    exec siscafrn -A -- -d -l 09 :
    That it means? So that one takes place? The documentation on the error
    indicates
    that any action is not necessary. And that the servants can have published
    or
    no. I have verified with tmadmin that the servants estan DEAD. He can
    be a problem
    of allocation of resources, can be that ipc does not have sufficient
    resources
    associate? Somebody podria to give an idea me on like acting? Thank you
    very much

  • During boot..contains a file system with errors ??

    Lately when I boot up my system, I receive the error dev/sda3 contains a file syetem with errors, force check.  I have to hit CTRL+D to continue.  Then it reboots, goes past sda3 to give the same error for sda4 which it checks...then I hit CTRL+D it reboots and usually continues to a working system.
    It has happenned many times in the past few weeks, however once boot up the system is fine.  Sda3 is my / partition and sda4 is home.  Should I check a log for more info, or should I manually run some checks?
    This makes my Arch system's boot up time seem to take as long as Ubuntu .
    Thanks

    glenn69 wrote:Thanks for the response, but that will simply perform the disk checks without the need for a reboot in between.
    Not quite - the disk checks during boot don't actually fix filesystem errors.  That's your job when you're dropped into the shell.  You may run fsck /dev/<your hd> (or fsck -y for non-interactive mode) to repair the filesystem.
    glenn69 wrote:That does help, but I'm a bit more interested in the WHY it is happening.  How do I find that out to determine a long term solution?
    Could be any number of reasons; I find an unclean shutdown is the most common cause for me.  But if this happens consistently after you manually repair the filesystems, there may be something wrong with your actual hard drive.
    Also, if you're not using a journaling filesystem (ex. ext3/4), try using one.

  • [SOLVED] USB Harddrive via fstab turned off during Boot - Error

    Hello^^
    I'm trying to mount my external USB Drive.
    I put the following line in fstab:
    /dev/sdb1 /media/Musik ext4 noauto,user,default 0 1
    I only want to start the Harddive occasionally.
    The problem is, when the drive is completly turned off during boot I get the following error:
    No such file or directory while trying to open /dev/sdb1
    Possibly non existend device?
    I thought that the noauto Option should prevent fstab from mounting the hdd???
    regards
    cl10k
    PS: Manual mounting works without any problems...
    Last edited by cl10k (2011-03-20 22:49:43)

    Let me give you a hand then. The following I have in my /etc/udev/rules.d/11-media-by-label-auto-mount.rules, and what it does is:
    -- pick the name of a drive,
    -- create a dedicated /media/mountpoint name (certainly, "mountpoint" is replaced by the name of your drive),
    -- mount the drive on boot,
    -- unmount the drive on shutdown and delete the /media/mountpoint.
    KERNEL!="sd[a-z][0-9]", GOTO="media_by_label_auto_mount_end"
    # Import FS infos
    IMPORT{program}="/sbin/blkid -o udev -p %N"
    # Get a label if present, otherwise specify one
    ENV{ID_FS_LABEL}!="", ENV{dir_name}="%E{ID_FS_LABEL}"
    ENV{ID_FS_LABEL}=="", ENV{dir_name}="usbhd-%k"
    # Global mount options
    ACTION=="add", ENV{mount_options}="relatime"
    # Filesystem-specific mount options
    ACTION=="add", ENV{ID_FS_TYPE}=="vfat|ntfs", ENV{mount_options}="$env{mount_options},utf8,gid=100,umask=002"
    # Mount the device
    ACTION=="add", RUN+="/bin/mkdir -p /media/%E{dir_name}", RUN+="/bin/mount -o $env{mount_options} /dev/%k /media/%E{dir_name}"
    # Clean up after removal
    ACTION=="remove", ENV{dir_name}!="", RUN+="/bin/umount -l /media/%E{dir_name}", RUN+="/bin/rmdir /media/%E{dir_name}"
    # Exit
    LABEL="media_by_label_auto_mount_end"
    Plenty of handy examples you can find in /lib/udev/rules.d/ and modify them so they meet you needs. I hope it clarifies the matter a bit.
    Last edited by bohoomil (2011-03-19 16:57:36)

  • [SOLVED] Borked systemd setup -- dbus errors during boot; can't login

    I have error messages very similar to this post. Unfortunately, as the author states, he never persisted in solving it but instead re-installed from scratch. I'd rather not do that.
    For reference, I have a pure systemd setup -- no rc.conf file, no initscripts package, etc.
    At boot I get the "Welcome to Arch!" messages followed by the various [OK] lines and then I get blindingly fast repeating lines about dbus not starting and attempting to restart it too quickly. If I walk away for about 1-2min, I finally see a login screen, but after entering my username/password, it just sits there and does nothing.
    As for suspects... I had systemd working fine.
    -- I updated some packages (not more than a few days worth and I'd have to check the list)
    -- I also took care of manual updates to some .pacnew files I periodically check for. In this group were some biggies: group, shadow, and passwd. I did recall the odd bit about uuidd changing from uid 995 to 68, but in reading about that since then, it doesn't seem to be a big deal.
    I've been booting in by appending
    systemd.unit=emergency.target
    to the kernel line, but my exploration hasn't been all that helpful. `journalctl since=date` reveals the errors, but I don't get much information about why dbus is having issues starting.
    emergency.target also doesn't seem to be that helpful since I can't do anything with a read-only system. I'd love some suggestions about what, specifically, to check for before I reboot from Windows back into Arch and record more careful notes, probably by jotting notes onto a flash drive. Any places to start? For reference, I've done:
    -- systemctl status dbus: lists as inactive (dead) and simply shows the errors I see at boot (failed to start)
    -- systemctl list-units
    -- systemctl list-unit-files
    -- journalctl and looking around for instances of fail or failed or dbus
    If I start systemd-logind.service or dbus.service, it displays a status message about running fsck and then takes me to a login prompt automatically. Then I can type in my username and password and then there's nothing after that. No prompt, just an apparent hang.
    Thanks for any suggestions -- I'll take them and then collect more detailed results and report back.
    Thanks!
    Last edited by jwhendy (2012-11-08 16:07:33)

    As I wondered, I think it's a problem with passwd. I don't have a dbus entry and must have missed it when I was copying things around between my version and the .pacnew. Downloading an install disc now since I can't seem to change it from the recovery console due to mounting root read-only.
    I'd love to know of a way to boot that avoids starting dbus and other things that might break while still having read/write access to root. Will mark solved once I update /etc/passwd and reboot.

  • RV180 (wired only) problems with firmware 1.0.4.14, fails to boot correctly + LAN ports power off during boot (downgrading to 1.0.3.10 = fine again).

    Hi All,
    A few months ago when 1.0.4.14 was released I was quick to update to this version from 1.0.3.10 but very quickly ran into issues.
    Bit of background info...  I am not doing anything complex with this box, basic IP4 network over all LAN ports, no VLANs, firewall enabled and allowing 2 port access rules to a static IP address.  Any static IPs are assigned manual at host level but all other devices receive DHCP IP addresses.  I don’t host VPN on this RV180 but I do with another.  Routing VPN has no issues. WAN is connected to another switch provided by my ISP who provides DHCP IP Address with their DNS etc.  Only LAN ports 1 and 2 are connected, port 1 to my Wireless AP (AP mode passing all requests to the RV180, DHCP etc.), port 2 connects to a 8 port Smart Switch (but all 'Smart' features are currently not in use, so basic switching only).  All other settings on the RV180 are on recommended defaults.
    Everything is working fine on 1.0.3.10 but I have all kinds of issues after updating to 1.0.4.14.  Here are the actions and experiences I had...
    1) Backup my RV180 config to txt file.
    2) Navigate to the firmware upgrade page and follow steps to complete the upgrade process from 1.0.3.10 to 1.0.4.14.  *router does the normal process of upgrading*
    3) RV180 reboots to complete but doesn’t come back up even after waiting 5-10 mins.   LAN ports enable during boot up (link lights on) but after about 2mins turn off (no link lights).  WAN light is on alongside the Power Light.
    4) Power cycle even with rest... Same results.
    5) Reset the RV180 to default settings.  I can sometimes get the unit to boot up and the LAN remains active and powered up.  The web UI is VERY slow compared with 1.0.3.10.  Internet sometimes works and sometimes doesn't (I would expect it all work without issue on default settings).
    6) I repeat this a few times, various resets, powered off waiting periods, etc. but I always have issues.  I did manage to get some log file information and the Kernel appears in the Alert, Error and also the Warning logs (please see attached files).
    7) I gave up at this point.  No major issues like this reported on the internet from a few google searches etc.  So I then reset to defaults (1.0.4.14), downgrade to 1.0.3.10 and finally reset to defaults again + restore backup config settings (with some manual changes).
    The router has remained like this and seem to be working fine, but I would like any security improvements from 1.0.4.14 firmware on my device.
    Anyone able to help, have the same issue or can advise me in any other ways?
    I see 1.0.3.10 isn’t displayed as a firmware download on the standard support page for the RV180 now.  Only 1.0.2.6 and 1.0.4.14.  Do I need to downgrade again to 1.0.2.6 before upgrading to the latest version?
    Regards,
    ~FAZ~

    Hi,
    I recently bought a RV180 router and immediately I encountered the same problem; practically I am not able to access the web GUI.
    The PC is directly connected to the router, nothing else is connected; the TCP/IP configuration is as follows:
    PC: 192.168.1.100
    RV180: 192.168.1.1
    GATEWAY: 192.168.1.1
    SUBNET MASK: 255.255.255.0
    Once the router is turned on, the power LED flashes fastly, the Ethernet LED is on but after few minutes it disappears and the PC detects a disconnection of the Ethernet cable.
    The router is not pingable and, as I said, the web interface is not reachable.
    I have tried to power cycle the router, to reset it (pressing the reset button for more than 3 second and for more than one minute), to access the rescue mode and download a new firmware through TFTP, but nothing worked.
    Few times, after many boot and reset trials,I was able to access the web interface and in one of these occasions I updated the firmware to 1.0.4.14 but once the router is powered off the problem arises again at the next power on.
    I have not tried yet to downgrade to an older firmware version.
    Can you suggest any solution? thank you.

  • Eth0 is being up and down for several time during boot

    My wicd doesn't connect to eth0 on the first attempt after boot up. It is configured to eth0 always have a higher priority to connect.
    My dmesg shows that eth0 being up and down for several time during boot. I have e1000e in my MODULES list.
    Here is my rc.conf
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
    # startup and during the boot process. If set to 'no', the C locale is used.
    # HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
    # in the hardware clock being left untouched (useful for virtualization)
    # Note: Using "localtime" is discouraged, using "" makes hwclock fall back
    # to the value in /var/lib/hwclock/adjfile
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # Note: if unset, the value in /etc/localtime is used unchanged
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.UTF-8"
    DAEMON_LOCALE="no"
    HARDWARECLOCK=""
    TIMEZONE="Asia/Hong_Kong"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
    # Replace every !module by an entry as on the following line in a file in
    # /etc/modprobe.d:
    # blacklist module
    # See "man modprobe.conf" for details.
    MOD_AUTOLOAD="yes"
    MODULES=(acpi-cpufreq fuse tp_smapi vboxdrv e1000e)
    # Udev settle timeout (default to 30)
    UDEV_TIMEOUT=30
    # Scan for FakeRAID (dmraid) Volumes at startup
    USEDMRAID="no"
    # Scan for BTRFS volumes at startup
    USEBTRFS="no"
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="antony-tp"
    # Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
    # Wired network setup
    # - interface: name of device (required)
    # - address: IP address (leave blank for DHCP)
    # - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
    # - broadcast: broadcast address (ignored for DHCP) (optional)
    # - gateway: default route (ignored for DHCP)
    # Static IP example
    # interface=eth0
    # address=192.168.0.2
    # netmask=255.255.255.0
    # broadcast=192.168.0.255
    # gateway=192.168.0.1
    # DHCP example
    # interface=eth0
    # address=
    # netmask=
    # gateway=
    # Setting this to "yes" will skip network shutdown.
    # This is required if your root device is on NFS.
    NETWORK_PERSIST="yes"
    # Enable these netcfg profiles at boot-up. These are useful if you happen to
    # need more advanced network features than the simple network service
    # supports, such as multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    # If something other takes care of your hardware clock (ntpd, dual-boot...)
    # you should disable 'hwclock' here.
    DAEMONS=(!hwclock syslog-ng dbus !network !dhcpcd rpcbind acpid @wicd nfs-common netfs @crond cups @laptop-mode @alsa @sensors ntpd @slim bluetooth)
    Here is a segment of my dmesg
    [ 2.759302] e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-k
    [ 2.759304] e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
    [ 2.759338] e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
    [ 2.759348] e1000e 0000:00:19.0: setting latency timer to 64
    [ 2.759467] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 2.766107] tpm_tis 00:0a: 1.2 TPM (device-id 0x0, rev-id 78)
    [ 2.766808] ACPI: AC Adapter [AC] (on-line)
    [ 2.776492] wmi: Mapper loaded
    [ 2.777212] mei: module is from the staging directory, the quality is unknown, you have been warned.
    [ 2.777781] thermal LNXTHERM:00: registered as thermal_zone0
    [ 2.777783] ACPI: Thermal Zone [THM0] (66 C)
    [ 2.778291] iTCO_vendor_support: vendor-support=0
    [ 2.780137] ACPI: Battery Slot [BAT0] (battery present)
    [ 2.780958] input: PC Speaker as /devices/platform/pcspkr/input/input4
    [ 2.781462] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
    [ 2.781547] iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
    [ 2.781919] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    [ 2.783139] cfg80211: Calling CRDA to update world regulatory domain
    [ 2.789182] [drm] Initialized drm 1.1.0 20060810
    [ 2.789538] hub 4-1:1.0: USB hub found
    [ 2.789616] hub 4-1:1.0: 8 ports detected
    [ 2.792925] Non-volatile memory driver v1.3
    [ 2.795877] thinkpad_acpi: ThinkPad ACPI Extras v0.24
    [ 2.795879] thinkpad_acpi: http://ibm-acpi.sf.net/
    [ 2.795881] thinkpad_acpi: ThinkPad BIOS 8DET54WW (1.24 ), EC unknown
    [ 2.795882] thinkpad_acpi: Lenovo ThinkPad X220, model 4290NL5
    [ 2.797236] thinkpad_acpi: detected a 8-level brightness capable ThinkPad
    [ 2.797352] thinkpad_acpi: radio switch found; radios are enabled
    [ 2.797466] thinkpad_acpi: possible tablet mode switch found; ThinkPad in laptop mode
    [ 2.799752] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
    [ 2.800067] Registered led device: tpacpi::thinklight
    [ 2.800091] Registered led device: tpacpi::power
    [ 2.800106] Registered led device: tpacpi::standby
    [ 2.800120] Registered led device: tpacpi::thinkvantage
    [ 2.800192] thinkpad_acpi: Standard ACPI backlight interface available, not loading native one
    [ 2.800254] thinkpad_acpi: Console audio control enabled, mode: monitor (read only)
    [ 2.801077] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input5
    [ 2.801162] sdhci: Secure Digital Host Controller Interface driver
    [ 2.801164] sdhci: Copyright(c) Pierre Ossman
    [ 2.801707] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
    [ 2.801709] Copyright(c) 2003-2011 Intel Corporation
    [ 2.801744] iwlwifi 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    [ 2.801753] iwlwifi 0000:03:00.0: setting latency timer to 64
    [ 2.801789] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
    [ 2.801791] iwlwifi 0000:03:00.0: pci_resource_base = ffffc90005abc000
    [ 2.801793] iwlwifi 0000:03:00.0: HW Revision ID = 0x34
    [ 2.801877] iwlwifi 0000:03:00.0: irq 49 for MSI/MSI-X
    [ 2.801913] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Advanced-N 6205 AGN, REV=0xB0
    [ 2.801962] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
    [ 2.802045] sdhci-pci 0000:0d:00.0: SDHCI controller found [1180:e822] (rev 7)
    [ 2.802067] sdhci-pci 0000:0d:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    [ 2.802107] sdhci-pci 0000:0d:00.0: setting latency timer to 64
    [ 2.802118] _regulator_get: 0000:0d:00.0 supply vmmc not found, using dummy regulator
    [ 2.802188] Registered led device: mmc0::
    [ 2.803329] mmc0: SDHCI controller on PCI [0000:0d:00.0] using DMA
    [ 2.815226] iwlwifi 0000:03:00.0: device EEPROM VER=0x715, CALIB=0x6
    [ 2.815229] iwlwifi 0000:03:00.0: Device SKU: 0X1f0
    [ 2.815231] iwlwifi 0000:03:00.0: Valid Tx ant: 0X3, Valid Rx ant: 0X3
    [ 2.815247] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
    [ 2.845674] iwlwifi 0000:03:00.0: loaded firmware version 17.168.5.3 build 42301
    [ 2.845820] Registered led device: phy0-led
    [ 2.850630] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
    [ 2.862431] usb 1-1.2: new low-speed USB device number 3 using ehci_hcd
    [ 2.943648] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) f0:de:f1:92:77:26
    [ 2.943651] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
    [ 2.943712] e1000e 0000:00:19.0: eth0: MAC: 10, PHY: 11, PBA No: 1000FF-0FF
    [ 2.943734] mei 0000:00:16.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    [ 2.943739] mei 0000:00:16.0: setting latency timer to 64
    [ 2.943817] mei 0000:00:16.0: irq 50 for MSI/MSI-X
    [ 2.944502] agpgart-intel 0000:00:00.0: Intel Sandybridge Chipset
    [ 2.945021] agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
    [ 2.946341] watchdog: INTCAMT: cannot register miscdev on minor=130 (err=-16).
    [ 2.946452] watchdog: error registering /dev/watchdog (err=-16).
    [ 2.946523] mei: unable to register watchdog device.
    [ 2.946598] agpgart-intel 0000:00:00.0: detected 65536K stolen memory
    [ 2.946692] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
    [ 2.946734] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
    [ 2.948359] snd_hda_intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
    [ 2.948422] snd_hda_intel 0000:00:1b.0: irq 51 for MSI/MSI-X
    [ 2.948444] snd_hda_intel 0000:00:1b.0: setting latency timer to 64
    [ 3.022245] usb 1-1.3: new full-speed USB device number 4 using ehci_hcd
    [ 3.172080] usb 1-1.4: new full-speed USB device number 5 using ehci_hcd
    [ 3.274597] Bluetooth: Core ver 2.16
    [ 3.274611] NET: Registered protocol family 31
    [ 3.274612] Bluetooth: HCI device and connection manager initialized
    [ 3.274614] Bluetooth: HCI socket layer initialized
    [ 3.274614] Bluetooth: L2CAP socket layer initialized
    [ 3.274618] Bluetooth: SCO socket layer initialized
    [ 3.275535] Bluetooth: Generic Bluetooth USB driver ver 0.6
    [ 3.276006] usbcore: registered new interface driver btusb
    [ 3.338454] usb 1-1.6: new high-speed USB device number 6 using ehci_hcd
    [ 3.444567] Linux media interface: v0.10
    [ 3.447387] Linux video capture interface: v2.00
    [ 3.448573] input: Logitech Trackball as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input6
    [ 3.448671] generic-usb 0003:046D:C404.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech Trackball] on usb-0000:00:1a.0-1.2/input0
    [ 3.448690] usbcore: registered new interface driver usbhid
    [ 3.448691] usbhid: USB HID core driver
    [ 3.449136] uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b217)
    [ 3.450945] input: Integrated Camera as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input7
    [ 3.450987] usbcore: registered new interface driver uvcvideo
    [ 3.450988] USB Video Class driver (1.1.1)
    [ 3.484049] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input8
    [ 3.491137] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0
    [ 3.491298] HDMI status: Codec=3 Pin=6 Presence_Detect=0 ELD_Valid=0
    [ 3.491486] HDMI status: Codec=3 Pin=7 Presence_Detect=0 ELD_Valid=0
    [ 3.491637] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
    [ 3.491709] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
    [ 3.491765] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
    [ 3.492050] i915 0000:00:02.0: power state changed by ACPI to D0
    [ 3.492053] i915 0000:00:02.0: power state changed by ACPI to D0
    [ 3.492059] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    [ 3.492062] i915 0000:00:02.0: setting latency timer to 64
    [ 3.538056] mtrr: no more MTRRs available
    [ 3.538058] [drm] MTRR allocation failed. Graphics performance may suffer.
    [ 3.538266] i915 0000:00:02.0: irq 52 for MSI/MSI-X
    [ 3.538270] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
    [ 3.538271] [drm] Driver supports precise vblank timestamp query.
    [ 3.538292] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
    [ 3.664501] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x940300/0x120c00
    [ 3.664518] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0
    [ 3.716317] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input12
    [ 4.407165] fbcon: inteldrmfb (fb0) is primary device
    [ 4.575259] Console: switching to colour frame buffer device 170x48
    [ 4.577042] fb0: inteldrmfb frame buffer device
    [ 4.577043] drm: registered panic notifier
    [ 4.607860] acpi device:01: registered as cooling_device4
    [ 4.607985] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input13
    [ 4.608039] ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
    [ 4.608122] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
    [ 4.757243] EXT4-fs (sda3): re-mounted. Opts: discard
    [ 4.765917] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: discard
    [ 4.776777] Adding 262140k swap on /dev/sda2. Priority:-1 extents:1 across:262140k SS
    [ 5.099467] NET: Registered protocol family 10
    [ 6.048650] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [ 6.098038] Bluetooth: RFCOMM TTY layer initialized
    [ 6.098055] Bluetooth: RFCOMM socket layer initialized
    [ 6.098057] Bluetooth: RFCOMM ver 1.11
    [ 6.278766] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
    [ 6.278893] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
    [ 6.568639] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
    [ 6.568775] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
    [ 6.684082] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 7.176563] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 7.226662] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 7.227110] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 10.229345] IBM TrackPoint firmware: 0x0e, buttons: 3/3
    [ 10.490618] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input14
    [ 10.817814] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [ 10.819315] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 11.186166] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
    [ 11.186292] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
    [ 11.313367] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 11.665342] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 11.717591] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 11.718042] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 11.964795] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 12.017213] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
    [ 12.017720] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 13.811264] EXT4-fs (sda3): re-mounted. Opts: discard,commit=0
    [ 13.826031] EXT4-fs (sda4): re-mounted. Opts: discard,commit=0
    [ 15.178905] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
    [ 15.180472] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 25.663056] eth0: no IPv6 routers present
    Any hint for tracing the root of this problem? Thank you very much!

    Hi ...
    If you have moved the Safari application from the Applications folder, move it back.
    As far as the cache goes, there's a work around for that when you can't empty the Safari cache from the menu bar.
    Go to    ~/Library/Caches/com.aple.Safari.Cache.db.  Move the Cache.db file to the Trash.
    Try Safari.
    Mac OS X (10.7.2)   <  from your profile
    If that is corrrect, you need to update your system software. Click your Apple menu icon top left in your screen. From the drop down menu click Software
    Update ...
    ~ (Tilde) character represents the Home folder.
    For Lion v10.7x:  To find the Home folder in OS X Lion, open the Finder, hold the Option key, and choose Go > Library

  • Read-Only Problem during Boot

    Hi,
    I tried to update my system today, like every week, with the standard command pacman -Syu. After installing all updates, my window manager (gnome3) crashed and i tried to restart my System. After the grub window appeared and I choosed my kernel the normal startup commands are shown until the Arch prompt appeared. The one where Arch Linux tried to start all relevant processes. After that there are only mistakes. All startup processes are busy or failing. The only message i get is, that the filesystem, i think thats the root partition (ext4), is read-only or another error: some files for startup cannot be created because they already exist.
    Getting to console is also impossible, because the system tries to start virtualbox additions, with an funny message, that it is busy and tries it again in 5 min (infinity loop). But shidt happens. I have read in another post that I can try another Linux System, mount my root partition and  do an
    fsck /dev/sda3 -p or -f
    . But it says that all is clean (sda3 is root and sda1 is /boot). The filesystem is ext4, so i tried also fsck.ext4, but it also say all is clean.
    After another boot i stoped at the position, where the fist error occur.
    Mounting Local Filesystems
    /etc/rc.sysinit: line 285: /etc/mtab: Read-only file System
    next one:
    Activating Swap
    /bin/rm: cannot remove '/etc/localtime': Read-only file system
    removing leftover Files
    /usr/bin/find: cannot delete 'var/run/cups.pid': Read-only file system
    After that message there are also al lot of analog errors.
    I have no other idea than an dirty filesystem. Is there another possibility to rescue my system without an fresh install. Im sorry but i cannot log any messages at that state of boot. So it is not easy to get better informations about special error codes.
    I have forget to give you some informations about my stats:
    - actual stable arch kernel 2.6.38
    - gnome 3
    - thinkpad t400
    Last edited by Psikon (2011-05-13 20:18:12)

    With udev 168-1 I obtain this message during boot:
    :: checking filesystems
    fsck.ext4: no such file or directory while trying to open /dev/sda6 (my root device)
    Possibly non-existent device?
    ***************** FILESYSTEM CHECK FAILED ****************
    * Please repair manually and reboot. Note that the root *
    * file system is currently mounted read-only. To remount *
    * it read-write type: mount -n -o remount,rw / *
    * When you exit the maintenance shell the system will *
    * reboot automatically. *
    but fsck run manually says it's all clean.
    I have to remount rw / partition and manually mount all the other partition, then I can switch to runlevel 3.
    With udev 167-2 (and prior) I can boot without any problems.
    I'm not sure it's a problem from udev, but downgrading it works for me.

  • "F11 System Recovery" during boot does not work after Cloning hard drive.

    Problem: “F11 System Recovery” during boot does not work after Cloning hard drive.
    HP Envy m6-1125dx UEFI Notebook Computer with GPT hard drive.
    Original Seagate Hard Disk GPT 700GB with Window 8.0_64 upgraded to Windows 8.1_64
    Startup Menu (F11 System Menu works properly) only on original hard drive.
    Following obtained from Disk Management & diskpart in Command Prompt.
                                     GPT Disk <700GB>
    Partition 1 WINRE NTFS Primary 235MB/400MB [Recovery]
    Partition 2 EFI System FAT32 (LBA) Primary 108MB/260MB [System]
    Partition 3 (NONE) Unformatted Primary 128MB/128MB [Reserve]
    Partition 4 Main NTFS Primary 90GB/195GB [Primary “C”]
    Partition 5 (NONE) NTFS Primary 372MB/450MB [Recovery]
    Partition 6 Data NTFS Primary 7GB/475GB [Primary “E”]
    Partition 7 NTFS Primary 26MB/350MB [Recovery]
    Partition 8 Recovery NTFS Primary 24GB/26GB [Recovery “D”]
    I have Cloned the original hard drive to a new HGST 1TB Hard Drive using four different methods (sector by sector):
    Acronis True Image 2015
    Acronis Backup for PC
    AOMEI Backupper Professional
    Macrium Reflect
    Each time the cloning process completes successfully and has the same original partition arrangement. The computer works properly except when trying to use the “F11 System Menu” key during boot. It gives the following error message:
    “Recovery
    Your PC needs to be repaired
    A required device isn’t connected or can’t be accessed.
    Error code: 0xc0000225
    You need to use the recovery tools on your installation media. If you don’t have any installation media (like a disc or USB device), contact your system administrator or PC manufacturer. “
    Any suggestions why the F11 System Recovery does not work during boot and how to fix the problem would be appreciated. I have does various disk checking and file checking on both the original and new hard drive with no errors.
    Thank you in advanced.

    Hi,
    How did you clone the HDD ? One-for-one or different method ?
    Regards.
    BH
    **Click the KUDOS thumb up on the left to say 'Thanks'**
    Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

Maybe you are looking for