The Zohran Effect: Far-Left Muslim Extremism Becomes the Face of the Democrat Party

From Roger Stone

After his shocking victory in the Democrat primary in the New York City Mayoral race, the Zohran Mamdani effect is taking hold throughout the country as other far-left Muslim radicals see this as their moment to seize power over their cities. Enter Omar Fateh. Fateh is an elected Democrat state senator in Minnesota. He is […]

Jul 30th 2025 4:21pm EDT

Source Link: stonecoldtruth.com/p/the-zohra…

Share, promote & comment with Nostr: dissentwatch.com/boost/?boost_…

Δεν θα μείνει πλάτανος στην Ήπειρο με την ασθένεια που έφεραν διάφορα συνεργεία απ την Πελοπόννησο.

Στο νομό Ιωαννίνων έχουν κόψει περισσότερα από 200 πλατάνια

epiruspost.gr/ekopse-ta-xera-p…

in reply to Fou

η Πελοπόννησος έχει ξεγυμνωθεί τελείως, δεν αναγνωρίζεις τις περιοχές που είχε πλατάνια, τρομερά στενάχωρο. Μακάρι να δράσουν γρήγορα μην έρθει πουθενά αλλού αυτό το θέαμα, ιδανικά χωρίς να ψάχνουν να αναθέτουν τα έργα οι δήμοι, να καθυστερούν και να πληρώνουμε εργολάβους χωρίς λόγο.

Είχα διαβάσει ότι τα πλατανοδάση υπάρχουν σχεδόν αποκλειστικά σε Ελλάδα και Τουρκία, είμαστε υπεύθυνοι για τη προστασία του είδους λοιπόν, πέρα από τη προστασία των οικοσυστημάτων και των τοπίων.

Φυσικά για την ασθένεια που ξεκίνησε από τη Μεσσηνία γνωρίζαμε τουλάχιστον 20 χρόνια αλλά οι πατριώτες που μας εξουσιάζουν δε νοιάστηκαν ποτέ για τις συνέπειές της. Τώρα έχει καταστρέψει όλη τη Πελοπόννησο και καταστρέφει Στερεά Ελλάδα (με το μεγαλύτερο πλατανοδάσος της χώρας στο Σπερχειό), Ήπειρο, Θεσσαλία και Εύβοια τη στιγμή που μιλάμε, ενώ έχει ήδη βρεθεί στην δυτική Μακεδονία.

Jeremy Corbyn says Labour MPs tell him 'you're doing the right thing' with a new party

thenational.scot/news/25355547…

This entry was edited (1 month ago)

Lavrov Holds Joint Presser With His Syrian Counterpart After Talks en.sputniknews.africa/20250731…
Unknown parent

pleroma - Link to source

Caleb James DeLisle

The problem with a Payment Processor Civil Rights Act is that some things which are legal are also really fucking likely to cause a chargeback. They could potentially decouple chargeback liability insurance from payment processing though.

But I suspect this is a downstream effect of some Project2025 sperge trying to get rid of porn. Unbanking is picrel

Για να προκόψει η χώρα και ο λαός της απαιτείται η εξής διοικητική / πληθυσμιακή αναδιαμόρφωση:

1. Μεταφορά όλων των δεξιών και νεοπασόκων σε Μακεδονία, Θράκη, Πελοπόννησο.

2. Μεταφορά όλου του υπόλοιπου πληθυσμού στις υπόλοιπες περιφέρειες.

3. #IpirosExit για να κρατάει τα μπόσικα των 1 και 2

τωρα που υπαρχει και μποτακι και τουλαχιστον αλλος ενας λογαριασμος που ανεβαζει απο infowar να συνεχισω να ανεβαζω η τα βλεπετε ηδη μια φορα; (εγω καμια φορα γραφω και το highlight του αρθρου)

  • ΝΑΙ (41%, 5 votes)
  • ΟΧΙ (0%, 0 votes)
  • ΝΑΙ αλλα για την Κυπρο δεν λες (58%, 7 votes)
  • ΟΧΙ αλλα για την Βορεια Ηπειρο δεν λες (0%, 0 votes)
12 voters. Poll end: 1 month ago

Power usage in Wyoming AI data center could eclipse consumption of the state's human residents by 5x

tomshardware.com/tech-industry…

2,1 επιπλεον εκατομμυρια ΑΦΜ πλεμπαιων με οφειλες σε εφορια ανω των 500ευρω χωρις ρυθμιση, θα δουν κινητα κ ακινητα τους να κατασχονται απο ΑΑΔΕ, οταν 1,6 εκατομμυρια ΑΦΜ ειναι ηδη υπο κατασχεση.
Κατασχεση χωρις εισοδηματικα κριτηρια διαβιωσης φυσικα, με απολυτη ατομικη ευθυνη για τα χρεη, λες κ το κρατος δεν διαμορφωνει διαρκως συνθηκες χρεοκοπιας κ ληστρικης φορολογιας κ ακριβειας

Απ τη μια λυπαμαι, απ την αλλη σκεφτομαι τους ψηφοφορους Μητσοτακη που τους παιρνει τα βρακια και γελαω

This entry was edited (1 month ago)
in reply to περαστικος

Το έχω δηλώσει, οι νεοφιλελεύθεροι και οι υποστηρικτές τους πρέπει να κυνηγηθούν σαν ζώα και να εκτελεστούν. Αυτή την στιγμή το σινάφι τους "πλήρωσε" (με μελλοντικά χρέη σε εμάς) τον Τραμπ ώστε να επέμβει στην Ουκρανία με στρατό των ΗΠΑ (δήλωση Merz). Αν πέσει η Ουκρανία έπεσε ο νεοφιλελευθερισμός, το ξέρουν αυτό, αλλά έτσι κι αλλιώς έχουν χάσει ότι και να γίνει στην Ουκρανία. Παντού τα ποσοστά τους έχουν πέσει σε απελπιστικά επίπεδα ~20%
in reply to Τρομοκρατιστής ✭

Η δήλωση Merz αναφέρθηκε εδώ (Judge Napolitano, Σημερινό 31/7) youtube.com/watch?v=kM4vqm0dsP…

Έχε υπόψιν σου ο Κούλης ήδη πήρε 1.2 δισ δάνειο για "όπλα" της Ούρσουλας

This entry was edited (1 month ago)

Lumumba's Africa. Victory of Soviet Union in WW2 + Africans in the WW2. Episode 61 | RT Documentary odysee.com/Lumumba%27s_Africa:…

South Sudan seeks sanctions relief in US deportation talks english.almayadeen.net/news/po…

5,000 excess deaths per week. That’s what U.S. insurance data is showing— and it lines up almost perfectly with the rollout of the COVID shots.

This isn’t speculation. It’s coming from Edward Dowd, a former BlackRock portfolio manager who’s been sounding the alarm using real-world data from the life insurance industry.

These are group life policies covering working-age Americans— healthy, employed people.

In 2021, after the vaccines were introduced, death rates in this group spiked dramatically, far above historical norms.

Dowd’s analysis found:

• 40% excess mortality in 2021 among 25–64 year olds
• Most deaths were non-COVID related
• The government, media, and pharma are completely silent

No honest society ignores a signal this big. But instead of investigations, we get censorship and gaslighting— because the truth threatens power, profit, and control.

They said the shots were “safe and effective.”

They knew they weren’t.

And now thousands are dying every week while the agencies we trusted look the other way.

Article: slaynews.com/news/insurance-in…

Video: rumble.com/v6wkxgc-insurance-i…

(Chile) Words of Gratitude for Each Gesture of Solidarity for our Trial, Aldo and Lucas Hernández abolitionmedia.noblogs.org/206…


(Chile) Words of Gratitude for Each Gesture of Solidarity for our Trial, Aldo and Lucas Hernández


It is the desire to send us affection, the movement of the body that goes on to develop acts of propaganda, action and solidarity that makes us write these lines. We approached that freedom in that fire on July 10 outside the USACH, our names sound in the streets of this city, also on that wall in Montevideo, Uruguay on which anonymous comrades wrote at night, they expressed that ideas will be a real threat, in those solidarity letters of different comrades who experience confinement just like us and send us pushes of conviction for these days of trial, also that oxygen that we breathed on the first day of trial with the rally outside the courts, where comrades, brothers, family went to accompany us and shout loudly our names and those of those who are in the prisons of this State, and who filled the entrance with papers, propaganda vindicating us, even the most filthy gendarme knew that we are not alone.

We are part of that incendiary joy of the youth when the glass breaks and the fuse lights the gas in the police cars on that morning in Providencia outside the José Victorino Lastarria High School, that fire that in the young people is a cry of war, revenge and lifelong experince. Grateful for the real affection of our people, that concern for our lives, compañeros, compañeras, siblings, relatives and loved ones who have never killed us. That genuine love embraces us in these moments. They show it every day in their concern and their desire to steal more than a smile from us in such a defining moment, and they undoubtedly achieve it completely. A hug to those who remember us and seek ways to be with us…

Aldo and Lucas from “La Gonzalina” and “Santiago Uno”.

End of July 2025.

(Chile) Palabras de agradecimiento x cada gesto solidario por nuestro juicio, Aldo y Lucas Hernández


informativoanarquista.noblogs.…

abolitionmedia.noblogs.org/?p=…

#AldoHernández #AnarchistPrisoners #chile #lucasHernández #southAmerica


China Condemns “Unprecedented Humanitarian Catastrophe” in Gaza, Urges Ceasefire and Lifting of Blockade telesurenglish.net/china-conde…

"Sur le plan médical, le doute n'est pas raisonnable" : l'Ordre national des médecins s'engage contre la loi Duplomb


#politique #agriculture #environnement #santé

Voilà un coup qui porte...

franceinfo.fr/environnement/lo…

Laurent Breton reshared this.

Μόλις ελευθέρωσα το 1ο tutorial στο κανάλι
Κατασκευή θήκης γυαλιών
Μπείτε, δείτε, ακούστε, θαυμάστε (λέμε τώρα), σχολιάστε και πείτε μου πώς σας φάνηκε

youtube.com/watch?v=P4Azn5YyK8…

"The rule of law presupposes that there are, well, rules. These rules are supposed to provide a consistent, repeatable, and, most important, knowable set of outcomes. Predictability is the key feature of a functioning rules-based system, because people have to know the rules—and the consequences of breaking them—before they act. The difference between living under the rule or law and living by the whims of a madman is that the rights, responsibilities, prohibitions, and privileges of your situation do not change radically every time a person in power throws a hissy fit.

But the Supreme Court has decided that rules and laws do not apply to Trump, and they don’t protect anybody from Trump. That means that the rule of law is functionally dead in this country (which shouldn’t be entirely surprising, given that this country almost never respects the rule of law in other countries). Nobody can know if the rights they have today will be the rights they have tomorrow. Nobody can know if a thing that is illegal for the government to do to them today will be illegal for the government to do to them tomorrow.

We see the truth of this country’s descent into lawlessness every single day. All you have to do is pick up a newspaper, turn on the television, or go to Trump’s social media account. Nearly every “news” story you’ll see falls into one of two categories: Trump did something, or Trump threatens to do something. Nobody can reliably say whether those actions or threats are “legal” because everybody knows (whether they will admit that to you are not) that rules and laws no longer apply to the Trump regime."

thenation.com/article/politics…

#USA #Trump #Democracy #RuleOfLaw #Authoritarianism

in reply to Miguel Afonso Caetano

"I am not naïve: I am well aware that the rich and powerful generally operate outside the rules and laws as they are applied to most regular people. What makes the Trump administration unique (in the American context) is that the lawlessness doesn’t just apply to him personally; it applies to any person, official, or institution he bestows his favor on. Homeland Security Secretary Kirsti Noem operates outside the rule of law as long as what she’s doing pleases Trump. Elon Musk operated outside the rule of law until he displeased Trump. ICE seemingly has the power to abduct people and brutalize citizens, noncitizens, and even elected officials that get in their way. And thanks to the ubiquitous pardons Trump has granted to his cronies and cult followers who attacked the Capitol on January 6, any barbeque-splattered thug in a MAGA hat might also operate beyond the rule of law as long as they’re doing something Trump wants them to do."
in reply to Miguel Afonso Caetano

"The analogy I’ve often used to explain our current legal system comes from the first Pirates of the Caribbean movie. I’m being entirely serious. There’s a brilliant little scene where Captain Jack Sparrow is trying to explain the law of the high seas to the naïve Will Turner. Sparrow says: “The only rules that really matter are these: what a man can do and what a man can’t do.” He explains that he can kill Turner right there on the spot, but that he can’t bring the ship they’re on into port all by himself. Sparrow’s inability to do what he wants long-term is the only thing constraining him from doing what he wants to do right now.

A pirate ship is not a democracy; it is a dictatorship. So too is the current American ship of state. The only thing constraining what Trump does today is what he wants to do tomorrow. The only people and institutions allowed to function are the ones Trump needs to help him accomplish his future aims. And the rules and laws do not exist to limit Trump, his officials, or his supporters; they exist to limit the options of people and forces who oppose Trump."

thenation.com/article/politics…

Μαλάκες δεξιοί ψηφοφόροι, να τα χάλια σας:

Νέες καταγγελίες για την παντελή απουσία μέτρων πυρασφάλειας στο Γενικό Νοσοκομείο Χατζηκώστα διατυπώνει η παράταξη Αγωνιστική Συσπείρωση Υγειονομικών (ΑΣΥ), δύο χρόνια μετά την κατάθεση της σχετικής μελέτης από την Πυροσβεστική Υπηρεσία.

#ΕΣΥ

epiruspost.gr/asy-gn-chatzikos…

[Proxmox/Debian 12] Drives randomly disconnect an unmount


Hey y'all

I've been running into this issue on my home's server, the host OS is Proxmox while i have a Debian 12 VM running within it as a VM i have two external HDD's (1tb, 5tb) running in a drive bay which are randomly disconnecting from the server and i can't seem to make heads or tails of the error in my journalctl, i don't think there is corruption on the drives but i'm hesitant to run any checks as i cannot back these up given how full they are.

The drives typically get recogniced under a different device name/ID right away. for example, /dev/sdb1 will now be /dev/sdd1, and that cycle just repeats every time they disconnect

This is kinda frustrating having to re-mount and re-add these to the VM, is there any way i could simply automate the re-mount of these drives and have the VM pick it up right away?

Jul 30 21:00:53 proxmox kernel:  sdb: sdb1
Jul 30 21:00:53 proxmox kernel:  sdc: sdc1
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Preferred minimum I/O size 4096 bytes
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
Jul 30 21:00:53 proxmox kernel: xhci_hcd 0000:00:0d.0: bad transfer trb length 112 in event trb
Jul 30 21:00:53 proxmox kernel: xhci_hcd 0000:00:0d.0: bad transfer trb length 112 in event trb
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Mode Sense: 67 00 10 08
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Write Protect is off
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Mode Sense: 67 00 10 08
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Write Protect is off
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] 9767541168 512-byte logical blocks: (5.00 TB/4.55 TiB)
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:1: Attached scsi generic sg2 type 0
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: Attached scsi generic sg1 type 0
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:1: Direct-Access     WDC WD10 EZEX-21WN4A0     0009 PQ: 0 ANSI: 6
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:0: Direct-Access     ST5000DM 000-1FK178       0009 PQ: 0 ANSI: 6
Jul 30 21:00:53 proxmox kernel: scsi host3: uas
Jul 30 21:00:53 proxmox kernel: usb 4-1: SerialNumber: RANDOM__1CC4CDBF833E
Jul 30 21:00:53 proxmox kernel: usb 4-1: Manufacturer: JMicron
Jul 30 21:00:53 proxmox kernel: usb 4-1: Product: JMS56x Series
Jul 30 21:00:53 proxmox kernel: usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Jul 30 21:00:53 proxmox kernel: usb 4-1: New USB device found, idVendor=152d, idProduct=0565, bcdDevice= 0.09
Jul 30 21:00:53 proxmox kernel: usb 4-1: new SuperSpeed USB device number 8 using xhci_hcd
Jul 30 21:00:53 proxmox systemd[1]: Unmounted root-mnt-1tb\x2dhdd.mount - /root/mnt/1tb-hdd.
Jul 30 21:00:53 proxmox systemd[1]: root-mnt-1tb\x2dhdd.mount: Deactivated successfully.
Jul 30 21:00:53 proxmox systemd[1]: Unmounting root-mnt-1tb\x2dhdd.mount - /root/mnt/1tb-hdd...
Jul 30 21:00:53 proxmox systemd[1]: Unmounted root-mnt-5tb\x2dhdd.mount - /root/mnt/5tb-hdd.
Jul 30 21:00:53 proxmox systemd[1]: root-mnt-5tb\x2dhdd.mount: Deactivated successfully.
Jul 30 21:00:53 proxmox systemd[1]: Unmounting root-mnt-5tb\x2dhdd.mount - /root/mnt/5tb-hdd...
Jul 30 21:00:53 proxmox pvestatd[1165]: status update time (17.646 seconds)
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] Synchronizing SCSI cache
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sde1): unmounting filesystem 181f4235-7fbf-4e0a-8ad1-fd4813367644.
Jul 30 21:00:53 proxmox kernel: JBD2: I/O error when updating journal superblock for sde1-8.
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost sync page write
Jul 30 21:00:53 proxmox kernel: JBD2: previous I/O error detected for journal superblock update for sde1-8.
Jul 30 21:00:53 proxmox kernel: Aborting journal on device sde1-8.
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sde1): shut down requested (2)
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] Synchronizing SCSI cache
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sdd1): unmounting filesystem f966a59f-db1a-433c-9977-040037e7d69e.
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: rejecting I/O to offline device
Jul 30 21:00:53 proxmox kernel: JBD2: I/O error when updating journal superblock for sdd1-8.
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sdd1, logical block 610304000, lost sync page write
Jul 30 21:00:53 proxmox kernel: Aborting journal on device sdd1-8.
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sdd1): shut down requested (2)
Jul 30 21:00:53 proxmox kernel: device offline error, dev sdd, sector 2002831328 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: usb 4-1: USB disconnect, device number 7
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 2002831328 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 9159739392 op 0x0:(READ) flags 0x200000 phys_seg 8 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: rejecting I/O to offline device
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 6653857768 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 CDB: Read(16) 88 00 00 00 00 01 8c 99 cf e8 00 00 00 08 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 6438292752 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 CDB: Read(16) 88 00 00 00 00 01 7f c0 8d 10 00 00 00 08 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sde, sector 822151464 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#8 CDB: Read(10) 28 00 31 01 09 28 00 00 08 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#8 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sde, sector 973345232 op 0x1:(WRITE) flags 0x808800 phys_seg 3 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#11 CDB: Write(10) 2a 00 3a 04 11 d0 00 00 18 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#11 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=47s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 9155874912 op 0x0:(READ) flags 0x200000 phys_seg 64 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
Jul 30 21:00:53 proxmox kernel: xhci_hcd 0000:00:0d.0: bad transfer trb length 112 in event trb
Jul 30 21:00:53 proxmox kernel: xhci_hcd 0000:00:0d.0: bad transfer trb length 112 in event trb
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Mode Sense: 67 00 10 08
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Write Protect is off
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Mode Sense: 67 00 10 08
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Write Protect is off
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] 9767541168 512-byte logical blocks: (5.00 TB/4.55 TiB)
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:1: Attached scsi generic sg2 type 0
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: Attached scsi generic sg1 type 0
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:1: Direct-Access     WDC WD10 EZEX-21WN4A0     0009 PQ: 0 ANSI: 6
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:0: Direct-Access     ST5000DM 000-1FK178       0009 PQ: 0 ANSI: 6
Jul 30 21:00:53 proxmox kernel: scsi host3: uas
Jul 30 21:00:53 proxmox kernel: usb 4-1: SerialNumber: RANDOM__1CC4CDBF833E
Jul 30 21:00:53 proxmox kernel: usb 4-1: Manufacturer: JMicron
Jul 30 21:00:53 proxmox kernel: usb 4-1: Product: JMS56x Series
Jul 30 21:00:53 proxmox kernel: usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Jul 30 21:00:53 proxmox kernel: usb 4-1: New USB device found, idVendor=152d, idProduct=0565, bcdDevice= 0.09
Jul 30 21:00:53 proxmox kernel: usb 4-1: new SuperSpeed USB device number 8 using xhci_hcd
Jul 30 21:00:53 proxmox systemd[1]: Unmounted root-mnt-1tb\x2dhdd.mount - /root/mnt/1tb-hdd.
Jul 30 21:00:53 proxmox systemd[1]: root-mnt-1tb\x2dhdd.mount: Deactivated successfully.
Jul 30 21:00:53 proxmox systemd[1]: Unmounting root-mnt-1tb\x2dhdd.mount - /root/mnt/1tb-hdd...
Jul 30 21:00:53 proxmox systemd[1]: Unmounted root-mnt-5tb\x2dhdd.mount - /root/mnt/5tb-hdd.
Jul 30 21:00:53 proxmox systemd[1]: root-mnt-5tb\x2dhdd.mount: Deactivated successfully.
Jul 30 21:00:53 proxmox systemd[1]: Unmounting root-mnt-5tb\x2dhdd.mount - /root/mnt/5tb-hdd...
Jul 30 21:00:53 proxmox pvestatd[1165]: status update time (17.646 seconds)
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] Synchronizing SCSI cache
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sde1): unmounting filesystem 181f4235-7fbf-4e0a-8ad1-fd4813367644.
Jul 30 21:00:53 proxmox kernel: JBD2: I/O error when updating journal superblock for sde1-8.
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost sync page write
Jul 30 21:00:53 proxmox kernel: JBD2: previous I/O error detected for journal superblock update for sde1-8.
Jul 30 21:00:53 proxmox kernel: Aborting journal on device sde1-8.
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sde1): shut down requested (2)
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] Synchronizing SCSI cache
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sdd1): unmounting filesystem f966a59f-db1a-433c-9977-040037e7d69e.
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: rejecting I/O to offline device
Jul 30 21:00:53 proxmox kernel: JBD2: I/O error when updating journal superblock for sdd1-8.
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sdd1, logical block 610304000, lost sync page write
Jul 30 21:00:53 proxmox kernel: Aborting journal on device sdd1-8.
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sdd1): shut down requested (2)
Jul 30 21:00:53 proxmox kernel: device offline error, dev sdd, sector 2002831328 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: usb 4-1: USB disconnect, device number 7
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 2002831328 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 9159739392 op 0x0:(READ) flags 0x200000 phys_seg 8 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: rejecting I/O to offline device
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 6653857768 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 CDB: Read(16) 88 00 00 00 00 01 8c 99 cf e8 00 00 00 08 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 6438292752 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 CDB: Read(16) 88 00 00 00 00 01 7f c0 8d 10 00 00 00 08 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sde, sector 822151464 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#8 CDB: Read(10) 28 00 31 01 09 28 00 00 08 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#8 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sde, sector 973345232 op 0x1:(WRITE) flags 0x808800 phys_seg 3 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#11 CDB: Write(10) 2a 00 3a 04 11 d0 00 00 18 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#11 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=47s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 9155874912 op 0x0:(READ) flags 0x200000 phys_seg 64 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#13 CDB: Read(16) 88 00 00 00 00 02 21 bb 90 60 00 00 02 00 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#13 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=41s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 9159851824 op 0x0:(READ) flags 0x200000 phys_seg 5 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#14 CDB: Read(16) 88 00 00 00 00 02 21 f8 3f 30 00 00 00 28 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#14 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=41s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 6438525440 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#15 CDB: Read(16) 88 00 00 00 00 01 7f c4 1a 00 00 00 00 08 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#15 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=30s
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: scsi host4: uas_eh_device_reset_handler FAILED to get lock err -19
Jul 30 21:00:53 proxmox kernel: scsi host4: uas_eh_device_reset_handler FAILED err -19
Jul 30 21:00:52 proxmox kernel: usb 4-1: device firmware changed
Jul 30 21:00:52 proxmox kernel: usb 4-1: reset SuperSpeed USB device number 7 using xhci_hcd
Jul 30 21:00:52 proxmox kernel: scsi host4: uas_eh_device_reset_handler start
Jul 30 21:00:52 proxmox kernel: sd 4:0:0:0: [sdd] tag#15 CDB: Read(16) 88 00 00 00 00 01 7f c4 1a 00 00 00 00 08 00 00
Jul 30 21:00:52 proxmox kernel: sd 4:0:0:0: [sdd] tag#15 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD IN 
Jul 30 21:00:41 proxmox kernel: sd 4:0:0:0: [sdd] tag#14 CDB: Read(16) 88 00 00 00 00 02 21 f8 3f 30 00 00 00 28 00 00
Jul 30 21:00:41 proxmox kernel: sd 4:0:0:0: [sdd] tag#14 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD IN 
Jul 30 21:00:41 proxmox kernel: sd 4:0:0:0: [sdd] tag#13 CDB: Read(16) 88 00 00 00 00 02 21 bb 90 60 00 00 02 00 00 00
Jul 30 21:00:41 proxmox kernel: sd 4:0:0:0: [sdd] tag#13 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD IN 
Jul 30 21:00:35 proxmox kernel: sd 4:0:0:1: [sde] tag#11 CDB: Write(10) 2a 00 3a 04 11 d0 00 00 18 00
Jul 30 21:00:35 proxmox kernel: sd 4:0:0:1: [sde] tag#11 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT 
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:1: [sde] tag#8 CDB: Read(10) 28 00 31 01 09 28 00 00 08 00
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:1: [sde] tag#8 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN 
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 CDB: Read(16) 88 00 00 00 00 01 7f c0 8d 10 00 00 00 08 00 00
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN 
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 CDB: Read(16) 88 00 00 00 00 01 8c 99 cf e8 00 00 00 08 00 00
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 
Jul 30 20:59:59 proxmox kernel: critical medium error, dev sdd, sector 6653857080 op 0x0:(READ) flags 0x4000 phys_seg 128 prio class 0
Jul 30 20:59:59 proxmox kernel: blk_print_req_error: 47 callbacks suppressed
Jul 30 20:59:59 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 CDB: Read(16) 88 00 00 00 00 01 8c 99 cd 38 00 00 04 00 00 00
Jul 30 20:59:59 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 Add. Sense: Unrecovered read error
Jul 30 20:59:59 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 Sense Key : Medium Error [current] 
Jul 30 20:59:59 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Jul 30 20:56:01 proxmox postfix/smtp[3945942]: 2F670200A1A: to=<proxmox.snowcap946@passmail.net>, relay=mx2.simplelogin.co[176.119.200.136]:25, delay=330448, delays=330369/0.01/79/0, dsn=4.4.2, status=deferred (l>
Jul 30 20:55:42 proxmox postfix/smtp[3945942]: 2F670200A1A: lost connection with mx2.simplelogin.co[185.205.70.136] while receiving the initial server greeting
This entry was edited (1 month ago)
in reply to ohshit604

I had a similar issue with a SAS drive In the backplane of a dell server. I thought for sure the drive was failing. Reseated it, cleaned the ports, ran some tests, just kept failing without any obvious signs why it was. Replaced it with a spare and same issue. That seemed very unlikely, so I put the old drive in another slot and its still running just fine going on 2 years without an issue. If you have another toaster give it a try.

The market is rife with cheapo junk tech. Ive seen several crapo off brand drive toasters fail, so thats possible. I don't know the brand of yours so I can't speak to them.

It could also just be the power supply for the toaster is crapping out, or doesn't provide enough amperage. Those power supplies dont always keep providing the same amount of power forever, sometimes it drops over time, and that could be the cause too. Or they could be poorly made, meaning they probably drop in even short time periods.

If you have another power supply with the same voltage and higher amperage, you could try that. You could also try running only one drive in there and see if it keeps failing, if no issues, you could try the other drive and see if that one has issues. If that one doesn't have issues either it could indicate power issues.

HANDALA, GAZA, ARRESTATION PAR ISRAËL : LA DÉPUTÉE CATHALA RACONTE TOUT


🔴 Soutenez, partagez, rejoignez la riposte pour une INFO libre, populaire sur la TNT et les réseaux-sociaux ! lemediatv.fr/campagne

Place de la République : rassemblement en soutien au peuple de Gaza et aux passagers du Handala

Hier soir, plusieurs centaines de personnes se sont réunies sur la place de la République, à Paris, pour exprimer leur solidarité avec le peuple gazaoui, bombardé et affamé par Israël. Le rassemblement avait également pour objectif de saluer le courage de celles et ceux qui ont embarqué à bord du Handala, un navire humanitaire destiné à briser le blocus imposé à Gaza.

Le bateau, chargé de denrées alimentaires, de couches et de lait infantile, a été intercepté en eaux internationales par les forces israéliennes. Les membres de l’équipage ont été arrêtés avant d’être expulsés.

Parmi eux se trouvait la députée française Gabrielle Cathala, qui est avec nous aujourd’hui pour livrer un témoignage exclusif sur cette opération et ses conditions de détention.

⚠️ Le Média est diffusé sur le canal 165 de la Freebox et sur le bouquet gratuit de Molotov TV.

Suivez Le Média sur sa seconde chaîne Youtube :
👉 https://www.youtube.com/@LeMédia24-7

👉 Pour signer la pétition pour une "TNT plus démocratique" et soutenir notre recours contre l'ARCOM : lemediatv.fr/campagne

👉 Pour recevoir les dernières actualités, le résumé de la semaine et être alerté des derniers programmes publiés du Média, directement dans votre boîte e-mail.
newsletter.lemediatv.fr

▶ Soutenez Le Média :
👉 soutenez.lemediatv.fr (CB - SEPA - Chèque)
👉 dons.lemediatv.fr (CB - SEPA - Chèque)
👉 fr.tipeee.com/le-media (CB - Paypal)

✅ Suivez-nous :
Instagram : instagram.com/lemedia_tv/
Facebook : bit.ly/FacebookLeMedia
BlueSky : bsky.app/profile/lemediatv.bsk…
Youtube : bit.ly/YouTubeLeMedia
Peertube : video.lemediatv.fr
Telegram : https://t.me/LeMediaOfficiel
TikTok : tiktok.com/@lemediatv

Rejoignez la communauté des Socios !

This entry was edited (1 month ago)
in reply to Obi-Two al-Menashani

I have stopped talking to my mother because I have discovered the relationship was one sided. She is not involved. Does not call or talk to her grandkids, just not there. One day I stopped reaching out and next thing I know it’s been over a year and I have not heard from her. Once I stopped contacting her, there was no contact back and no drama. It sucks for her grandkids but I’m not forcing a relationship upon them that they will have to be those ones that carry it.