On 2022-09-07, Zé Loff <[email protected]> wrote:
>
> On Wed, Sep 07, 2022 at 06:14:59PM +0100, Zé Loff wrote:
>> On Wed, Sep 07, 2022 at 06:42:54PM +0200, Danny König wrote:
>> > Hi,
>> >
>> > first time I need your support regarding a broken softraid0. After a
>> > normal reboot the softraid0 (RAID 1, two disks sd0 and sd1, softraid0
>> > as sd5) was broken what means no mounts, no nothing.
>> >
>> >
>> > root@core-fs:~ => disklabel -p g /dev/sd0c
>> > # /dev/sd0c:
>> > type: SCSI
>> > disk: SCSI disk
>> > label: ST16000NM003G-2K
>> > duid: b1c256d6dc122fa7
>> > flags:
>> > bytes/sector: 512
>> > sectors/track: 63
>> > tracks/cylinder: 255
>> > sectors/cylinder: 16065
>> > cylinders: 1945332
>> > total sectors: 31251759104 # total bytes: 14902.0G
>> > boundstart: 0
>> > boundend: 31251759104
>> > drivedata: 0
>> > 16 partitions:
>> > # size offset fstype [fsize bsize cpg]
>> > a: 14902.0G 0 RAID
>> > c: 14902.0G 0 unused
This looks like a bad layout to me. I do not think that the offset
should have been set to 0.
> Actually, I'll just quote scan_ffs's manpage:
>
> 1. Panic. You usually do so anyways, so you might as well get it over
> with. Just don't do anything stupid. Panic away from your
> machine. Then relax, and see if the steps below won't help you
> out.
You missed a bit, 3rd paragraph of DESCRIPTION.
scan_ffs works only on FFS file systems, not FFS2 file systems.
--
Please keep replies on the mailing list.
