I created ext3 on sda1 (using mke2fs -j) and it worked for last 20 days.
But after tiday reboot it stopped working - if it would be bad entry in fstab
I would still be able to mount it by hand, but I can't. I have some data
on it that I would rather not lose (I don't have enough space to make
If you have your original debian net-inst dvd, it's probably time to
put the dvd into the drive then reboot the computer into rescue mode.
Then run fsck.ext4 -c /dev/sda1 enter and watch the fun. This will
use badblocks nondestructively and set off a repair operation which
should end up with
On Sat, Nov 9, 2013 at 8:49 AM, Jude DaShiell jdash...@shellworld.net wrote:
If you have your original debian net-inst dvd, it's probably time to
put the dvd into the drive then reboot the computer into rescue mode.
Funny thing (actually not so) - my optic drive is dead. But why do I
have to
On 2013-11-09, darkestkhan darkestk...@gmail.com wrote:
I created ext3 on sda1 (using mke2fs -j) and it worked for last 20 days.
But after tiday reboot it stopped working - if it would be bad entry in fstab
I would still be able to mount it by hand, but I can't. I have some data
on it that I
On 11/09/2013 04:09 AM, darkestkhan wrote:
Funny thing (actually not so) - my optic drive is dead. But why do I
have to reboot
into recovery mode? System itself works correctly - /boot is on sda2
and everything
else is on LVM at sda3
If I understand you correctly that you can boot and use
5 matches
Mail list logo
