My Arch won't boot anymore something about bad blocks

It was working fine. I booted it up this morning said it found some bad blocks on some of my Linux partitions. How do I scan the surface of my drives with Archlinux.?. Is that even possible with Linux?. This is my USB drive that has the bad blocks.

Quicken2k wrote:Boot with ro 1?. I'm new to Arch and need a bit more info. Are you telling me to boot up in read only mode?. How?.
No worries! Simply, boot your computer and when you get to GRUB, select your Arch install and hit 'e'. Now you can edit the 'kernel' line. Append 1 (one) to the end of the line. Hit enter again, and hit 'b' to boot into single user mode. Now you can login as root, and perform whatever fsck's and debugging. Be sure to report back.

Similar Messages

Arch won't boot anymore

Hello again
I've spent the last few days familiarizing myself with arch and setting up my system. Now I've encountered a problem I can't get rid off myself: After selecting arch from grub, pretty much nothing happens. All I see is the following output:
- image - (I'm sorry I can't seem to be able to keep the image rotated in a readable way...)
However, those lines, along with a few more have always appeared. But now I'm stuck there, the only keys that I've found to work are Ctrl+Alt+Delete.
I don't know what caused the problem but I've undone the last few things I changed. I reverted fstab back to the state it was after generating it during the installation. I removed the last few installed packages up to virtualbox. I'd rather not remove virtualbox because it's already set up and I rebooted successfully a few times after installing it. I also removed the two nouveau packages (xf86-video-nouveau and nouveau-dri) because they are named there. Using the fallback option in grub leads to the same result.
Can anyone offer some sort of direction what could cause this?

ackalker wrote:That means the system isn't in a total freeze. If you're lucky, there may even be some information logged which can help you.
Yeah that's true. The cursor is blinking as well.
ackalker wrote:There may be indications there of something that went wrong. Good luck :-)
Well I found that log and had a look. What I saw first is that the timestamp of the entries don't match. The entry I just created shows up as being 2 hrs later than it actually is. At some point in the log it says "Time has been changed" and the timestamp matches.
I took note of all the red entries:
"Failed to find module 'vboxdrv'" -> I removed virtualbox but this looks like it's attempting to load some component of that
"Failed to start Load Kernel Modules" -> That doesn't sound good. This line only appears on recent entries though, most likely after I tried downgrading the Kernel, as barko suggested. When I manually installed a kernel version it was 3.8.3-2 which shows up correctly in the log ("kernel: Linux version 3.8.3-2-ARCH (tobias@T-POWA-LX) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Sun Mar 17 13:04:22 CET 2013").
"GLib-GObject-CRITICAL: g_object_ref: assertion `object->ref_count > 0' failed" and "GLib-GObject-CRITICAL: g_object_unref: assertion `object->ref_count > 0' failed" -> these 2 lines appear in succession and 6 times (each)
"host name not found: de.pool.ntp.org" -> IIRC that's my mirror. This appears twice, just after internet connection is established (I'm connected via ethernet).
"watchdog watchdog0: watchdog did not stop" -> this appears after shutting down.
I have the complete log, should I upload the part of the log about this 1 session? If yes, how best to upload it?

Re: Satellite C850 won't boot anymore - broken HDD

Hello Folks,
I bought a *Toshiba Satellite C850 - 1F2* with *+Windows 8+*.
After installing, upgrading to *+Windows 8.1+* and setting up everything, the whole machine worked pretty fine.
BUT since yesterday the laptop won't boot anymore!
When I turn it on, the HDD makes click and click and the system tries to boot from DVD, from USB, from HDD, from IPV4, from IPV6 and then it says, that there is no bootable device.
Unfortunately I wanted to make the +Windows 8 Restoration-/Rescue-DVDs+ this weekend!
Huh!!!
Well, I still have an *+original Windows-7-DVD and license+*, which would be good as well (I used it the last years).
*YET*, I cannot install *+Windows 7+*.
It says something like that, that +this system is not available for Secure Boot+.
I read about "Secure Boot".
So I pressed F2, turned the laptop on and could with this reach the BIOS.
It is a *+InsydeH20 Rev. 3.7+*.
*BUT*, when I go to "Boot Mode" I can only see, that this option is greyed and I cannot change from +UEFI Boot+ to +CSM Boot+.
Even the change of the HDD made no difference.
I put in my old HDD with Windows 7 installed (wich works in the other laptop), but the system won't boot, for it is +not suitable for Secure Boot+.
*So, WHAT NOW?*
I mean, it cannot really be the Toshiba politics, that you need to throw away your laptop, if the HDD breaks, can it?
For I didn't create the Rescue-DVD, I have just my Windows 7 DVD and another HDD with installed Windows 7.
Do I need to buy another Windows 8 licence and another HDD, to install Windows 8 (suitable for Secure Boot) again?
Would it even work like that?
Or is there any chance to upgrade the BIOS, for that I can then change from UEFI Boot to CSM Boot?
Or is there any other chance, to use my other HDD with Windows 7, or at least a new clean HDD, on wich I then can install my Windows 7 OS?
I hope, that someone can give me any good advice, what to do now ... without throwing the Toshiba laptop away ;)
Thanks in advance!

If the HDD died, in needs to be replaced.
If notebook is still covered by warranty, the HDD will be replaced free of charge. If warranty isnt valid, you will need to pay for the new HDD.
I think this understandable.
_Now some facts about the Recovery disk._
If you did not create a recovery disk in the past, you could order the recovery medium on this page: http://backupmedia.toshiba.eu/landing.aspx
The recovery disk would install the Toshiba image and would set the notebook back to the same state like at the first day of purchase.
_Regarding the Win 7 installation:_
Usually to install the non UEFI capable system, the secure boot needs to be disabled and boot mode needs to be set to CSM mode.
If this isnt possible you should update the BIOS but to do that you need an running Windows system (Win 8).

Won't boot anymore but in safe mode

My laptop won't boot anymore. I get a gray screen with a prohibition sign. Here's what I found so far:
If I boot in the verbose mode it gets stuck on something like Looking for boot device.
I zapped the PRAM. Didn't help.
I can boot in safe mode.
I used Disk Utility to check the drive and permisions. Everything ok.
I can't boot from the original Snow Leopard DVD. I press C, the drive spins then stops.
I reinstalled Snow Leopard from the safe mode. Didn't help.
In safe mode Safari is crazy slow. Firefox runs full speed.
Any idea?

Reinstall OS X without erasing the drive
Do the following:
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install the Combo Updater for the version you prefer from support.apple.com/downloads/.
Unless you can boot from your installer DVD there's nothing you can do to reinstall OS X, so I'm not sure how you did reinstall as you said.
Booting From An OS X Installer Disc
1. Insert OS X Installer Disc into the optical drive.
2. Restart the computer.
3. Immediately after the chime press and hold down the "C" key.
4. Release the key when the spinning gear below the dark gray Apple logo appears.
5. Wait for installer to finish loading.

[SOLVED] Arch won't boot after I created a separate /var parition

Arch won't boot after I created a separate /var parition on an existing installation.And let me confess: it was maybe stupid trying to do it on an existing install.
I edited the fstab correctly, copied the files using rsync preserving permissions. Then I kept a backup of /var using tar. Then went on to delete everything under /var, ie /var/*, the /var folder is still there. All this I did from a live CD. After that I booted into my arch linux. Here I get messages about systemd successfully finishing fsck on each of my partitions, then the screen starts blinking. And there is no more output. Pressing Ctrl+Alt+Delete causes systemd to stop its services and reboot.
Having realized I had borked my system, I removed the /var line from fstab and restored /var from the tar file I made earlier. Again I did this from a live cd. Rebooted into my arch system, and again similar issues, namely that after fsck and messages informing a few services had started, the screen keeps blinking.
The live cd I used for reorganizing my partitions was elementary OS freya. They have GParted in there. I also have an arch install iso lying aroung from May 2013. If necessary, I can download the latest version. I am currently typing from a Windows installation I dual boot from.
I don't know how to extract any boot logs as I am locked out of the system. Here is my fstab in any case:
# Filesystem information
# /dev/sda5 LABEL=fs_root
UUID=b9d739cf-fd8c-46dd-a919-bd827dc47c66 / ext4 rw,noatime,data=ordered 0 1
# /dev/sda9 LABEL=fs_var
UUID=ec0f7a49-dccd-43ab-8651-9aa3fdb41cc7 /var ext4 rw,noatime,data=ordered 0 2
# /dev/sda2 LABEL=fs_boot
UUID=0e8ab31a-3bda-4b85-a901-a36f21b1583d /boot ext2 rw,noatime 0 2
# /dev/sda6 LABEL=fs_home
UUID=d9e63c47-274e-447f-ad01-0d97afe0fd34 /home ext4 rw,noatime,data=ordered 0 2
# /dev/sda7 LABEL=fs_swap
UUID=7301227c-e9f3-41b8-9d0f-4cf3c159491c none swap defaults 0 0
# /dev/sda3 LABEL=fs_win
UUID=12B639D1B639B5D7 /fs_win ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,nofail,noauto,x-systemd.automount 0 0
# /dev/sda3 LABEL=fs_share
UUID=D272269772268079 /fs_share ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,noauto,nofail,x-systemd.automount 0 0
I would greatly appreciate any help.
Last edited by richcocoa (2015-05-03 18:04:44)

Have you moved everything from /var to /new_var (i named it for learning purpose)? You shoud copy content from /var but not on the fly but booting from arch iso cd, and than you shoud mount your / into arch-chroot environement, mount all of your mount points and than copy content from default /var to new /var. The copying should be done with this
cp -rax
and you can add -v switch to verbose output. I have my own /var moved the same way.
The simples way is:
-boot the arch iso cd
-mount all of your mount point (i created here in this step /new_var to move /var to a new place, and this /new_var i put in /etc/fstab as /var later)
-copy /var to /new_var with -rax or -vrax (recursive, archive, this filesystem or verbose, recursive, archive, this filesystem switches)
-umount all of it
-reboot.
Last edited by firekage (2015-05-02 07:49:20)

Powermac G5 1.8Ghz June 2004 won't boot anymore

Hi all,
Past week i've bought a second hand PM G5. At first it seems to be all ok, but right now its not working anymore.
I've managed to install the OSX on the first evening i've had the PM G5. After installing evrything seemed to be fine. But after 30 minutes surfing on the internet, it froze. I had to give it an hard reset by holding down the power button.
After turning it of, it won't boot anymore. after a few times trying with 10 secconds between it, i unpluged the powercabel for 2 minutes. Wile turning it on after 2 minutes, it was booting , but it stopped booting after 1,5 minute and froze.. after hard resetting it, i've managed to boot it right. The OS seemed to be ok again, but after 5 till 10 minutes it froze again.
Right now it won't boot anymore... it starts (without the front light, this light only blinks fast once i turn it on, but after that no more. Sometimes it won''t even flash.
I've been buzzy replacing some components to get to know if it was a hardware fail. I've first replaced the PSU with two other PSU's from the PM G5, but won't do a thing.
The i've replaced the memory with 4 kind of difrent pairs, but won't do a thing either. At last i replaced the Logic Board, this won't even do a thing about it.
Of course i replaced the PRAM battery first, but also this won't help me.
I've tested it in AHT, but evrything was working well, according to AHT. I've managed to get the system log, but nothing scarry though here also, only some 122 errors some times. (download the system log here: http://www.mijnbestand.nl/Bestand-F4DDN66WLRCI.log )
I've reset al things possible like PRAM reset, PMU reset. Nothing seem to be working.
What can i do next to get this thing work?? I'm getting nut's here..
Please help..
Thanks a Lot
MArtijn Snoek

Hi martijnsnoek, and a warm welcome to the forums!
Can you count the beeps or flashes?
1 beep = no RAM installed
2 beeps = incompatible RAM types
3 beeps = no good banks
4 beeps = no good boot images in the boot ROM (and/or bad sys config block)
5 beeps = processor is not usable
In addition to the beeps, on some computers the power LED will flash a corresponding number of times plus one. The LED will repeat the sequence after approximately a 5-second pause. The tones are only played once.
Note: In this case, a flash is considered to be 1/4 second or 250 ms or greater in length.
http://support.apple.com/kb/HT1547
So, with the info you given, two things come to mind...
Bad solder joints around the RAM slots, try heating that area with a Hair Dryer for 3 to 5 minutes, then see if it starts.
If you can get it running, Get Temperature Monitor to see if it's heat related...
http://www.macupdate.com/info.php/id/12381/temperature-monitor
And/or iStat Pro...
http://www.islayer.com/apps/istatpro/
If you have any temps in the 70°C/160°F range, that's likely it.
BTW, have you blown the dust out of it since you got it?

Won't boot anymore after nvidia-xconfig

Hey Guys,
Got a problem with my Arch Linux here, hope you can help.
Today I tried to install the official Nvidia Driver and BumbleBee following along the great Wiki on this topic.
Everything worked just fine and I also could run optirun gfxgear or somemthing like this.
I wanted to switch to the Nvidia Settings in the settings menu and it told me to configure my xconfig and restart x so I typed nvidia-xconfig in the terminal and it gave me an success output.
I restarted my system and now it hangs on the graphical thing I think. It won't boot anymore.
Hope you can help me out.
Thanks alot
Edit: My Nvidia Card is a Nvidia GT 740M if this matters
Last edited by Whitz (2015-02-09 11:02:41)

No, I have a laptop with 2 graphic cards an intel hd4000 and a nvidia gt 740m.
I ran the Arch Linux installation well until I tried to get the nvidia gt working with bumblebee.
I followed the wiki of the bumblebee topic and it worked well. I wanted to switch into the nvidia settings and it told me my x isnt configured properly and I should type nvidia-xconfig and restart X.
After the restart it won't boot to the graphical interface anymore.
Hope this cleared up the things
Also I dont get any errors but it just wont load..
Last edited by Whitz (2015-02-09 12:08:49)

Btrfs: System won't boot anymore after unclean shutdown

Hi,
I have a problem with my ArchLinux (kernel 3.19.2-1-ARCH).
I have my root partition as BTRFS and no /boot partition.
After an unclean shutdown the system won't boot anymore.
GRUB loads the kernel and the kernel starts but it hangs saying: Mounted /dev/sda3 on real root.
Then, I have to start a Live CD and do:
btrfsck /dev/sda3
After that the system boots correctly.
I've tried adding fsck to the HOOKS in the mkinitcpio.conf file and in fact it tries to fsck the filesystem (but with BTRFS, fsck.btrfs doesn't work...)
What can I do?
Thanks

I'm also having this problem. I tried booting up the netinstall image to debug it, but I can't mount my btrfs volume from there either: mount just hangs. After a while, the kernel goes:
[...] INFO: task mount:612 blocked for more than 120 seconds.
[...] Not tainted 3.19.2-1-ARCH #1
[...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[...] INFO: task btrfs-transacti:636 blocked for more than 120 seconds.
[...] Not tainted 3.19.2-1-ARCH #1
[...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
From this post I guessed that I might just need to wait so that I could defrag the volume once it was mounted, but it's been hanging for over 15min now (the message above continues to come up periodically).
Like the OP in the thread I linked to above, my btrfs volume is inside an LVM volume (which is on dm-crypt). Don't know whether that's relevant.
Output of btrfs-check:
Checking filesystem on /dev/pixie/btrfs
UUID: e04cc661-e31a-4dbf-870d-664bc913e34a
found 76855677062 bytes used err is 1
total csum bytes: 72928436
total tree bytes: 2092515328
total fs tree bytes: 1888452608
total extent tree bytes: 104644608
btree space waste bytes: 357251032
file data blocks allocated: 181197139968
referenced 109440282624
btrfs-progs v3.19
dmesg output:
[ 36.824998] Btrfs loaded
[ 36.826713] BTRFS: device fsid e04cc661-e31a-4dbf-870d-664bc913e34a devid 1 transid 98618 /dev/dm-3
[ 46.219014] BTRFS info (device dm-3): disk space caching is enabled
[ 46.259830] BTRFS: detected SSD devices, enabling SSD mode
[ 240.333313] INFO: task mount:539 blocked for more than 120 seconds.
[ 240.335542] Not tainted 3.19.2-1-ARCH #1
[ 240.337795] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 240.340263] mount D ffff8800cf2837f8 0 539 453 0x00000000
[ 240.340277] ffff8800cf2837f8 ffff8800cf2331b0 0000000000013f00 ffff8800cf283fd8
[ 240.340286] 0000000000013f00 ffffffff81818540 ffff8800cf2331b0 ffff8802094f67a8
[ 240.340291] 0000000000000004 ffff8800cf283758 ffffffffa0a2fc91 ffff8802094f67a8
[ 240.340298] Call Trace:
[ 240.340335] [<ffffffffa0a2fc91>] ? set_extent_buffer_dirty+0x71/0xc0 [btrfs]
[ 240.340357] [<ffffffffa0a05796>] ? btrfs_buffer_uptodate+0x56/0x80 [btrfs]
[ 240.340366] [<ffffffff8155e999>] schedule+0x29/0x70
[ 240.340389] [<ffffffffa0a47745>] btrfs_tree_lock+0x65/0x200 [btrfs]
[ 240.340396] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
[ 240.340410] [<ffffffffa09e5cd9>] btrfs_search_slot+0x799/0xaa0 [btrfs]
[ 240.340425] [<ffffffffa09e79f5>] btrfs_insert_empty_items+0x75/0xd0 [btrfs]
[ 240.340446] [<ffffffffa0a47a37>] btrfs_insert_orphan_item+0x67/0xa0 [btrfs]
[ 240.340465] [<ffffffffa0a4a12e>] insert_orphan_item+0x5e/0x90 [btrfs]
[ 240.340482] [<ffffffffa0a4c531>] replay_one_buffer+0x361/0x380 [btrfs]
[ 240.340504] [<ffffffffa0a2f244>] ? alloc_extent_buffer+0x34/0x370 [btrfs]
[ 240.340523] [<ffffffffa0a488f3>] walk_down_log_tree+0x1d3/0x410 [btrfs]
[ 240.340540] [<ffffffffa0a48bfb>] walk_log_tree+0xcb/0x1d0 [btrfs]
[ 240.340558] [<ffffffffa0a507f7>] btrfs_recover_log_trees+0x1e7/0x490 [btrfs]
[ 240.340575] [<ffffffffa0a4c1d0>] ? replay_one_dir_item+0xf0/0xf0 [btrfs]
[ 240.340596] [<ffffffffa0a08b3e>] open_ctree+0x17ae/0x2030 [btrfs]
[ 240.340609] [<ffffffffa09dd633>] btrfs_mount+0x843/0x920 [btrfs]
[ 240.340618] [<ffffffff8117b7aa>] ? pcpu_alloc+0x35a/0x680
[ 240.340628] [<ffffffff811d5d68>] mount_fs+0x38/0x1c0
[ 240.340634] [<ffffffff8117bb05>] ? __alloc_percpu+0x15/0x20
[ 240.340641] [<ffffffff811f116b>] vfs_kern_mount+0x6b/0x120
[ 240.340647] [<ffffffff811f4184>] do_mount+0x224/0xb40
[ 240.340653] [<ffffffff811f4dae>] SyS_mount+0x7e/0xe0
[ 240.340661] [<ffffffff81562809>] system_call_fastpath+0x12/0x17
[ 240.340671] INFO: task btrfs-transacti:561 blocked for more than 120 seconds.
[ 240.342927] Not tainted 3.19.2-1-ARCH #1
[ 240.345175] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 240.348473] btrfs-transacti D ffff88020b88bd98 0 561 2 0x00000000
[ 240.348483] ffff88020b88bd98 ffff880211edc590 0000000000013f00 ffff88020b88bfd8
[ 240.348491] 0000000000013f00 ffff8802162289f0 ffff880211edc590 ffff8802094a70c8
[ 240.348496] ffff8802094d8000 ffff880200000000 ffff8802094d8000 ffff880200000033
[ 240.348501] Call Trace:
[ 240.348511] [<ffffffff811b5d1a>] ? kmem_cache_alloc+0x16a/0x180
[ 240.348525] [<ffffffffa09e07ca>] ? btrfs_free_path+0x2a/0x40 [btrfs]
[ 240.348543] [<ffffffffa0a64213>] ? __btrfs_run_delayed_items+0xf3/0x1d0 [btrfs]
[ 240.348550] [<ffffffff8155e999>] schedule+0x29/0x70
[ 240.348568] [<ffffffffa0a0b555>] btrfs_commit_transaction+0x2a5/0xbe0 [btrfs]
[ 240.348573] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
[ 240.348590] [<ffffffffa0a06fc5>] transaction_kthread+0x1d5/0x240 [btrfs]
[ 240.348605] [<ffffffffa0a06df0>] ? btrfs_cleanup_transaction+0x5a0/0x5a0 [btrfs]
[ 240.348611] [<ffffffff81091748>] kthread+0xd8/0xf0
[ 240.348617] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
[ 240.348624] [<ffffffff81562758>] ret_from_fork+0x58/0x90
[ 240.348629] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
Last edited by ouroboros8 (2015-04-02 12:37:25)

Mac mini won't boot anymore

My Mac mini won't boot anymore. It's been running fine for months.
It's running Leopard Server 10.5.2 Build 9C31
It starts to boot, I get the first spinning gear with the gray screen, then the blue desktop blinks, then a second spinning gear on a gray screen and it appears to hang (the gear stops spinning).
I booted off the install DVD, ran disk utility, repaired the HD, repaired the permissions: the behavior is the same.
Safe mode doesn't work (same hang as above).
Single user mode does work.
I can connect to it via Server Admin while it appears hung.
The last few lines of the system log are:
May 15 18:38:58 server emond[67]: SetUpLogs: uid = 0 gid = 0
May 15 18:38:58 server emond[67]: SetUpLogs: opening /Library/Logs/EventMonitor/EventMonitor.error.log
May 15 18:38:59 server kextd[23]: writing kernel link data to /var/run/mach.sym
May 15 18:39:09 server KernelEventAgent[59]: tid 00000000 received unknown event (12)
May 15 18:39:20 server kernel[0]: display: Not usable
May 15 18:39:20 server com.apple.KerberosAutoConfig[126]: Kerberos configuration is up to date
May 15 18:39:20 server com.apple.ATSServer[125]: FODBCheck: New annex file created
May 15 18:39:21 server ARDAgent [130]: ******ARDAgent Launched******
May 15 18:39:21 server com.apple.KerberosAutoConfig[132]: Kerberos configuration is up to date
May 15 18:39:22 server ARDAgent [130]: call logout from LoginLogoutProxyCallBackFunction
May 15 18:39:22 server com.apple.launchd[1] (com.apple.RemoteDesktop.agent): Throttling respawn: Will start in 9 seconds
May 15 18:39:24 server loginwindow[58]: Login Window Started Security Agent
May 15 18:39:29 server servermgrd[53]: servermgr_calendar: created default calendar virtual host
May 15 18:39:31 server ARDAgent [146]: ******ARDAgent Launched******
May 15 18:39:32 server ARDAgent [146]: ******ARDAgent Ready******
May 15 18:39:33 server mdworker[109]: (Error) SyncInfo: Boot-cache avoidance timed out!
May 15 18:39:54 server Python[47]: CGImageSourceCreateWithData data parameter is nil
May 15 18:39:54 server com.apple.wikid[47]: Thu May 15 18:39:54 server.jeff.carpenter.name Python[47] <Error>: CGImageSourceCreateWithData data parameter is nil\n
May 15 18:39:56 server kernel[0]: AppleYukon2 - bad packet received. length: 1440, packet status bits: MII error
May 15 18:39:56 server kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
May 15 18:49:54 server kernel[0]: serialnumberd 194 FSWRITEDATA SBF /dev/dtracehelper 13 (seatbelt)
May 15 18:49:54 server kernel[0]: serialnumberd 194 FSREADDATA SBF /dev/autofs_nowait 13 (seatbelt)
May 15 18:49:54 server kernel[0]: serialnumberd 194 FSREADDATA SBF /usr/sbin 13 (seatbelt)
May 15 18:55:12 server kernel[0]: AppleYukon2 - bad packet received. length: 23, packet status bits: MII error
Any ideas?

Yes, it's been running Server since I purchased it.
I doubt the serial number is in use elsewhere: I purchased the 10-user version at a retail store in a sealed package and I've only installed it once.

TS3212 itunes won't download because something about "mobile device not authorized?"

itunes won't download because something about "mobile device not authorized?"

Hi buckirich,
Thanks for using Apple Support Communities. It sounds like you may need to restart the Apple Mobile Device Service. This article has instructions for doing this:
How to restart the Apple Mobile Device Service (AMDS) on Windows
http://support.apple.com/kb/ts1567
If that doesn't resolve the issue, I would recommend trying a thorough uninstall and reinstall of iTunes as described here:
Removing and reinstalling iTunes and other software components for Windows Vista, Windows 7, or Windows 8
http://support.apple.com/kb/HT1923
Cheers,
- Ari

Satellite L40 18P won't boot anymore

Hello folks,
my Satellite L40 18P won't boot anymore. All I get is the Power LED to go green. The DVD ROM drive blinks and I can open and close it - but that's it. Nothing else happens.
Any idea in the forum what I can do to get the notebook boot again ? Or please ask questions for additional details.
many thanks, Johi 13

Hi,
wow, that was fast.
No, I can't see anything - the screen stays black. I do not hear the HDD start, neither do I hear the fan.
This behavior appeard for the first time yesterday evening.
Last activity was (if I remember correctly) closing the lid and sending the notebook to standby.
So far, I haven't tested it with an external monitor.
thanks, Johi13

SRW248G4P switch won't boot anymore

I have a Linksys Cisco Small Business switch model SRW248G4P which won't boot anymore. This is what I see with Putty when it boots (console interface):
Image Loader 1.0.1
Loading Diagnostic Image File : SRW224G4P_SRW248G4P_boot.bix
Diagnostic 1.0.1
in
The boot file seems to be the problem.
Does anyone have a solution for this problem? Some kind of hardware reset?
Kind regards
(I know it is not officially supported anymore, but I am still looking for some help)

Hi Aleksandra,
Thank you for your reply. By pressing Crtl+u rapidly while booting I managed to get in the download/xmodem menu.
Output:
Image Loader 1.0.1
File Name                         S/Up Type Size       Create Time
$logfile_1                          0    3         64 1193046:28:15
Factory_Default_Config.cfg          0    5        354 24:01:02
SRW224G4P_SRW248G4P_boot.bix        1    1    1377600 00:01:03
SRW224G4P_SRW248G4P_image.bix       1    2    3517532 00:03:42
certificate                         0    8      18040 24:00:55
startup-config                      1    5       5596 25:40:57
startup1.cfg                        0    5       5537 24:01:14
Free Space : 2097152
[X]modem Download [D]elete File [S]et Startup File
[Q]uit
Select>
Which image should I send to the switch?
The image provided by the official support page:
http://software.cisco.com/download/type.html?mdfid=282414078&flowid=3659
(version 1.0.2 or version 1.3.1)
Or the image referred to by vasukris (Moorthy) (above) (version 1.2.3 or version 1.2.2b)
Considering the advice of Tom Watts
( https://supportforums.cisco.com/discussion/11733231/srw248g4p-loader-binary-checksum-error-runtime-loading-fail-system-halt )
"1.2.2a is 1.0.6 boot code.
1.2.2b is 1.0.1 boot code.
1.2.3.0 is 1.0.2 boot code
It looks like you're using 1.0.1 boot code so the 1.2.2b firmware should be for you."
Thank you in advance!

Intel D2700DC + Arch won't boot without display

I've faced really wierd (to me) problem running Arch as mini webserver on the Intel D2700DC mini-ITX board with Atom D2700 integrated and NM10 Express chipset.
I successfully installed the system, configured network and started sshd to continue setting up other services remotely via ssh console. Then I disconnected the keyboard and display from the case and put it under the table. After that I was quiet surprised that the system was not starting up anymore.
After some investigation I've found that the system is not booting if no display is attached to the DVI port of the motherboard. If I start the system with display disconnected, I can hear one beep that notifies about successful BIOS POST, HDD led blinks 2-3 times, and then just nothing happens. System isn't booting up. If I attach the display right after that - nothing is seen on the screen, and display is immediately falling into sleep mode. Keyboard is still active though, and if I press ctrl+alt+del - the system is restarting, and, if display was just connected, it boots ok then. Also it boots fine from the cold state if the display was attached to the DVI port at the time of powering on.
As I can assume from the timings and HDD led blinking, the boot process stops right after GRUB is loaded. There's nothing in system log, cause it seems that boot hangs just before the kernel is loaded by GRUB. I'm really stuck and don't know how to work around this situation, because if the display was disconnected when system was powered on - then there's no way to see anything on the screen until next reboot, and if the display was connected - then the system boots OK.
One more thing to notice:
There was an old CentOS installation on the HDD, to which I installed Arch Linux. I've tried to boot it once or twice before installing Arch, and, as I could remember, it could boot up without display connected, on the very same hardware. So I suppose it's definitely something in Arch that is preventing the system to boot without the display.
I guess that when no display is connected at boot time, NM10 chipset completely disables onboard video, and because of this we can't see anything on the display until the system is restarted. But this somehow affects Arch, so it can't boot without any video hardware present.
Last edited by rand256 (2012-05-10 10:23:28)

I'm afraid there's no such option, but it looks like arch isn't booting just because no graphics card is detected in the system when display it disabled during powering up.
There is a couple of similar topics about some other linux distros can't boot without video card inserted ([1], [2]) with some recommendations on what to do in such a case.
I've followed them - including enabling serial console in /etc/inittab, setting nomodeset in kernel line in grub's menu.lst, checking for enabled splash-screens... but that didn't help.
Does anyone know what options should be tuned in order to boot Arch without any active graphics card present in the system hardware?

Arch won't boot, FS not detected, Kernel Panic.

Ok so here is the situation. I have arch linux installed on sda1, which is a sata drive, samsung. Seems lately I been having problems getting arch to boot because it doesn't know what type filesystem my root device has. It goes on and tells me that I can use the kernel parameter rootfstype= to solve the issue, but yet when I try this, it does nothing. I stop getting the error, about unknown FS type, but arch still won't boot. Init fails...
I have tried everything on these forums to fix the problem and not one thing in general has solved the issue. What seems to be most consistent about this problem, is it takes me at least 20 - 30 times of rebooting before it will finally go through and boot. But, even then this is not foolproof. Last night I tried at least 30+ times of rebooting, powering off and still it would not boot.
So after reading the forums some more I found an article somewhat related to my problem and it was suggested that I add my root FS type as a module and then remove the filesystem hook in mkinitcpio.conf. I tried this approach and at the same time downgraded to 2.6.24.2-1 kernel26 so mkinitcpio would generate the new image. Then I rebooted and arch loaded just fine. So then I rebooted and again, unknown fs type on root device error.
So I retraced my steps and tried the same process again, only this time when I rebooted I got same problem. So as it seems, nothing I did to mkinitcpio.conf did anything to alleviate my problem.
As of right now, I managed to get the fallback image to work(but fallback does not load all the time, just this last time I tried it it worked), but I am scared to death to turn off my machine because I know it's not gonna reboot without a lot of hassle.
So can anyone help me diagnose this problem? What can I do to get the kernel to boot and mount the root device with ext3 and pass init on boot up? I am completely lost when it comes to this...
here is my mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="ext3 pata_amd ata_generic sata_nv"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
# This is identical to the above, except the old ide subsystem is
# used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
# This setup assembles an pata raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev pata raid encrypt filesystems"
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata sata"
here is my fallback.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
# BusLogic is added to support VMWARE arch booting in fallback image
MODULES="BusLogic"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
#BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm, or encrypted root is needed.
# HOOKS="base"
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect ide scsi sata filesystems"
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev ide scsi sata usb filesystems"
# This setup assembles an ide raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev ide filesystems raid encrypt"
# This setup loads an LVM volume group on a usb device.
# HOOKS="base udev usb filesystems lvm"
HOOKS="base udev ide pata scsi sata usbinput raid filesystems"
modules I need
sudo mkinitcpio -M
Password:
Modules autodetected:
ata_generic
libata
pata_acpi
pata_amd
sata_nv
cdrom
ide-core
amd74xx
generic
forcedeth
sd_mod
sr_mod
usbcore
ehci-hcd
ohci-hcd
jbd
ext3
Last edited by jacko (2008-04-15 19:53:35)

I had a similar issue (I think, can you post the exact error the kernel panics with to check?) and it seemed grub or the kernel had difficulties with finding my root device which was specified as a device node in /dev. The solution for me was to change the root parameter in my kernel line in grub's menu.lst to root=/dev/disk/by-label/<label>, I'm sure UUID and such will work fine too. After doing that I haven't encountered a single such kernel panic. More info about persistent device naming can be found here.

Arch won't boot on Virtual Box afted updating

I instaled Arch as guest on Vbox, after updating, it won't boot any more. It prints the message "Loading udev...SCSI subsystem initialized" and then the VM crash and the window is inmediately closed.
I searched on the Vbox forum and others have the same problem.
See: http://forums.virtualbox.org/viewtopic. … 890#p83890
Probably is an issue with Arch, because a clean install from core iso does work, but does not after updating.

What do you mean under updating ? pacman -Syu ? And what packages was installed?
Isn't there any virtualbox log or something ?

My Arch won't boot anymore something about bad blocks

Similar Messages

Maybe you are looking for