Boot-Up Run Of Of Space - Porteus3.0
Posted: 26 Dec 2013, 16:12
Seasons Greetings!
I hope all had happy holidays, while I have a small emergency on my hands.
It might have with trying to use CopyAgent service after after installing and configuring 32bit Porteus 3.0 XFCE 4.10 on my 8gig flash. There's a possibility that Copy downloaded its cloud copy of my files into the File System folder instead of /mnt/Documents/Copy while I trying to install the Copy app overnight. I woke up to a black screen. I had re-run Porteus several times and take out my Seamonkey and OpenOffice and GIMP modules to fix a boot-up screen I could copy the following from.
First the start-up screen alerts Normal boot-up until --
Recovering journal. Triggering udev. events /sbin/
Failed to start message bus: Failed to close
"var/run/dbus/dbus.pid". No space left on device.
Sed: Couldn't flush /etc/sedoHW4KIT No space left on device
INIT: Entering runlevel: 4 sed couldn't flush /etc/lxdm/sedgf0JHT: No space left on device
And similar lines go on. So ironically I can't even access the file I made of my evaluations of 3.0! Or my most recent SeaMonkey files since they're locked up in the File System folders some where (Why I must find a way to use a alias/short-cut way of having Seamonkey store its Mail files in my safe Documents or Copy folder). By using another Porteus flash to look inside the plighted Porteus one, I see that the File System folder has 960 megs free while the Documents folder where Copy is has 5.1 gigs free, so there's a count error somewhere when boot-up reports no more space.
I spent a lot of time configuring and getting this rendering of Porteus right and I'd hate to chuck it without a fight. Is there anyway to fool or fix the save file so it doesn't know or see that there's no space left on the device?
Thanks for any assist!
Jim in NYC
I hope all had happy holidays, while I have a small emergency on my hands.
It might have with trying to use CopyAgent service after after installing and configuring 32bit Porteus 3.0 XFCE 4.10 on my 8gig flash. There's a possibility that Copy downloaded its cloud copy of my files into the File System folder instead of /mnt/Documents/Copy while I trying to install the Copy app overnight. I woke up to a black screen. I had re-run Porteus several times and take out my Seamonkey and OpenOffice and GIMP modules to fix a boot-up screen I could copy the following from.
First the start-up screen alerts Normal boot-up until --
Recovering journal. Triggering udev. events /sbin/
Failed to start message bus: Failed to close
"var/run/dbus/dbus.pid". No space left on device.
Sed: Couldn't flush /etc/sedoHW4KIT No space left on device
INIT: Entering runlevel: 4 sed couldn't flush /etc/lxdm/sedgf0JHT: No space left on device
And similar lines go on. So ironically I can't even access the file I made of my evaluations of 3.0! Or my most recent SeaMonkey files since they're locked up in the File System folders some where (Why I must find a way to use a alias/short-cut way of having Seamonkey store its Mail files in my safe Documents or Copy folder). By using another Porteus flash to look inside the plighted Porteus one, I see that the File System folder has 960 megs free while the Documents folder where Copy is has 5.1 gigs free, so there's a count error somewhere when boot-up reports no more space.
I spent a lot of time configuring and getting this rendering of Porteus right and I'd hate to chuck it without a fight. Is there anyway to fool or fix the save file so it doesn't know or see that there's no space left on the device?
Thanks for any assist!
Jim in NYC