It will make sure you have a clean file system without any on-disk corruption, and 2 it will make sure that you do not have any operating system drivers that have been corrupted. This backup, install, restore will do 2 things. When the operating system setup asks if you have data to restore, say yes, and point it at one of your backups. Use the operating system installer to erase and install a clean version of your operating system. Once you have your data safely backed up, you have a way to re-install the operating system. I actually prefer to have one backup be a bootable clone via SuperDuper (always free for a full clone), or Carbon Copy Cloner (free 1 month fully enabled demo mode). Either create a bootable installer, or make one of your backups a bootable clone.
Get a copy of your current operating system's installer. 2 backups would be better to 2 different output devices, using 2 different backup utilities (why, because when it comes to my own data, I'm paranoid meaning I've been burned before) If your 32GB is from Apple, then the likelihood it is RAM is very VERY low.Ĭonsider doing a full backup of your boot device. Highly unlikely based on the panic signature, but sometimes 3rd party RAM can cause problems, but every memory related kernel panic never looks like this.The file system is corrupt, and this is finding a weakness in the file system drivers (NOTE: a corrupt file system should not cause a panic if that is the cause, the file system developers are at fault not intentionally, but the top 2 rules for a file system developer are, you NEVER corrupt the user's data (this is job 1), your code never causes a kernel panic, no matter what it sees on the disk, or odd conditions that occur (this is not as bad as corrupting user data)).Since the Logitech is new, and the panic is again in the file system, I think you can ignore it.
You are still panic'ing in the file system code.Īnd you still have the SoftRAID driver installed, along with a Logitech driver ĕ.7.5Ĭom.Logitech.Control Center.HID Driverē.9.5
0 kommentar(er)
