Festplatte lässt sich nicht einhängen

Jiggo0815 · Jan 14th 2025

Hallo zusammen,

Da mein System nach Updates den Geist aufgeben hat und nicht mehr erreichbar war habe ich heute auf meinem Raspi 5 Raspberry Pi OS Lite 64bit und OMV installiert. Alles lief wunderbar, meine BTRFS formatierte Platte welche vorher eingehängt war wurde erkannt. Als ich sie einhängen wollte, da kam diese Fehlermeldung:

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color fstab 2>&1' with exit code '1': rpi5:
----------
ID: create_filesystem_mountpoint_84318174-c159-4e15-a5c0-200b62e66ec2
Function: file.accumulated
Result: True
Comment: Accumulator create_filesystem_mountpoint_84318174-c159-4e15-a5c0-200b62e66ec2 for file /etc/fstab was charged by text
Started: 15:53:31.496160
Duration: 0.921 ms
Changes:
----------
ID: mount_filesystem_mountpoint_84318174-c159-4e15-a5c0-200b62e66ec2
Function: mount.mounted
Name: /srv/dev-disk-by-uuid-a9f4c423-26c1-48d5-a961-a6f8f5d1685b
Result: False
Comment: mount: /srv/dev-disk-by-uuid-a9f4c423-26c1-48d5-a961-a6f8f5d1685b: can't read superblock on /dev/sda.
dmesg(1) may have more information after failed mount system call.
Started: 15:53:31.497876
Duration: 88.568 ms
Changes:
----------
ID: append_fstab_entries
Function: file.blockreplace
Name: /etc/fstab
Result: True
Comment: No changes needed to be made
Started: 15:53:31.586969
Duration: 3.343 ms
Changes:
----------
ID: fstab_systemctl_daemon_reload
Function: module.run
Result: True
Comment: State was not run because none of the onchanges reqs changed
Started: 15:53:31.591247
Duration: 0.006 ms
Changes:


Summary for rpi5
------------
Succeeded: 3
Failed:    1
------------
Total states run:     4
Total run time:  92.838 ms
[ERROR   ] Command 'mount' failed with return code: 32
[ERROR   ] stderr: mount: /srv/dev-disk-by-uuid-a9f4c423-26c1-48d5-a961-a6f8f5d1685b: can't read superblock on /dev/sda.
dmesg(1) may have more information after failed mount system call.
[ERROR   ] retcode: 32
[ERROR   ] mount: /srv/dev-disk-by-uuid-a9f4c423-26c1-48d5-a961-a6f8f5d1685b: can't read superblock on /dev/sda.
dmesg(1) may have more information after failed mount system call.


OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color fstab 2>&1' with exit code '1': rpi5:
----------
ID: create_filesystem_mountpoint_84318174-c159-4e15-a5c0-200b62e66ec2
Function: file.accumulated
Result: True
Comment: Accumulator create_filesystem_mountpoint_84318174-c159-4e15-a5c0-200b62e66ec2 for file /etc/fstab was charged by text
Started: 15:53:31.496160
Duration: 0.921 ms
Changes:
----------
ID: mount_filesystem_mountpoint_84318174-c159-4e15-a5c0-200b62e66ec2
Function: mount.mounted
Name: /srv/dev-disk-by-uuid-a9f4c423-26c1-48d5-a961-a6f8f5d1685b
Result: False
Comment: mount: /srv/dev-disk-by-uuid-a9f4c423-26c1-48d5-a961-a6f8f5d1685b: can't read superblock on /dev/sda.
dmesg(1) may have more information after failed mount system call.
Started: 15:53:31.497876
Duration: 88.568 ms
Changes:
----------
ID: append_fstab_entries
Function: file.blockreplace
Name: /etc/fstab
Result: True
Comment: No changes needed to be made
Started: 15:53:31.586969
Duration: 3.343 ms
Changes:
----------
ID: fstab_systemctl_daemon_reload
Function: module.run
Result: True
Comment: State was not run because none of the onchanges reqs changed
Started: 15:53:31.591247
Duration: 0.006 ms
Changes:


Summary for rpi5
------------
Succeeded: 3
Failed:    1
------------
Total states run:     4
Total run time:  92.838 ms
[ERROR   ] Command 'mount' failed with return code: 32
[ERROR   ] stderr: mount: /srv/dev-disk-by-uuid-a9f4c423-26c1-48d5-a961-a6f8f5d1685b: can't read superblock on /dev/sda.
dmesg(1) may have more information after failed mount system call.
[ERROR   ] retcode: 32
[ERROR   ] mount: /srv/dev-disk-by-uuid-a9f4c423-26c1-48d5-a961-a6f8f5d1685b: can't read superblock on /dev/sda.
dmesg(1) may have more information after failed mount system call. in /usr/share/php/openmediavault/system/process.inc:247
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(187): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges()
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array()
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(155): OMV\Rpc\ServiceAbstract->callMethod()
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(628): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}()
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(152): OMV\Rpc\ServiceAbstract->execBgProc()
#7 /usr/share/openmediavault/engined/rpc/config.inc(208): OMV\Rpc\ServiceAbstract->callMethodBg()
#8 [internal function]: Engined\Rpc\Config->applyChangesBg()
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array()
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod()
#11 /usr/sbin/omv-engined(544): OMV\Rpc\Rpc::call()
#12 {main}

Display More

Könnt ihr mir da helfen? Bin noch recht unerfahren in solchen Sachen.

Vielen Dank.

Beste Grüße

Tim

chente · Jan 14th 2025

Quote from Jiggo0815

can't read superblock on /dev/sda

This message suggests some type of damage to the hard drive. It could also be a simple cable connected incorrectly, I would check that.

I would look at the result of a simple SMART test. If you don't know how to interpret it, you can post it here so someone can help you.

Jiggo0815 · Jan 16th 2025

Hi

I did a SMART test with CMD with the result OK. Also checked the SSD with AOMEI Partition Assistant. Found no bad sectors.

Tried also another cable and all other usb ports on my Raspberry Pi.

Same result...

macom · Jan 18th 2025

Check the filesystem with fsck

Jiggo0815 · Jan 19th 2025

Wie mache ich das? Ich habe Raspberry OS auf einer SD Karte installiert.

Allerdings bekomme ich den fsck Befehl nicht ausgeführt.

macom · Jan 20th 2025

Quote from Jiggo0815

Allerdings bekomme ich den fsck Befehl nicht ausgeführt.

Was hast du denn versucht? Und welche Rückmeldung hast du vom System bekommen?

fsck(8) — util-linux — Debian bookworm — Debian Manpages

Jiggo0815 · Jan 27th 2025

Wenn ich fsck eingebe bekomme ich die Fehlermeldung:

Permission denied while trying to open /dev/sda
You must have r/w access to the filesystem or be root

Dann gehe ich über

sudo -s

Dann gibt er mir die Rückmeldung:

fsck from util -linux 2.38.1

Dann kommt direkt wieder die Kommandozeile

macom · Jan 27th 2025

Versuch

sudo fsck /dev/sda

Thread

[How-To] Post content in a code box

Whenever you want to post output from the command line or a compose file, please post it inside a code box.

To open a code box press the </> button in the toolbar of the box in which you write the post (see picture below)
Copy and paste the output of a command or code inside
Hide sensitive data, such as passwords, email addresses or web domains
Do not hide non-sensitive data like uuid of drives or device names as they might help to trouble shoot problems
When posting output, please post
- the command

…

macom

Dec 27th 2024

Jiggo0815 · Jan 27th 2025

Da bekomme ich auch direkt die Meldung

fsck from util -linux 2.38.1

und im Anschluss wieder die Kommandozeile

Festplatte lässt sich nicht einhängen

ryecoaaron Jan 14th 2025

Participate now!