* [9front] stuck on boot
@ 2024-09-27 1:12 william
2024-09-27 4:47 ` Sean Hinchee
0 siblings, 1 reply; 5+ messages in thread
From: william @ 2024-09-27 1:12 UTC (permalink / raw)
To: 9front
This has been working fine for a few months. How do I rescue this?... Runs forever
998M memory: 311M kernel data, 687M user, 1937M swap
bootfs: Fri May 10 04:45:03 GMT 2024
fingerprint: e719fc4a4a78fcde0b8fb5d649046087396a970c
nusb/usbd: no hubs
/dev/sdC0: QEMU HARDDISK
/dev/sdC0/9fat dos
/dev/sdC0/data
/dev/sdC0/fscache cwfs64x
/dev/sdC0/fsworm
/dev/sdC0/nvram
/dev/sdC0/other
/dev/sdC0/plan9
/dev/sdD0: QEMU DVD-ROM
bootargs is (tcp, tls, il, local!device)[local!/dev/sdC0/fscache -a tcp!*!564]
current fs is "main"
12 uids read, 3 groups used
63-bit cwfs as of Thu May 9 23:43:48 2024
last boot Thu Sep 26 19:48:46 2024
checktag pc=210e58 n(4) tag/path=Tnone/0; expected Tsuper/2
w"/dev/sdC0/fsworm" block 56637 WORM SUPER BLOCK READ FAILED
checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(dcde) tag/path=Tnone/0; expected Tdir/278
checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(ddce) tag/path=Tnone/0; expected Tdir/8097
init: exec error: directory entry not found: '/bin/rc'
init: rc exit status: init 298: exec
checktag pc=210e58 n(4) tag/path=Tnone/0; expected Tsuper/2
w"/dev/sdC0/fsworm" block 56637 WORM SUPER BLOCK READ FAILED
checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(dcde) tag/path=Tnone/0; expected Tdir/278
checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(ddce) tag/path=Tnone/0; expected Tdir/8097
init: exec error: directory entry not found: '/bin/rc'
init: rc exit status: init 298: exec
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9front] stuck on boot
2024-09-27 1:12 [9front] stuck on boot william
@ 2024-09-27 4:47 ` Sean Hinchee
2024-09-27 6:09 ` william
0 siblings, 1 reply; 5+ messages in thread
From: Sean Hinchee @ 2024-09-27 4:47 UTC (permalink / raw)
To: 9front
Looks like cwfs disk or worm corruption to me
If you boot from a live image can you mount the fs manually without issue?
S
On 9/26/24 6:12 PM, william@thinktankworkspaces.com wrote:
> This has been working fine for a few months. How do I rescue this?... Runs forever
>
> 998M memory: 311M kernel data, 687M user, 1937M swap
> bootfs: Fri May 10 04:45:03 GMT 2024
> fingerprint: e719fc4a4a78fcde0b8fb5d649046087396a970c
> nusb/usbd: no hubs
>
> /dev/sdC0: QEMU HARDDISK
> /dev/sdC0/9fat dos
> /dev/sdC0/data
> /dev/sdC0/fscache cwfs64x
> /dev/sdC0/fsworm
> /dev/sdC0/nvram
> /dev/sdC0/other
> /dev/sdC0/plan9
> /dev/sdD0: QEMU DVD-ROM
> bootargs is (tcp, tls, il, local!device)[local!/dev/sdC0/fscache -a tcp!*!564]
> current fs is "main"
> 12 uids read, 3 groups used
> 63-bit cwfs as of Thu May 9 23:43:48 2024
> last boot Thu Sep 26 19:48:46 2024
> checktag pc=210e58 n(4) tag/path=Tnone/0; expected Tsuper/2
> w"/dev/sdC0/fsworm" block 56637 WORM SUPER BLOCK READ FAILED
> checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(dcde) tag/path=Tnone/0; expected Tdir/278
> checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(ddce) tag/path=Tnone/0; expected Tdir/8097
> init: exec error: directory entry not found: '/bin/rc'
> init: rc exit status: init 298: exec
>
>
>
> checktag pc=210e58 n(4) tag/path=Tnone/0; expected Tsuper/2
> w"/dev/sdC0/fsworm" block 56637 WORM SUPER BLOCK READ FAILED
> checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(dcde) tag/path=Tnone/0; expected Tdir/278
> checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(ddce) tag/path=Tnone/0; expected Tdir/8097
> init: exec error: directory entry not found: '/bin/rc'
> init: rc exit status: init 298: exec
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9front] stuck on boot
2024-09-27 4:47 ` Sean Hinchee
@ 2024-09-27 6:09 ` william
2024-09-28 21:51 ` william
0 siblings, 1 reply; 5+ messages in thread
From: william @ 2024-09-27 6:09 UTC (permalink / raw)
To: 9front
My ignorance kind of shows. I'm not sure how to do that. Its a qemu image.
I can't print the offset so im not sure what to do
mount doesn't work including guestmount
sudo guestmount -a 9front1.img -i --ro /mnt/plan9
guestmount: no operating system was found on this disk
ubuntu@ip-10-0-2-79:~$ sudo mount -t vfat -o loop,offset=512 9front1.img /tmp/plan9
mount: /tmp/plan9: wrong fs type, bad option, bad superblock on /dev/loop10, missing codepage or helper progra
ubuntu@ip-10-0-2-79:~$ fdisk -l -o Device,Start 9front1.img
Disk 9front1.img: 1.68 GiB, 1805647872 bytes, 3526656 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
I tried to break out of it using !rc at bootprompt and not sure what I can do next.
I might be able to build another qemu image and load initialize 9front then mount the local file sytem
and try to access the damaged image. I just don't want to loose the data. Any way I can rescue?
Thoughts?
Quoth Sean Hinchee <henesy.dev@gmail.com>:
> Looks like cwfs disk or worm corruption to me
>
> If you boot from a live image can you mount the fs manually without issue?
>
> S
>
> On 9/26/24 6:12 PM, william@thinktankworkspaces.com wrote:
> > This has been working fine for a few months. How do I rescue this?... Runs forever
> >
> > 998M memory: 311M kernel data, 687M user, 1937M swap
> > bootfs: Fri May 10 04:45:03 GMT 2024
> > fingerprint: e719fc4a4a78fcde0b8fb5d649046087396a970c
> > nusb/usbd: no hubs
> >
> > /dev/sdC0: QEMU HARDDISK
> > /dev/sdC0/9fat dos
> > /dev/sdC0/data
> > /dev/sdC0/fscache cwfs64x
> > /dev/sdC0/fsworm
> > /dev/sdC0/nvram
> > /dev/sdC0/other
> > /dev/sdC0/plan9
> > /dev/sdD0: QEMU DVD-ROM
> > bootargs is (tcp, tls, il, local!device)[local!/dev/sdC0/fscache -a tcp!*!564]
> > current fs is "main"
> > 12 uids read, 3 groups used
> > 63-bit cwfs as of Thu May 9 23:43:48 2024
> > last boot Thu Sep 26 19:48:46 2024
> > checktag pc=210e58 n(4) tag/path=Tnone/0; expected Tsuper/2
> > w"/dev/sdC0/fsworm" block 56637 WORM SUPER BLOCK READ FAILED
> > checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(dcde) tag/path=Tnone/0; expected Tdir/278
> > checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(ddce) tag/path=Tnone/0; expected Tdir/8097
> > init: exec error: directory entry not found: '/bin/rc'
> > init: rc exit status: init 298: exec
> >
> >
> >
> > checktag pc=210e58 n(4) tag/path=Tnone/0; expected Tsuper/2
> > w"/dev/sdC0/fsworm" block 56637 WORM SUPER BLOCK READ FAILED
> > checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(dcde) tag/path=Tnone/0; expected Tdir/278
> > checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(ddce) tag/path=Tnone/0; expected Tdir/8097
> > init: exec error: directory entry not found: '/bin/rc'
> > init: rc exit status: init 298: exec
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9front] stuck on boot
2024-09-27 6:09 ` william
@ 2024-09-28 21:51 ` william
2024-09-28 22:07 ` Romano
0 siblings, 1 reply; 5+ messages in thread
From: william @ 2024-09-28 21:51 UTC (permalink / raw)
To: 9front
I tried to go a little further
bootargs is (tcp, tls, il, local!device)[local!/dev/sdC0/fscache -c] !rc
% cwfs64x -c
config: noauth
auth disabled
config: end
current fs is "main"
12 uids read, 3 groups used
63-bit cwfs as of Thu May 9 23:43:48 2024
last boot Sat Sep 28 16:43:01 2024
checktag pc=210e58 n(4) tag/path=Tnone/0; expected Tsuper/2
w"/dev/sdC0/fsworm" block 56637 WORM SUPER BLOCK READ FAILED
% mount -c /srv/cwfs /n/fscache /dev/sdC0/fscache
mount: mount /n/fscache: attach -- unknown user or failed authentication
I already changed the plan9.ini file to
bootfile=9pc64
bootargs=local!/dev/sdC0/fscache -c
console=0
I did the noauth at the end at the config prompt and it still loops
This is all a pain to do without 'ed' I have to use 'echo' and 'cat' statements just to build or change
files.
Quoth william@thinktankworkspaces.com:
> My ignorance kind of shows. I'm not sure how to do that. Its a qemu image.
>
> I can't print the offset so im not sure what to do
>
> mount doesn't work including guestmount
>
> sudo guestmount -a 9front1.img -i --ro /mnt/plan9
> guestmount: no operating system was found on this disk
>
>
> ubuntu@ip-10-0-2-79:~$ sudo mount -t vfat -o loop,offset=512 9front1.img /tmp/plan9
> mount: /tmp/plan9: wrong fs type, bad option, bad superblock on /dev/loop10, missing codepage or helper progra
> ubuntu@ip-10-0-2-79:~$ fdisk -l -o Device,Start 9front1.img
> Disk 9front1.img: 1.68 GiB, 1805647872 bytes, 3526656 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
>
> I tried to break out of it using !rc at bootprompt and not sure what I can do next.
>
> I might be able to build another qemu image and load initialize 9front then mount the local file sytem
> and try to access the damaged image. I just don't want to loose the data. Any way I can rescue?
>
> Thoughts?
>
>
>
> Quoth Sean Hinchee <henesy.dev@gmail.com>:
> > Looks like cwfs disk or worm corruption to me
> >
> > If you boot from a live image can you mount the fs manually without issue?
> >
> > S
> >
> > On 9/26/24 6:12 PM, william@thinktankworkspaces.com wrote:
> > > This has been working fine for a few months. How do I rescue this?... Runs forever
> > >
> > > 998M memory: 311M kernel data, 687M user, 1937M swap
> > > bootfs: Fri May 10 04:45:03 GMT 2024
> > > fingerprint: e719fc4a4a78fcde0b8fb5d649046087396a970c
> > > nusb/usbd: no hubs
> > >
> > > /dev/sdC0: QEMU HARDDISK
> > > /dev/sdC0/9fat dos
> > > /dev/sdC0/data
> > > /dev/sdC0/fscache cwfs64x
> > > /dev/sdC0/fsworm
> > > /dev/sdC0/nvram
> > > /dev/sdC0/other
> > > /dev/sdC0/plan9
> > > /dev/sdD0: QEMU DVD-ROM
> > > bootargs is (tcp, tls, il, local!device)[local!/dev/sdC0/fscache -a tcp!*!564]
> > > current fs is "main"
> > > 12 uids read, 3 groups used
> > > 63-bit cwfs as of Thu May 9 23:43:48 2024
> > > last boot Thu Sep 26 19:48:46 2024
> > > checktag pc=210e58 n(4) tag/path=Tnone/0; expected Tsuper/2
> > > w"/dev/sdC0/fsworm" block 56637 WORM SUPER BLOCK READ FAILED
> > > checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(dcde) tag/path=Tnone/0; expected Tdir/278
> > > checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(ddce) tag/path=Tnone/0; expected Tdir/8097
> > > init: exec error: directory entry not found: '/bin/rc'
> > > init: rc exit status: init 298: exec
> > >
> > >
> > >
> > > checktag pc=210e58 n(4) tag/path=Tnone/0; expected Tsuper/2
> > > w"/dev/sdC0/fsworm" block 56637 WORM SUPER BLOCK READ FAILED
> > > checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(dcde) tag/path=Tnone/0; expected Tdir/278
> > > checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(ddce) tag/path=Tnone/0; expected Tdir/8097
> > > init: exec error: directory entry not found: '/bin/rc'
> > > init: rc exit status: init 298: exec
> >
>
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9front] stuck on boot
2024-09-28 21:51 ` william
@ 2024-09-28 22:07 ` Romano
0 siblings, 0 replies; 5+ messages in thread
From: Romano @ 2024-09-28 22:07 UTC (permalink / raw)
To: 9front
I am pretty sure this has been brought up before. You may want to search the archives both on 9front and 9fans. IIRC you want to start with -C to drop you in config mode and then recover main. But the devil is in the details so doing a search for WORM SUPER BLOCK READ FAILED might dreg something up.
On Sat, Sep 28, 2024, at 2:51 PM, william@thinktankworkspaces.com wrote:
> I tried to go a little further
>
> bootargs is (tcp, tls, il, local!device)[local!/dev/sdC0/fscache -c] !rc
> % cwfs64x -c
> config: noauth
> auth disabled
> config: end
> current fs is "main"
> 12 uids read, 3 groups used
> 63-bit cwfs as of Thu May 9 23:43:48 2024
> last boot Sat Sep 28 16:43:01 2024
> checktag pc=210e58 n(4) tag/path=Tnone/0; expected Tsuper/2
> w"/dev/sdC0/fsworm" block 56637 WORM SUPER BLOCK READ FAILED
>
> % mount -c /srv/cwfs /n/fscache /dev/sdC0/fscache
> mount: mount /n/fscache: attach -- unknown user or failed authentication
>
> I already changed the plan9.ini file to
>
> bootfile=9pc64
> bootargs=local!/dev/sdC0/fscache -c
> console=0
>
> I did the noauth at the end at the config prompt and it still loops
>
> This is all a pain to do without 'ed' I have to use 'echo' and 'cat'
> statements just to build or change
> files.
>
>
> Quoth william@thinktankworkspaces.com:
>> My ignorance kind of shows. I'm not sure how to do that. Its a qemu image.
>>
>> I can't print the offset so im not sure what to do
>>
>> mount doesn't work including guestmount
>>
>> sudo guestmount -a 9front1.img -i --ro /mnt/plan9
>> guestmount: no operating system was found on this disk
>>
>>
>> ubuntu@ip-10-0-2-79:~$ sudo mount -t vfat -o loop,offset=512 9front1.img /tmp/plan9
>> mount: /tmp/plan9: wrong fs type, bad option, bad superblock on /dev/loop10, missing codepage or helper progra
>> ubuntu@ip-10-0-2-79:~$ fdisk -l -o Device,Start 9front1.img
>> Disk 9front1.img: 1.68 GiB, 1805647872 bytes, 3526656 sectors
>> Units: sectors of 1 * 512 = 512 bytes
>> Sector size (logical/physical): 512 bytes / 512 bytes
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>>
>> I tried to break out of it using !rc at bootprompt and not sure what I can do next.
>>
>> I might be able to build another qemu image and load initialize 9front then mount the local file sytem
>> and try to access the damaged image. I just don't want to loose the data. Any way I can rescue?
>>
>> Thoughts?
>>
>>
>>
>> Quoth Sean Hinchee <henesy.dev@gmail.com>:
>> > Looks like cwfs disk or worm corruption to me
>> >
>> > If you boot from a live image can you mount the fs manually without issue?
>> >
>> > S
>> >
>> > On 9/26/24 6:12 PM, william@thinktankworkspaces.com wrote:
>> > > This has been working fine for a few months. How do I rescue this?... Runs forever
>> > >
>> > > 998M memory: 311M kernel data, 687M user, 1937M swap
>> > > bootfs: Fri May 10 04:45:03 GMT 2024
>> > > fingerprint: e719fc4a4a78fcde0b8fb5d649046087396a970c
>> > > nusb/usbd: no hubs
>> > >
>> > > /dev/sdC0: QEMU HARDDISK
>> > > /dev/sdC0/9fat dos
>> > > /dev/sdC0/data
>> > > /dev/sdC0/fscache cwfs64x
>> > > /dev/sdC0/fsworm
>> > > /dev/sdC0/nvram
>> > > /dev/sdC0/other
>> > > /dev/sdC0/plan9
>> > > /dev/sdD0: QEMU DVD-ROM
>> > > bootargs is (tcp, tls, il, local!device)[local!/dev/sdC0/fscache -a tcp!*!564]
>> > > current fs is "main"
>> > > 12 uids read, 3 groups used
>> > > 63-bit cwfs as of Thu May 9 23:43:48 2024
>> > > last boot Thu Sep 26 19:48:46 2024
>> > > checktag pc=210e58 n(4) tag/path=Tnone/0; expected Tsuper/2
>> > > w"/dev/sdC0/fsworm" block 56637 WORM SUPER BLOCK READ FAILED
>> > > checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(dcde) tag/path=Tnone/0; expected Tdir/278
>> > > checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(ddce) tag/path=Tnone/0; expected Tdir/8097
>> > > init: exec error: directory entry not found: '/bin/rc'
>> > > init: rc exit status: init 298: exec
>> > >
>> > >
>> > >
>> > > checktag pc=210e58 n(4) tag/path=Tnone/0; expected Tsuper/2
>> > > w"/dev/sdC0/fsworm" block 56637 WORM SUPER BLOCK READ FAILED
>> > > checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(dcde) tag/path=Tnone/0; expected Tdir/278
>> > > checktag pc=2010d9 cw"/dev/sdC0/fscache"w"/dev/sdC0/fsworm"(ddce) tag/path=Tnone/0; expected Tdir/8097
>> > > init: exec error: directory entry not found: '/bin/rc'
>> > > init: rc exit status: init 298: exec
>> >
>>
>>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2024-09-28 22:09 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-09-27 1:12 [9front] stuck on boot william
2024-09-27 4:47 ` Sean Hinchee
2024-09-27 6:09 ` william
2024-09-28 21:51 ` william
2024-09-28 22:07 ` Romano
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).