Hi there,
my system was working well for over a year or so.
Since a few days it reboots immediately after login, at maybe four of five startups. I can see the desktop for 0.5 second, and then it goes black and reboots.
In the cases where it doesn't reboot, it runs flawlessly.
I tried -f boot...
You wont believe it :banghead:
It was the f.. power cable. That's why it always worked fine in the docking station. And swapping SATA cable didn't help.
My theory is that it had enough power for reading. But writing obviously needs more power and then the voltage went too low.
Good to know! Thanks.
It's the system drive with a lot of software. The good thing is that I still can read from it.
After swapping cable it couldn't even boot anymore. Then again I put it in the docking station and it works flawlessly.
I wonder if this is a mechanical problem. Maybe the plug...
Thanks for your reply. It's quite an old model, it's just called "Solid State Drive. The model number is SDSSDP128G.
I tried different ports, but actually I'm not sure if I swapped the cable before the problems started. So I'll try this again.
I have a Z97 chipset so I'm not using any special...
I have an update: I put the disk in a docking station and connected it through eSATA. Like that the error disappeared. I did a file system repair and a access rights repair... I also did a disk benchmark with good results...
But as soon as it's connected as internal drive, the issues are there...
My system drive which is a "SanDisk Solid State" model started to disappear all of a sudden.
It boots fine, the system seems stable. I can browse the web, watch utube... But after a while things start to get unresponsive.
I found out that I can speed up the freezing by writing large files, i.e...
Same issue here...
Did you find a solution?
I think it's more related to USB / booting from USB. When you google for the line "waiting on ioproviderclass ioresources" you will find some hints.
One solution could be to install from a SATA drive instead of a USB stick.
Edit:
This thread could...
There are messages about still valid PIDs and stray processes in the end, which have to be killed with -SIGTERM...
Could this be the source of the issue?
This time, the root file system was not corrupted. But I think that the shutdown process looks similar each time.
I will take a photo each...
Hi guys
Any idea how to debug this issue? It is really running very stable, except of this file system corruption thing.
When I boot with -v option, I see this as last lines on shutting down, before power goes off:
Could not unmount /home, /net
Could this be the issue?
Is there a way to...
Hi there,
I managed to install 10.8.5 and I'm using it with Pro Tools (DAW) for quite a while now without any issues, except of this one:
After maybe one of ten regular shutdowns (no panics) the system drive needs FS repair, which can not be handled by a simple fsck -fy. So I have to boot into...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.