Moderator: fredx181
I run FossaDog (2020-11-15) from a USB stick and have an hard disk with my data connected to my pc.
When Fossa was started up, the disk was normally seen and it's partitions were mountable. However, after some time, Fossa started acting up in the form of either loosing partition informations (showing as unrecognized ) or loosing the disk access at all (it's device file in the /dev stop to exist)
I'm just having a look at Fossapup64-9.5 atm . I have not had a browser crash in years but it does with seamonkey in this distro and thats not too impressive.
The Australian State Governments have all enacted laws to steal your assets on your death. All legal paperwork is binned and all assets seized on one disgruntled child's complaint.Move them well before you die or go into a home.
April wrote: Mon Apr 19, 2021 3:01 amI'm just having a look at Fossapup64-9.5 atm . I have not had a browser crash in years but it does with seamonkey in this distro and thats not too impressive.
Wrong topic
Well not really kind sir . They are both based on Fossa and it seems to be raising OLD problems. So I thought to add it.
The Australian State Governments have all enacted laws to steal your assets on your death. All legal paperwork is binned and all assets seized on one disgruntled child's complaint.Move them well before you die or go into a home.
mcgiwer wrote: Sun Apr 18, 2021 8:57 amI run FossaDog (2020-11-15) from a USB stick and have an hard disk with my data connected to my pc.
When Fossa was started up, the disk was normally seen and it's partitions were mountable. However, after some time, Fossa started acting up in the form of either loosing partition informations (showing as unrecognized ) or loosing the disk access at all (it's device file in the /dev stop to exist)
I quickly tried to reproduce the problem you have, but cannot, and I have very little time these days, sorry.
Hopefully someone else will be able to help.
Fred
but this topic is related to a disk reorganisation issue, so your browser issues are off-topic here, even if it's also related to FossaDog (like many topic's in the UbuntuDogs forum
mcgiwer Yeh ,well, tough eh! Shove it.
I'm coming to the belief that Fossapup64-9.5 is not very stable and I guess Phil666 is pretty busy with the numerous issues mentioned here and he's probably the only one able to work it out .
As I said I have not had a crash in my Puppies for probably 10 years and suddenly this one starts .
I am going back to xenialpup64-7.5 as that can be recommended as the most stable release I have found over the time to date .
Its the release that has also given the least trouble by way of file system errors even with a 6.5 Gig savefile.
So for any newcomers I would suggest don't try fossapup64-9.5 yet ,rather use xenialpup64-7.5.
This thread is but one of many that indicate to me anyway that Fossapups have problems.
The Australian State Governments have all enacted laws to steal your assets on your death. All legal paperwork is binned and all assets seized on one disgruntled child's complaint.Move them well before you die or go into a home.
With those kinds of issues, I'd suspect that the hard drive itself more than it being a linux bug.
Have you tried to run any of the hard drive analysis/fixup programs?
Maybe the scan in gparted would be a good place to start?
NOTE: The issues apply mainly to FossaDog with is run from a USB stick without savefile (not saving changes)
I did. When it was correctly detected then the disk check hasn't returned any errors.
When the problems suddenly stared to occur, the disk's partition table is seen "unreorganized" (or similiar named) or the system is complaining with i/o error's.
The only solution to make it that it becomes seen correctly again, I needed to shutdown the system without saving the changes and after a bit to start up it again from the begining
The first thing I'd do then is see if you can duplicate it on another usb stick.
Also, how did you install it and can you show us your equivalent of the menu.1st file.
I don't know what's wrong, but these are just general trouble shooting steps to try to narrow it down, or at least for me to be able to set up to duplicate it for Fred.
dancytron wrote: Fri Apr 23, 2021 7:49 pmThe first thing I'd do then is see if you can duplicate it on another usb stick.
Unfortunatelly, it's the only usb stick I have and I can't afford myself to buy another one 
I had "burned it out" from the official iso avaliable from: this page with the
Code: Select all
dd if=<ISO> of=/dev/sdbThe usb was empty and checked for errors before the "burning"
If you mean the boot menu then it's the standard one... I haven't edited any of the GRUB entry
dancytron wrote: Fri Apr 23, 2021 7:49 pmI don't know what's wrong, but these are just general trouble shooting steps to try to narrow it down, or at least for me to be able to set up to duplicate it for Fred.
I don't know neither. It's starange that suddenly, while normal usage, it looses a support of a disk or "think" that it's partition table got damaged, causing to seein it's structure as "unreorganized" or throwing I/O errors, with vanish after the power off and restart
I don't know neither. It's starange that suddenly, while normal usage, it looses a support of a disk or "think" that it's partition table got damaged, causing to seein it's structure as "unreorganized" or throwing I/O errors, with vanish after the power off and restart
I hate to say it, but that sounds like the USB drive is failing. Can you do a regular frugal install to your hard drive instead?