hello all, I hit / is full for my smartos, how to find out the core dump? anyone could advice?

check /root, 9 times out of 10 it's because you put something there

core dumps are configured to go into a separate file system so it won't be those

there is nothing under /root dir

the /root is empty, nothing is there

ncdu is available in the tools repo, that can be useful to see exactly where disk usage is, using e.g. "ncdu -x /" so that it only shows usage in the ramdisk

is there any core dump that fill the ramdisk space?

13:18 < jperkin> core dumps are configured to go into a separate file system so it won't be those

everything on SmartOS is configured so that writes do not go to the ramdisk, have a think about anything you have done in the GZ recently that may have written a file to somewhere inside it

okay, thank you jperkin, I’m going to check it with ncdu

you can doublecheck the output of coreadm

tsoome: thank you for the advice

Neat, a lot of people.

I've been wanting to evaluate SmartOS, but I'm struggling a bit with the instructions about non-interactive install ... they're telling me to put a file in `private/answers.json` on the installation media, but I can't tell how to mount said media to be able to make that file.

Which filesystem is the USB image?

(or can I simply add a random partition and make a directory there or something?)

DarkUranium: on the pcfs partition on the USB stick, though honestly for something I'm going to install once and then leave for possibly decades it only takes a few minutes to follow the install instructions and then I'm sure I did everything right

It's more a practical issue of not always having a KVM interface. (mostly just an issue of my test computer[s], but)

Basically, I don't have a display of any kind on the PC ATM. I could hook it up, but.

(I'm testing this on a random home PC)

Though I guess I'll just do that, heh.

jperkin: Oddly enough, though, all the various tools seem to be struggling with the partition table, reporting it as corrupt. Only gdisk managed to figure out the layout so far.

(and even that is reporting the GPT portion as "damaged")

that's odd, I mean it's been >10 years since I installed mine but I'm pretty sure it just mounted automatically after writing on macOS

hopefully someone else has some more recent experience ;)

gdisk gives me a "Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended."

And it was the only one that even managed to give me a partition table.

So something's definitely funky.

(I tried all sorts of tools, even Windows' diskpart and stuff)

Right now, I'm extracting it with dd so that I can mount the loader partition with `mount` xD

(FreeBSD's mount doesn't have an `-o offset=...`)

jperkin: Dunno who needs to know, but gdisk has identified 4 problems with the partition table. For one, it's not GPT-compliant.

Using the tool's recovery options has exposed the partitions to FreeBSD, finally (so that I get /dev/da0p{N} instead of just /dev/da0)

I'm pointing it out because it smells like a bug to me.

It's entirely possible that the FreeBSD GPT code is pickier than ours.

Definitely. Though like I said, I also tried in Windows (I didn't have a Linux machine handy to test on)

Though TBF, Windows is .... Windows.

sommerfeld: I suspect the core issue might've been the failing CRC checks. But gdisk fixed everything at once by using the backup table, so I can't really isolate that one issue.

Nor do I care to, TBH. It works now ^^