KT6 Delta won't boot after clearing the BIOS

I have just put together the machine as per my signature and run into a few problems. The XP 2800 mobile is not recognised as such but as a XP1800 when I set the FSB to 133. Am I right in saying this CPU should run at 1.65 volts as it seems to wants to run at 1.75. I changed the V Core to 1.65 and it boots ok but when I tried it at 1.6 it did not want to boot, ie no video output. I no longer get the single BIOS bleep and the monitor stays on standby. This has happened before and I got it running again by clearing the CMOS and reseating the RAM but this time I have done the same and it won't boot. Is there anything else I should be doing please. Many thanks.
Having looked at the Socket A sticky I see that my diagnostic D bracket is showing 1,2 and 3 showing red and four not on at all which would seem to point at the graphics as being the problem.

Hello!
Voltages should be set to "CPU default" or similar. Your processor comes in different versions, try setting to 166 instead of 133. Always when changing processor one should clear CMOS, by powering off, unplugging power cable, and then move JBAT jumper for a short time, a minute or so.

Similar Messages

My Mac Pro won't boot after installing the latest update

Im running the latest OSX on my mac and recenty did a small updated that i believe contain a few security thing and bug fixs but when restarting the machine after the update it would not boot again after the apple logo has appeard apple script is displayed on the screen contain what i think is boot script failing to run. I have been able to boot the system in safe mode. does anyone have and solution for this as i realy don't want to reinstall the OS
Thanks

The most common cause for "Won't boot after software Update" is Directory Damage that existed before the Update, but was made worse by adding files during the Update.
The most common cure for that Directory Damage problem is to boot in Safe Mode, which takes five minutes to repair the disk, then comes up demanding your username and password, even if you normally auto-login.
Rarely, third-party add-ons are made obsolete by an update. In this case, booting in Safe Mode (with few Apple extensions and NO third-party extensions loaded) works fine, even if normal mode does not work.
Have you tried normal mode again after your Safe Boot?

X1 carbon 20A7 won't boot after 1.13 BIOS update, ecreen also corrupted.

After updating the BIOS to 1.13 the X1 refuses to boot . After several attempts to diagnose the problem (trying to boot under legacy and uefi with various rescue pen drives) I doing a restore with the recovery media (created using the inbuilt software) but that didn't help, it just wiped my partitions and reinstalled windows (I'm assuming since I have no way to check at this point) but still refuses to boot. I can boot the windows rescue thumb drive under legacy though. After the update the screen was also corrupted, picture here http://i.imgur.com/ScfD1Uz.jpg.
At this point I'm not sure what to do anymore, it seems that the BIOS update failed in some way or somehow broke something.

this seems to have caused uneven lighting in the LED display, very strange problem. You may need to get warranty service on it.
Regards,
Jin Li
May this year, be the year of 'DO'!
I am a volunteer, and not a paid staff of Lenovo or Microsoft

IMac G3 won't boot after updating the firmware and upgrading the OS!

Hi! Everyone,
I have an iMac G3 333MHz (five flavors) which comes with 192MB of RAM and 6GB of hard drive. Originally, it was OS 8.5.1 installed, later upgraded to OS 9.2.2. Of course, the firmware has been updated by the appropriate method provided by the on-screen instructions before the installation of 9.2.2. After successfully updating the firmware and installing Mac OS 9.2.2, the system booted up and worked fine. However, after shutting it down and powering it up a few days later, I have encountered a critical problem:
1. At first, the iMac would chime and displayed a smiley-mac finder face.
2. No question mark appeared and the system halted because it stayed at the same screen for about 5 minutes! Also, the keyboard wouldn't respond. For instance, the LED signal light wouldn't light on when Caps Lock was pressed.
3. I assumed that this is just a typical crash and rebooted the machine via the "reset" button on the right side of the machine.
4. After restarting, well, no luck, the same condition. Therefore, I rebooted it again by using the method mentioned above.
5. The condition of sticking at the smiley-mac finder face occurred again! However, this time the iMac wouldn't chime and just displayed the mac face.
6. Another restart, well, it was getting worse... no chime and no smiley-mac finder face but a white screen.
7. I was frustrated then and shut the machine down forcefully by rebooting it again and pressing on the power bottom quickly before the screen appears. Also, I unplugged the power cord.
---------- After a few hours later ----------
8. Okay, I then plugged the power cord in and booted it up again, this time, it would chime but stuck at the white screen. => No smiley-mac finder face appeared!
9. Rebooted it again, the result was as same as step 8.
10. Another restart, the smiley-mac face finally appeared but still... stuck here and this time, no chime.
11. I then shut the machine forcefully by using the method mentioned above and let the machine rest for about a day with the power cord unplugged.
---------- After resting for a day ----------
12. I booted it up and it would chime, but no screen (the power button was orange, not green). I then forcefully shut down the machine.
13. Waited for about a minute and powered it up. This time, I tried to clear the PRAM, but no chime and gave me a white screen. => No luck! As mentioned, the keyboard's LED signal light wouldn't light on even though the Caps Lock key has been pressed.
*Note: The keyboard has been tested on the other computers and it worked. Also, I tried different USB ports to plug the keyboard in. => The USB ports were all in working condition， as I can know from the last successful start up.
14. Forcefully shut the machine down and tried to enter the Open firmware, no luck. It didn't enter and gave my a white screen.
15. Conclusion:
1) After resting for a while, the iMac would chime.
2) Rebooting too much times would cause the machine not to chime and leaded the screen to become white instead of the smiley-mac finder face.
3) However, rebooted the machine when the screen became white, the smiley-mac finder face would appear again without chime.
By the way, I could hear the hard disk spinning up so that means the hard disk is working.
Can anyone help me solve this problem? Is it related to the firmware update? Any suggestions will be appreciated! Thanks!
Andy

OK, I will try replacing the PRAM battery. Also, the PowerMac G3 and the other iMac 233MHz had the dead batteries. They are still working though... Should I replace them along with the iMac 333MHz? In case of not replacing, will they malfunction in future times? There are some symptoms on this two machines: 1. iMac 233MHz - No chime and no sound when adjusting system volume (the bi sound is not available), but iTunes and other applications can still use the audio device and output the sound via internal speakers; 2. PowerMac G3 450MHz - Will chime but sometimes hard to boot: 1) Chime but no screen; 2) No respond after pressing the power button => the power signal light won't light on. Every time I experienced this, I would open its case, pressing a small button (not quite understand what it does... anyway, just works if system halted.) near the PRAM battery and wait for about a minute, then close the case, and it boots. However, I have to reset "Date & Time"...

KT6 Delta won't boot - Compatability Issue?

I am upgrading two systems and neither will boot.
Motherboard: MSI KT6 Delta
CPU: AMD Athlon XP 2500+ (Barton)
Ram: DDR 400 (PC3200) Two 512MB
CPU fan runs but D-Bracket 2 has all four red lights.
Should JPW1 connecter be used? I do not see anything to plug into it
Help!

I found the following in a September post:
JPW1
When MSI designed the TURBO2 board, they included the jpw1 as a just in case sort of a thing. The original atx plug is what you need to use. The jpw1 can be used too, IF your p/s has the p4 style connecter that plugs into it. If it doesn't, and you are experiencing no problems with stability, do not worry about it. This plug provides the cpu with it's own source of power. All newer power supplys that are p4 ready, come with this plug. I bought a new supply,so I use it ,but there are lots of TURBO2 owners that are not using it, and are not experiencing any problems. Good luck with your rig,BIGDADDY51 CT.USA edit: I reread your post .Plug it in it won't hurt.

Solaris 10 won't boot after changing the CPU

Hi. I was running Solaris on my Intel-based desktop machine. It was running fine. One day I upgraded my CPU and since then Solaris won't start. Immediately after it tries to load itself, it displays something on the screen really fast ( something with "dumping" in it) and then reboots.
I runned Solaris in fail safe but I cannot run reboot -r for example. It says that reboot has wrong parameter or something. And I don't know what else to do.
Please help.
Thanks.
P.S. I'm not 100% sure that the problem is related to changing the CPU. Maybe I configured something wrong when working in Solaris prior to the hardware change. But I think that's unlikely because I'm usually pay attention when changing settings in Solaris and don't dive in dark waters.

Right after I wrote my previous post I looked again at the web page Darren recommended and I figured out what it was all about. I had troubles understanding the procedure in the first place because I wasn't familiar with mounting partitions and I didn't know what /a refers to. On another site I found out about the command that saved me: mount /dev/dsk/c0d0s0 /a A bit later I found out that when starting Solaris in single user mode (failsafe for example) the partition is mounted automatically to /a when you choose to update the boot archives.
(As a tip for beginners like me, once in single user mode use the Delete key instead of Backspace :P ).
So, the procedure explained on that site is:
In case of a hardware mismatch, use one of the two methods that follow:
Method 1 (Recommended)
1.Move path_to_inst          ex: # mv /a/etc/path_to_inst /a/etc/ORIGINAL_PATH_TO_INST      2.Remove all old device links          ex: # rm /a/dev/rdsk/c* ; rm /a/dev/dsk/c* ; rm /a/dev/rmt/*   3. Rebuild path_to_inst and devices          ex: # devfsadm -r /a -p /a/etc/path_to_inst Note: If you are worried about the bootblock being corrupt, reinstall it.       # cd /a/usr/platform/`uname -i`/lib/fs/ufs
      # /a/usr/sbin/installboot bootblk /dev/rdsk/<c#t#d#s0> 4.Unmount the root slice and reboot          ex: # umount /a ; init 6Method 2
From the OK> prompt, do a 'boot -ar'.
Accept the default for all questions except the path_to_inst file.
When you get to that one, specify /dev/null.
It should then prompt you if you want to create a new /etc/path_to_inst file from scratch. Say yes.
So I tried method 1, but no success. First of all I noticed that the devfsadm command didn't create the /a/etc/path_to_inst file. As many times I have tried it (even after I read a lot more on the Internet regarding these commands) I never made it to work. Somewhere on the net somebody asked about the "-p" argument that is not explained in the man pages of the command and the answer was that it specifies the path to the path_to_inst file wich makes sense but doesn't work. Somewhere else it was suggested that the "-p" argument to be ignored and the new path_to_inst file to be looked under /etc ; this was not the case for me.
I tried method 1 many times with small variations, within the virtual or the real machine, but it never worked.
So I tried method 2 as well, but no luck either. First of all, for all other beginners facing this kind of problem, on a x86 machine there is no OK> prompt; it's a SPARC "feature". But "boot -r" commands or alike can be issued using "reboot -- -r".
So I have tried all the variations I could find on the internet -r,-a,-ra,-rav, but this command didn't work either. I always got the message
bootadm: Cannot update menu. Cannot reboot with requested arguments.I never quite figured what "menu" is all about. My guess was that it refered to the grub menu/commands for booting and that it couldn't change those. So I
read on the net a few things about the booting commands in GRUB bootloader and I tried a few variation but they never worked. Indeed the changes I did to the commands were not saved, as the bootadm erros would indicate. Am I wrong?
After reading about the GRUB commands I got a little bit more familiar to what goes on at booting time and later I found an article in the Sun Documentation called x86: How to Boot the Failsafe Archive to Forcibly Update a Corrupt Boot Archive ( http://docs.sun.com/app/docs/doc/819-2379/6n4m1vlfi?a=view ). There I so this command
To forcibly update the corrupt boot archive, type:
     # bootadm update-archive -f -R /a
Unmount the device.
     # umount /a
Reboot the system.
     # init 6I have tried it, looked like it is searching through the hard-disk, after a while finished and I rebooted but with no effect.
This is where I am now.
Any idea of why devfsadm would not create the path_to_inst file?
Any ideas of what to do else or where I could have got it wrong?
Thank you.

Dual boot KT6 Delta won't boot from either bootable drive?

Recently my system has been playing me up and the monitor refuses to wake up or come in the morning. The only way to get it back is to press the reset button. This morning however I cannot get any further than the post screen where it shows me all the system details, it refuses to start to load either OS from the two hard drives. Where should I start to look to fault find please. Thanks for your help in advance.

Quote from: pompeyrodney on 22-February-07, 22:34:17
Thanks for the help, I am interested to know how many amps I should be looking for and could you guys recommend a good PSU for not much money. Thanks again.
look here for good PSU suggestion:
https://forum-en.msi.com/index.php?topic=104400.msg768358#msg768358
you should look for single rail PSU with high amperes provided on +12V
what memory you use?

Won't boot after using windows Bios flash utility

I used the windows bios flash utility i found on the toshiba website for this sat a135-s2386, all looked good until reboot, now just a white screen.

Attitude is not going to get you far.
Let's try a proper system reset, and see if this helps bring the unit back. Power off your system, unplug everything including the AC, remove the battery, press and hold down the power on button for 30 seconds, replace battery and AC, power on, if you see the Toshiba logo press the 'F2' key to enter BIOS Setup, in setup press 'F9' to load setup defaults, press 'F10' to save and exit, then try to boot into Windows.
Please let us know what happens. Good luck.
Mike

Mac won't boot after the latest update. It is loading the update and suddenly shuts down

My MacBook Pro won't boot after a minor update. The update was all fine and my Mac acted like it used to but when I tried to boot my Mac it just loads the the update then goes back to the Apple logo and then shuts down.
I hope that someone has got a solution because I do not want to restore my Mac for the 4th time.....

Hello JonasHallund,
We've an article that contains information and steps that can help get your MacBook Pro to boot again.
Troubleshooting: My computer won't turn on
http://support.apple.com/kb/TS1367
Cheers,
Allen

Mac OS won't boot after 2007-009 1.1 update

Hi all
Fairly major problem here. Mac OS X won't boot after the 2007-009 1.1 security update.
What I am left with is the mac boot screen, and not a lot happening. No rotating loading animation.
Any help would be really appreciated.
Thanks

I have been booting up for...2.45 hours now
Good grief!
Here are a few hints about what you should have done:
There are no guarantees, but following this procedure when installing updates and upgrades on your Mac will go a long way towards avoiding unpleasant after effects and ‘post-update stress disorder’.
It is also worth noting that it is an extreme rarity for updates to cause upsets to your system, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
So before you do anything else:
If you can, make a full backup first.
Turn off sleep mode for both screen and hard disk.
Disconnect all peripherals except your keyboard and mouse.
1. Repair Permissions (in Disk Utility)
2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
3. Download the correct version of the COMBO update from the Apple download site. If your car runs on gasoline you would not want to fill the tank with diesel, so don’t try to install the PPC updater on an Intel Mac!
If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
Using the Combo updater ensures that all system files changed since the original 10.4.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.4.9 to 10.4.10. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
Now proceed as follows:
4. Close all applications.
5. Unplug all peripherals except your keyboard and mouse.
6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
8. Once your Mac is awake, repair permissions again, and you should be good to go!
If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious!
9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them 10.4.10. compliant. Give them a weeks or two while you regularly check their websites for updates. This applies particularly to plug-ins for Safari 3.
N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
Lastly, Apple's own article on the subject of Software Update may also be useful reading:
http://docs.info.apple.com/article.html?artnum=106695
If you are updating Safari (or just have):
Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If you have installed 10.4.11 and Safari is crashing, the very first thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari. Remember: Tiger up to 10.4.10 used Safari 2.0.4 or, if you downloaded it, Safari 3.0.3 beta. Safari 10.4.11 uses Safari 3.0.4 which is not a beta. If Safari 3.0.4 on 10.4.11 is not the fastest browser you have ever used, then something is wrong!
Moreover, trying to revert to Safari 2 when running 10.4.11 can have repercussions, as Safari 3.0.4 uses a completely different webkit on which other applications like iChat, Mail and Dashboard Widgets etc also rely.
Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party ad-on. Two such add-on that have been frequently mentioned here for causing such problems are Piclens and Pithhelmet. If you have them, trash them.
Additional tips on software installation here:
http://docs.info.apple.com/article.html?artnum=106692

X99 Sli Plus Blue bios won't boot after update.

Hello i tried to update the "blue bios" to the most recent Bios version.Following all the appropriate steps i updated the BioS and got the appropriate message (something like that,i can't remember the exact message) "Update was succesful your system now will reboot".After the reboot blue bios just won't boot.I cleared CMOS,i used the Multi BIOS switch (manual page en-30) to flash the blue bios trying all the versions from 1.7 down to 1.3 but nothing seems to work.The green BioS work fine on the default v1.3.My question is what should i do to make the blue bios work again?
CPU: Intel - 5820k
GPU: Radeon Sapphire R9 270x
Ram: Crucial Ballistix Sport 8GB Kit (4GBx2) DDR4 2400 MT/s (PC4-19200) CL16 SR x8 Unbuffered DIMM 288-Pin Memory BLS2K4G4D240FSA

I can't see anything about you preparing the stick as instructed.
Quote from: flobelix on 22-February-15, 01:47:26
A.) Download >>this<< bios archive and place it on your desktop. Do not decompress.
B.) Download and install the >>MSI HQ Forum USB flasher<< .
C.) Insert your FAT32 formatted usb stick.
D.) Make sure that all win 8 options are disabled. (Fast Boot etc) Also make sure the legacy USB is enabled.
E.) Start the forum flash tool and select option 1. Then point the tool at the compressed archive we downloaded earlier. Then to your USB Flash Drive.
F.) Boot to the USB from working bios B.
G.) Once it booted successfully switch to bios A without powering down or rebooting
H.) Now follow the directions and let the tool flash bios A with version 1.7

Mac mini won't boot after RAM upgrade.

Tried installing new RAM in my Mac Mini, 512MB stock to 2GB of Crucial. Followed the directions to a T, grounded myself the whole time.
Things I've tried so far:
1. Resetting the PRAM, no luck.
2. Holding option at start-up, shows no icon.
3. Holding shift, no luck.
4. Holding X, nothing.
How do I get it to accept a CD if it won't boot?

Welcome to Apple Discussions!
You clearly have a problem, but you don't describe exactly what that is other than that your mini won't boot after the upgrade. What happens when it starts up? Does it attempt to start and hang up on the grey or blue screens, or does it start beeping at you almost immediately after you try and start it up, and also flash the power light?
If the former, then you may have dislodged a connector while working inside the system, in which case opening it up and checking that everything is firmly connected would be the first thing to do. If the latter, then the beeping/light flashing is the system telling you it has failed the power-on self test and the pattern of beeps/lights indicates why. In your case likely the system can't find workable memory. In that instance, opening the system and ensuring that the RAM is firmly and fully seated would be a good step, and if the mini continues to fail, then replacing the new RAM with the original to test that the system will then start.
It is not likely that anything had damaged your MacOS install in the process of upgrading, thus normally no reason to need to boot to CD as a result of a RAM issue.

Macbook pro won't boot after installing update 10.9.3

macbook pro won't boot after installing update 10.9.3

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. 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. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually login 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.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

MacBook Pro won't boot after trying to install 10.7.3 update. Start up stalls at Apple logo and spinning gear.

MacBook Pro won't boot after trying to install 10.7.3 update. Start up stalls at Apple logo and spinning gear. Computer won't even start in safe mode.

My daughter's MacBook Pro was doing exactly the same thing. I don't know if it had anything to do with the latest update. She called me about a week ago saying that her MacBook began running slower by the day . She then called me Friday and told me that it wouldn't get past the gray screen and the gear just kept on spinning. I did everything I could over the phone including Safe mode which it wouldn't go into and thought maybe it was the hard drive. She took it to the Apple store. Originally, they also thought it was the hard drive. It ended up being a corrupted operating system (Lion). Apple genius simply re-installed Lion and she's back up and running. Good thing she backed up right before it crapped out. She'll be restoring everything tonight. Don't know if re-installing Lion will help your situation, but it did the trick for my daughter.

[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)

KT6 Delta won't boot after clearing the BIOS

Similar Messages

Maybe you are looking for