On this page
A live session is the temporary Ubuntu desktop running from the USB. It is a safe place to ask two questions before installation:
- Does the everyday hardware work well enough?
- Can Ubuntu see the internal drive you intend to use?
Most live-session changes disappear after shutdown. That is useful for testing, but it means this session is not your finished system.
Test hardware one item at a time
Live-session hardware checklist
- Display resolution is readable and scaling is sensible.
- The desktop remains stable while windows move and resize.
- Brightness keys and display controls respond.
- Keyboard letters, numbers, punctuation, and chosen layout are correct.
- Touchpad, mouse, clicking, scrolling, and gestures needed by you work.
- Wi-Fi finds networks and connects; Ethernet works when relevant.
- Bluetooth can be enabled and detects a test device when needed.
- Speakers and headphone output play sound.
- The microphone and webcam are detected in a suitable test application.
- Suspend and resume work without a frozen or black display.
- Battery level is reported on a laptop.
- An external monitor and required USB ports work.
- The internal SSD or hard drive is visible and has the expected model and capacity.
Failure in one item does not automatically mean Ubuntu can never work. Drivers, firmware updates, or a newer kernel may help. Record the exact device model and symptom. A missing internal disk, however, is a stop condition because the installer cannot safely target a disk it cannot see.
Open Terminal without copying the prompt
The Terminal is a text window where a command asks the system to do something. Open it from the application search or with Ctrl + Alt + T.
You may see a prompt similar to this:
Example prompt — do not typemiyuru@miyuru-7400:~$
The prompt identifies the user, computer, and current folder. It ends with $ for an ordinary user. Do not type or copy the prompt. The tilde ~ is a short name for the current user’s home folder; you do not need to use it in this check.
lsblk -o NAME,SIZE,TYPE,FSTYPE,MODEL,MOUNTPOINTS
Type the line exactly, then press Enter. It is a read-only listing command. It does not format or partition anything.
lsblkmeans “list block devices,” such as disks and their partitions.-ois an option that selects output columns. The hyphen marks an option.- The comma-separated names request these columns:
NAME: the system’s current device name.SIZE: approximate capacity.TYPE: disk, partition, or another block-device type.FSTYPE: filesystem such asvfatwhen known.MODEL: manufacturer or product model when reported.MOUNTPOINTS: folders where a filesystem is currently attached.
Read a USB-only result
Here is an anonymized result based on a real beginner situation. It is sample output, not another command:
Sample output — do not type
NAME SIZE TYPE FSTYPE MODEL MOUNTPOINTS
sda 114.6G disk SanDisk
└─sda1 114.6G part vfat /cdromSeveral clues identify this as the installation USB:
- SanDisk matches the physical USB’s manufacturer.
- 114.6G is consistent with a USB sold around 128 GB; manufacturers and operating systems display capacity differently.
- Its partition uses vfat, a filesystem commonly present on boot media.
- The partition is mounted at
/cdrom, which is strong context that the live system started from it.
The leading slash in /cdrom means the folder begins at the top, or root, of Ubuntu’s filesystem. It does not mean “a drive letter” as it would in Windows.
What is missing matters just as much: there is no expected 256 GB, 512 GB, or 1 TB internal disk in this sample.
Device names are clues, not identities
/dev/sda is not always the USB and is not always the internal disk. It is a name assigned for this boot. An internal NVMe SSD often appears as nvme0n1; an internal SATA disk might appear as sda; USB names can be sda, sdb, or something else depending on what was detected first.
Use a bundle of evidence:
- Model.
- Capacity.
- Which physical devices are connected.
- Filesystem and partitions.
- Mount point.
- Whether the entry matches the internal-drive details recorded before boot.
Never format a device based on its name alone.
Common mistakes and recovery
Copying the prompt with the command. Run only the lsblk line. If the shell says a username or hostname is not a command, clear the line and type only the command.
Assuming size must equal the package label. A 128 GB device can appear around 114–123 GB depending on units and layout. Match model and context too.
Treating a partition as a second disk. Indented entries such as sda1 belong to the disk above them.
Opening the installer because the desktop works. Hardware testing is not complete until internal storage is visible and identified.
Ignoring a failed suspend test. Resume failures can affect everyday reliability. Record them and seek model-specific support before committing the computer.
Practice
Knowledge check
In the sample, name four facts that point to the installer USB: SanDisk model, roughly 115 GB
capacity, VFAT partition, and /cdrom mount point. Then explain why sda alone is insufficient.
What to learn next
If the internal disk is missing, continue immediately to Ubuntu Installer Shows Only the USB Drive. If it is visible and hardware works, read Ubuntu Installation Options Explained before opening the installer.