Error creating new share. Read Only File Systems

[Please complete the below template with details of the problem reported on your Web-UI. Be as detailed as possible. Community members, including developers, shall try and help. Thanks for your time in reporting this issue! We recommend purchasing commercial support for expedited support directly from the developers.]

Brief description of the problem

Shares are in ReadOnly. Trying to figure out why and , how to repair them

Detailed step by step instructions to reproduce the problem

[write here]

Web-UI screenshot

[Drag and drop the image here]

Error Traceback provided on the Web-UI

Traceback (most recent call last): File "/opt/rockstor/src/rockstor/rest_framework_custom/generic_view.py", line 41, in _handle_exception yield File "/opt/rockstor/src/rockstor/storageadmin/views/share.py", line 181, in post add_share(pool, sname, pqid) File "/opt/rockstor/src/rockstor/fs/btrfs.py", line 584, in add_share toggle_path_rw(root_pool_mnt, rw=True) File "/opt/rockstor/src/rockstor/system/osi.py", line 618, in toggle_path_rw return run_command([CHATTR, attr, path]) File "/opt/rockstor/src/rockstor/system/osi.py", line 176, in run_command raise CommandException(cmd, out, err, rc) CommandException: Error running a command. cmd = /usr/bin/chattr -i /mnt2/Pool-0. rc = 1. stdout = ['']. stderr = ['/usr/bin/chattr: Read-only file system while setting flags on /mnt2/Pool-0', '']

I’ve got a feeling that’s not going to be a lot of help, so here’s this

# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT

sdf 8:80 0 3.7T 0 disk /mnt2/Pool-0

sdi 8:128 0 3.7T 0 disk

sr0 11:0 1 1024M 0 rom

sdg 8:96 0 3.7T 0 disk

sda 8:0 0 465.8G 0 disk

├─sda2 8:2 0 4G 0 part [SWAP]

├─sda3 8:3 0 461.3G 0 part /mnt2/rockstor_rockstor

└─sda1 8:1 0 500M 0 part /boot

sdh 8:112 0 3.7T 0 disk

====================

Nov 1 13:44:39 ironsides kernel: sd 0:0:3:0: [sdi] tag#2 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Nov 1 13:44:39 ironsides kernel: sd 0:0:3:0: [sdi] tag#2 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00
Nov 1 13:44:39 ironsides kernel: sd 0:0:3:0: [sdi] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Nov 1 13:44:39 ironsides kernel: sd 0:0:3:0: [sdi] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 42 4c 20 00 00 00 20 00 00
Nov 1 13:44:39 ironsides kernel: blk_update_request: I/O error, dev sdi, sector 4344864
Nov 1 13:44:39 ironsides kernel: BTRFS error (device sdf): bdev /dev/sdi errs: wr 0, rd 2, flush 0, corrupt 0, gen 0
Nov 1 13:44:39 ironsides kernel: BTRFS: error (device sdf) in btrfs_run_delayed_refs:2971: errno=-5 IO failure
Nov 1 13:44:39 ironsides kernel: BTRFS info (device sdf): forced readonly
Nov 1 13:44:39 ironsides kernel: BTRFS: error (device sdf) in btrfs_run_delayed_refs:2971: errno=-5 IO failure
Nov 1 13:44:53 ironsides kernel: BTRFS error (device sdf): pending csums is 262144
Nov 1 13:44:54 ironsides dbus[3261]: [system] Activating via systemd: service name=‘org.freedesktop.hostname1’ unit=‘dbus-org.freedesktop.hostname1.service’

Hi @LBarry,

Welcome to the forum; I wished it were under better circumstances, though. I’m not an expert in the matter, but it seems to me like you are unfortunately facing hardware issues, especially when seeing the following error:

Now, these relate to your sdi device, while the other btrfs related errors relate to sdf, but from your lsblk output, it seems that only sdf is mounted. Should I understand that all these 4Tb drives are under a same pool? Would you be able to post a screenshot of your “Pools” page, as well as one for the pool details for the pool(s) in question?

In addition, some btrfs-specific info could show something helpful:

btrfs fi show

as well as:

btrfs dev stats /mnt2/Pool-0

Finally, would you able to tell us more about your disks setup as well as the version of Rocsktor you are using? In particular, the following lines…

tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK

… seem to indicate you might be using some USB passthrough “device” so are you using some sort of USB drive dock, or something similar? Are all your drives connected directly to the motherboard via SATA?
It could be a bad drive, or maybe some flaky connection/cable, or even flaky USB controller if you are using one, for instance; that’s why I was curious about your setup.

In any case, I would make sure your backups are refreshed in the meantime while your pool is mounted read-only, in case you have indeed a failing piece of hardware somewhere.

Sorry for not giving a more clear answer, but hopefully it’ll bring more element of answer.

1 Like