Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
T
tails
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 960
    • Issues 960
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 11
    • Merge Requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #16748

Closed
Open
Created May 23, 2019 by anonym@anonymMaintainer

create-usb-image-from-iso uses the wrong version of syslinux

Originally created by @anonym on #16748 (Redmine)

(This is only about my local runs since the results on Jenkins are broken because earlier steps fail, and this feature has inter-scenario dependencies.)

The step “Booting Tails from a USB drive upgraded from USB with persistence enabled” fails with booting looking like this:

I’ve causally looked at the volume in a VM, and it has the appropriate partitions, so only the boot bits seem to have been corrupted (not investigated that at all yet).

I cannot reproduce this manually: I installed to USB, cloned the volume, then booted one of them and upgraded the other, and that worked fine, which is essentially what the test suite does (it doesn’t copy, but redoes the same exact installation (we don’t supply an --old-iso so the same ISO will be used) so it shouldn’t matter).

Feature Branch: bugfix/16748-use-syslinux-from-chroot

Attachments

  • booterror.png

Related issues

Edited May 21, 2020 by anonym
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tails_3.14.1
Milestone
Tails_3.14.1 (Past due)
Assign milestone
Time tracking
None
Due date
None