Swinstall could not

You asked how you would reinstall Windows while bypassing the error and I showed you to do this with an illustrated tutorial on how to Clean Install Windows 10 from booted media which I provide that has been used by millions of people successfully. You just ignored that and said I didn't answer how to reinstall Windows while bypassing the crashing, well you do it just like it shows in that tutorial by triggering the media before it has a chance to start Windows.

Now please go back and this time read my reply including the illustrated tutorials, and then ask back questions if needed. I will be here to help until this case is resolved, as long as you are polite and cooperative. Greetings, to provide a summary: My laptop is a Asus Xca. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. Cancel Submit. Hi Kiara. Since the errors revolve around the hard drive I would make bootable media to test the hard drive.

Also, the disk space used by the logfile will not be freed as long as the daemon is running. If you inadvertently remove the daemon logfile while it is running, you must kill and restart the daemon if you want to see subsequent daemon log messages and free up the disk space used by the logfile.

You can stop kill a daemon by typing:. If you are trying to access a tape depot and see the following error message in the daemon logfile, it means that the tape is either corrupt or is not in SD-UX format. Make sure that you have correctly specified the tape device and that the correct tape is in the drive.

For example, SD-UX does not read update format tapes. An installation may fail while only part way through the process. Recall the session file swinstall. By default, SD-UX checkpoints to the fileset level, meaning that the operation will start transferring files with the last fileset to be attempted.

SD-UX does not support checkpointing below the file level. See Appendix A for more information. Another SD command is running that prevents the swinstall or swremove command from running. Wait for that command to finish and try again.

ACL permissions. Inter-host Secrets. Working With Depot Images. Slow Network Performance. Disk Space Analysis Is Incorrect. Packager Fails. Command Logfile Grows Too Large. Daemon Logfile Is Too Long.

Cannot Read a Tape Depot. Installation Fails. Look for any file sets that are not in the configured state and manually enter the swconfig command, for those patches that are not in the configured state. If the CRA fails in this way during a swinstall or swremove operation the system will automatically reboot to complete the requested operation.

You can also remove the database for Service Control Manager, mysql, by executing the following command: swremove mysql. If your system is running Secure Path, upon update to HP-UX 11i v3, a migration script will execute and perform the following actions:. Update all the Secure Path virtual aliases with the new style device special files.

If the virtual aliases provided by Secure Path 3. After the cold-install or update to HP-UX 11i v3 is complete, manually mount the file systems.

The system will use the default value instead. NFS manpage files is missing:. For some third-party product installation scripts, dtksh is required for scripts to launch license-acceptance dialogs for Mozilla.

For swlist or swverify on HP—UX 11i v1, you can safely ignore this message. If VxFS 5. Make sure you copy data from your DLV 7 file systems onto file systems created at layout version 5 or 6 before updating to HP-UX 11iv3.

If you have created any VxFS file system with disk layout version 2 or version 3, these file systems cannot be mounted under VxFS 4. Use the vxfsconvert command to upgrade the disk layout to version 4 before upgrading to VxFS 4.

See the Veritas 4. Email: ste Kinda weird but I remember it working for me a while back. Kyle Barton. Reply to author.

Report message as abuse.