Arch Linux

EmptySpirit

Member

Registered: 2023-01-06

Posts: 2

mount fails on boot

Hello,
I'm having an issue with a freshly installed arch, intended as headless file server for home use. Constantly fails cold boot with "Dependency failed for Local File Systems" error.

Aside from ssd with root partiotion system have 5 sata hdds connected to it, 2 of them are part of software raid array, and the other 3 are standalone.

/etc/fstab:

# /dev/sda1
UUID=6d7925dd-8460-4251-a699-c090f16a8b5c       /               ext4            rw,relatime     0 1
# /dev/sda2
UUID=98accd66-c841-446b-83a8-a510d3fa87f3       none            swap            defaults        0 0

/dev/md0p1      /mnt/raid       ext4    defaults        0 0

/dev/sdf1       /mnt/aux3       ntfs-3g uid=1000,gid=1001,dmask=0,fmask=0       0 0
/dev/sde1       /mnt/aux2       ntfs-3g uid=1000,gid=1001,dmask=0,fmask=0       0 0
/dev/sdb1       /mnt/aux1       ntfs-3g uid=1000,gid=1001,dmask=0,fmask=0       0 0

lsblk:

sda           8:0    0 111.8G  0 disk
├─sda1        8:1    0   100G  0 part  /
└─sda2        8:2    0  11.8G  0 part  [SWAP]
sdb           8:16   0 931.5G  0 disk
└─sdb1        8:17   0  31.8M  0 part
sdc           8:32   0 931.5G  0 disk
└─sdc1        8:33   0 931.5G  0 part
  └─md0       9:0    0 931.4G  0 raid1
    └─md0p1 259:0    0 931.4G  0 part  /mnt/raid
sdd           8:48   0 931.5G  0 disk
└─sdd1        8:49   0 931.5G  0 part
  └─md0       9:0    0 931.4G  0 raid1
    └─md0p1 259:0    0 931.4G  0 part  /mnt/raid
sde           8:64   0   1.8T  0 disk
└─sde1        8:65   0   1.8T  0 part  /mnt/aux2
sdf           8:80   0 465.8G  0 disk
└─sdf1        8:81   0 465.8G  0 part  /mnt/aux3

offender in question is /dev/sdb. for some reason on boot kernet thinks that it's size is 33 mb, instead of 1TB:

dmesg | grep sdb:

[    2.099166] sd 1:0:0:0: [sdb] 65134 512-byte logical blocks: (33.3 MB/31.8 MiB)
[    2.099183] sd 1:0:0:0: [sdb] Write Protect is off
[    2.099186] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    2.099212] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.099246] sd 1:0:0:0: [sdb] Preferred minimum I/O size 512 bytes
[    2.123404]  sdb: sdb1
[    2.123410] sdb: p1 size 1953520002 extends beyond EOD, enabling native capacity
[    2.598375]  sdb: sdb1
[    2.598381] sdb: p1 size 1953520002 extends beyond EOD, truncated
[    2.598518] sd 1:0:0:0: [sdb] Attached SCSI disk
[    2.615064] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[    2.615130] sdb: detected capacity change from 65134 to 1953525168
[  437.417248]  sdb: sdb1

interestingly enough, after i poke it with fdisk /dev/sdb (list partitions with p and then just quit with q) it starts showing corrently via lsblk and mounts manually without any issues.
Also, more often than not, it mounts everything correctly on reboot

Is this purely a hardware issue?

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 9,003

Website

Re: mount fails on boot

An intermittent problem would usually suggest a hardware issue, yes. Check the cable and/or connector first.

Note that you should use UUIDs in /etc/fstab, they are more consistently reliable than block device names.

---

Jin, Jîyan, Azadî

EmptySpirit

Member

Registered: 2023-01-06

Posts: 2

Re: mount fails on boot

An intermittent problem would usually suggest a hardware issue, yes. Check the cable and/or connector first.

Note that you should use UUIDs in /etc/fstab, they are more consistently reliable than block device names.

Yep is was hardware error: it follows the drive when I change ports or cables, sorry for wasting your time. Apparently it started acting up on the day I installed arch and I assumed it was related.
At least I copied all the data before it given up the ghost completely - now it shows having 30mb capacity no matter what I do.

and yes i switched to uuids after

Thanks!

Slithery

Administrator

From: Norfolk, UK

Registered: 2013-12-01

Posts: 5,776

Re: mount fails on boot

Please remember to mark the thread as [SOLVED].
CoC - How to post

---

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles