• 0 Posts
  • 3 Comments
Joined 3 years ago
Cake day: June 15th, 2023
  • y0din@lemmy.worldtoSelfhosted@lemmy.world•ChatGPT fried my drive!?English
    34·
    11 hours ago

    Right now there isn’t enough information to conclude that the drive is “bricked”.

    sg_format on a SAS drive with DIF enabled can absolutely make the disk temporarily unusable to the OS if the format parameters no longer match what the HBA/driver expects, but that is very different from a dead drive.

    To make any determination, more data is required. At minimum (boot with a live Linux USB drive if you are unable to get to this information):

    Please provide verbatim output from:

    • dmesg -T (from boot and when the drive is detected)
    • sblk -o NAME,MODEL,SIZE,PHY-SeC,LOG-SeC
    • fdisk -l /dev/sdX
    • sg_inq /dev/sdX
    • sg_readcap -l /dev/sdX
    • sg_modes -a /dev/sdX

    Also specify:

    • Exact drive model
    • HBA model and firmware
    • Kernel version / distro
    • Whether the controller supports DIF/DIX (T10 PI)
    • Whether other identical drives still work in the same slot/cable

    Common possibilities (none can be confirmed without logs):

    • Drive formatted with DIF enabled but HBA/OS not configured for it
    • Logical/physical block size mismatch (e.g. 520/528 vs 512/4096)
    • Format still in progress or left the drive in a non-ready state
    • Mode pages changed that Linux does not like by default

    Things that are usually recoverable on SAS drives:

    • Re-formatting with correct sector size and DIF disabled
    • Clearing protection information
    • Power-cycling the drive after format completion
    • Formatting from a controller that fully supports the drive’s feature set

    Actual permanent bricking from sg_format alone is rare unless firmware flashing or vendor-specific commands were involved.

    Until logs are posted, all anyone can honestly say is:

    The drive is not currently usable, but there is no evidence yet that it is permanently damaged.

    If you can share this information it might be possible to get the drive back online, though I make no promises.

    (edit typos)

  • y0din@lemmy.worldtoAsk Lemmy@lemmy.world•Is anyone else suddenly waking up super early for no reason?
    5·
    8 months ago

    It could definitely be stress-related, especially if you had a particularly bad night of sleep before this started.

    When you don’t sleep well, your body can reset its cortisol production cycle. Cortisol—the hormone tied to stress and alertness—typically starts rising in the early hours of the morning, around 3–4 a.m., as part of a normal circadian rhythm.

    But if you’re under even mild or subconscious stress, that spike can happen earlier or be stronger than usual, causing you to wake up prematurely and feel too alert to fall back asleep.

    It’s like your body’s stuck in a “high alert” mode even if nothing obvious is triggering it.

    Could be the birds that have already been mentioned as well, I am no expert, nor medical trained, but this reason is more common than you might think when waking up early. It’s the same reason you might find yourself waking before the alarm when you really need to be on time, like before going on vacation and you cannot miss your flight.

    Here is a link to one of many in regards to sleep and cortisol

    https://sleepdoctor.com/pages/health/cortisol

    (edit: added part of the sentence that got lost before posting and figured I might add a link if someone wants to read more)