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 us
broken-ext4-superblock-in-ubuntu/
Summary:
Says to do:
mke2fs -n /dev/sda1
to discover where the superblock backups are stored
then to replace the bad superblock
e2fsck -b block_number /dev/sda1
'block_number' being the first backup block number in the mke2fs -n
output.
Excuse me if
On Sat, Nov 9, 2013 at 8:49 AM, Jude DaShiell 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 reboot
into recovery mod
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 and watch the fun. This will
use badblocks nondestructively and set off a repair operation which
should end up with you h
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 backu
Well, using e2fsck could not work since the primary superblock is
damaged hand hence not writable. Instead, debugfs came to my rescue.
It allows to enter the blocksize and the superblock to be used for
filesystem to debug, and one can enter an interactive session or let run
a script. Phantastic!
U
OK, the problem is solved. If ever you happen to be in the same situation
and have to recover data from a partition with damaged primary superblock,
you can try the following. We use an example where the failing
partition is /dev/hda4 with block size 4kb and an intact backup superblock
at block 32
Hi
After a system crash, the superblock of /dev/hda4
(used for not so important data, hence no backup, sigh) is no longer readable.
An attempt to mount that device yields
/mnt # mount -t ext3 /dev/hda4 hda4
mount: wrong fs type, bad option, bad superblock on /dev/hda4,
missing
Greetings Donald,
On Sun, 28 Apr 2002, Donald R. Spoon wrote:
> I have a couple of friends that had similar problems & complaints. In
> one case the "sr" block device was not being loaded, and in the second
> case the "scd0" was not sym-linked to the "sr0" device. In both cases
> they got the
[EMAIL PROTECTED] (Marcin Fusinski) wrote:
Greetings!
I forgot to add that CDRW burns just fine (readable) CDs - the only
porblem is with mounting...
If anyone knows what causes those probs, please let me know. Thanks.
Regards,
Martin,
I have a couple of friends that had similar problems
Greetings!
I forgot to add that CDRW burns just fine (readable) CDs - the only
porblem is with mounting...
If anyone knows what causes those probs, please let me know. Thanks.
Regards,
--
Marcin Fusinski qrchaque(at)master(dot)pl
UIN: 127801366 GG: 1854531
--
To UNSUBSCRIBE, e
Greetings!
I noticed (yesterday) that mounting (either /cdrom or /cdrw) gives error
message:
mount: wrong fs type, bad option, bad superblock on /dev/cdrw,
or too many mounted file systems
The drives are: old PIO-4 LG CDROM and TEAC616EB CDRW.
And more info:
Attached scsi CD-ROM sr0 at
On Tue, Aug 28, 2001 at 01:41:37PM +1000, Serge Rey wrote:
> ...
>
> i tried a reboot, to see if i could get into the windows partition but
> when i selected that stanza in lilo, lilo hangs at "L?"
> (again, this used to work prior to this recent problem).
>
> i can boot into linux just fine.
T
On Tue, Aug 28, 2001 at 01:58:39PM +1000, Tony Bartholomaeus wrote:
> Does -
>
> mount -t vfat /dev/hda1 /win98
nope:
[EMAIL PROTECTED]:~$ sudo mount -t vfat /dev/hda1 /win98
mount: wrong fs type, bad option, bad superblock on /dev/hda1,
or too many mounted file systems
--
Serg
Does -
mount -t vfat /dev/hda1 /win98
- work?
> -Original Message-
> From: Serge Rey [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 28 August 2001 1:42 PM
> To: debian-user@lists.debian.org
> Subject: bad superblock recovery help?
>
>
>
> here is a strange
on (cause it is where i store all my
mp3 files) and got the following message:
[EMAIL PROTECTED]:~$ mount /win98
mount: wrong fs type, bad option, bad superblock on /dev/hda1,
or too many mounted file systems
in the past this mount worked fine.
since this previously worked, i'm ruli
>> installed under sid=unstable the new kernel with the latest
>> lilo now i can't boot the normal way, it stops when mounting
>> my root partition, with an superblock error, and the option
>> to maintain with the root password, or strg+d to boot normal
>> way. with strg+d it reboots, and with the
>> installed under sid=unstable the new kernel with the
>> latest lilo now i can't boot the normal way, it stops
>> when mounting my root partition, with an superblock
>> error, and the option to maintain with the root
>> password, or strg+d to boot normal way. with strg+d
>> it reboots, and with t
installed under sid=unstable the new kernel with
the latest lilo
now i can't boot the normal way, it stops when
mounting my root partition, with an superblock error, and the option to maintain
with the root password, or strg+d to boot normal way. with strg+d it reboots,
and with the password
From: Mo Oishi <[EMAIL PROTECTED]>
> e2fsck -b 8193
>
> Attempts to read block from filesystem resulted in short read while trying
> to open /dev/hda2...
> cfdisk tells me that this still is a legit filesystem/partition.
The "short read" message says there _is_ a problem with the partition table
Hello, all,
I'm having unexplained problems booting my debian box. I shutdown linux
yesterday morning and booted win 95 from /dev/hda1. When I tried to reboot
linux (/dev/hda2) in the evening using lilo, I got nothing but the
"starting linux" statement. I used the base rsc1440.bin disk (my boot
fl
21 matches
Mail list logo
