3 ms·

Yes, during the very first day! Without any power interrupts during OS reinstall.( see here https://news.ycombinator.com/item?id=26203799 https://news.ycombinat

Yes, during the very first day! Without any power interrupts during OS reinstall.( see here https://news.ycombinator.com/item?id=26203799 https://news.ycombinator.com/item?id=26203799) I think Disk Utility in recovery partition has some serious bugs and it can make it 'not bootable'

shawnz 6y ago
I believe you could intentionally make it not bootable using Disk Utility if you delete the firmware partition (thus requiring a DFU mode recovery) but that is an expected behavior
- lovelyviking 6y ago
  You could also delete firmware partition without such intent because Disk Utility will hang and do it for you, which is less expected I believe.
  - shawnz 6y ago
    Presumably there is a remote chance of the firmware being unintentionally destroyed by crashing software on any computer system.
    - lovelyviking 6y ago
      Presumably it's a very reproducible bug during very basic operation but with easiness of getting 'healthy' supply of COVID while accessing another Mac in the repair-shop I would rather not play with it to find out more unless Apple sends me another 20 Macs and pays a lot for this headache.
      - shawnz 6y ago
        Maybe it is easily reproducible, and that would certainly be concerning (at least until the issues are patched). But there's no reason to believe that based on one person's singular occurrence of the bug. I hope you get a chance to repro the issue eventually so that we can all benefit. Eventually it will be possible to do the DFU restore from non-OSX systems using idevicerestore, so that should make the testing more convenient.
        lovelyviking 6y ago
        Honestly I do not observe any 'concerning' here, I've just get downvoted for sharing facts. I hope I would not 'get a chance' to reproduce it because that would mean my work would stop again. I could easily reproduce it with another Mac but I don't have one. And my previous one have gracefully failed completely. ( https://news.ycombinator.com/item?id=25809097 https://news.ycombinator.com/item?id=25809097) >But there's no reason to believe that based on one person's singular occurrence of the bug. Some times it depends which person it is. With all modesty I can observe tendencies with Apple bugs for some years now. There are very obvious for me reasons why those bugs appear and why they would appear more. I've got too much of bugs and I've started to talk about some of them because I just can't stand it. Apple should be Way better then this and for me it seems like no one really cares too much. I do care. Product should be done with some love for goodness sake...
        deleted 6y ago
        [deleted]
        shawnz 6y ago
        > With all modesty I can observe tendencies with Apple bugs for some years now. There are very obvious for me reasons why those bugs appear and why they would appear more. So then there are really two points you are trying to make here: M1 has a buggy boot process, but really more importantly is that Apple's product quality has been declining as a general trend. Maybe the latter is true, I don't know (I've never owned an Apple computer prior to the M1). And I don't want to diminish that issue. But I don't think it is fair to assume everyone will have the bugs you had just because you believe their product quality is declining. Of course if you assume every bug you face is a typical occurrence then it will only reinforce your existing notions about the product quality, without really helping anyone else to get informed about the true state of the product.
        lovelyviking 6y ago
        >without really helping anyone else to get informed about the true state of the product. I believe this is exactly what I am trying to do: Helping anyone else to get informed about the true state of the product. And I want it to be fixed and gladly report about it.
Maxious 6y ago
> Don’t ever format a drive of M1 Macs from recovery mode > Because Apple doesn’t put a warning alerting that it doesn’t really format a drive and Big Sur installer is stupid and it doesn’t see it as a “clean” drive but it see the “Data” Volume and it tries to find a user to authorize the installation, but since the drive has no users, it fails. https://news.ycombinator.com/item?id=26177263 https://news.ycombinator.com/item?id=26177263
- xenadu02 6y ago
  While the bug is unfortunate it is also easily avoided: always delete a volume group together. Don't leave some volumes from the group laying around.

shawnz 6y ago

I believe you could intentionally make it not bootable using Disk Utility if you delete the firmware partition (thus requiring a DFU mode recovery) but that is an expected behavior

lovelyviking 6y ago
You could also delete firmware partition without such intent because Disk Utility will hang and do it for you, which is less expected I believe.
- shawnz 6y ago
  Presumably there is a remote chance of the firmware being unintentionally destroyed by crashing software on any computer system.
  - lovelyviking 6y ago
    Presumably it's a very reproducible bug during very basic operation but with easiness of getting 'healthy' supply of COVID while accessing another Mac in the repair-shop I would rather not play with it to find out more unless Apple sends me another 20 Macs and pays a lot for this headache.
    - shawnz 6y ago
      Maybe it is easily reproducible, and that would certainly be concerning (at least until the issues are patched). But there's no reason to believe that based on one person's singular occurrence of the bug. I hope you get a chance to repro the issue eventually so that we can all benefit. Eventually it will be possible to do the DFU restore from non-OSX systems using idevicerestore, so that should make the testing more convenient.
      - lovelyviking 6y ago
        Honestly I do not observe any 'concerning' here, I've just get downvoted for sharing facts. I hope I would not 'get a chance' to reproduce it because that would mean my work would stop again. I could easily reproduce it with another Mac but I don't have one. And my previous one have gracefully failed completely. ( https://news.ycombinator.com/item?id=25809097 https://news.ycombinator.com/item?id=25809097) >But there's no reason to believe that based on one person's singular occurrence of the bug. Some times it depends which person it is. With all modesty I can observe tendencies with Apple bugs for some years now. There are very obvious for me reasons why those bugs appear and why they would appear more. I've got too much of bugs and I've started to talk about some of them because I just can't stand it. Apple should be Way better then this and for me it seems like no one really cares too much. I do care. Product should be done with some love for goodness sake...
        deleted 6y ago
        [deleted]
        shawnz 6y ago
        > With all modesty I can observe tendencies with Apple bugs for some years now. There are very obvious for me reasons why those bugs appear and why they would appear more. So then there are really two points you are trying to make here: M1 has a buggy boot process, but really more importantly is that Apple's product quality has been declining as a general trend. Maybe the latter is true, I don't know (I've never owned an Apple computer prior to the M1). And I don't want to diminish that issue. But I don't think it is fair to assume everyone will have the bugs you had just because you believe their product quality is declining. Of course if you assume every bug you face is a typical occurrence then it will only reinforce your existing notions about the product quality, without really helping anyone else to get informed about the true state of the product.
      - lovelyviking 6y ago
        >without really helping anyone else to get informed about the true state of the product. I believe this is exactly what I am trying to do: Helping anyone else to get informed about the true state of the product. And I want it to be fixed and gladly report about it.

Maxious 6y ago

> Don’t ever format a drive of M1 Macs from recovery mode > Because Apple doesn’t put a warning alerting that it doesn’t really format a drive and Big Sur installer is stupid and it doesn’t see it as a “clean” drive but it see the “Data” Volume and it tries to find a user to authorize the installation, but since the drive has no users, it fails. https://news.ycombinator.com/item?id=26177263 https://news.ycombinator.com/item?id=26177263

xenadu02 6y ago
While the bug is unfortunate it is also easily avoided: always delete a volume group together. Don't leave some volumes from the group laying around.