Changing Kernel in Manjaro Live

Yes, if you look upper I've mentioned that I was able accesing partition through KDE neon with no problem
I tried it again today - again, with zero problems

Then maybe your Manjaro live USB is done wrong? Some programs won't handle correctly Arch systems. Also, some people had luck by simply using different USB sticks.

That's also my current working theory - I am installing systems with external HDD
Previously, no problem but the key difference when I was making live burning with Rufus - Ubuntu-based distros asked for DD mode and I clicked Yes

Rufus never does this with Arch

Is there any other way to make live usb with dd from Windows?

Yup, creating bootable live USB is what causes problems with Manjaro installation (and possibly Arch-based distros in general)
Created live-USB with Fedora (Rufus installed Syslinux) - it is working correctly, I was able to proceed with the installation to disk setup. Everything worked fine

Did you try the current 20.0-rc1 ISOs? They got uploaded yesterday? We ship with kernel 5.6. Also use etcher to burn our ISOs.

@adamcade You will be better off making a separate post rather than posting off-topic in someone else's.

Also, welcome to the forum. When you do post your own, can I suggest you have a read of this How to provide good information in your posts at the moment we have no clue as to what your actual problem is.

3 Likes

Nothing, same error. Used etcher. Live USB is working relatively fine - cannot proceed to drive setup
Here's system info using this command

inxi -Fxxx0
System:
  Host: manjaro-gnome Kernel: 5.6.3-2-MANJARO x86_64 bits: 64 compiler: gcc 
  v: 9.3.0 Desktop: Gnome 3.36.1 wm: gnome-shell dm: GDM 3.34.1 
  Distro: Manjaro Linux 
Machine:
  Type: Desktop Mobo: Gigabyte model: P55-UD3 serial: <root required> 
  BIOS: Award v: F9 date: 06/23/2010 
CPU:
  Topology: Quad Core model: Intel Core i5 760 bits: 64 type: MCP 
  arch: Nehalem rev: 5 L2 cache: 8192 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 22393 
  Speed: 1199 MHz min/max: 1197/2794 MHz boost: enabled Core speeds (MHz): 
  1: 1199 2: 1319 3: 1250 4: 1391 
Graphics:
  Device-1: NVIDIA GF114 [GeForce GTX 560 Ti] vendor: Micro-Star MSI 
  driver: nvidia v: 390.132 bus ID: 01:00.0 chip ID: 10de:1200 
  Display: x11 server: X.org 1.20.8 driver: nvidia compositor: gnome-shell 
  resolution: <xdpyinfo missing> 
  OpenGL: renderer: GeForce GTX 560 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 390.132 
  direct render: Yes 
Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio 
  vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  chip ID: 8086:3b56 
  Device-2: NVIDIA GF114 HDMI Audio vendor: Micro-Star MSI 
  driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0e0c 
  Device-3: BEHRINGER UMC202HD 192k type: USB driver: snd-usb-audio 
  bus ID: 1-2:3 chip ID: 1397:0507 
  Device-4: Alesis VMini type: USB driver: snd-usb-audio bus ID: 5-2:3 
  chip ID: 13b2:00a2 serial: Ver00.10 
  Sound Server: ALSA v: k5.6.3-2-MANJARO 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Gigabyte driver: r8169 v: kernel port: de00 bus ID: 03:00.0 
  chip ID: 10ec:8168 
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: 00:24:1d:d3:4d:f4 
Drives:
  Local Storage: total: 1.66 TiB used: 347.1 MiB (0.0%) 
  ID-1: /dev/sda vendor: Western Digital model: WD3200AAJS-00YZCA0 
  size: 298.09 GiB speed: <unknown> serial: WD-WCAYU3281917 rev: 0A01 
  scheme: MBR 
  ID-2: /dev/sdb vendor: Seagate model: ST31000528AS size: 931.51 GiB 
  speed: 3.0 Gb/s rotation: 7200 rpm serial: 6VPB3CVE rev: CC46 scheme: MBR 
  ID-3: /dev/sdg type: USB vendor: Samsung model: HM500JI size: 465.76 GiB 
  serial: 101A108A00462 scheme: MBR 
Partition:
  ID-1: / size: 11.72 GiB used: 347.1 MiB (2.9%) fs: overlay source: ERR-102 
Sensors:
  System Temperatures: cpu: 41.0 C mobo: N/A gpu: nvidia temp: 45 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 45% 
Info:
  Processes: 219 Uptime: 11m Memory: 15.63 GiB used: 1.56 GiB (10.0%) 
  Init: systemd v: 244 Compilers: gcc: N/A Shell: zsh v: 5.8 
  running in: gnome-terminal inxi: 3.0.37 

And sudo fdisk -l (it freezes after those dev/loop and not going anywhere else)

sudo fdisk -l                                                            
Disk /dev/loop0: 66.5 MiB, 69259264 bytes, 135272 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 637.8 MiB, 668758016 bytes, 1306168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 1.35 GiB, 1444450304 bytes, 2821192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 584.11 MiB, 612483072 bytes, 1196256 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

And sudo -E calamares -d

sudo -E calamares -d                                                 [69]
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
qt5ct: using qt5ct plugin
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
13:00:45 [6]: Calamares::Settings::Settings(const QString&, bool)
    Using Calamares settings file at "/etc/calamares/settings.conf" 
13:00:45 [6]: void Logger::setupLogfile()
    Using log file: "/home/manjaro/.cache/calamares/session.log" 
13:00:45 [6]: void CalamaresApplication::init()
    Calamares version: 3.2.22-1 
13:00:45 [6]: void CalamaresApplication::init()
            languages: "ar, as, ast, be, bg, ca, cs_CZ, da, de, el, en, en_GB, eo, es, es_MX, es_PR, et, eu, fi_FI, fr, gl, he, hi, hr, hu, id, is, it_IT, ja, ko, lt, ml, mr, nb, nl, pl, pt_BR, pt_PT, ro, ru, sk, sl, sq, sr, sr@latin, sv, th, tr_TR, uk, zh_CN, zh_TW" 
13:00:45 [6]: void CalamaresApplication::initQmlPath()
    Using Calamares QML directory "/usr/share/calamares/qml" 
13:00:45 [6]: Calamares::Branding::Branding(const QString&, QObject*)
    Using Calamares branding file at "/usr/share/calamares/branding/manjaro/branding.desc" 
13:00:45 [2]: void Calamares::flavorAndSide(const YAML::Node&, const char*, Calamares::Branding::PanelFlavor&, Calamares::Branding::PanelSide&)
    WARNING:Branding setting for sidebar is missing, using "widget" "left" 
13:00:45 [2]: void Calamares::flavorAndSide(const YAML::Node&, const char*, Calamares::Branding::PanelFlavor&, Calamares::Branding::PanelSide&)
    WARNING:Branding setting for navigation is missing, using "widget" "bottom" 
13:00:45 [2]: Calamares::Branding::Branding(const QString&, QObject*)
    WARNING:Invalid or missing *slideshowAPI* in branding file. 
13:00:45 [2]: Calamares::Branding::Branding(const QString&, QObject*)
    WARNING:the branding component "/usr/share/calamares/branding/manjaro" does not ship translations. 
13:00:45 [6]: Calamares::Branding::Branding(const QString&, QObject*)
    Loaded branding component "manjaro" 
13:00:45 [6]:  ..  Loaded QRC translation "tz_" "en_US" 
13:00:45 [6]:  ..  Loaded QRC translation "calamares_" "en_US" 
13:00:45 [6]: void CalamaresApplication::init()
    STARTUP: initSettings, initQmlPath, initBranding done 
13:00:45 [6]: void CalamaresApplication::init()
    STARTUP: initModuleManager: module init started 
13:00:45 [6]: void Calamares::ModuleManager::doInit()
    Found 46 modules 46 names 
13:00:45 [6]: void CalamaresApplication::initView()
    STARTUP: initModuleManager: all modules init done 
13:00:45 [6]: void CalamaresApplication::initView()
    STARTUP: initJobQueue done 
13:00:45 [6]: CalamaresWindow::CalamaresWindow(QWidget*)
    Available desktop QSize(1440, 900) minimum size QSize(1024, 520) 
13:00:45 [6]:  ..  Proposed window size: 1024 560 
13:00:45 [2]: QString Calamares::Branding::stylesheet() const
    WARNING:The branding component "/usr/share/calamares/branding/manjaro" does not ship stylesheet.qss. 
13:00:45 [6]: void CalamaresApplication::initView()
    STARTUP: CalamaresWindow created; loadModules started 
13:00:45 [6]: void Calamares::Module::loadConfigurationFile(const QString&)
    Loaded module configuration "/etc/calamares/modules/welcome.conf" 
13:00:45 [6]: void Config::initLanguages()
    Matching locale QLocale(English, Latin, United States) 
13:00:45 [6]:  ..  Matched with index 10 "en_US" 
13:00:45 [6]:  ..  Loaded QRC translation "tz_" "en_US" 
13:00:45 [6]:  ..  Loaded QRC translation "calamares_" "en_US" 
13:00:45 [6]: void Config::setLocaleIndex(int)
    Index 10 Selected locale QLocale(English, Latin, United States) 
13:00:45 [6]:  ..  Loaded QRC translation "tz_" "en_US" 
13:00:45 [6]:  ..  Loaded QRC translation "calamares_" "en_US" 
13:00:45 [6]: WelcomePage::WelcomePage(Config*, QWidget*)
    Welcome string false "Manjaro Linux 20.0-rc1 \"Lysia\"" 
13:00:45 [6]: Calamares::RequirementsList GeneralRequirements::checkRequirements()
    Need at least storage bytes: 8482560409 

I tried making live USB using dd from my linux laptop. No use. Same error

I honestly have no idea what to do

Did you have any terminal output of this no-partitioning issue? I believe gparted has some cli possibilities so maybe try that and see what is the error. At this point we need to come out with some debug ideas.

My feeling is, since calamares can't do partitioning and the same is with gparted, it all comes down to that issue. Is it hardware related, software related? If Ubuntu or Fedora work fine, then my guess is that something in Manjaro is not working for your current hardware and/or BIOS/UEFI setup.

Nothing, it just freezes, no output whatsoever

It would be a huge bummer if it is really a compatibility issue
My motherboard is Gigabyte model: P55-UD3

How long have you waited? With some issues, operations could try to run for hour or more till they output some error.

Or maybe open some task manager where you could watch gparted processes to see if they are doing something or are unresponsive, or in zombie state - then you would know if you should wait or not. I'm not sure if that will do something, I'm just fishing.

Also, with what operation it freezes? During simple disk structure reading? During format? During resize? During deletion, changing partition table?

I found some topics about gparted freezing during resizing ntfs parition:

The general gparted freezing issue:

https://www.linuxquestions.org/questions/debian-26/gparted-just-hangs-and-i-don't-know-why-502353/

So in the case above, it was looking for floppy disk and dmesg was helpful here. So check all possible logs, like dmesg, journalctl, kernel logs. I don't think that Xorg or DM logs would be relevant here thou.

journalctl -b -p3

journalctl -k

sudo dmesg -H

or orther. I'm not an expert on logs so you may want to research that or get another opinion.

disk structure reading

This. It cannot reach the structure

OK, this is something. It looks like the drive is not accessible at all. Hmmm...

Look for commands checking disks, manual mount, checking id's. Also look for kernel and dmsg logs.

So the first test would be to find the disk and mount it. I guess finding will give you nothing, so you have to install or use some disk checking apps. I'm not in this topic, but I guess this is a direction you could pursue and it might point you or us to the right direction eventually.

For example, check commands:

lsblk
lsblk -io KNAME,TYPE,SIZE,MODEL
hwinfo --disk
df
blkid
fdisk -l
parted -l

etc.

Check those out, look for help or man pages, experiment with commands, look for info on other sites.

https://www.lostsaloon.com/technology/how-to-list-disks-in-linux/

Check out also disk test utility like fsck, so first try help pages:

fsck --help

And some other info:

This all could be a dead end or a solution somewhere.

This indeed is something. Almost feels like a detective case :smiley:

I'll run throug those commands and let know what the outputs would give

Yeah, debugging is like detective work and it could be tiring as it requires a lot of digging and learning. So sometimes you need to stop and start it later with a fresh mind, because some cases cannot be fixed right away.

I had some wifi problem and I needed over a week to solve it... and most of the time I wasn't doing anything, just debugging, learning and thinking, then leaving it be, because this was too much and I had to do breaks. I thought many times on giving up and reinstalling the system but then I thought "no, let's wait and try again later", so I did and finally I fixed the problem, but it was a long and heavy road.

I might actually be on to something

So, live-USB can in fact read whole filesystem perfectly but it cannot write anything to any disk

~ »> lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 66.1M 1 loop /run/miso/sfs/livefs
loop1 7:1 0 637.8M 1 loop /run/miso/sfs/mhwdfs
loop2 7:2 0 1.4G 1 loop /run/miso/sfs/desktopfs
loop3 7:3 0 584.1M 1 loop /run/miso/sfs/rootfs
sda 8:0 0 298.1G 0 disk
└─sda1 8:1 0 298.1G 0 part
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 233.5G 0 part
├─sdb2 8:18 0 232.4G 0 part
├─sdb3 8:19 0 242.9G 0 part
└─sdb4 8:20 0 222.8G 0 part
sdg 8:96 0 465.8G 0 disk /run/miso/bootmnt
├─sdg1 8:97 0 2.7G 0 part
└─sdg2 8:98 0 4M 0 part
sr0 11:0 1 1024M 0 rom 

And

~ »> hwinfo —disk
47: SCSI 800.3: 10600 Disk
[Created at block.256]
Unique ID: FKGF.U_Jt4BKDVLA
Parent ID: 5YuN.7fGVoNxh7p9
SysFS ID: /class/block/sdf
SysFS BusID: 8:0:0:3
SysFS Device Link: /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host8/target8:0:0/8:0:0:3
Hardware Class: disk
Model: "Generic USB MS Reader"
Vendor: usb 0x058f "Generic"
Device: usb 0x6362 "USB MS Reader"
Revision: "1.03"
Serial ID: "058F312D81B"
Driver: "usb-storage", "sd"
Driver Modules: "usb_storage"
Device File: /dev/sdf (/dev/sg6)
Device Files: /dev/sdf, /dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:3, /dev/disk/by-id/usb-Generic_USB_MS_Reader_058F312D81B-0:3
Device Number: block 8:80-8:95 (char 21:6)
Speed: 480 Mbps
Module Alias: "usb:v058Fp6362d0129dc00dsc00dp00ic08isc06ip50in00"
Driver Info #0:
Driver Status: uas is active
Driver Activation Cmd: "modprobe uas"
Driver Info #1:
Driver Status: usb_storage is active
Driver Activation Cmd: "modprobe usb_storage"
Drive status: no medium
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #44 (USB Controller)

48: SCSI 800.1: 10600 Disk
[Created at block.256]
Unique ID: ofUZ.ESrhO6fmky3
Parent ID: 5YuN.7fGVoNxh7p9
SysFS ID: /class/block/sdd
SysFS BusID: 8:0:0:1
SysFS Device Link: /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host8/target8:0:0/8:0:0:1
Hardware Class: disk
Model: "Generic USB CF Reader"
Vendor: usb 0x058f "Generic"
Device: usb 0x6362 "USB CF Reader"
Revision: "1.01"
Driver: "usb-storage", "sd"
Driver Modules: "usb_storage"
Device File: /dev/sdd (/dev/sg4)
Device Files: /dev/sdd, /dev/disk/by-id/usb-Generic_USB_CF_Reader_058F312D81B-0:1, /dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:1
Device Number: block 8:48-8:63 (char 21:4)
Drive status: no medium
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #44 (USB Controller)

49: IDE 700.0: 10600 Disk
[Created at block.245]
Unique ID: WZeP.joBV+y0U0g1
Parent ID: W60f.j28U1_5PIZC
SysFS ID: /class/block/sdb
SysFS BusID: 7:0:0:0
SysFS Device Link: /devices/pci0000:00/0000:00:1f.5/ata8/host7/target7:0:0/7:0:0:0
Hardware Class: disk
Model: "ST31000528AS"
Device: "ST31000528AS"
Revision: "CC46"
Driver: "ata_piix", "sd"
Driver Modules: "ata_piix"
Device File: /dev/sdb
Device Files: /dev/sdb, /dev/disk/by-id/wwn-0x5000c5003277cfba, /dev/disk/by-id/ata-ST31000528AS_6VPB3CVE, /dev/disk/by-path/pci-0000:00:1f.5-ata-2
Device Number: block 8:16-8:31
Drive status: no medium
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #20 (IDE interface)

51: SCSI 900.0: 10600 Disk
[Created at block.245]
Unique ID: 2UT6.1xH864Gryb7
Parent ID: sClz.FzpUetDZLSB
SysFS ID: /class/block/sdg
SysFS BusID: 9:0:0:0
SysFS Device Link: /devices/pci0000:00/0000:00:1a.7/usb1/1-3/1-3:1.0/host9/target9:0:0/9:0:0:0
Hardware Class: disk
Model: "SAMSUNG HM500JI"
Vendor: usb 0x18a5 "SAMSUNG"
Device: usb 0x0214 "HM500JI"
Serial ID: "101A108A00462"
Driver: "usb-storage", "sd"
Driver Modules: "usb_storage"
Device File: /dev/sdg (/dev/sg7)
Device Files: /dev/sdg, /dev/disk/by-path/pci-0000:00:1a.7-usb-0:3:1.0-scsi-0:0:0:0, /dev/disk/by-id/usb-SAMSUNG_HM500JI_101A108A00462-0:0
Device Number: block 8:96-8:111 (char 21:7)
Speed: 480 Mbps
Module Alias: "usb:v18A5p0214d0103dc00dsc00dp00ic08isc06ip50in00"
Driver Info #0:
Driver Status: uas is active
Driver Activation Cmd: "modprobe uas"
Driver Info #1:
Driver Status: usb_storage is active
Driver Activation Cmd:
"modprobe usb_storage"
Drive status: no medium
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #41 (USB Controller)

52: SCSI 800.2: 10600 Disk
[Created at block.256]
Unique ID: Frkd.ESrhO6fmky3
Parent ID: 5YuN.7fGVoNxh7p9
SysFS ID: /class/block/sde
SysFS BusID: 8:0:0:2
SysFS Device Link: /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host8/target8:0:0/8:0:0:2
Hardware Class: disk
Model: "Generic USB SM Reader"
Vendor: usb 0x058f "Generic"
Device: usb 0x6362 "USB SM Reader"
Revision: "1.02"
Driver: "usb-storage", "sd"
Driver Modules: "usb_storage"
Device File: /dev/sde (/dev/sg5)
Device Files: /dev/sde, /dev/disk/by-id/usb-Generic_USB_SM_Reader_058F312D81B-0:2, /dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:2
Device Number: block 8:64-8:79 (char 21:5)
Drive status: no medium
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #44 (USB Controller)

53: SCSI 800.0: 10600 Disk
[Created at block.256]
Unique ID: LUEV.ESrhO6fmky3
Parent ID: 5YuN.7fGVoNxh7p9
SysFS ID: /class/block/sdc
SysFS BusID: 8:0:0:0
SysFS Device Link: /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host8/target8:0:0/8:0:0:0
Hardware Class: disk
Model: "Generic USB SD Reader"
Vendor: usb 0x058f "Generic"
Device: usb 0x6362 "USB SD Reader"
Revision: "1.00"
Driver: "usb-storage", "sd"
Driver Modules: "usb_storage"
Device File: /dev/sdc (/dev/sg3)
Device Files: /dev/sdc, /dev/disk/by-path/pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0, /dev/disk/by-id/usb-Generic_USB_SD_Reader_058F312D81B-0:0
Device Number: block 8:32-8:47 (char 21:3)
Drive status: no medium
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #44 (USB Controller)

54: IDE 401.0: 10600 Disk
[Created at block.245]
Unique ID: 3OOL.H66XZODYM81
Parent ID: w7Y8.nR5gkHXAaR1
SysFS ID: /class/block/sda
SysFS BusID: 4:0:1:0
SysFS Device Link: /devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:1/4:0:1:0
Hardware Class: disk
Model: "WDC WD3200AAJS-0"
Vendor: "WDC"
Device: "WD3200AAJS-0"
Revision: "0A01"
Driver: "ata_piix", "sd"
Driver Modules: "ata_piix"
Device File: /dev/sda
Device Files: /dev/sda, /dev/disk/by-id/wwn-0x50014ee204c86c0b, /dev/disk/by-id/ata-WDC_WD3200AAJS-00YZCA0_WD-WCAYU3281917, /dev/disk/by-path/pci-0000:00:1f.2-ata-1
Device Number: block 8:0-8:15
Drive status: no medium
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #3 (IDE interface)

Sudo parted shows thi

~ »> sudo parted -l
Warning: Error fsyncing/closing /dev/sda1: Input/output error

fdisk -l is stuck on loop

and df shows this

~ >>> df /dev/sda                                                              
Filesystem      Size  Used Avail Use% Mounted on
dev             7.8G     0  7.8G   0% /dev
~ >>> df                                                                       
Filesystem      Size  Used Avail Use% Mounted on
dev             7.8G     0  7.8G   0% /dev
run             7.9G  108M  7.8G   2% /run
/dev/sdg        2.7G  2.7G     0 100% /run/miso/bootmnt
cowspace        256M     0  256M   0% /run/miso/cowspace
overlay_root     12G  375M   12G   4% /run/miso/overlay_root
/dev/loop0       67M   67M     0 100% /run/miso/sfs/livefs
/dev/loop1      638M  638M     0 100% /run/miso/sfs/mhwdfs
/dev/loop2      1.4G  1.4G     0 100% /run/miso/sfs/desktopfs
/dev/loop3      585M  585M     0 100% /run/miso/sfs/rootfs
overlay          12G  375M   12G   4% /
tmpfs           7.9G   65M  7.8G   1% /dev/shm
tmpfs           7.9G     0  7.9G   0% /sys/fs/cgroup
tmpfs           7.9G  8.8M  7.9G   1% /tmp
tmpfs           7.9G  2.2M  7.9G   1% /etc/pacman.d/gnupg
tmpfs           1.6G   84K  1.6G   1% /run/user/1000
/dev/sdb1       234G  177G   57G  76% /run/media/manjaro/F43A25F33A25B390
~ >>> df /dev/sdb                                                              
Filesystem      Size  Used Avail Use% Mounted on
dev             7.8G     0  7.8G   0% /dev
~ >>> df /dev/sdg                                                              
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdg        2.7G  2.7G     0 100% /run/miso/bootmnt

This is the most important part. So, my external HDD, from which I've made all my previous linux installations is usually listed as sdg
The disk my systems are installed to is sdb
And the other one is sda
In ubuntu and fedora there was no problem

But in Manjaro for some reason the listing of disks is somewhat messed up
It is as if the system thinks that sda sdb are part of the external HDD
But there cannot be 2 sda 2 sdb, especially on one HDD

So this creates conflict in system

1 Like

OK, now we are getting somewhere. No write access to the target disk. This is still not explaining why gparted was stuck at discovering disks thou.

I'm not sure if I understand what is scrambled on Manjaro. Each sd is a different disk so if you say you have:

  1. sdg - external HDD (a live system)
  2. sdb - disk 1 where you want to install Manjaro
  3. sda - disk 2 - some other disk, as you called it

so no mix up, because sdb and sda are different disks.

I checked df on my computer and found out it doesn't show all partitions, so there is no EFI and Windows parition, but that's probably because they are not mounted. Let me check. Yes, I was right, when a disk is mounted, df utility shows it.

Another thing I don't understand are the sizes of your disks.

/dev/sdg        2.7G

Not sure how much live iso should have but it looks too little.

/dev/sdb1 7.8G 

This is way too little to install a system, at least a normal system. I have 40GB for my root and now it's 97% used. You could probably install Manjaro with 20GB but it would quickly run out of space. 7.8 is just a show stopper and maybe that is why it doesn't want to write to that disk, because it's too small and doesn't meet the requirements. But that doesn't hold up if I consider that detection is the problem. If disk is too small, installer should simply warn about this, so probably that's not it either.

Clearly I'm not understanding something here.

That's exactly the problem
I have three disks (lsblk)
SDA - 298G
sdb - 931G
sdg-465G - external hdd on which live usb is installed

But for some reason df shows that
sda, sdb are the same size as /dev folder on live usb - 7.8 G

Well, when you are creating live usb, dd is emulating DVD drive, so the disk takes as much space as the data on it, so even if you have 2 TB HDD and put live system there, it will show as 6-12GB, dependently on the system. Of course, the space is still there, but not in the current format of the disk, so seeing live system as less is completely OK. However, I can't explain the rest.

It looks like sda doesn't have any partition (hence only sda, not sdaX).
sdg not having other partition is OK for life system too.
sdb has one mounted partition sdb1 and it's only 7.8G, so maybe this is the only mounted parition but there may be more partitions.

We need a tool to list everything, mounted or not.

I already did this
This is what the real setup looks like

~ »> lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 66.1M 1 loop /run/miso/sfs/livefs
loop1 7:1 0 637.8M 1 loop /run/miso/sfs/mhwdfs
loop2 7:2 0 1.4G 1 loop /run/miso/sfs/desktopfs
loop3 7:3 0 584.1M 1 loop /run/miso/sfs/rootfs
sda 8:0 0 298.1G 0 disk
└─sda1 8:1 0 298.1G 0 part
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 233.5G 0 part
├─sdb2 8:18 0 232.4G 0 part
├─sdb3 8:19 0 242.9G 0 part
└─sdb4 8:20 0 222.8G 0 part
sdg 8:96 0 465.8G 0 disk /run/miso/bootmnt
├─sdg1 8:97 0 2.7G 0 part
└─sdg2 8:98 0 4M 0 part
sr0 11:0 1 1024M 0 rom

Forum kindly sponsored by