SG-300 52p POE and the case of Native vlan forgotten on a Port-channel
Hi
We have recently changed our access switched to Cisco Small Business SG-300 52p on which is working firmware
SW version 1.3.5.58
We found out a very annoying problem on Port-channel and default vlan topic.
Our switch have a default vlan diffrent to the vlan 1 that depends on the floor they are, and this native vlan is at first defined on the portchannel of our central switch, a Cisco 3750
Example of a central switch port-channel with a define native vlan:
interface Port-channel2
description TO 1F
switchport trunk encapsulation dot1q
switchport trunk native vlan 6
switchport trunk allowed vlan 4-6,11,13
switchport mode trunk
on the SG300 side the configuration is this:
interface Port-channel2
description 1F
switchport trunk allowed vlan add 4-5,11,13
!next command is internal.
macro auto smartport dynamic_type switch
As you can see there is no "switchport trunk native vlan 6" simply because the SG300 once i write it on the command line, it accepts the command but the command sentence is not written on the conf (why?!)
the result is that everytime the SG300 is restarted on the port-channel i got two AUTO CREATED commands on the configuration "
switchport trunk native vlan 1
switchport default-vlan tagged
that let not work the network on that floor until i manually write on the SG300
no switchport default-vlan tagged
switchport trunk native vlan 6
These command, as said, works once i write them but are not viewed on a "sh run" and so saved on the conf so every time SG 300 is restarted i need to re-write them.
Is this a bug?
have i made some mistake?
Please let me know
regards
Pietro
Figure out!
the problem was on macro i have to write this:
macro auto processing type switch disabled
and then everything starts going as it should be
Regards
Pietro
Similar Messages
-
I must have gotten a corrupted sector on my disk drive I place my Adobe Photoshop Elements 6 CD in the drive and it asked to install or repair or uninstall. I clicked repair and after a minute it asked for disk 1. I could not find a disk one and my case only has space for one disk. What should I do?
Jim Hamilton.PSE6 is a very old program (more than 6 years old) so what exactly are you trying to do? Have you got PSE6 already on your machine? If so, to uninstall it, all you need to do is to go to the Windows Control Panel and uninstall it under Add/Remove programs icon.
If you are trying to install it again on top of what is already installed then the best way is to uninstall it from the machine before installing again after rebooting. Also, if the disk happens to be damaged then try copying the contents from the disk to a temporary folder on your machine and then try installing from that temporary folder by clicking on the setup.exe file.
Hope this helps. -
MacBook Pros and the case getting black spots?
My old PB17 had all sorts of problems with the area around the keypad starting to get "black spots" after a few months of use.
I got the case replaced once because I complained about it, and then put a pad-thingie around the trackpad, where I rest my palms. So it is pristeen right now and for when I sell or give away the old one.
Now that my new MacBook Pro has I arrived I was wondering: these cases looks the same as the old PB - so do they have the same "black holes in the aluminum" problem?
dougYup, MacBook Pro's are affected by this. Mine is having quite the significant problem with these little speckles.
http://www.flickr.com/photos/34606175@N00/281060903/
http://www.flickr.com/photos/34606175@N00/281060906/ -
300 Series POE and legacy devices
Greetings;
I convinced the powers that control my paycheck to stick with Cisco for small POE switch deployment. Yay!
So, I opened up my shiny new piece of hardware (a SF302-08MP aka SRW208MP-K9-NA), plugged in a Cisco 1230 and an 1121 AP AND... nothing.
I thought to myself, looks like Cisco is following the 802.af standard. I grabbed my crimper, swapped pins 4 and 5 with 7 and 8, and... nothing... again...
Now, the whole reason I pressed so hard for this equipment is that I wanted to be certain that our Cisco devices would be supported. The weird part is that an older Linksys (by Cisco or whatever) POE switch works just fine.
Knowing that there are two types of 802.af (one that delivers power via pins 1,2,3, and 6, and the other 4,5,7, and 8), it does not make sense that a switch (especially a Cisco switch) that says it complies with 802.af, would only comply with one type (I'm pretty sure the standard requires both).
Do I have a faulty switch, or an unhealthy attachment to a company that I adore?Hi, My name is Eric Moyers. I am a Network Support Engineer in the Cisco Small Business Support Center.
Currently there is no testing from Cisco to certify the use of any third party PoE adapters or extenders with any of our Small Business Equipment like the SF300 switches. While there are several out in the market, while using third party equipment that has not been certified can potentially work, they have an equal chance of not working or damaging equipment. Before using such devices I would make sure that they will replace any equipment that is damaged from the use of their products, because Cisco may not depending on the circumstances.
I am by no means saying that customers can not use third party equipment. I just want all of our customers to have all of the information.
Eric Moyers
Cisco Network Support Engineer
1-866-606-1866 -
PoE and the WAP4410N - need a recommendation...
Looking for a Cisco, low-cost power injector solution to push the WAP4410N. Network is all cat6 and the AP is 100ft away...
Thanks, Mark
I'm long on Cisco - I believe in the future...Hi, My name is Eric Moyers. I am a Network Support Engineer in the Cisco Small Business Support Center. Currently there are no PoE injectors that are certified to work with any of the Small Business Access Points. The current recommendation is to purchase a small unmanaged switch, similar to the SD208P.
Cisco does recognize that this is a need of our customers and we are currently developing one specifically for these devices, Sunfortunately there is no known timeline for when this will be available.
There are some currently available through Cisco Enterprise and other 3rd party vendors, however we can not guarantee that they will work or not damage your unit.
I hope that this answers your question. Please let me know if I can provide any further assistance.
Eric Moyers
Cisco Network Support Engineer
CCNA, CCNA-Wireless
1-866-606-1866 -
Android R.* access and the case of the missing styleable
Hi,
I'm trying to use appcompat-v7 in my ANE and access it via the R.* mechanism.
The packaging step of the ANE works fine.
However, when building the final .apk using this ANE, the styleable elements disappear. The other resources (such as drawables, etc) are present just fine in the output.
The artifacts I'm using are classes.jar and the res folder from inside the .aar for appcompat-v7: \android-sdk\extras\android\m2repository\com\android\support\appcompat-v7\19.0.1\appcompa t-v7-19.0.1.aar
The end result is that the generated apk contains and R file for this library, and an R.styleable, but it's empty (by comparison in a properly built non-air android app this R.styleable would contain quite a few different fields). The other R. classes seem to be properly populated with a merge of the resource ids - R.string, R.layout, etc.
Here's (a trimmed down version) of the platform.xml I'm using when packaging the ANE:
<platform xmlns="http://ns.adobe.com/air/extension/4.0">
<packagedDependencies>
<packagedDependency>support-v4-19.0.1.jar</packagedDependency>
<packagedDependency>android.support.v7.appcompat-classes.jar</packagedDependency>
</packagedDependencies>
<packagedResources>
<packagedResource>
<packageName>android.support.v7.appcompat</packageName>
<folderName>android.support.v7.appcompat-res</folderName>
</packagedResource>
</packagedResources>
</platform>
Here are the errors I'm seeing during install time:
D/dalvikvm﹕ DexOpt: couldn't find static field Landroid/support/v7/appcompat/R$styleable;.ActionBarLayout
D/dalvikvm﹕ DexOpt: couldn't find static field Landroid/support/v7/appcompat/R$styleable;.ActionBarWindow
D/dalvikvm﹕ DexOpt: couldn't find static field Landroid/support/v7/appcompat/R$styleable;.Theme
...the list continues here
and at runtime:
java.lang.NoSuchFieldError: android.support.v7.appcompat.R$styleable.ActionBarWindow
So the question is: are styleable attributes supported in air native extensions?
Thanks,
RaduNimisha1,
Thank you for the info but it seems R.styleable still has something wrong. As suggested, I'm using AIR beta 14.0.0.125 and I set JAVA_HOME
in the machine, pointing to JDK 1.6.0. I'm on Mac OSX 10.9.3, by the way.
I used apktool again to compare the apk with the one created by Eclipse. All the xml files of the resources are in 'res' now but the difference is in
the file named R$styleable.smali which is located at
APK_ROOT/smali/android/support/v7/appcompat/R$styleable.smali
The one created by Eclipse contains the declarations for ActionBarWindow but the one by Flash Builder doesn't.
I wonder if something is still missing... anyhow it would be great if you could help me again. Thanks.
middletail -
Migrating iPhoto to Aperture 3 and the case of missing photos
I love the new Aperture 3 and am so excited to migrate from iPhoto. I have used the Aperture feature of importing an entire iPhoto library directly into a new Aperture library. This doesn't produce any errors (except for a handful of missing photos which aren't too important), but when I look at the resultant Aperture library (8 hours later), I am missing a LOT of photos. My iPhoto library has about 24,000 photos and my Aperture library only has about 16,000. Because of the differences in the way Aperture and iPhoto keep track of edits, my Aperture library should have considerably more photos than iPhoto and not less. Please help!
In new iLife 09 (or iPhoto 09), some pics are now black in the Event, simply an outline of dotted lines. Yet, when I cursor fast, they appear, so I know there are still there.
That doesn't mean that they are "still there". It means that a cached version of the image exists.
I recall, when migrating photos it noted that the photos in iPhoto (old system) needed to be formatted to new iPhoto, so I allowed. Makes me wonder if something in a pic title or such is the issue.
That's a standard procedure when you upgraded to the later version of iPhoto. Happens every time to up a version, and to everyone.
With regard to Portrait. When I import from iPhoto to Aperture, any Portrait picture has a 2nd verson next to it, but in the Horizontal. All Horizontal pics, there is only the one version of the pic.
Your camera has an Auto-Rotate feature. However, the camera does not actually rotate any pixels in the file, but instead flags it with an instruction: "Display me this way". iPhoto, seeing the flag, reads the intention and creates a modified version. Hence the second version of the Portrait pics and no second version of the Landscape ones. The landscape ones don't have an auto-rotate tag.
For the dotted line problem, try rebuild your iPhoto Library: Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild.
Regards
TD -
Native Vlan Effect on the Overall Network Performance
Dear Experts,
I would like to know that did Native Vlan affect the overall Network performance and make the whole network slow and can be cause for all Network devices to be failure or disconnect. I am facing this issue for the network that after apply Vlan dot1q tag native" in global Config the user disconnect from the network and also the devices.
Kindly assist on this issue with the practical scenario and result oriented conclusion.
Further I have following Devices in the Network Catalyst 4500, Nexus 5548, FIC 6248, UCS 5018 and Catalyst 3750.
The issue is this the VLAN 50 which is for UCS is not able to access from the LAN network even we added the VLAN 50 on all the Switches and it propogated to whole network so we make Vlan 50 as Native and added "switchport trunk native vlan 50 on trunks ports from Nexux 5548 to Fabric Interconnect and to Core Switch 4500. After added vlan 50 as native vlan we can access the UCS from LAN.
But after adding native vlan 50 on all trunks the Network Administrator complaining that network is slow and few servers are disconnecting.
here for the information that server vlan is 1.
Waiting for the answer.
Thanks,
JH
Thanks,
JHHello.
1. Could you please draw interconnectivity diagram of all the devices?
2. Could you chose any LAN device (on the same switch as UCS) and post here running config of the device that interconnects them? -
I Shut down my Mac by holding in the power button after my iMac froze and now when I try to turn it back it on all I get is the grey screen with Apple loge and the timer and doesn't get any further. I have tried the diagnostic test but nothing was found.
Take each of these steps that you haven't already tried. Stop when the problem is resolved.
To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.
Step 10
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 11
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 12
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 13
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider. -
MBP and the Thermal Paste Discussions
I've read with interest the postings on this web site regarding the MBP heat issues and the possibility that too much thermal paste is causing that problem. I've spent quite a few years designing computer motherboards using Intel processor chips, and want to share some thoughts on the topic. I only mention my background because one thing this business has taught me is that we can all be easily mislead by our test data if our process for gathering the data isn't rigorous (and, believe me, I've learned that lesson many times).
First, the excess thermal paste is definitely a problem, regardless of whether it is the root cause of the heat issue. Some of the photos posted on the various web sites show thermal paste covering bypass capacitors on the chip carriers (the green fiberglass boards that carry the CPU and GPU die). Thermal pastes can cause stray capacitances that can interfere with circuit operation. Standard industry practice is to use only as much paste as is necessary to achieve a layer that is about as thin as a single layer of tissue paper (or less). The amount used by Apple is far too large, particularly because the paste in coming into contact with other electrical components and conductors. A common failure mode associated with degraded bypass capacitors is random (and unrepeatable) crashes due to corrupted digital data in the processor chip.
In addition, all thermal pastes contain various types of fluids. Over time, these fluids evaporate, and frequently they condense elsewhere inside a computer. When CD drives were first introduced years ago, a common cause of mid-lifetime failures was condensates on the optics of the laser. The condensation fogs the lens and interferes with the ability of the laser to focus while reading and writing data. The contamination was traced to outgassing by thermal pastes, greases, sulfurized elastomers, and similar items used to build the computer. (Note that the Apple service manual for the MBP refers to the thermal paste as “thermal grease”.) Consumer electronics manufacturers learned to minimize the use of such materials in computer designs. The amount of thermal paste shown in the Apple service manual is very large, and I wouldn't rule out that it might contribute to future DVD drive failures.
It is difficult to say, based on the available data, that reducing the amount of thermal paste actually contributes to improving the thermal behavior of the MBP. Part of the problem is that the procedure to remove the pastes involves disassembling the laptop, and this introduces the possibility that the disassembly/reassembly process is inadvertently fixing the problem.
First, the high case temperatures could be the result of loose or poorly placed thermal sensors. If the disassembly/reassembly process fixed a loose sensor, or loose sensor electrical connection, or placed the sensor in a better position, you would get lower case temperatures, and possibly (inadvertently) attribute this to less paste.
Second, the cooling system design in the MBP requires that the die caps on the chip carriers be pressed tightly against the pads on the heat sink, so that heat is transferred efficiently. If the MBP is not assembled properly, (i.e., if the logic board mounting screws are not properly torqued, or the logic board is not mechanically aligned properly to ensure a tight fit to the heat sink), it is possible that this will manifest itself as high case temperatures. In the Intel processor chips there are two paths for heat to travel – out of the die cap, and through the electrical contacts to the motherboard. If the die cap isn’t properly cooled, heat will instead go into the motherboard, and the case temperature will rise. There is a possibility that the disassembly/reassembly process will fix a loose or misaligned logic board problem, with the result that the case temp will be reduced.
Also, if you work through the details of the thermal model that results from excess paste, it's hard to see how it would result in more heat to the case and less to the heat sink. Most of the photos on the web appear to show thin paste on top of the die, indicating that there was probably a low thermal resistance path to the heat sink prior to disassembly. The excess paste to the sides will simply further reduce the thermal resistance between the chip carrier and the heat sink. I may be missing something, but it's hard to envision how this lower thermal resistivity between the CPU and the heat sink drives more heat into the case. But it is also possible that the disassembly process destroys evidence of the actual connection to the heat sink, so this failure mode is hard to judge.
The best way to determine if removing the excess paste is actually helping would be to measure the exhaust air temperature from the cooling fans before and after removing the excess paste. I haven't seen such data, but if it were taken, and showed that the exhaust air was at a significantly higher temperature after the fix than before it, then we would know that the fix worked. If not, then the heat is going elsewhere, and it is possible that fix has actually made things worse.
Finally, all the symptoms we're seeing can be explained by poor software calibration and/or incorrect software control of the CPU clock speed. I wouldn't rule out a software fix at his point.
I'm not saying removing the paste is not a fix, only that there are still open questions that remain to be answered. It would be hard for me to recommend that anyone rework an MBP for the thermal problem in the absence of additional data.
For myself, I own an MBP, and though I have access to an electronics lab and some great technicians, I intend to buy Applecare, and in the meantime wait for a fix (or at least more information) from Apple.
Best of luck to everyone who has this issue - thats what we get for being early adopters.
G5 2.5 DP Mac OS X (10.4)
G5 2.5 DP Mac OS X (10.4)
G5 2.5 DP Mac OS X (10.4)
G5 2.5 DP Mac OS X (10.4)
G5 2.5 DP Mac OS X (10.4)
G5 2.5 DP Mac OS X (10.4)Well I replaced my thermal compound and the temperature on my cpu went down and the temperature of my case went down also. The fans also kick in sooner leaving me to believe that the heat is being properly distributed the heatsink whereas before it was not as there was too much thermal compound making it act like an insulator.
I cannot say if the exhaust air is any hotter, but I know overall my laptop is much more cooler and never gets extremely HOT. Even under heavy loads the areas where it used to get really hot, above f keys, palm area, underneath the MBP are not hot to the point where someone could burn themself at all.
I really do hope that Apple does address this issue because I could not live with the heat before, I always had to hook up an external keyboard because my hands got too sweaty from the palm rest and the keyboard. Now everything is operating like any other laptop I've owned and I am a very satisifed Apple user. Let's hope that Apple is really looking into it and will have a reasonable answers for all MBP users in a reasonable amount of time. -
IMac starts with sound but remains with Apple logo and the clock running indefinetely
After software upgrade ( from mavericks to new mavericks ) iMac doesn't start anymore. It remains always in the same mode: after the sound of start the Apple logo and the clock that runs indefinitely without the start of the software. Someone knows what to do?
Take each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.”
b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
c. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use either of the techniques in Steps 1b and 1c to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 10. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 10
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 11
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 12
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider. -
Please please help! I'm a college student taking finals. Need it fixed asap
Take each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a boot failure is to secure your data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since your last backup, you can skip this step.
There are several ways to back up a Mac that is unable to boot. You need an external hard drive to hold the backup data.
a. Boot into the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.”
b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
c. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
Sometimes a boot failure can be resolved by resetting the NVRAM.
Step 3
If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
Step 4
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 5
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to boot, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can boot now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
If you've booted from an external storage device, make sure that your internal boot volume is selected in the Startup Disk pane of System Preferences.
Step 6
Boot in safe mode. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you boot in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, your boot volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 6.
If you can boot and log in now, empty the Trash, and then open the Finder Info window on your boot volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then reboot as usual (i.e., not in safe mode.)
If the boot process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 7
Launch Disk Utility in Recovery mode (see Step 1.) Select your startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then reboot as usual.
Step 8
Reinstall the OS. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 9
Repeat Step 6, but this time erase the boot volume in Disk Utility before installing. The system should automatically reboot into the Setup Assistant. Follow the prompts to transfer your data from a Time Machine or other backup.
Step 10
This step applies only to older Macs (not current models) that have a logic-board ("PRAM") battery. Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a boot failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 11
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider. -
What is the case that comes with the iPod Video?
My Friend just got a Nano and the case that came with is is just like a little sleeve that the iPod slides into....it also has no access to any controls (hold button, Dock connector, Click whell, etc.) and cannont see the screen.. you have to take the ipod out to use it....is it that same thing for the iPod video?
Dell Windows XP Pro Future owner of iPod video 30GB or 60GB (5G)The case that came with my 5th generation black iPod video sounds similar to the one you're describing. It is totally enclosed and the only items that I have access to are the headphone jack (top) and the hold button (also on the top). If I put the iPod into the case upside down I can have access to the usb connector. This isn't meant to be a case for use (other than turning it on and going) but I've been able to push through the case to skip songs, rewind, etc.
So, in short, it's nothing fancy but it has done a good job of protecting my iPod against scratches. -
Should my Macbook (black 2008) be warped and the battery bloated?
A few weeks ago I noticed that the battery was bloated and the case had warped.
I have difficulty typing too as my wrist rests on the 'rests' and it clicks the mouse so end up typing and deleting text all over the place.
Is there anything (cheap) that can be done to fix this. I'm a student and can't afford too much..If you can get to an Apple store they may replace the battery for free. If not try eBay.
Black Batteries: http://shop.ebay.com/i.html?_nkw=macbook+black+battery&_sacat=0&LH_BIN=1&_sop=12 &_dmpt=Laptop_Batteries&_odkw=macbook+white+battery&_osacat=0&_trksid=p3286.c0.m 270.l1313 -
Which switch for POE and 7940G phones?
I have 2 (and maybe soon 5 more) 7940G phones to add to my network, which already has a Netgear POE capable switch. I've since discovered that early Cisco POE isn't the same thing as current POE, and the switch doesn't power the phones.
I was looking at adding a Cisco SD208P 8-port switch to power the phones, but I soon discovered it only has 4 POE ports, and I'm not sure that this switch will even power the 7940G phones. And if the other 5 phones show up, I'll need two of those switches with no room for expansion on the voice network.
Will this switch power those phones?
Is there another small switch available so I don't have to replace my existing switch infrastructure to get these phones to work? Or do I need to scrap the phones and get something newer that will work with the current POE standards?Will,
I would look at the ESW520 8 port switch, it will power the phones and will have the "*" VLAN's already setup in them.
Side note "*": This assumes that you are using VLAN100 and Cisco Voice system for the switch
Have a great day
Maybe you are looking for
-
How do I use find my iPhone with a iPod Touch 3gs?
Well I tried using it on a friends iPod Touch, because I lost mine. I tried regestring but It didn't work, to my dismay I learned that MobileMe was closed to new subscribers. I tried doing it on iCloud, but iCloud is only for iOS 5. So how do I regi
-
I have a macbook running on 10.6.8 and my itunes running on 11.1.1 .... i cant get my itunes to show Itunes Radio in my music tabs.... someone help
-
Hi there I have an issue in resetting (using FBRA) clearing GL document which belongs to 2007. This clearing doc has few line items, which were generated while clearing other GL docs . While I thought it might be due to a closed period, I tested in m
-
I've started first workflow. I would like to automate the process of cleaning out my email periodically from my ISP. There is a web based method. The workflow works fine until I get to the page where I have to enter my user name in one field and pass
-
How to make a push transition without the obnoxious fade aspect
I see that a view controller can do a push over transition where the new view pushes over the old view; the UIView animations have a push but their implementation adds an obnoxious fade aspect, how is the view controller doing theirs? Must be an undo