Here's an odd thing: every so often when powering up my #! laptop it won't boot.
The error messages are always variations on the theme of 'no boot device', 'invalid partition table' 'no boot partition' etc.
I boot with a usb stick to check, and sure enough the partition table has been changed to some random configuration. This has occurred maybe half a dozen times this year.
Now, I can hack my way round it in a couple of minutes so it's not a huge headache, but I'm at a loss as to what could be causing this to happen and so curiosity prompts this posting.
If anyone has a suggestion or an inkling of an idea (or if you need more information from me) I'd love to hear from you...
I'll make a guess and say that your partition table is probably changed around by updates to grub or kernel packages (assuming you run no other weird operating system). The issue may arise from using grub-legacy; you could try upgrading to grub2. See the Archlinux wiki for caveats. It might be that you've got an UEFI-enabled system booting from a MBR disk in conjunction with grub-legacy (thread)...
the partition table has been changed to some random configuration.
I demand proof!
Please post the partition tables "before" and "after" this randomisation process you describe:
sudo parted -l
Thanks for the suggestions @twoion.
No UEFI here; 100% BIOS (should keep things simpler, right?!).
No grub-legacy; apt-cache policy reports grub2 installed.
No other weird operating systems either
H_o_a_Stick, I can provide the now (as it should be)
Model: ATA OCZ-ONYX (scsi) Disk /dev/sda: 32.0GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 32.0GB 32.0GB primary ext4 boot
but alas not the messed up one - I didn't think to capture it :8
All I can say is that the partition shrunk by 2.5gb leaving unallocated space at the end and parted complained of 'invalid signature ffff'.
It may occur again tomorrow or not for several weeks - no rhyme nor reason AFAICS...
That sounds more like a hardware problem...
Is the drive old?
I presume it's an SSD.
Yep, it's an SSD, around 2 to 3 years old now.
My first thought was a possible hardware problem too; it's just strange that all can be perfect for weeks on end, no read/write errors or freezes, and then suddenly no boot.
Probably pure coincidence that I pulled it from my other laptop about a year ago, installed it in this current one, put #! on it and since then I've had this issue.
I won't mark this as solved just yet, given the nature of the query, but it may be time to invest in a nice new SSD
They're pretty cheap these days (relatively speaking) and the longevity of the new ones may even exceed a spinning drive.
Oh dear, I predict my spending some hard-earned very soon...
Update (Does anyone care? Probably not 8.( ): New ssd fitted, clean install of #!; we'll see what happens...
If the problem persists your computer is most likely haunted. Call an exorcist
I don't think it would happen again. Head_on_a_Stick was probably right
Last edited by olegabrielz (2014-12-16 14:49:59)
^ Head_on_a_Stick is usually right. (Bell, book and candle at the ready though, just in case...)
I would be really suprised if Linux would even install on the old drive tbh. I had an old Windows drive like that. Too many bad blocks and it's buffers were full so linux said nope. Would be one good way to test if the drive is actually going bad though, now that you have a new one. Just try to reinstall Linux on it and see it parted refuses the drive.
^ That is exactly what I'm doing The old ssd is in my old testing/experimental laptop & running fine at the moment. (In fact it's improved the performance of the old lappy hugely.)
Time will tell...