If any errors have been found during fsck then most probably that
numbers
changed due to filesystem internal error. The reason for such error may
be
for example, incorrect system shutdown - such as switching the power off
without issuing 'halt' command before it.'
Of course, it is possible that th
On Lun 28 Oct 2002 09:47, Alexey Fadyushin wrote:
> It seems that not only ownership but also the device major and minor
> numbers
> for some of your disks have changed. You could not fsck or remount your
> /dev/hda2
> because /dev/hda2 device entry in /dev is no longer points to your hard
> disk d
It seems that not only ownership but also the device major and minor
numbers
for some of your disks have changed. You could not fsck or remount your
/dev/hda2
because /dev/hda2 device entry in /dev is no longer points to your hard
disk due
to changed major/minor. These numbers for /dev/hda2 should
On Lun 28 Oct 2002 08:57, Alexey Fadyushin wrote:
> You can change group for that devices with the command
>
> chown :disk /dev/hda*
I can't. It's read-only.
> If the file system with /dev directory is mounted readonly,
> you will need to remounyt it read-write before changing group.
> To remount
You can change group for that devices with the command
chown :disk /dev/hda*
If the file system with /dev directory is mounted readonly,
you will need to remounyt it read-write before changing group.
To remount file system read-only use the folloeing command
mount -wno remount /
Alexey Fadyushi
I'm having problems with a PC that was working great, and one day I booted it
and it couldn't start swap, nor could it remount root in rw mode:
Letting it boot and checking the /dev/ tree I get this:
[root@ultra8 root]# ls -l /dev/hda*
brw-rw1 root disk 3, 0 abr 11 2002 /dev
